Import final parity gate compares retired VDC dates after MOVILBA-242

Sub-tickets

Activity

• db04-mba-l-ca created · 1w ago
  parent=#3979
• db04-mba-l-ca progress · 1w ago
  2026-10-06 diagnosis: MOVILBA-242 applied 10-01 removed fecha_vigencia_desde/hasta from installed reconciler writes and projects both through v_vehiculos_export_vdc from v_vehiculos_hist_ultimo. The 518 importer gate at tools/rutap-snapshot-import.py:1298 still compared stored legacy VDC dates and produced 18 false differences after correct 1140-book reconciliation (estado_id matched on all 18). Patched PROD final gate to compare d.estado_id + e.fecha_vigencia_desde/hasta from published v_vehiculos_export_vdc, LEFT JOIN and e.id IS NULL fail-closed. Patched DEV preserve-tests branch to stop writing legacy dates and compare published fecha_vigencia_hasta. PROD read-only: 2419 active VDC rows, 2419 matching export-view rows. ROLLBACK mutant on VDC id5564/AH992CY: UPDATE 1 legacy date only, old gate 1 diff, new gate 0, ROLLBACK and independent read original date unchanged. Forced-missing-view SELECT makes new gate 1 diff. git diff --check clean. No repo tests run before audit; no import applied.
• audit-mba-l-cc audited · 1w ago
  audit pass: tools/rutap-snapshot-import.py diff reviewed in full: final paridad gate + dev-preserve reconcile query, both switched from stored VDC dates to v_vehiculos_export_vdc canonical dates
  payload

  {"scope":"tools/rutap-snapshot-import.py diff reviewed in full: final paridad gate + dev-preserve reconcile query, both switched from stored VDC dates to v_vehiculos_export_vdc canonical dates","outcome":"pass","evidence":"Confirmed MOVILBA-242 migration stopped writes to d.fecha_vigencia_*; view exists (2459 rows DEV) with the needed columns. ROLLBACK rehearsal on PROD VDC id=5564: corrupting stored fecha_vigencia_hasta flags old gate (d vs e distinct, 1) but new gate's date terms read e/reconcile-source only, architecturally blind to the corrupted stored column. Fail-closed e.id IS NULL OR... confirmed in diff text. PROD currently 0 stale-vs-canonical mismatches (consistent with the aborted import having rolled back cleanly, no data corruption).","reportRef":null}

• db04-mba-l-ca progress · 1w ago
  Audit PASS event 2026-10-06T19:57:51.657Z on complete one-file importer diff. Sent exact-path SHIP to coder03 (hub tag db04-mba-l-ca-mux3pn7vryon), then released tools/rutap-snapshot-import.py lock. PROD snapshot-9 --apply remains rolled back with prior code; retry only after this diff is deployed. No data change by this item.
• db04-mba-l-ca progress · 1w ago
  2026-10-06 post-import verification: patch v5.6.179 committed (7f4c6c1a) and PROD health serviceId 25434=179. PROD snapshot 11 and DEV snapshot 21 both point to 1140 book md5 eb2e2683..., 5558 raw and normalized rows. DEV and pod /api/health still serviceId 25297=178 while /srv/dev-movilba-web/package.json says 179; awaiting DEV service and pod rollout to 179 before close (Elazar DoD). coder03 notified hub tag db04-mba-l-ca-mux3wxm2x7pm.
• db04-mba-l-ca completed · 1w ago
  2026-10-06 DoD verified: audited one-file importer parity correction committed as 7f4c6c1a v5.6.179; PROD app.movilba.com health 25434, local DEV dev01 health 25434 per coder03, public DEV redirect and direct OpenShift pod independently returned 25434 after successful oc rollout status. The transient 178/179 mixed-replica interval resolved; coder03 also measured 6/6 cache-busted pod samples at 179. db03 then committed 2026-10-06-1140 workbook PROD snapshot 11 and DEV snapshot 21 with final parity 0 diffs, 5558/5558 normalized rows, and DEV preservation green. No pending MOVILBA-723 action.