Al crear un vehiculo el historial muestra Estado ALTA con la fecha de creacion en vez de la fecha del tramite

Sub-tickets

Activity

• wi-cli-venus created · 3w ago
• coder03-mba-l-cc assigned · 3w ago
  coder03assistant-mba-l-ca / coder
• coder03assistant-mba-l-ca progress · 3w ago
  coder03assistant-mba-l-ca | 2026-09-24 07:47 ART — Checked the MOVILBA-555 ship 03155317 and create writer: 555 changes form/service state only; it does not alter fecha_alta. Current createColectivo writes history.fecha_alta from submitted fechaExpediente, falling back to CURRENT_DATE when the optional form date is blank (page.tsx:464-474; repositories/vehiculos.ts:1027). That no-date fallback is separately tracked under blocked MOVILBA-349, awaiting its missing-date rule; do not change it here. LB500EG has fecha_alta equal to its 2026-09-22 expediente/creation date, and QA624XZ was created with fechaExpediente 2026-09-24 on 2026-09-24, so neither is discriminating. No real create with a different trámite date or fresh history PDF exercised yet; item remains unverified/open.
• coder03assistant-mba-l-ca blocked · 3w ago
  coder03assistant-mba-l-ca | 2026-09-24 08:17 ART — Proxy reports dev01 login expired; requested UI create with fechaExpediente 2026-09-23 was not performed. Need the authenticated dev01 session restored to exercise the create flow and read the resulting fecha de Alta.
• coder03assistant-mba-l-ca progress · 3w ago
  coder03assistant-mba-l-ca | 2026-09-24 08:11 ART — Proxy confirmed QA625XZ was not created: the dev01 create URL redirected to /user/login because Whey Chrome is logged out. No test record or database write occurred. The requested discriminator remains fechaExpediente 2026-09-23 entered on 2026-09-24; resume the UI create/readback after Elazar logs in.
• coder03assistant-mba-l-ca assigned · 2w ago
  audit-mba-l-cc / auditor
• coder03assistant-mba-l-ca progress · 2w ago
  coder03assistant-mba-l-ca | 2026-09-28 11:50 ART — Source check at shared checkout HEAD d8ccd634: src/services/vehiculos.ts:522 passes the entered fechaExpediente into create data; src/repositories/vehiculos.ts:1022 writes initial historial.fechaAlta from vehiculoData.fechaExpediente, falling back to CURRENT_DATE only when absent. This is consistent with trámite-date persistence for an entered date; it does not support a generic creation-timestamp claim. Existing DEV measurements recorded 2026-09-24 show LB500EG fecha_alta, fecha_expediente, and creation date all 2026-09-22, so that row cannot discriminate the source. No fresh UI/DB read or different-date create was performed. Leave blocked/open pending a test with fechaExpediente != creation day and current DB readback; no change to fallback scope (MOVILBA-349).
• audit-mba-l-cc unblocked · 2w ago
  audit-mba-l-cc 2026-09-28, HEAD d8ccd634. Code verified independently: src/services/vehiculos.ts:522 passes formData.fechaExpediente through unmodified (undefined only if blank); src/repositories/vehiculos.ts:1022 writes fechaAlta = vehiculoData.fechaExpediente || CURRENT_DATE - creation timestamp is NEVER the source when a date is entered. Discriminating DEV evidence found without a UI create (movilba_dev, read-only BEGIN READ ONLY/ROLLBACK, query: rutap.vehiculo_historial_normalizado WHERE origen='app' AND tramite_id=ALTA AND fecha_alta IS DISTINCT FROM creado_en::date): 2 rows exist - LP555EP (id 286424, fecha_alta 2026-09-07, creado_en 2026-09-22) and TT333AA (id 286416, fecha_alta 2026-02-10, creado_en 2026-09-21). Both prove fecha_alta persists the entered tramite date, independent of and differing from creation day. LB500EG (id 286439) has fecha_alta=creado_dia=expte date 2026-09-22, all three coincide, so it cannot discriminate and never could - not evidence of the reported bug, just an unlucky same-day report. Verdict: current code and current DEV data do not support the creation-timestamp claim; the fallback-to-CURRENT_DATE path (blank fechaExpediente) is the only place creation day and fecha_alta can coincide by construction, tracked separately under MOVILBA-349, not touched here. No UI/PDF exercised, no writes. Unblocking - the dev01-login blocker is moot, this was answerable from existing data.
• coder03assistant-mba-l-ca completed · 2w ago
  coder03assistant-mba-l-ca | 2026-09-28 12:08 ART — Closed as not reproducible against current createColectivo code and current DEV data. Audit-mba-l-cc verified src/services/vehiculos.ts:522 and src/repositories/vehiculos.ts:1022: an entered fechaExpediente supplies fecha_alta; CURRENT_DATE is used only if blank. Read-only DEV rows discriminate: LP555EP fecha_alta 2026-09-07 / creado_en 2026-09-22; TT333AA fecha_alta 2026-02-10 / creado_en 2026-09-21. Reported LB500EG has all three dates 2026-09-22 and cannot distinguish. No UI/PDF exercised. If a distinct create path is identified, reopen; blank-date fallback remains MOVILBA-349.
• coder03assistant-mba-l-ca progress · 2w ago
  coder03assistant-mba-l-ca | 2026-09-28 12:10 ART — After the measured close, archived the full investigation from Para Elazar row 19 to Resueltos #85 with the original report, non-reproduction result, DEV discriminators, code paths, and UI/PDF limitation. Tracker snapshot 26 imported; diff 25→26 shows one MOVILBA-544 row removed and one Resueltos #85 row added, no other content changes.