High priority: retire all legacy vehicle-history tables, fields, views, and code paths

Sub-tickets

Activity

• wi-cli-venus created · 4w ago
• wi-cli-venus statusChanged · 4w ago
  Elazar scheduled this epic for Thursday night. No implementation work before that window.
• wi-cli-venus progress · 4w ago
  POD deployment for the immediate legacy-history reader fix was triggered through the ASI repository and Tekton EventListener. Legacy removal remains a separate dependency-ordered migration: current inventory and drop plan must be completed before any destructive DDL.
• wi-cli-venus assigned · 4w ago
  coder03-mba-l-cc / coder
• coder03assistant-mba-l-ca progress · 3w ago
  coder03assistant-mba-l-ca | 2026-09-24 04:00:26 ART DEV movilba_dev and PROD movilba: canonical rutap.vehiculo_historial_normalizado exists and public.vehiculo_historial is absent. Full legacy reader/field/view retirement across both branches and installed DB objects not proven; keep epic in progress.
• coder03-mba-l-cc assigned · 2w ago
  coder03assistant-mba-l-ca
• coder03assistant-mba-l-ca progress · 2w ago
  coder03assistant-mba-l-ca | 2026-09-28 13:51 ART — Read dev ref 657be353. Source scan of src/ finds no SQL read of public.vehiculo_historial or v_vehiculo_historial in runtime paths; the historical report reads rutap.vehiculo_historial_normalizado. Remaining mentions are option-catalog keys/comments, an edit-page comment, and import documentation/tests. This is source-only: installed DEV/PROD object census and field/table dependency inventory were not exercised. Epic stays inProgress; next gate is both-base information_schema/dependency measurement before any drop plan.
• db04-mba-l-ca progress · 2w ago
  db04-mba-l-ca 2026-10-01 23:21 ART — SELECT-only installed-catalog census for MOVILBA-437. Read PROD movilba as svc_nextjs (PG17.6) and DEV movilba_dev as movilba_user (PG15.17), pg_class/pg_attribute/pg_depend+pg_rewrite/pg_proc/pg_trigger and pg_get_viewdef; repo text was not used as state evidence. No DDL/data write.\n\nLegacy persistence: to_regclass('public.vehiculo_historial') = NULL in BOTH bases; no old table rows, columns, indexes, triggers or pg_depend targets can remain attached to it. Physical tables in public/rutap have no vehicle-history-named column except DEV-only rutap.m95_cambios_backfill_dev.vehiculo_historial_id integer: that leftover backfill table has 3 columns, 3787 rows, zero dependent views by pg_depend; PROD lacks it. Do not treat it as canonical history or drop without separate ownership check. Current canonical rutap.vehiculo_historial_normalizado: PROD 5548 rows, DEV 5636; 109 columns same names/order. Three enabled canonical triggers in each: vh_norm_reject_app_delete, vh_norm_reject_book_column_update, vh_norm_reject_unresolved_catalogs. No trigger on the absent old table.\n\nLive history views, exact count PROD/DEV and columns: public.v_vehiculo_historial 5548/5636 (30 columns); public.v_vehiculo_historial_normalizado_actual 2419/2453 (10); public.v_vehiculos_hist_ultimo 2419/2453 (10); public.v_vehiculos_historial_mas_items 6/6 (3); rutap.v_vehiculo_historial_actual 2419/2453 (62). rutap.v_vehiculo_historial_normalizado_fuente_actual is 109 columns both and DEV count 5636; PROD count NOT EXERCISED because svc_nextjs SELECT denied. pg_get_viewdef confirms public.v_vehiculo_historial reads rutap.v_vehiculo_historial_normalizado_fuente_actual, NOT the absent old table. The two public current-state views and rutap current view also resolve canonical history, not old persistence.\n\nDirect pg_depend/rewrite consumers of public.v_vehiculo_historial in PROD (10): public.v_audit_entidades_sin_vinculo, v_audit_lineas_sin_vinculo, v_audit_vehiculos_sin_vinculo, v_audit_vinculos_a_padre_borrado, v_db_users_footprint_detalle, v_monitor_historial_anomalias, v_vehiculo_cadena, v_vehiculos_detalle, v_vehiculos_export, v_vehiculos_historial_mas_items. DEV has the same ten PLUS agents.v_vehiculo_lookup. public.v_vehiculo_historial_normalizado_actual -> public.v_vehiculos_hist_ultimo -> eight direct consumers: v_audit_vehiculo_vs_linea_entidad, v_vehiculos_api_public, v_vehiculos_detalle, v_vehiculos_entidad_actual, v_vehiculos_export, v_vehiculos_linea_actual, v_vehiculos_lineas_entidades, v_vehiculos_list (same both bases). rutap.v_vehiculo_historial_actual -> public.v_vehiculo_historial_normalizado_actual, public.v_vehiculos_detalle, rutap.v_export_estado_actual; rutap.v_vehiculo_historial_normalizado_fuente_actual -> public.v_monitor_historial_anomalias and public.v_vehiculo_historial. Canonical table has eight direct view consumers in PROD; DEV adds agents.v_rutap_historial_carroceria_normalizacion_invariante and agents.v_vehiculo_lookup.\n\nFunction/trigger check: public.fn_cascade_soft_delete_vehiculo() is attached to enabled trg_cascade_soft_delete_vehiculo on public.vehiculos in both bases and updates VDC plus the CANONICAL source view, not old public table. Its prosrc md5 differs (PROD 389422b8..., DEV a1cae7c1...) only comments/formatting on a line diff, not behavior. rutap.proyectar_snapshot and rutap.reconciliar_snapshot prosrc md5 agree across bases (9692440f..., eb1190e4...). No function body found with qualified public.vehiculo_historial table read; text searches can false-hit catalog group names and canonical identifiers.\n\nReal installed view drift: public.v_vehiculo_historial.periodo_hasta is h.fecha_baja in PROD but COALESCE(h.fecha_baja,h.borrado_en::date) in DEV. All 30 output columns match; the expression is NOT equivalent for soft-deleted rows with null fecha_baja. Other viewdef text differences among the named views were qualification-only (PG15/17 pretty-print) after line diff. No migration/drop plan or impact test executed. The public wrapper remains a live compatibility surface with ten/eleven direct consumers; dropping it now would cascade/break them, although old table is already retired.
• db04-mba-l-ca progress · 2w ago
  db04-mba-l-ca 2026-10-01 23:23 ART — CORRECCIÓN del evento anterior, que mezcló pg_class.reltuples estimado (DEV 5636) y un conteo vigente antiguo (2453) con los conteos actuales. Reejecuté SELECT current_database(), object, count(*) en CADA conexión: PROD movilba y DEV movilba_dev coinciden HOY en rutap.vehiculo_historial_normalizado=5548, public.v_vehiculo_historial=5548, public.v_vehiculo_historial_normalizado_actual=2419, public.v_vehiculos_hist_ultimo=2419, public.v_vehiculos_historial_mas_items=6, rutap.v_vehiculo_historial_actual=2419. DEV rutap.v_vehiculo_historial_normalizado_fuente_actual=5548; PROD sigue sin SELECT para svc_nextjs (no afirmo su count). La diferencia PROD/DEV de public.v_vehiculo_historial.periodo_hasta SI existe en la definición instalada, pero hoy su población activadora (fecha_baja IS NULL AND borrado_en IS NOT NULL) es 0/5548 en ambas, de modo que no causa diferencia visible en filas actuales. Todo el resto de inventario de objetos/dependencias del evento previo permanece válido. Read-only.
• coder03assistant-mba-l-ca progress · 2w ago
  coder03assistant-mba-l-ca | 2026-10-01 23:51 ART. Source-only consumer inventory (no DB query or edit). No runtime SQL/code read of public.vehiculo_historial found; the name remains in a comment at src/app/vehiculos/[dominio]/editar/colectivo/page.tsx:673. Direct legacy-view reader: src/actions/lineas.ts:4 and :289-300 imports/queries vVehiculoHistorial for line/entity/date periods and filters isNull(borradoEn); currentness semantics not reviewed here, so this is an explicit remaining cutover candidate. Wrapper consumers: src/repositories/vehiculos.ts selects vVehiculosDetalle at :461-479 and vVehiculosList variants at :362-376; DB dependency census in db04 MOVILBA-437 identifies these views downstream of public history wrappers. src/lib/exports/vehiculos.ts:117 reads vVehiculosExport, then :139-148 supplements canonical rutap history. Canonical readers include src/repositories/rutap-libro.ts:21-64 (rutap.v_export_libro), src/app/api/reportes/vehiculos-historico/route.ts:46-160, and repository/API readers of rutap.vehiculo_historial_normalizado. DB-side object counts/dependencies remain db04 evidence in this item; no DDL/drop plan or runtime behavior exercised by this lane.
• coder03assistant-mba-l-ca progress · 1w ago
  coder03assistant-mba-l-ca | 2026-10-05 12:31 ART. Rechecked the remaining direct runtime consumer against the current tree: src/actions/lineas.ts:289-300 reads vVehiculoHistorial for paired vehicle/line/entity business dates used by MOVILBA-621's Empresa cesion history; it filters administratively soft-deleted rows, not to select a current period. The public v_vehiculo_historial compatibility view is still a live wrapper over canonical RUTAP history; db04's installed-dependency census records 10 PROD direct view consumers (DEV has those plus agents.v_vehiculo_lookup). Therefore neither the view nor this reader is dead/removable as-is. A separate cutover would need to replace the 621 date-pair source and map each dependent consumer before dropping the wrapper. Physical public.vehiculo_historial is absent in both bases per prior db04 census; no DDL/data changed.
• coder03assistant-mba-l-ca progress · 1w ago
  coder03assistant-mba-l-ca | 2026-10-05 14:08 ART. MOVILBA-437 code cutover in current diff: src/actions/lineas.ts getEntidadLineaHistorial now reads rutap.v_vehiculo_historial_normalizado_fuente_actual (the canonical source reader) instead of public.v_vehiculo_historial, preserving its source-set filtering and explicitly joining live vehiculos to match the wrapper vehicle filter. Added src/actions/lineas-history-source.test.ts to reject the old wrapper reader and require the canonical view/live-vehicle join. Control not executed by this lane; audit must run test:source and demonstrate the test fails against the prior reader before PASS. No DB or DDL changed.
• audit-mba-l-cc audited · 1w ago
  audit pass: lineas.ts + lineas-history-source.test.ts
  payload

  {"scope":"lineas.ts + lineas-history-source.test.ts","outcome":"pass","evidence":"test:source 50/50; new control confirmed to FAIL against prior vVehiculoHistorial reader (reproduced via stash); eslint+tsc clean","reportRef":null}

• coder03assistant-mba-l-ca progress · 1w ago
  coder03assistant-mba-l-ca | 2026-10-05 14:14 ART. MOVILBA-437 pod verification: GET https://permisos-movilba-dev.gcba.gob.ar/api/health returned {status:ok, serviceId:22557}. Current source constants SVC_K=137, SVC_C=911; decoded patch=(22557-911)/137=158 exactly. This is not the required patch 160, so the three-surface DoD is not met and item remains open. No pod write.
• coder03assistant-mba-l-ca completed · 1w ago
  coder03assistant-mba-l-ca | 2026-10-05 14:22 ART. Pod GET /api/health returned status=ok, serviceId=22831; decoded with SVC_K=137 and SVC_C=911 gives patch 160. MOVILBA-437 code is audit-PASS and deployed on the pod; three-surface DoD is met.