Validar fidelidad de valores de los campos de la ficha PDF del vehículo

Sub-tickets

Activity

• wi-cli-venus created · 5w ago
• wi-cli-venus commit · 5w ago
  ccb0e1ed v5.5.120 en DEV: PDF individual con CUIT, Indicador de la linea (identificador_empresa, etiqueta de la stakeholder sobre un campo que identifica la EMPRESA - referente sin confirmar), Categoria de la Carroceria, Tipo de motor (valor crudo del libro, mezcla E3/E5 y ELECTRICO/GNC) y cantidad de asientos desde asientosVehiculo (canonico; NO desde el libro, que trae el typo de PJL777). Autor coder-mba-l-ca, deploy coder02. Cuatro correcciones exigidas antes de shipear: el spread del SSOT ya no pisa identificacionCamarasAdas/mdvrId/ipMdvr en la ficha ni en el editor, asientos vuelve al canonico, IP ADAS/IP MDVR quedan gateados por el id 24 para no publicar las clases E01/E02/E03, y Estandar de Emisiones sigue en el PDF ademas de Tipo de motor. NO EJERCITADO: nadie abrio el PDF en dev01 con este build.
• wi-cli-venus note · 5w ago
  Version viva en DEV es 5.5.121 (03a8e605), no 5.5.120. coder-mba-l-ca corrio el deploy canonico despues de que ccb0e1ed ya habia aterrizado, asi que el pre-hook commiteo solo el bump automatico de package.json. Verificado: git diff --stat ccb0e1ed..dev/dev = package.json, 1 linea. El fuente de 414 sigue siendo ccb0e1ed y el PASS de audit sigue valiendo. Salio MOVILBA-415 de la review: la ficha gatea el equipamiento contra el literal 24 en cinco lugares (una la agrego este commit) contra la regla de MOVILBA-317.
• wi-cli-venus audit-finding · 3w ago
  Tracker download 2026-09-19 reopens PDF item #6: stakeholder says Entidad and Indicador de linea are the same datum and only one must appear in the PDF. Treat this as a concrete duplicate-output requirement while the broader field-definition work remains open.
• wi-cli-venus note · 3w ago
  Entrypoints medidos por db04-mba-l-ca en el checkout actual 2026-09-23 12:16 ART (Resueltos #70). NO son prueba de deploy ni de salida, son puntos de entrada de comportamiento: src/app/vehiculos/[dominio]/page.tsx:740-800 (campos generales del PDF), mapa de historial desde :1013. Pendiente de mi lado: medir el COMPORTAMIENTO en el arbol actual y recien despues datarlo por ancestria - un SHA no contesta 'esto esta vivo' (c4fc618c dio 'branch --contains' vacio y eso solo dice 'no es ancestro de dev/main hoy', con 116 ramas locales y 22 remotas sacadas el 09-22).
• coder03-mba-l-cc note · 3w ago
  coder03-mba-l-cc 2026-09-24 - The Para Elazar answer published for this row is false by irrelevance and has to come out. Snapshot 10 of the tracker carries Respuesta='El historial del PDF no repite Entidad ni Indicador de linea cuando no cambiaron', while the stakeholder's own Verificado cell in the same row says 'Indicador de linea y entidad son el mismo dato. Tiene que haber uno solo. En la exportacion de PDF'. Those are two different subjects: she is not reporting repetition ACROSS history rows, she is reporting that one datum is printed under two labels in Informacion General. The answer therefore does not address the complaint even if it is true of the history block, and it reads to her as a resolution. This item's own audit-finding of 2026-09-19 already states the requirement in her terms - Entidad and Indicador de linea are the same datum and only one must appear in the PDF - so bwi contradicts the published cell. Item is backlog, unassigned, priority 2, nothing shipped for it since ccb0e1ed, and ccb0e1ed is what ADDED the second label: it put 'Indicador de la linea' into the PDF from identificador_empresa, recorded in that commit event as the stakeholder's label over a field that identifies the EMPRESA, referent unconfirmed. So the duplicate is ours and it is deployed. Correction to apply to the tracker: clear the Respuesta and mark the row reopened against MOVILBA-414, same treatment as MOVILBA-456 row 7. What stays open underneath and is NOT a coder decision: which of the two labels survives is vocabulary, and the definition of 'Indicador de la linea' comes from Eugenia - the repo has numero_linea and color_linea and nothing named that.
• coder03-mba-l-cc note · 3w ago
  coder03-mba-l-cc 2026-09-24 - CONFIRMED on Elazar's real PDF, not inferred. /data-lezama/movilba/import-reports/2026-09-24-0507-movilba-AC736PL-reporte01.pdf: 'Indicador de la linea' and 'Entidad' both print COLECTIVEROS UNIDOS S.A.I.F.(C.U.S.A.), byte for byte, four lines apart. The DEV row's raw_identificador_empresa matches that string exactly, so the two labels are two renderings of one datum and the stakeholder's reading is right. The duplicate entered with ccb0e1ed (v5.5.120), which added 'Indicador de la linea' to the individual PDF alongside the Entidad line that was already there - see the commit event of 2026-09-10 on this item. Emitters: src/app/vehiculos/[dominio]/page.tsx:749 (label 'Indicador de la linea', value vehiculo.datosSsotPdf?.identificadorEmpresa) and :761 (label 'Entidad', value entidadCadenaNombre). Removing one of the two is the whole fix for the duplicate; the rest of this item's eight-field requirement is separate and unmeasured. Which of the two labels survives is the stakeholder's call, not ours - do not pick it silently.
• coder03-mba-l-cc assigned · 3w ago
  coder04-mba-l-ca / coder
• coder03-mba-l-cc priorityChanged · 3w ago
  1
• coder04-mba-l-ca progress · 3w ago
  coder04-mba-l-ca | 2026-09-24 05:35 ART Measured MOVILBA-414 against shared dev checkout and real DEV PDF /data-lezama/movilba/import-reports/2026-09-24-0507-movilba-AC736PL-reporte01.pdf. All eight title concepts appear in this sample: CUIT 30-54624397-0; line indicator; category M3; emissions E5; tipo de motor E5; seats 28; IP ADAS BK0D1FBPAJ00038; IP MDVR 303033303300. Caveat: emission/type-motor both render E5 while Unidad Propulsora is GO; I have not established whether that is intended semantics or a bad source mapping. Confirmed defect: line indicator and entity both render COLECTIVEROS UNIDOS S.A.I.F.(C.U.S.A.), matching raw identificador_empresa. Tracker Verificado says keep one label but does not identify which. No code touched; page.tsx also contains coder03's in-flight MOVILBA-174 hunks. Need Eugenia's choice of surviving label before editing; seven other concepts are present in this sample, not population-verified.
• coder03assistant-mba-l-ca progress · 3w ago
  coder03assistant-mba-l-ca | 2026-09-24 05:44:21 ART. Under live tracker workbook lock, added Para Eugenia #88 at first empty physical row 12 as an unanswered question: real 24/09 DEV PDF for AC736PL renders Indicador de la linea and Entidad with the same COLECTIVEROS UNIDOS S.A.I.F.(C.U.S.A.) value; asks which label Eugenia prefers to retain. D12 blank, E12 PENDIENTE, F12 records real-PDF/source-field provenance. Existing #86/#87 unchanged. Verified live XLSX row, style, and legible rendering; SHA-256 c2769c7849ce8936ea4255a5d997cc6c8a38d9be4e2c47d269d837999c6bc34c. Imported tracker SQLite snapshot 14 (3677 cells); diff 13→14 only adds Para Eugenia row #88, zero other sheet changes. No PDF code change and no answer claimed.
• coder04-mba-l-ca statusChanged · 3w ago
  coder04-mba-l-ca | 2026-09-24 05:51 ART. Re-measured current shared dev checkout and the real AC736PL PDF. All eight requested concepts are visible in that one PDF: CUIT, Indicador de la línea, carrocería M3, Tipo de motor E5, 28 seats, IP ADAS, Cámara MDVR, and IP MDVR. Existing tracker Convenciones row 12 defines Tipo_Motor E3/E5 as emissions standard; the PDF also separately prints Estándar de Emisiones E5, so no new semantic decision inferred. Confirmed duplicate remains: Indicador de la línea and Entidad both print the identical company name. Para Eugenia #88 asks which label to keep and remains PENDIENTE. This is one-record output evidence only, not a population/source audit. No code changed; did not touch page.tsx because coder03 has MOVILBA-174 edits there.
• coder04-mba-l-ca progress · 3w ago
  coder04-mba-l-ca | 2026-09-24 ART. Elazar decidió resolver la pregunta Para Eugenia #88 quitando la fila duplicada ‘Indicador de la línea’ y conservando ‘Entidad’. En el PDF de la ficha también se renombró ‘CUIT de la empresa’ a ‘CUIT’. El cambio de código está pendiente de auditoría; el BWI amplio MOVILBA-414 sigue abierto para los demás campos.
• audit-mba-l-cc audited · 3w ago
  audit pass: page.tsx PDF hunks only: 'Indicador de la línea' row removed, 'CUIT de la empresa' -> 'CUIT'; 574 chasis hunks excluded. typecheck, eslint page.tsx, test:source 37/37 (dirty tree). Not run: rendered PDF, committed tree; other 414 fields open.
  payload

  {"scope":"page.tsx PDF hunks only: 'Indicador de la línea' row removed, 'CUIT de la empresa' -> 'CUIT'; 574 chasis hunks excluded. typecheck, eslint page.tsx, test:source 37/37 (dirty tree). Not run: rendered PDF, committed tree; other 414 fields open.","outcome":"pass","evidence":"audit-mba-l-cc 2026-09-24. Diff read: 8 lines removed, 1 label changed. grep src/tools: zero remaining 'Indicador de la línea'/'CUIT de la empresa'. Elazar decision per coder04 bwi note 10:56Z (peer-relayed).","reportRef":null}

• audit-mba-l-cc note · 3w ago
  audit-mba-l-cc | 2026-09-24 census requested by coder03-mba-l-cc, from a source read of src/app/vehiculos/[dominio]/page.tsx (working tree), NOT a rendered PDF (coder04's 05:35 real-PDF AC736PL note covers that). 1) The title's 2/2/1/3 split does not match the tree. All 8 render: CUIT (label 'CUIT', datosSsotPdf.cuit, :763); Categoria de la Carroceria (datosSsotPdf.carroceriaCategoria, :841, raw literal, no FK); Tipo de motor (raw datosSsotPdf.tipoMotor, :869); Cantidad de asientos (:846); IP ADAS (:946, only when ADAS=Si); Camara MDVR (Si/No flag, :965); IP MDVR (:971, only when MDVR=Si). 'Indicador de la linea' is gone from the working tree (see 2). The mislabels are already correct. The documented removal is MOBAAPI-661 dropping vehiculos.categoria_regulatoria_id (docs/reference/vehiculo-data-model.md:8-14); the PDF now takes the category from the period literal instead. 2) Collapse to one label: implemented ONLY in the uncommitted working tree (row removed at page.tsx:754 hunk). HEAD still emits both rows. Not in any deploy. 3) page.tsx dirty hunks: 9 = 581 x3 (import :29, render :1444, comment :1450), 414 x2 (:754, :772), 574 x4 (:812,:816,:1363,:1367). 451 hunks are already committed. Each has a scoped PASS from me, all on the DIRTY tree, none sha-bound. 574's page hunks need vehiculos.ts + vehiculos.chasis-marca.test.ts in the same commit or the test is red on a clean tree and the DTO still overrides. I ran typecheck + test:source 37/37 on HEAD d45cd52e + exactly those 3 files in a clean scratch copy: green. Not run: rendered PDF.
• coder03-mba-l-cc commit · 3w ago
  coder03-mba-l-cc 2026-09-24 08:11 ART - shipeado en dev 8ba2fcdb (v5.6.57), --only src/app/vehiculos/[dominio]/page.tsx + src/repositories/vehiculos.ts + src/repositories/vehiculos.chasis-marca.test.ts. 414: se elimina la fila 'Indicador de la linea' de la ficha y 'CUIT de la empresa' pasa a 'CUIT'; el item NO se cierra, porque el censo de audit contra el arbol dice que los OCHO campos del titulo renderizan y el split 2/2/1/3 del titulo esta vencido y hay que reescribirlo. 574: Marca y Modelo del chasis pasan de datosSsotPdf (crudo del libro) a chasisFabricante/chasisModelo (catalogo) en cuatro lugares, las dos superficies de esta pagina; siguen crudos los cuatro lectores de export e historico que censo coder04, asi que el item sigue abierto. 581: sale ValidadoraEntitySection de la ficha con su import; el formulario de edicion y la card del home siguen sucios en el arbol de coder04, asi que la ocultacion NO esta completa. Gates: los corrio audit-mba-l-cc sobre HEAD d45cd52e mas estos tres archivos en copia limpia, typecheck + test:source verdes; el deploy volvio a correr test:source 38/38, lint y typecheck sobre el commit. NO EJERCITADO: nadie abrio la ficha renderizada ni genero un PDF.
• coder03assistant-mba-l-ca progress · 3w ago
  coder03assistant-mba-l-ca | 2026-09-24 08:11 ART — Stakeholder question resolution for live tracker todo-rutap-importacion-prestaciones.xlsx, Para Eugenia #88: Elazar decided to remove the duplicate PDF label ‘Indicador de la línea’ and retain ‘Entidad’. The question is resolved; this does not close MOVILBA-414, which remains open for its other ficha-PDF field requirements. The change shipped in 8ba2fcdb (v5.6.57); current BWI commit event notes no rendered ficha/PDF exercise, so this is the label decision record, not a deployment/render verification. Archive the complete question and decision in Resueltos and import a new tracker snapshot.
• audit-mba-l-cc audited · 3w ago
  audit pass: Bound to sha 8ba2fcdb (v5.6.57): git archive of the commit in a clean copy: typecheck, eslint on 3 files, test:source 37/37. 3 files byte-identical to the ones I audited dirty. Not run: rendered ficha/PDF, DB.
  payload

  {"scope":"Bound to sha 8ba2fcdb (v5.6.57): git archive of the commit in a clean copy: typecheck, eslint on 3 files, test:source 37/37. 3 files byte-identical to the ones I audited dirty. Not run: rendered ficha/PDF, DB.","outcome":"pass","evidence":"audit-mba-l-cc 2026-09-24. cmp of git show 8ba2fcdb:<file> vs audited copy: same for page.tsx, vehiculos.ts, chasis-marca.test.ts. Covers the ticket's own hunks only; 574 stays open (4 raw readers).","reportRef":null}

• coder04-mba-l-ca titleChanged · 3w ago
  Validar fidelidad de valores de los campos de la ficha PDF del vehículo
• coder04-mba-l-ca descriptionChanged · 3w ago
  was: Pedido relevado por coder-mba-l-ca (2026-09-09): el PDF individual de vehiculo debe traer CUIT de la empresa, 'Indicador de la linea', categoria de carroceria (M2/M3), tipo de motor (EIII/EV), cantidad de asientos, IP ADAS, Camara MDVR e IP MDVR. Medido contra src/app/vehiculos/[id]/page.tsx handleExportPDF (lineas 476-631), unico generador de esa ficha (downloadReport + components/pdf/GenericReport.tsx). Estado real por campo: (1) Cantidad de Asientos YA sale, linea 510 - no falta. (2) Estandar de Emisiones YA sale, linea 520. (3) 'tipo de motor EIII/EV' NO es un campo: EIII es estandar_emisiones y EV es unidad_propulsora, dos columnas independientes desde MOBAAPI-661 - una sola etiqueta no puede expresar las dos; hay que decidir si se imprimen las dos. (4) IP ADAS: la columna se llama identificacion_camaras_adas y el PDF la rotula 'ID Camaras ADAS' (linea 548), gateada por adas_presente_id=24. (5) IP MDVR: existe como ip_mdvr y el PDF la rotula 'ID MDVR' (linea 552) - defecto de ROTULO, no ausencia. (6) 'Camara MDVR': ambiguo. mdvr_id es un flag Si/No de opciones que ya sale como 'MDVR' (linea 551) y camaras_internas es un CONTEO que ya sale como 'Camaras Internas' (linea 550); ninguna columna se llama 'camara MDVR'. (7) Categoria M2/M3: categoria_regulatoria_id fue BORRADA por MOBAAPI-661 el 2026-06-30 porque era constante 'M3 - Colectivos' para todo colectivo (cero informacion); sobrevive solo en vehiculos_archive y en la tabla de import cruda. Reponerla es revertir una decision con ticket, no llenar un hueco: primero hace falta una fuente que traiga la distincion. (8) CUIT: falta de verdad - el PDF imprime solo el nombre de la entidad (linea 485); el CUIT vive en entidades y el camino de resolucion ya lo usa MOVILBA-268. (9) 'Indicador de la linea': no existe en el repo ni en la base - lineas tiene numero_linea y color_linea y nada mas; el PDF imprime numeroLinea como 'Linea' (linea 482). El vocabulario lo fija el dominio: la definicion la da Eugenia, no un carril; candidatos a descartar son numero_linea, color_linea e interno. FALTAN DE VERDAD: CUIT, 'Indicador de la linea' (sin definir) y la distincion M2/M3 (sin fuente).
• coder04-mba-l-ca progress · 3w ago
  coder04-mba-l-ca | 2026-09-24 11:10 ART — Releí MOVILBA-414 y los eventos contra HEAD 32e7f40c. git grep de ‘Indicador de la’ en src da 0 hits; commit 8ba2fcdb confirma el retiro de esa fila y CUIT renombrado. Reemplacé el título/descripción obsoletos: siete conceptos distintos siguen en alcance; lo pendiente es validar fidelidad semántica/fuente, especialmente Tipo de motor frente a emisiones/unidad propulsora. La auditoría disponible es un censo de fuente, no un PDF renderizado después del deploy ni validación poblacional. src/services/vehiculos.ts está sucio en el checkout compartido y no es parte de mis cambios.
• coder03assistant-mba-l-ca progress · 2w ago
  coder03assistant-mba-l-ca | 2026-09-28 11:31 ART — Elazar requested production deployment of the resolved label change while coder03 handles other work. Target 8ba2fcdb is audited, but the only approved production ship path merges the entire dev branch: dev f53b3efc is 20 commits / 47 files ahead of main 4dddb541, so it would include unrelated work beyond MOVILBA-414. The shared checkout also has unrelated tracked modifications; mba-deploy-prod.sh requires a clean tree and would abort. No production deploy was run; no other lane's changes were altered. Awaiting scope/checkout resolution.
• audit-mba-l-cc audit-finding · 2w ago
  audit-mba-l-cc 2026-09-28, HEAD d8ccd634, static+DB, no writes. Files: src/app/vehiculos/[dominio]/page.tsx:750-975 (handleExportPDF), src/repositories/vehiculos.ts:210-280 (columnasDesdeFicha), :458-510 (getVehiculo, datosSsotPdf). 6/7 concepts confirmed correct: CUIT (datosSsotPdf.cuit <- e.cuit, real), asientos, ADAS/MDVR Si-No + IP fields (catalog-backed via opciones, text IDs passthrough), categoria carroceria (see MOVILBA-546 finding, correct given NULL). NEW FINDING on 'Tipo de motor' (page.tsx:869-870): prints vehiculo.datosSsotPdf.tipoMotor, sourced from vehiculo_historial_normalizado.tipo_motor = nullif(btrim(raw book text)) per docs/migrations/2026-09-08-movilba-269-proyectar-snapshot-DEV.sql:377 - RAW, not catalog-resolved. This is alongside, not instead of, the already-catalog-backed 'Estandar de Emisiones' field (estandarEmisionesNombre, line 858). MOVILBA-342's own gate (docs/migrations/2026-09-08-movilba-341-342-emisiones-y-creado-por-DEV.sql:555-562) RAISE EXCEPTIONs if any row has nonblank tipo_motor without a resolved estandar_emisiones_id - so a catalog resolution exists for every value shown raw here. Under CLAUDE.md hard rule 2 (2026-09-24, 'no surface displays raw book text for a field that has a catalog behind it'), this is a violation unless Eugenia explicitly asked for the raw label as a second field - the in-code comment (page.tsx:867-868) claims that, but no entry exists in docs/reference/ssot-overrides.md and no ticket is cited. Not fixed (audit does not change code). Scope: static code read + 2 migration files; DB not queried (grep-only, sufficient - migration text is the enacted DDL/DML).
• coder03assistant-mba-l-ca progress · 2w ago
  coder03assistant-mba-l-ca | 2026-09-28 11:51 ART — Reconciliation check: Para Elazar row 5 still says the label-choice question awaits a preference, but the decision is already recorded in Resueltos #84 / Para Eugenia #88: retain ‘Entidad’, remove ‘Indicador de la línea’. This settles only that label question; MOVILBA-414 remains inProgress for remaining PDF field/source fidelity. Download 2026-09-28-1133 adds no new answer or evidence for the remaining fields. Audit-mba-l-cc is assigned to verify the remaining PDF field mapping and MOVILBA-546 against code plus read-only DEV/PROD DB artifacts.
• coder03assistant-mba-l-ca progress · 2w ago
  coder03assistant-mba-l-ca | 2026-09-28 11:54 ART — Tracker reconciliation completed in live workbook: Para Elazar row 5 now records Elazar's resolved label choice and explicitly leaves MOVILBA-414 open for remaining PDF field fidelity. The duplicate active Para Eugenia #88 row was removed; its complete decision record remains in Resueltos #84. SQLite snapshot 23 imported after the write; diff 22→23 shows only those two Para Elazar cell changes plus removal of the already-archived duplicate #88, with all other sheets unchanged.
• coder03assistant-mba-l-ca progress · 2w ago
  coder03assistant-mba-l-ca | 2026-09-28 12:03 ART — Audit-mba-l-cc's static code/migration review found 6/7 PDF concepts aligned and one remaining issue: page.tsx:869-870 emits raw datosSsotPdf.tipoMotor; migration 2026-09-08-movilba-269-proyectar-snapshot-DEV.sql:377 preserves raw book text, while the emissions catalog has a resolved ID under MOVILBA-342's gate. No SSOT override authorizing a second raw-label field was found. Audit did not query DB or render a PDF. MOVILBA-414 remains inProgress with the type-motor field discrepancy open; audit finding is durable on the item.
• coder03assistant-mba-l-ca progress · 2w ago
  coder03assistant-mba-l-ca | 2026-09-28 12:04 ART — Updated live tracker Para Elazar row 5 from audit-mba-l-cc's static finding: six of seven PDF field concepts align; tipoMotor is emitted as raw text at page.tsx:869-870 despite a catalog-resolved emissions value and no documented SSOT override. Label decision remains resolved separately (retain Entidad). MOVILBA-414 stays inProgress for this remaining fidelity issue. Tracker import snapshot 25; PDF render/live DB were not part of this audit.
• coder04-mba-l-ca progress · 2w ago
  coder04-mba-l-ca | 2026-09-28 12:46 ART — Removed the raw tipo_motor PDF row mislabeled as Tipo de motor and removed its datosSsotPdf DTO mapping in src/app/vehiculos/[dominio]/page.tsx and src/repositories/vehiculos.ts. The catalog-backed Estándar de Emisiones row remains. No remaining datosSsotPdf.tipoMotor references. Sent these two hunks to audit-mba-l-cc; waiting for scoped verdict. MOVILBA-574 remaining raw readers are unchanged.
• audit-mba-l-cc audited · 2w ago
  audit pass: 2-file diff: page.tsx ficha row + interface field, vehiculos.ts repo projections (both actual blocks); typecheck/lint/test:source all green
  payload

  {"scope":"2-file diff: page.tsx ficha row + interface field, vehiculos.ts repo projections (both actual blocks); typecheck/lint/test:source all green","outcome":"pass","evidence":"raw tipo_motor removed from ficha PDF surface; estandar_emisiones remains canonical. Note: types/vehiculos.ts:147 datosSsotPdf.tipoMotor left stale (unused, non-breaking) - not blocking","reportRef":null}

• coder04-mba-l-ca progress · 2w ago
  coder04-mba-l-ca | 2026-09-28 12:56 ART — Current BWI history records the two-file tipo_motor correction and audit-mba-l-cc PASS at 2026-09-28T15:48Z (page PDF row + repository DTO projection). Item remains inProgress for fidelity of the other six distinct PDF concepts; no generated PDF or live DB validation performed in this update.
• coder03-mba-l-cc note · 2w ago
  coder03-mba-l-cc 2026-10-01 17:35: the remaining leg of this item is not measurable with any instrument that exists today, and that is now its own item, MOVILBA-643. The ficha PDF is assembled inside handleExportPDF in src/app/vehiculos/[dominio]/page.tsx:725, inline between :745 and :1092, from a dozen variables derived from client component state, so nothing outside the component can produce the same ReportSection[]. Re-implementing the assembly to measure it would measure my copy, not the shipped surface, so it is not evidence. The renderer itself is not the obstacle - @react-pdf/renderer renders to a buffer in node and the only DOM in downloadReport is the blob download - so extracting the assembly into a pure function is what unblocks all three items at once. Until 643 lands, the only valid instrument is a real browser session on dev01, which needs Elazar at the login form. Do not report this as 'needs an authenticated session' without naming 643: the obstacle is the missing seam, not the session.
• coder04-mba-l-ca progress · 2w ago
  coder04-mba-l-ca | 2026-10-02 11:10 ART. tipoMotor raw-row removal is audit-PASSed. Remaining fidelity review spans the other six concepts and a generated PDF; MOVILBA-643 is the missing seam for measuring the shipped PDF assembly. This is not a generic authenticated-session blocker.
• coder04-mba-l-ca progress · 1w ago
  coder04-mba-l-ca | 2026-10-05 12:22 ART. PROD PDF fidelity sample measured by proxy-mba-w-cc on app.movilba.com, build v5.6.150, AI578HM. Artifact: /data-lezama/movilba/evidencia/MOVILBA-664/2026-10-05-1211-movilba-AI578HM-reporte01.pdf (SHA256 2c0d55e0...f808b0afcc). Rendered page text compared field-by-field to pdftotext -layout: all visible-by-default fields match (Información General, Entidad, Equipamiento Tecnológico, Chásis/Motor/Carrocería, Información Operativa, Estado Actual, visible Historial Cambios). Residual: expanding UI 'Ver más datos (2)' reveals Modelo de carrocería: TODO BUS and Estado: Alta, neither appears anywhere in PDF Cambios; PDF ends at Identidad: Sí | Más datos:. Thus full history field fidelity is not confirmed; classify/resolve the two-field omission before closing. No code change.
• coder03assistant-mba-l-ca note · 1w ago
  coder03assistant-mba-l-ca | 2026-10-05 13:43 ART Internal tracker instruction removed from stakeholder-facing Comentario para Claudia cell in archived live workbook SHA cb74a882. Original Pendientes L61: 'Reabierto según BWI MOVILBA-414.'
• coder03-mba-l-cc note · 1w ago
  coder03-mba-l-cc | 2026-10-05 14:53 ART. Live PASS on PROD app.movilba.com v5.6.161 for AI578HM, checked by proxy-mba-w-cc after Elazar's login. The on-screen Cambios list, with 'Ver mas datos' expanded, and the downloaded ficha PDF carry the same 35 fields in the same order with the same values. That includes Modelo de carrocería TODO BUS and Estado Alta, which the PDF was missing before. There are no extra or missing fields and no unchanged field shown as a change. Evidence: /data-lezama/movilba/evidencia/MOVILBA-456/2026-10-05-1453-movilba-AI578HM-reporte01.pdf (sha256 4966a684). The pod and DEV are on 161 as well. NOT EXERCISED: any vehicle other than AI578HM.
• coder04-mba-l-ca completed · 1w ago
  coder04-mba-l-ca | 2026-10-05 14:53 ART. Closed per coder03: proxy visually checked the PROD v5.6.161 AI578HM PDF and recorded evidence on the item. The PDF matches the ficha for all visible-by-default fields and the previously omitted disclosure fields are now present per MOVILBA-456.