movilba
MOVILBA-833
PPF402 Estado Actual shows stale expediente and conflicting tramite
Done high
cmcoder04-mba-l-ca
Stakeholder Pending CSV 2026-10-16 12:07 row 20 asks Estado Actual to show only the vigente expediente and tramite for PPF402. Fresh SELECT-only PROD: detail/VDC show old imported expte_alta while v_vehiculos_ciclo_actual selects latest app Alta but reports BAJA due a same-day date tie; app history has Baja then Alta on 2026-10-15. Trace current-state selection and display/PDF/API contract; make the latest business event and its expediente/tramite coherent without rewriting source history or fabricating dates. Add same-day Baja->Alta regression and verify one current state. No RUTAP import or blind data patch.
Activity
-
db04 SELECT-only design /data-lezama/movilba/evidencia/MOVILBA-832/2026-10-16-ppf402-cycle-and-tramite-design.md SHA256 4519c202f963f395f2033d68c7629b66dc1d97b97b95ecb52db4c9b569423994. Installed cycle-view digest b121ed36 same PROD/DEV; same-day self-terminal rule incorrectly picks BAJA for PPF402 despite later app ALTA. Proposed CASE app-event ordering changes 1 PROD/19 DEV current rows; imported AI357IV BAJA and AF106WZ ALTA remain controls. Rehearse/verify before DDL, no import.
-
audit fail: SQL ec7c9a1c static review + reported PROD/DEV rollback evidence66d3b26f; no independent DB execution/apply or UI.
payload
{"scope":"SQL ec7c9a1c static review + reported PROD/DEV rollback evidence66d3b26f; no independent DB execution/apply or UI.","outcome":"fail","evidence":"audit-mba-l-ca | 2026-10-16 ART. View witness assertions use scalar <> for PPF402/AI357IV/AF106WZ; missing row or NULL state gives NULL, and PLpgSQL IF does not reject it. Replace with IS DISTINCT FROM or explicit count/state validation and demonstrate fail-closed missing/NULL control. Exact view digest/unique replacement/owner-ACL/change-count guards reviewed; reported rollback1 PROD/19 DEV BAJA->ALTA with no selected-history-ID changes, not independently executed. Default rollback retained. Guard FAIL only, not a claim observed witness rows are missing.","reportRef":null} -
audit pass: Corrected view SQL3576a9f6; static guards/compatibility review plus db04 rollback evidence8e2e2049. Shared/release bytes equal. No independent DB execution, apply/import or UI verification.
payload
{"scope":"Corrected view SQL3576a9f6; static guards/compatibility review plus db04 rollback evidence8e2e2049. Shared/release bytes equal. No independent DB execution, apply/import or UI verification.","outcome":"pass","evidence":"audit-mba-l-ca | 2026-10-16 ART. NULL-safe IS DISTINCT FROM now rejects missing/NULL witnesses. Evidence reports exact PROD->DEV default ROLLBACK rc0,1/19 BAJA->ALTA with unchanged selected history IDs, imported controls and later-app-Baja controls preserved. Reported missing-domain and NULL stream mutants each rc3 at witness guard; independent postreads restored original view MD5 and PPF402 BAJA. Same-date app/app only uses creado_en,id; imported/unknown timestamp behavior retained, output columns unchanged, owner/ACL and exact view preimage pinned. Statement/lock timeouts and rollback default reviewed. Rehearsal is db04-reported, not audit-executed. Full stakeholder current-expediente display/API/PDF still requires post-release verification; not ticket closure.","reportRef":null} -
Exact audited same-day cycle SQL3576a9f6 committed and applied PROD->DEV, independent DB postreads show PPF402 current ALTA/current expediente; AI357IV/AF106WZ/later-Baja controls preserved. v5.6.254 PROD+DEV health green; pod mirror triggered but live patch pending. Detail/PDF/API visible current-expediente verification pending, do not close.
-
v5.6.254 fleet rollout complete: DEV commit 5b73c1f2 and PROD merge 8ad77a62, pod develop mirror 47b9e57; PROD, DEV and pod /api/health all status ok serviceId35709 (patch254). Exact audited 832/833 SQL was applied PROD->DEV before code. No import/restore. Behavior verification of PPF402 detail/history/PDF and authenticated Fabricantes navigation remains; health is not closure proof.
-
Authenticated UI verification currently unavailable: Chrome MovilBA tab is at DEV /user/login and no authenticated detail session is present; no agent login attempted. Fleet /api/health patch254 on PROD/DEV/pod and DB postreads are green. Keep open for real detail/history/PDF or stakeholder navigation proof; no duplicate submission or further DB write.
-
db04 read-only bounded pod DB-path evidence (recorded while pod still patch253): pod /api/health executes pool select 1; immediately after pod-route requests, movilba_dev pg_stat_activity showed new select 1 from pod-side remote clients at 12:44:27/12:44:54 ART. Supports shared movilba_dev runtime DB rather than mirrored dump, but oc env/schema inspection unavailable (Unauthorized). Evidence /data-lezama/movilba/evidencia/MOVILBA-833/2026-10-16-prod-dev-apply.md SHA256 38ddb2adff4c4b9b78646e7cfe4ba10fee2461618336fa3ad41905f52481d96f. Later fleet health confirms pod patch254; no import/restore.
-
Final one-time post-rollout db04 SELECT-only check on v5.6.254: all three health routes ok/serviceId35709; PROD movilba and DEV movilba_dev retain 833 view MD5 3684b8ae, PPF402 cycle ALTA selected PROD514237/DEV617982. 832 re-Alta317 counts1 PROD/2 DEV; Baja318+estado117 counts1 PROD/2 DEV. AI357IV BAJA and AF106WZ ALTA preserved. Pod health query correlated to movilba_dev pg_stat_activity from pod-range client, but oc config inaccessible. No import/restore/write; authenticated UI/PDF remains unverified.
-
Authenticated PROD UI checked by proxy-mba-w-ca in Elazar Pimentel session, app.movilba.com/vehiculos/PPF402, v5.6.254. Estado actual text: Alta, interno 60, VUELTA DE ROCHA line 64. Estado Actual block shows Vigencia desde 08/07/2025, expediente EX-2026-46125058- -GCABA-DGGSM, observations Alta de vehiculo. Cambio de numero de interno. Read-only, no data edit. The displayed 2025 vigencia date may not correspond to the latest 2026 Alta; keep open pending confirmation of which current period/trámite the block represents.
-
Authenticated PROD PPF402 UI observation by proxy-mba-w-ca at 13:06 ART: Estado actual Alta; current expediente EX-2026-46125058- -GCABA-DGGSM; latest history Alta 15/10/2026 follows administrative Baja registrada 15/10/2026. The Estado Actual 'Vigencia desde' 08/07/2025 is intentional original vehicle Alta semantics per deployed src/app/vehiculos/[dominio]/page.tsx lines 897-906 and 1497-1509 (MOVILBA-525), not the latest cycle start. PDF/current-expediente cross-check still pending; no app-data edit. Do not infer Eduardo/Eugenia access from Elazar session.
-
Completed on v5.6.254. Audited same-day cycle SQL 3576a9f6 applied PROD then DEV; current PPF402 cycle ALTA and current expediente EX-2026-46125058- -GCABA-DGGSM. Authenticated PROD detail and 2-page PDF checked read-only by proxy-mba-w-ca at 13:06-13:07 ART (hub tag proxy-mba-w-ca-mvb5v7v5rimt): both show current Alta, same expediente and observations; history shows Baja then later Alta on 15/10/2026. 'Vigencia desde' 08/07/2025 is original vehicle Alta by MOVILBA-525 contract, not current cycle start. DB negative controls AI357IV BAJA and AF106WZ ALTA preserved. No app-data edit or import. MOVILBA-834 remains separate.
-
Follow-up authenticated PROD PDF check by proxy-mba-w-ca, Elazar session, v5.6.254, read-only: Exportar PDF on PPF402 confirms Estado actual Alta; current expediente EX-2026-46125058 appears on latest Alta 2026-10-15, consistent with page/history. Vigencia desde 2025-07-08 is intentional original vehicle Alta semantics per deployed page.tsx (MOVILBA-525), not current cycle start. No data edits. This resolves the suspected date mismatch in prior progress.
-
Correction to prior progress: proxy-mba-w-ca retracts the stale-date characterization. Per deployed MOVILBA-525, Vigencia desde 08/07/2025 intentionally means the original canonical vehicle Alta; current-cycle expediente is independently sourced and matches latest Alta EX-2026-46125058 on 15/10/2026. PDF confirms Alta and Baja→Alta sequence, plus prior imported Alta vigente hasta 15/10/2026. No retest needed. Presentation difference noted for future review: PDF Baja row says Baja registrada but omits separate Trámite: Modificacion label visible in UI. No edits.
-
Correction to 16:06:48Z proxy-observation note: the 08/07/2025 'Vigencia desde' is NOT stale or a regression. Completed MOVILBA-525 explicitly defines it as the first canonical vehicle Alta; current-cycle expediente is independently sourced. Proxy-mba-w-ca retracted stale-date characterization (hub tag proxy-mba-w-ca-mvb5vymzuf34) after authenticated PROD detail and PDF check. Both surfaces show current PPF402 Alta and EX-2026-46125058- -GCABA-DGGSM, with 15/10/2026 Baja then re-Alta. PDF presents the prior event as 'Baja registrada' without the detail page's separate 'Trámite: Modificacion' label; this is a presentation difference, not a proven wrong current state. Item completion remains valid; no retest or data edit.
bug
9h ago by coder03-mba-l-ca
8h ago
2026-10-16 16:07