Falta el bloque de baja del EX-2026-41544750 en el historial de AG232XB y AG202SZ
Eugenia amplia el reporte: en https://dev01.movilba.com/vehiculos/AG232XB y en AG202SZ, despues de la Res. SECT 56/2026 FALTA el bloque de historial correspondiente al EX-2026-41544750- -GCABA-DGGSM, tramite Modificacion, que es la BAJA. Lo que si se ve es el periodo 01/04/2026 - 15/09/2026 con el cambio de CUIT 30-54622797-5 -> 33-70223426-9 y de empresa TRANSP. AUTOMOTORES 12 DE OCTUBRE S.A.C. -> NUDO S.A. En PARQUE MOVIL RUTAP los datos son: Fecha ALTA 01/04/2026, Observ 'Se cedio la linea a la empresa NUDO S.A.', ALTA Res. SECT 56/2026. Medir primero si el expediente de baja existe en el libro vigente y en vehiculo_historial de las dos bases, y recien despues mirar la vista que arma el historial de la ficha. Afecta a dos dominios, asi que no es un dato suelto.
Activity
-
db03-mba-l-cc / db
-
db03 midio y el dato esta bien en las tres puntas, 2026-10-01: el libro (snapshot 8/20, 2026-09-30-1305, vigente) trae AG202SZ fila_excel 3914 y AG232XB fila_excel 3915 con tramite=Modif, alta 2026-04-01, baja 2026-09-15, expte_alta 'Res. SECT 56/2026' y expte_baja 'EX-2026-41544750-...', y rutap.vehiculo_historial_normalizado tiene las dos filas identicas en PROD (vehiculo_id 4433/4438) y en DEV, origen=import y borrado_en NULL. O sea que el bloque que falta no falta en la base: se pierde al armar el historial de la ficha. Sigue db03, ahora SI sobre la vista - el 'pare antes de la vista' del enunciado era para no saltar a la conclusion, no un limite de alcance. Correccion al enunciado: 'libro 2026-10-01-1040' nombra el XLSX del tracker, no un parque-rutap nuevo; no bajo ningun libro nuevo.
-
coder03-mba-l-cc 2026-10-01 11:05 ART - DIAGNOSIS, not a DB defect. db03 measured rutap.vehiculo_historial_normalizado for both vehiculos 4433 (AG202SZ) and 4438 (AG232XB): expte_baja = raw_expte_baja = 'EX-2026-41544750- -GCABA-DGGSM', neither NULL, chain CTE and buildChainEvents 1:1, nothing dropped. Do NOT touch v_vehiculos_detalle: no consumer reads a per-element baja key out of its historial jsonb (only pdf/GenericReport.tsx:150 reads the DTO .historial), and the ficha + vehicle PDF both come from getVehiculoHistorial -> src/repositories/rutap-historial.ts, which already maps expteBaja at line 116. Actual defect is in the UI, src/components/HistoryPeriodContent.tsx:106. The 'Baja registrada el' date and the 'Expediente de baja' line are emitted ONLY when esBajaEvento is true, and esEventoDeBaja (src/lib/historial-vehiculo.ts:126-139) requires origen === 'app'. These rows are origen = 'import', so for a book-origin period that carries its own fecha_baja + expte_baja the two fields are never promoted to the face and fall into historyDisclosure - which is the 'Ver mas datos (33)' fold Eugenia is looking at. Same gate on the PDF side: src/app/vehiculos/[dominio]/page.tsx:1015 and 1070-1076 put the expediente de baja in the footer 'Mas datos' line instead of the block. Fix direction: an import period whose fecha_baja and expte_baja are set must show both on the face, same as the alta expediente, independently of origen. esEventoDeBaja keeps its current meaning (an app-written zero-length closure event) - the face-promotion condition is what must stop depending on it. Four surfaces: ficha, PDF, XLSX export and /api/v1 - check each before declaring it fixed.
-
coder04-mba-l-ca / coder
-
coder04-mba-l-ca | 2026-10-02 10:54 ART. The measured source has both fecha_baja and expte_baja on the two imported periods; the application-history reader already maps both to RutapHistorialItem. Added a shared predicate requiring both values without changing esEventoDeBaja (app closure classifier). Ficha and PDF now promote the documented baja case to the face; Modificacion date labels remain Desde/Hasta. The XLSX route already selects both values and RUTAP_HISTORICAL_COLUMNS already emits Fecha_Baja / Expte. Baja. The history JSON mapper already returns fechaBaja/expteBaja; the route is /api/vehiculos/[id]/historia, with no /api/v1 history route in src/app/api/v1. Added screen/PDF/API assertions. No tests, DB query, PDF render, or download executed in this pass; request audit.
-
Measurement is recorded in the accompanying progress event: both imported periods carry fecha_baja and expte_baja; four-surface source review done; implementation ready for audit, runtime surfaces unexercised.
-
audit pass: tieneBajaDocumentada predicate hunks in historial-vehiculo.ts, HistoryPeriodContent.tsx, vehiculo-pdf-history.ts, page.tsx; esEventoDeBaja unchanged as state classifier. Tests ran, pass.
payload
{"scope":"tieneBajaDocumentada predicate hunks in historial-vehiculo.ts, HistoryPeriodContent.tsx, vehiculo-pdf-history.ts, page.tsx; esEventoDeBaja unchanged as state classifier. Tests ran, pass.","outcome":"pass","evidence":"Face-promotion and footer-suppression both gated on same tieneBajaDocumentada flag, mutually exclusive, no double-render into disclosure (consumedFace.add confirmed both branches).","reportRef":null} -
coder04-mba-l-ca | 2026-10-02 11:35 ART. Audit PASS is recorded for shared tieneBajaDocumentada behavior in ficha/PDF; commit 6f523894 is an ancestor of main (production promotion 0b9a55b5). Both measured imported periods carried fecha_baja and expte_baja. PDF render/browser display remains unexercised by audit.
-
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 L52: 'Anexo Bajas: todo-rutap-anexos.xlsx, hoja Bajas; cotejar siempre con el libro vigente.'