movilba
MOVILBA-545
· child of MOVILBA-572 Un periodo escrito por la app deja en NULL los campos descriptivos del SSOT y las cuatro superficies los resuelven DESDE EL PERIODO, asi que muestran 'No registrado' con el dato presente en el vehiculo base Done
Marca y Modelo figuran 'No registrados' en la ficha y en el PDF despues de un alta
Done normal
cmcoder04-mba-l-ca
Reported by Fabri, Para Elazar item 13, example dominio LP680EG. Both the vehicle page and the exported PDF show the fields as not registered after a vehicle is created. Establish first whether the value was never persisted or is persisted and not resolved for display - those are different bugs and the second one is the four-surfaces class.
Activity
-
audit-mba-l-ca / auditor
-
audit-mba-l-ca | 2026-09-24 05:09 ART. READ-ONLY finding, no code/data change. DEV example LP680EG now belongs to vehiculo_id 6777 whose current dominio is LP680FF; no LP680EG/TT333AA base vehiculo exists in PROD. DEV v_vehiculos_detalle for 6777 resolves chasis_fabricante=YUTONG, chasis_modelo=ZK6128HG, chasis_id=126, but rutap.v_vehiculo_historial_actual selects app period 286433 with chasis_marca/modelo NULL. Source trace: GET /api/vehiculos/[id] -> VehiculoService -> vehiculoRepository.findById joins v_vehiculos_detalle to that current-period view and sets datosSsotPdf.chasisMarca/Modelo from the period; both HTML ficha and its PDF use those same null fields and print No registrado; the internal JSON response also contains those null fields. Edit form instead holds chasisId from the base vehicle and renders its catalog option. Historial RUTAP XLSX/CSV projects coalesce(raw_chasis_marca, chasis_marca) and coalesce(raw_chasis_modelo, chasis_modelo), also blank on this app period. DEV census over selected current rows: 11 have base chassis brand/model present but period values NULL; PROD 0/2413 selected rows (no app current rows). This is a source-resolution split, not absence of base chassis data. The report's original plate is no longer the current plate; no authenticated browser/PDF request was exercised. Cross-ref MOVILBA-553 for the same brand/model gap on TT333AA. Coder should decide the correct period-vs-ficha source and test page, edit, export, JSON together.
-
parent=MOVILBA-572
-
coder03assistant-mba-l-ca / coder
-
coder03assistant-mba-l-ca | 2026-09-24 07:42 ART — Prior DEV read-only evidence in this item identifies the exact example as vehiculo 6777, now dominio LP680FF: base FK chasis_id resolves to YUTONG / ZK6128HG, while current app period 286433 has chasis_marca/modelo NULL; repository feeds those period NULLs to ficha and PDF, causing No registrado. Current shared checkout has coder04's uncommitted MOVILBA-574 diff changing those same page/DTO fields to catalog labels. 574 is assigned to coder04 and its newly broadened all-surface export work is not yet in that diff. I will not edit the overlapping chassis paths; 545 remains open pending one audited, deployed 574 solution or evidence of a separate persistence defect. No new render performed.
-
coder03assistant-mba-l-ca | 2026-09-24 10:40 ART — coder04-mba-l-ca confirms MOVILBA-545 should be treated as covered by MOVILBA-574 unless a persistence audit finds a separate defect. Current DEV evidence: vehicle 6777/LP680FF has a valid chasis_id resolving to YUTONG / ZK6128HG, while the app period's raw chasis_marca/modelo are NULL; this is a catalog-display/export gap addressed by 574. No separate missing catalog FK or persistence defect identified. Keep 545 open until 574 is audited and deployed or a distinct persistence defect is measured.
-
coder03-mba-l-cc 2026-10-01 16:20: this item no longer carries its own question. MOVILBA-545, 546, 553 and 572 share one measured cause - the four surfaces resolve the descriptive chassis and body fields from the vehicle's period, and a period written by the app leaves them NULL while the value is present on the vehicle's chassis and carroceria rows; the parque report resolves them from the chassis catalog instead, which is why that one surface is correct. audit-mba-l-cc verified the split independently in code: src/lib/exports/vehiculos.ts:157 reads the chassis catalog, src/repositories/vehiculos.ts:504 (ficha and PDF) reads the period's own column. The single decision - catalog for all four surfaces, or keep the book's raw text and accept blanks on app-created rows - is asked once in the tracker, 'Para Elazar' row 45, filed under MOVILBA-572 with A recommended. Do not implement either option on any of the four items before his answer.
-
Consolidated into the single source-of-truth decision asked in Para Elazar row 45 under MOVILBA-572. Period-vs-catalog is Elazar's call; no implementation before his answer.
-
coder03assistant-mba-l-ca | 2026-10-01 22:18 ART. New, separate create rule is decided: colectivo alta must require chasis; this does not resolve the original catalog-display question still blocking MOVILBA-545 under MOVILBA-572. Source measurement: alta form has no required marker/required constraint on chasisId (agregar/colectivo/page.tsx:662-676); create service maps missing/blank chasisId to undefined and calls createColectivo (services/vehiculos.ts:515-549); repository inserts NULL when absent (repositories/vehiculos.ts:929). Edit path has no chasis-required guard. Blank edit input sanitizes to null, but service converts null with ?.toString() to undefined and repository ignores undefined, so edits to other fields leave a pre-existing NULL untouched and the form currently cannot clear a non-NULL chassis through that route. No existing rows changed. Code change queued behind MOVILBA-621 audit.
-
coder04-mba-l-ca / coder
-
coder04-mba-l-ca | 2026-10-02 12:42 ART. The ficha/PDF current vehicle values already read v_vehiculos_detalle catalog labels; the shared historial reader now resolves historical chasis_id/carroceria_id to catalog labels for ficha/PDF/API values and changes. This covers the reported chassis/body manufacturer and model blanks. Category remains outside this change pending MOVILBA-546 research. Audit review requested under parent MOVILBA-572.
-
coder04-mba-l-ca | 2026-10-02 12:49 ART. Elazar's catalog-source decision is implemented for chassis marca/modelo; ficha/PDF/API use the shared period-history resolver, and audit-mba-l-cc recorded scoped PASS in MOVILBA-572. SHIP path sent to coder03; awaiting commit.
-
2026-10-02 12:59 coder03-mba-l-cc: v5.6.144 live on PROD, DEV and pod (proxy: serviceId 20639 -> 144). SIN EJERCITAR: ficha/PDF in browser, real Historial RUTAP download.
-
Stakeholder feedback, tracker online 2026-10-05 13:24 (Eugenia/Fabri), relayed by coder03: Covered by 632: chasis becomes required at alta, so Marca/Modelo can no longer end up 'No registrados'.
-
coder04-mba-l-ca | 2026-10-05 13:00 ART. Chasis omission is covered by the same already-shipped MOVILBA-638 code in current HEAD cf54f30f: src/app/vehiculos/agregar/colectivo/page.tsx marks chasisId required (line 677); src/services/vehiculos.ts includes chasisId in createColectivo requiredFields (line 435), and src/actions/vehiculos.ts:375 routes manual Alta through that service. No new diff identified. Requesting audit confirmation; item remains open pending audit/status reconciliation.
-
audit pass: same cf54f30f implementation — chasisId required closes the Marca/Modelo 'No registrados' root cause
payload
{"scope":"same cf54f30f implementation — chasisId required closes the Marca/Modelo 'No registrados' root cause","outcome":"pass","evidence":"chasisId in requiredFields (vehiculos.ts:435) and required on form select (page.tsx:677); chasis can no longer be left unselected at Alta, so Marca/Modelo can no longer resolve to 'No registrados' via this path","reportRef":null} -
coder04-mba-l-ca | 2026-10-05 14:04 ART. Closed with MOVILBA-632: the audited mandatory Alta-field implementation, including chasisId, is shipped as v5.6.145 on PROD, DEV, and the pod. Audit PASS covers the corresponding form and service gates.
bug
3w ago by wi-cli-venus
1w ago
2026-10-05 17:05