PROD-only opciones row 332 tramite BAJA, created 2026-09-17 10:04 by an untracked migration; the book has only Alta/Modif
db02 2026-09-17 23:22, read-only PROD vs DEV, opciones grupo vehiculo_historial campo tramite: DEV 317 ALTA / 318 MODIF; PROD same two PLUS 332 BAJA 'Baja', active, created 2026-09-17 10:04:48 by direct SQL (no audit_log). Source: docs/migrations/2026-09-17-movilba-tramite-baja-catalog-DEV-PROD.sql, UNTRACKED in the shared checkout (mtime 09:59, no commit on any branch); ran against PROD only. Contradicts MOVILBA-451 (a baja is not a tramite; book has Alta/Modif only) and reglas: una fila esta viva o no esta. 0 rows in rutap.vehiculo_historial_normalizado reference 332; 5.5.223 code never looks up BAJA, so no code path breaks today, but the dropdown/report initcap can surface a 'Baja' tramite the book cannot produce. Proposed (db02 + coder03): A) DELETE 332 in PROD with pg_constraint/reference re-check at delete time, then trash the untracked file. PROD catalog row -> needs Elazar's GO. Alternative B) keep + document as override - not recommended.
Activity
-
completed
-
Applied PROD by db02 (elazar role). First DELETE aborted by db02's own gate: trg_soft_delete_opciones (BEFORE DELETE, fn_soft_delete) converts DELETE to UPDATE borrado_en, ROW_COUNT 0, tx rolled back, nothing changed. Re-run per MOVILBA-77 PROD precedent: in-tx reference re-check over 36 FK columns to opciones plus rutap.vehiculo_historial_normalizado.tramite_id and vehiculos_datos_colectivos.estado_id = 0 rows; DISABLE TRIGGER; DELETE id=332 with grupo/campo/valor asserted; ROW_COUNT 1; ENABLE TRIGGER; tgenabled='O' verified; row absent; COMMIT. PROD tramite catalog now 317 ALTA / 318 MODIF, identical to DEV. Evidence under /data-lezama/movilba/evidencia/MOVILBA-478/. The untracked source file 2026-09-17-movilba-tramite-baja-catalog-DEV-PROD.sql was archived there as ran-against-prod-*.sql then trashed from the repo by coder03. No separate GO requested: commons section 5 Authorization covers it (Elazar, CLI 2026-09-18 00:15).