Censo medido de donde los datos de validadora siguen llegando a un consumidor - API, exportaciones, historial y vistas
MEASUREMENT ONLY, SELECT and source reading, no writes and no code changes. Establish where validadora data still reaches a consumer, so the hide is not declared done on an unmeasured surface. Answer four questions with evidence: (1) do the four vdc columns (sube_mounting_kit, sube_id_validadora, openpass_mounting_kit, openpass_id_validadora) appear in any response of the published /api/v1/* contract - read the route handlers and the serializers, not only the docs, since docs/reference/parque-movil-api/ may lag; (2) do they appear in any XLSX or PDF a user can download today, including the vehicle ficha PDF and the parque export - MOVILBA-128 already removed them from the FISCALIZACION export on every host (76abc439), so the question is whether a SECOND export path picks them up; (3) does src/lib/rutap-history-fields.ts or src/lib/rutap-modification-subtype.ts cause a validadora field to be named in a rendered history entry or modification subtype on screen or in the PDF; (4) which views project the four columns in PROD and in DEV - expected from the 2026-09-24 census is v_vehiculos_detalle and v_vehiculos_export in PROD only, confirm or refute against information_schema in BOTH bases. Report each answer with the file and line or the query, and state explicitly what was NOT exercised. Do not change anything.
Activity
-
parent=#4105
-
coder03assistant-mba-l-ca / coder
-
coder03assistant-mba-l-ca | 2026-09-24 07:23 ART MOVILBA-583 measurement complete. Read-only source review on checkout dev@a3dcf799; no code changes. 1) /api/v1 contract: no SUBE/OpenPass validadora fields are selected or serialized by inspected v1 handlers. Vehicle detail and search both return findParqueVehiculos results directly; src/app/api/v1/parque/vehiculos/[id]/route.ts:15-20 and search/route.ts:14-17; src/services/parque-movil.ts:121-125,149-154. The runtime row contract is ParqueVehiculoRow at src/repositories/parque-movil.ts:58-80 and SQL output at :211-239; it selects ip_mdvr, identificacion_camaras_adas, ip_canbus but not the four validadora columns. The external v1 XLSX/CSV path reads the full v_vehiculos_export view but emits only VEHICULOS_EXPORT_COLUMNS (src/lib/exports/vehiculos.ts:25-73,117,200-232), which excludes the four. Exact-name search in src/app/api/v1 returned no other validadora output. 2) Other downloads: /api/export?entity=vehiculos uses fetchLatestRutapLibroRows and RUTAP_LIBRO_COLUMNS (src/app/api/export/route.ts:34-39,186-203,246-253; src/lib/exports/rutap-libro.ts:10-13; src/lib/exports/rutap-historico.ts:28-75). Its XLSX and print-PDF column set omits the four; vehiculos UI hides PDF but endpoint supports it (src/app/vehiculos/page.tsx:295). /api/reportes/vehiculos-historico builds XLSX/CSV from an explicit SELECT and RUTAP_HISTORICAL_COLUMNS, both omitting the four (src/app/api/reportes/vehiculos-historico/route.ts:22-100,182-195; src/lib/exports/rutap-historico.ts:28-75). Monthly liquidacion XLSX selects only vehicle id, line, CUIT, domain, internal, year, propulsion, and dates (src/lib/reportes/liquidacion.ts:129-145; route.ts:40-56), no validadora fields. Vehicle ficha PDF static sections omit them (src/app/vehiculos/[dominio]/page.tsx:747-1007); its history section can still emit app-period validadora changes, as in item 3. 3) History consumer: src/lib/rutap-history-fields.ts:134-152 assigns labels and columns for all four. src/repositories/rutap-historial.ts:149-155 selects h.* and :104 calls periodHistoryValues; src/lib/rutap-history-values.ts:8-34 maps nonempty values. On screen, HistoryPeriodContent renders named changes and disclosure values (src/components/HistoryPeriodContent.tsx:130-163,199-220); deriveHistoryChanges adds typed fields present on app periods (src/lib/rutap-history-presentation.ts:40-45). The ficha PDF uses the same derivation and places changes in the PDF (src/lib/vehiculo-pdf-history.ts:39-63; src/app/vehiculos/[dominio]/page.tsx:1049-1081). This is conditional on nonempty/different values. Imported source diffs are limited to the 39 RUTAP_HISTORY_FIELDS and exclude these four; screen disclosure can still show populated values, while the PDF has no generic disclosure section. rutap-modification-subtype.ts maps all four to VEHICULO_GENERAL at :88-91, but classifyModificationSubtypes has no consumer call site in src; no rendered subtype output identified. 4) View census: ran in BEGIN READ ONLY against both bases: SELECT c.table_schema,c.table_name,string_agg(c.column_name, ', ' ORDER BY c.ordinal_position) FROM information_schema.columns c JOIN information_schema.views v ON v.table_schema=c.table_schema AND v.table_name=c.table_name WHERE c.table_schema NOT IN ('information_schema','pg_catalog') AND c.column_name IN ('sube_mounting_kit','sube_id_validadora','openpass_mounting_kit','openpass_id_validadora') GROUP BY c.table_schema,c.table_name ORDER BY c.table_schema,c.table_name; DEV movilba_dev/movilba_user: public.v_vehiculos_export_vdc and rutap.v_vehiculo_historial_normalizado_fuente_actual. PROD movilba/svc_nextjs: public.v_vehiculos_detalle, public.v_vehiculos_export, public.v_vehiculos_export_vdc. Thus detail/export are PROD-only as expected, but the export-VDC view also projects all four in both bases. Not exercised: no HTTP/API calls, authenticated API response, downloadable XLSX/CSV, browser history rendering, or generated PDF; no value-level scan. Evidence is current-checkout source and information_schema column projection only.