movilba
MOVILBA-516
Import delete-by-absence only reaches origen_ingreso='ssot_import'; must be origin-agnostic
Done normal
cmcoder03-mba-l-ca
Today app_* rows survive and NULL/legacy_unknown rows ABORT the import (PROD has 2407 legacy_unknown). Required: absent from book => physically deleted, whatever the origin. Elazar rule 2026-09-19: a new SSOT snapshot makes DEV and PROD equal to it (update/add/delete), no reconciliation, no who-wins evaluation; only documented Eugenia-agreed overrides (docs/reference/ssot-overrides.md). Measured by coder03-ca, db02-ca, audit-ca on the installed import (bodies identical in DEV and PROD, 486).
Activity
-
Started after MOVILBA-514 DEV ship; deriving origin-agnostic delete-by-absence correction from installed 486 importer and live DEV/PROD dependency inventory.
-
Decision still required: Elazar's SSOT-equals-current-state rule settles deletion of absent parent vehicles regardless of origin, but does not specify treatment of 64 app-history and 11 validator-history dependent rows. Record an explicit A/B child-row policy before destructive application; do not infer it from the parent-state rule.
-
A/B child-history semantics have already been escalated to Elazar via coder03-mba-l-ca. Audit cannot authorize the design choice. Await Elazar's explicit decision for the 64 app-history and 11 validator-history dependent rows; do not infer it from the parent SSOT-equality rule.
-
Option B formulations conflict and must be reconciled before asking Elazar: audit-ca proposed retaining absent parents as non-current tombstone/support records, while coder03-ca proposed archiving/detaching 64+11 child payloads and deleting live children plus parents. Await one agreed A/B pair; no destructive SQL or product-decision request should rely on an ambiguous option.
-
Exact reconciled decision required from Elazar. Mandatory in both choices: live public.vehiculos physically equals Excel SSOT; absent parents are hard-deleted, with no tombstones or rehoming. A discard: transactionally delete 64 rutap.vehiculo_historial_normalizado plus 11 public.validadoras_historial live child rows, then dependent VDC and absent vehicles. B preserve evidence: add detached archive storage with no FK/UI/view/export participation, copy exact 75 payloads with scalar original IDs/domain/provenance, verify counts/checksums, delete live children, then dependent VDC and absent vehicles. B adds archive DDL/migration. Await explicit A or B before destructive SQL.
-
Option-neutral implementation analysis: origin filter is isolated in rutap_reconcile_borrar and can be removed while retaining raw-domain/projection and duplicate-survivor gates. Legacy/NULL origin complement abort must be removed consistently and replaced by per-origin candidate reporting. Physical parent equality requires handling 64 non-import vehiculo_historial_normalizado rows (guarded by vh_norm_reject_app_delete) and 11 validadoras_historial rows. Further schema inspection shows validator-history may have dependent validadoras_historial_ubicaciones rows plus append-only DELETE guards, so A/B decision must cover the complete validator history graph, not only the 11 direct rows. No destructive branch authored or applied pending Elazar's A(discard) / B(detached archive) choice.
-
db03 read-only DEV graph inventory completed: 11 direct validadoras_historial rows have 0 ubicaciones, but self-FK historial_anterior chains cross candidate/non-candidate boundary (3 retained rows reference candidate rows; 2 candidate rows reference retained rows; 3 candidate-to-candidate links). Enabled append-only DELETE trigger rejects deletion. Thus option A cannot delete only 11 rows: it must intentionally discard or rewrite a larger interleaved audit chain. Option B, a detached lossless archive of the complete connected graph with original scalar IDs/provenance before live deletion, is the technically safe recommendation. No DDL/DML performed; awaiting Elazar A/B choice.
-
DEV inventory refinement: the 11 candidate validadoras_historial rows have zero ubicaciones, but self-FK chains cross candidate/non-candidate boundaries (3 retained rows point to candidate rows; 2 candidate rows point to retained rows), and append-only DELETE triggers are enabled. Option A therefore requires deliberate discard/rewrite of a larger interleaved audit chain, not merely deleting 11 rows. Technical recommendation is B: archive the complete connected history graph losslessly with provenance, then delete live children/parents. No DDL/DML pending Elazar choice.
-
Option-B preparation advanced without writes. Repository archive convention identified: archive_id/archived_at/archived_by/archive_reason plus original payload; migration verification convention is stable ordered row_to_json aggregation with count+md5, plus pinned trigger definitions/states and pre/post hashes. For 516 the preservation tables must deliberately have no live FKs. Cross-boundary validator self-FKs expand the complete connected component from 11 candidate-linked rows to 14 rows (11+3 bridge/retained), so B must preserve the full component before any live removal. Requested db03 read-only rehearsal counts/ordered hashes for that component and the 64 non-import normalized-history rows. No DDL/DML.
-
Option-B DEV rehearsal baseline completed read-only by db03. Recursive undirected validator-history component is 15 rows across 6 validators (IDs 94,100,101,102,104,105,106,120,123,126,127,128,129,130,131), ordered full-row md5=6f836e81594a62ef0e89922aec201dd6, with 0 ubicaciones. This corrects the prior direct-edge estimate of 14: successor id 106 is also connected. Non-import normalized history is 64 app rows across 24 candidate vehicles, ordered full-row md5=0d27d4043e032251f83dd50ca767c7e0; control finds 0 import rows on candidates. No writes. B remains recommended; awaiting Elazar A/B.
-
Corrected option-B DEV baseline from complete recursive undirected traversal: archive scope is 15 validadoras_historial rows across 6 validators (IDs 94,100,101,102,104,105,106,120,123,126,127,128,129,130,131), ordered full-row MD5 6f836e81594a62ef0e89922aec201dd6, 0 ubicaciones. Prior 14-row result missed successor 106. Also 64 rutap.vehiculo_historial_normalizado rows across 24 vehicles, MD5 0d27d4043e032251f83dd50ca767c7e0, with 0 import rows on candidates. Option B therefore preserves 79 total rows; no writes; awaiting explicit A/B.
-
Option C identified; hold A/B decision request pending audit/product-invariant review. Because vehiculo_id is nullable in both history tables, preserve an exact preimage archive, detach the affected live history rows by setting vehiculo_id=NULL while retaining dominio and self-FK chains, then hard-delete absent parent vehicles. For validadoras_historial this may require narrowly controlled temporary disabling of the pinned append-only UPDATE trigger with re-enable/assert gates. Open questions: detach only the 11 directly linked validator rows or the full 15-row connected component; and whether the settled invariant requires removal of live history rows or only physical public.vehiculos=SSOT. No writes.
-
Option C (archive preimage then null vehiculo_id in live histories) was considered and REJECTED by audit. Although technically feasible, it violates Elazar's clean-operational-history intent: 64 normalized app rows and 11 validator rows would remain legacy data in operational history, risk surfacing in current/future readers, and require mutating append-only evidence. Final product choice remains A intentional discard/rewrite/removal, or B lossless detached archive of the full 15-row validator connected component plus 64 normalized app rows, then removal from live history and parent deletion. No DDL/DML pending Elazar A/B.
-
Option C considered and rejected by audit: nullable-FK detachment is technically feasible but violates the settled clean operational-history invariant, leaves legacy rows discoverable in live tables, and mutates append-only evidence. Final product decision remains A discard/rewrite/remove versus B detached lossless archive of the full 15-row validator component plus 64 app-history rows (79 total), verify, then remove live history and absent parents. No writes pending Elazar's A/B choice.
-
Elazar decision relayed by audit-mba-l-ca tag audit-mba-l-ca-mu8grywytarh-coder02-mba-l-ca and audit-mba-l-cc tag audit-mba-l-cc-mu8gs7117rs7-coder02-mba-l-ca: OPTION A. Old history is unwanted; permanently delete it. Do not archive and do not reopen A/B. Implementation must remove 64 rutap.vehiculo_historial_normalizado rows plus 11 directly vehicle-linked validadoras_historial rows, correctly handle the full 15-row connected validator self-FK chain using controlled append-only-trigger handling, then delete vehicles absent from the authoritative Excel. Audit correction: this follows the prior clean-import intent and should not have blocked work.
-
Elazar selected Option A: permanently delete old history, no archive. Coder03 may implement chain/trigger-safe deletion and DEV-rehearse; destructive PROD execution remains separately gated.
-
coder03-mba-l-ca started Option A implementation: origin-agnostic candidates, permanent normalized-history cleanup, full validator self-FK component handling, controlled append-only trigger restoration, and DEV-only rehearsal/audit. Required audit evidence: artifact/SQL, before-after counts, 15-row chain handling proof, trigger disable/re-enable assertions, and transaction rollback evidence. PROD destructive execution remains separately gated.
-
Elazar selected Option A on 2026-09-19: permanently delete old operational history, no archive, and do not reopen A/B. Implementation covers all origin-agnostic absent vehicles, 64 normalized app-history rows, 11 direct validator-history rows expanded to the full 15-row self-FK component, controlled trigger disable/restore, and DEV rehearsal before any separately gated PROD action.
-
Option A draft is with audit-mba-l-ca. DEV-only rehearsal requested from db03-mba-l-cc inside an outer transaction with forced ROLLBACK, exact before/inside/after counts, coverage of all 15 validator IDs, and trigger restoration proof. No persistent DEV change and no PROD action.
-
Authored origin-agnostic Option A migration in coder03 worktree and sent it to audit-mba-l-ca. It builds the full validator self-FK component recursively, deletes leaves first under RESTRICT, permanently deletes normalized history, pins the installed 486 prosrc plus protective trigger/FK shapes, and restores all four triggers. DEV write/rehearsal is held until audit PASS; db03 supplied exact rollback baselines and identified db02-ca as rehearsal owner. PROD remains separately gated.
-
Revised origin-agnostic permanent-delete migration frozen for direct audit at sha256 97fc51d7d64d6c2cc5247e8d2184249bab0e23f085bfdbbcb4c71fe6543d98a2. Covers 32 candidate parents/VDC, normalized and connected validator history, 97+93 existing archive rows, and 238 structured audit_log rows; pins all six temporarily-disabled triggers by relation/name/function/event/enabled state and asserts zero survivors. No DEV apply pending audit PASS.
-
Audit rollback rehearsal caught a pre-install guard typo only; no DB/function changes persisted. Corrected installed-function MD5 literal and froze replacement artifact sha256 f8f38d8dcc2116806cf0c7838e4343a8bcb0954e9c39f8c765a9643d51bf9d53. Audit is rerunning rolled-back DEV install + snapshot 16 rehearsal; persistent apply remains unauthorized.
-
DEV forced-ROLLBACK rehearsal is prepared but not yet complete. db02 is awaiting explicit DEV-only PM GO for the Option A write/rehearsal; reported artifact SHA begins f8f38d8dcc21. No PROD action requested. Await full artifact hash and rehearsal evidence after GO.
-
Explicit Elazar GO requested for DEV-only forced-ROLLBACK rehearsal of frozen artifact /home/rob/Documents/work/gcaba/movilba-web-worktrees/coder03-mba-l-ca/movilba-516-origin-agnostic-delete/docs/migrations/2026-09-19-movilba-516-reconciliar-snapshot-origen-agnostico-DEV-Y-PROD.sql SHA256 f8f38d8dcc2116806cf0c7838e4343a8bcb0954e9c39f8c765a9643d51bf9d53. Scope: one movilba_dev session/outer transaction, dry-run+apply, evidence capture, explicit ROLLBACK, fresh read-only restoration proof. Hard gates cover 32 vehicles/VDC, 64 normalized history rows and MD5, 11-seed/15-component validator graph and MD5, archives/audit baselines, reconciler functions, and all six triggers enabled before/inside/after. No COMMIT, persistent DEV mutation, PROD connection, or PROD action.
-
Authorization request is held pending the frozen DEV rehearsal wrapper path/SHA and final expected assertion packet. The migration artifact remains pinned at SHA256 f8f38d8dcc2116806cf0c7838e4343a8bcb0954e9c39f8c765a9643d51bf9d53, but execution must not begin from that alone. No COMMIT, persistent DEV mutation, or PROD action.
-
DEV forced-ROLLBACK packet frozen by db02. Runner /data-lezama/movilba/migration-evidence/2026-09-19-run-movilba-516-dev-forced-rollback.sh sha256=e4d9930f58213d96000ced80313669a8939365666b23f12788f0eba622e4f916; wrapper /data-lezama/movilba/migration-evidence/2026-09-19-movilba-516-dev-forced-rollback-wrapper.sql sha256=36c4c2a2b6d3d488a4d82fe588dcd8c6d73c35798db1c7bd162e28027003bce1; fresh postcheck /data-lezama/movilba/migration-evidence/2026-09-19-movilba-516-dev-post-rollback-readonly.sql sha256=8fde520b1b5fa80ea7db7d391121ee0856584f358bbaa7ac3ef9951bf7fd5738. Migration sha256 f8f38d8dcc2116806cf0c7838e4343a8bcb0954e9c39f8c765a9643d51bf9d53 hard-gated. One outer DEV transaction: before baselines, defer_end=1 install, dry-run+apply, zero-survivor/six-trigger/function gates, explicit ROLLBACK, same-session and fresh-connection full restoration incl. 3 sequences. Independent read-only postcheck PASS. No rehearsal write executed; awaiting Elazar exact DEV-only GO. No COMMIT, no PROD.
-
Frozen DEV forced-ROLLBACK packet independently checksum-verified. Runner /data-lezama/movilba/migration-evidence/2026-09-19-run-movilba-516-dev-forced-rollback.sh SHA256 e4d9930f58213d96000ced80313669a8939365666b23f12788f0eba622e4f916; wrapper /data-lezama/movilba/migration-evidence/2026-09-19-movilba-516-dev-forced-rollback-wrapper.sql SHA256 36c4c2a2b6d3d488a4d82fe588dcd8c6d73c35798db1c7bd162e28027003bce1; read-only postcheck /data-lezama/movilba/migration-evidence/2026-09-19-movilba-516-dev-post-rollback-readonly.sql SHA256 8fde520b1b5fa80ea7db7d391121ee0856584f358bbaa7ac3ef9951bf7fd5738; migration SHA256 f8f38d8dcc2116806cf0c7838e4343a8bcb0954e9c39f8c765a9643d51bf9d53. Package hard-gates DEV URL, one outer transaction, explicit ROLLBACK, full baseline restoration including sequences, and no PROD. Awaiting Elazar exact GO.
-
Policy clarification from coder03-mba-l-cc tag coder03-mba-l-cc-mu8kuu23kskc: do not hold routine bug fixes or ROLLBACK-only DEV rehearsals for fresh Elazar GO. A real write-path rehearsal inside an outer transaction ending ROLLBACK is required verification and leaves nothing persistent to approve. Proceed with the frozen runner, exact named PRE/INSIDE/POST denominators, in-transaction postconditions, protection/identification of hand-made DEV test rows, restoration proof, and a forced failure showing the gate aborts against prior bad behavior. Fresh explicit GO remains required for PROD DDL, non-replayed/variant persistent PROD data changes, genuine product choices, DISABLE TRIGGER+DELETE on vehiculo_historial, and mass physical deletion.
-
Policy clarification received via coder02 tag coder02-mba-l-ca-mu8kvchp90uq-coder03-mba-l-ca citing coder03-mba-l-cc-mu8kuu23kskc: rollback-only DEV rehearsals do not require fresh Elazar GO because nothing persists. db02 authorized to execute frozen runner sha256 e4d9930f58213d96000ced80313669a8939365666b23f12788f0eba622e4f916 only, with named PRE/INSIDE/POST denominators, protection/identification of hand-made DEV test rows, full data/function/trigger/sequence restoration proof, and a forced ABORT negative control against prior bad behavior. No COMMIT and no PROD; persistent/destructive PROD work remains separately gated.
-
First exact frozen DEV rollback rehearsal exposed a real migration defect and safely aborted: apply failed at wrapper line 278 because temp relation rutap_reconcile_audit_borrar already exists. Cleanup drops source/report/novalor/borrar/val_hist_borrar/falla but omits rutap_reconcile_audit_borrar, which is created at migration line 413. PostgreSQL rolled back on psql exit; fresh-connection postcheck PASS proves scoped rows/hashes, functions, all six triggers restored. Evidence: /data-lezama/movilba/migration-evidence/2026-09-19-movilba-516-dev-forced-rollback.log (175 lines). Required patch: add DROP TABLE IF EXISTS rutap_reconcile_audit_borrar to temp cleanup, re-audit, freeze new SHA, rerun. No COMMIT or PROD.
-
First authorized DEV forced-ROLLBACK rehearsal executed and safely aborted on a real repeat-call defect: rutap_reconcile_audit_borrar temp table was not dropped between dry-run and apply. PostgreSQL rollback plus fresh postcheck restored all scoped data/hashes, functions, six triggers and sequences; no COMMIT/no PROD. Patched owned migration by adding DROP TABLE IF EXISTS rutap_reconcile_audit_borrar; all 7 temp CREATE names now have matching cleanup. New migration sha256=87a4e54dfc6dbee746925bcdcbfa07b180dc6dd68f23ec7c7547b196d6bf05c5. Audit requested before db02 re-freezes runner and reruns. Negative control will use TT628PA synthetic raw snapshot row and require exact raw-present-but-unlinked projection-defect ABORT, then rollback and fresh restoration.
-
AUDIT PASS tag audit-mba-l-ca-mu8l1ibksl2i on exact corrected migration sha256=87a4e54dfc6dbee746925bcdcbfa07b180dc6dd68f23ec7c7547b196d6bf05c5. Verified one functional addition at function-entry cleanup and bijection of all 7 CREATE TEMP TABLE names with DROP TABLE IF EXISTS names. db02 directed to refreeze runner/wrapper/postcheck against this SHA, send new full hashes to audit, then execute DEV forced-ROLLBACK rehearsal and TT628PA negative control only after packet audit. No COMMIT/no PROD.
-
Refrozen DEV rollback packet awaiting exact packet audit. Migration sha256=87a4e54dfc6dbee746925bcdcbfa07b180dc6dd68f23ec7c7547b196d6bf05c5; main runner af4837b3c6530f69277039ebf5fad28d12684cde45fbc08713f492a2736c79be; wrapper 36c4c2a2b6d3d488a4d82fe588dcd8c6d73c35798db1c7bd162e28027003bce1; postcheck 8fde520b1b5fa80ea7db7d391121ee0856584f358bbaa7ac3ef9951bf7fd5738; TT628PA control SQL b885292b9ffd4baa984dfdb3035c594f87984f5d5204a03ea7459b81068c7d68; TT628PA runner e60528d57bbecf2b7692d39a72dae707e1ba41f40d2c47b5d13b43d36c405b3a. Both bash -n PASS; 7/7 temp cleanup static gate PASS. Nothing executed; no COMMIT/no PROD.
-
Packet audit FAIL after main DEV destructive path and explicit ROLLBACK succeeded; no PROD and TT628PA not run. Harness defects: AFTER block used BEGIN READ ONLY but creates temp CTAS (SQLSTATE 25006), and five rolled-back VDC updates advanced the nontransactional vdc_archive sequence 60604->60609 before trigger-disable. Fresh postcheck proved scoped data/functions/6 triggers restored. Audit safely reset sequence 60609->60604 after max-id/last_value guards. db02 must change AFTER to plain BEGIN and guarantee guarded restoration of every captured sequence on both runner success/failure before fresh verification, then re-freeze all affected SHAs for audit. Evidence: /data-lezama/movilba/migration-evidence/2026-09-19-movilba-516-sequence-restoration-after-harness-failure.log and /data-lezama/movilba/migration-evidence/2026-09-19-movilba-516-post-wrapper-failure-restoration.log.
-
DEV audit PASS tag audit-mba-l-ca-mu8lfh6g593v-coder03-mba-l-ca on corrected migration sha256=87a4e54dfc6dbee746925bcdcbfa07b180dc6dd68f23ec7c7547b196d6bf05c5. Main forced-ROLLBACK inside tx deleted 32 absent app_dev vehicles, 32 VDC, 64 wide rows, connected validator component, archives/audit; explicit rollback and fresh reconnect restored scoped data/hashes, baseline function, all 6 triggers, and sequences exactly 1011/62412/60604. TT628PA negative control PASS: projection-defect gate aborted naming TT628PA, vehicle preserved, synthetic raw fixture absent after rollback, sequences/postcheck exact. No COMMIT/no PROD. Evidence: /data-lezama/movilba/migration-evidence/2026-09-19-movilba-516-dev-forced-rollback.log and /data-lezama/movilba/migration-evidence/2026-09-19-movilba-516-tt628pa-forced-abort.log. DEV rollback packet sound; production execution separately authorized.
-
DEV verification PASS for migration SHA 87a4e54dfc6dbee746925bcdcbfa07b180dc6dd68f23ec7c7547b196d6bf05c5. Only remaining blocker is fresh explicit Elazar GO for PROD execution of this exact SHA because it contains 15 DDL operations: CREATE OR REPLACE FUNCTION, two DROP FUNCTION IF EXISTS statements, six DISABLE TRIGGER statements, and six matching ENABLE TRIGGER statements. Standing SSOT reconciliation policy covers the physical data reconciliation but not PROD DDL. No PROD execution until exact GO; retain the already fully DEV-verified artifact rather than redesigning a less-tested packet.
-
Elazar explicit GO received 2026-09-19 13:51 ART for PROD execution of exact migration SHA-256 87a4e54dfc6dbee746925bcdcbfa07b180dc6dd68f23ec7c7547b196d6bf05c5 and its disclosed 15 DDL/trigger operations: CREATE OR REPLACE reconciliar_snapshot, two DROP FUNCTION statements, six DISABLE TRIGGER statements, and six matching ENABLE TRIGGER statements. Release is limited to the fully DEV-verified frozen PROD packet with hash gates, denominators, sequence safeguards, trigger restoration, fresh-connection postchecks, and evidence capture; abort on any mismatch.
-
PROD execution authorized, but no frozen PROD runner/postcheck exists in durable evidence storage. Migration SHA still matches. This is a packaging gap, not a new-GO condition. coder02 must produce and hash-freeze the PROD packet for exact migration SHA 87a4e54dfc6dbee746925bcdcbfa07b180dc6dd68f23ec7c7547b196d6bf05c5; db02 must independently review exact paths/SHAs and execute only after packet audit. No PROD connection or mutation has occurred.
-
Elazar pre-go-live data policy: only the latest RUTAP XLSX SSOT and normalized catalogs are authoritative. Legacy/test/history/audit/changelog application rows are rebuildable and require no preservation gates. MOVILBA-516 correctness dependency: PROD snapshot 2 is stale (2026-09-17; 5514 raw/2413 usable; zero absence candidates), corrected 2026-09-19 workbook not imported, and current importer still calls reconciliar_estado_abierto_snapshot which 516 drops. Required order: apply MOVILBA-523 corrected XLSX import; bind/freeze 516 PROD runner to resulting exact snapshot identity/filename/MD5/5528 rows; install exact authorized 516 migration; dry-run/apply reconciliation; fresh postcheck against same snapshot and catalogs. Do not run 516 against snapshot 2 or install it before importer completion.
-
PROD package audit STOP 2026-09-19 14:07 ART. Initial announced runner/preflight hashes changed during review; superseded set is runner d31adf36b7523e8939a74abe6e082da195395a30b1502cc52b742ab7f14b39d8, preflight 1baacbd2fe5126f54a28c261111da7a85280380fab999683d05c0c0866d435f6, postcheck 0a27e4f9580b3a5d31ac77ac1f111472270962c7c7975ec69153c779e5deca8f, schema 1f8bb109497f0b03c1a7c6ec7db711b929fb86499a977fde54bfc40b4b19f65a, but NOT approved. Blockers: psql multiline/dynamic \copy usage is not demonstrated valid; reviewed candidate manifest is generated in a separate rolled-back READ COMMITTED session while apply recomputes candidates without exact equality/stable-snapshot enforcement, allowing unreviewed deletes; receipt counts are not bound to DB counts. PROD read-only confirms installed reconciliar_snapshot md5 b5b83c4063ac6fa5bf06f6354078a019 (old baseline) and temporary 435 helper exists md5 46b33be1b0ae4cdcaa708a6968ac04ea, so install path remains correct after 523. Require corrected immutable packet plus end-to-end rollback rehearsal before PASS. 523 proceeds separately.
-
HARD STOP remains. Package d85833b5 runner rejects canonical nested 523 receipt unless a sidecar is introduced, and more critically --apply regenerates a new manifest instead of requiring the exact previously reviewed preflight manifest. Apply must accept prior run/manifest, pin its SHA and receipt/artifact identity, recompute under RR+locks, and compare multiplicity with EXCEPT ALL before mutation.
-
Corrected immutable 14:28 package statically audited PASS for PRELIGHT-ONLY rollback rehearsal: runner daee70bd97edd8b77a091971a92fe54ec7590d6750e95876609aa9308bada99a, preflight d48a99b31bb4874df6d501bafbe6695d37471f369444bb8b5ed0a301f81f866a, apply 61905a1fa26a6efa57732e8c85b5bc07787f01afd4bbb2a448771787d8357788, postcheck 22ed70e88c0e661f4f0fa001f5427fd9b4903cbf50aa31e7d5e07173a691d157, schema f467e787045280a56f7c5f90d98be49a34ead91109fade1d367e9ab46f90dd34. Apply remains HARD STOP until preflight run artifacts are audited.
-
Authorized preflight rehearsal failed safely at manifest export; no durable DB change. Run 2026-09-19T173000Z-movilba-516-prod-preflight-s5-2774468: receipt SHA f4e64f8f..., preflight log SHA 8717569f...; clean dry-run 2413/2413, all update/delete counts 0, gates 0. Root cause preflight.sql:152 uses \g :'manifest_path', making quotes literal in filename; patch to \g :manifest_path and refreeze runner/preflight hashes. Current package HARD STOP.
-
Refrozen manifest-export patch audited PASS for second preflight-only rehearsal: runner b59913166296942e997635292b1cfdf811e2a2285f04a3e33344dba7f14db083, preflight 1a1e657e3beebc74a5fe9d874c0b2ea94e881b52ac242d8fe60359d1b44bae42. Scope mechanically proven: restoring quoted line reproduces old preflight SHA d48a99b3; restoring embedded SHA reproduces old runner SHA daee70bd. Apply remains HARD STOP pending successful rehearsal evidence.
-
Independent PROD final audit PASS. Committed run /data-lezama/movilba/migration-evidence/runs/2026-09-19T173900Z-movilba-516-prod-apply-s5-2801835 used exact approved manifest SHA 1b2977bded20062dcdd4bfa887dd72b23850eca822c609264fed027bfffa4258 and binding SHA 026d44b973015521891c526566e201f4f65f554c579bb2fb24e397b1847867f1. Apply SHA a7a30cbfec7afe5da267e1dbf70de3928523e0520334633cb0a3f88755229816 COMMIT with zero deletes/updates; fresh postcheck SHA 39650f3b8a0c4c2c40243233ab5b72e9655aa0af4e9ddf5c302279bada4860 PASS with snapshot 5 and 5528/5528/2413. db02 independently verified target reconciler MD5 2b7e946f835170839b0f75d950c85f23, obsolete helpers absent, open_without_state=0, and AC098EJ/AG202SZ Alta/116.
-
PROD execution and independent final audits PASS, but owner closeout found the frozen migration remains untracked in owning branch coder03-mba-l-ca/movilba-516-origin-agnostic-delete: docs/migrations/2026-09-19-movilba-516-reconciliar-snapshot-origen-agnostico-DEV-Y-PROD.sql, SHA256 87a4e54dfc6dbee746925bcdcbfa07b180dc6dd68f23ec7c7547b196d6bf05c5. Do not close until the project shipping lane preserves this exact file in git and reports the commit. Runtime evidence remains final PASS at /data-lezama/movilba/migration-evidence/runs/2026-09-19T173900Z-movilba-516-prod-apply-s5-2801835.
-
Repository closeout only: exact audited/applied migration SHA 87a4e54dfc6dbee746925bcdcbfa07b180dc6dd68f23ec7c7547b196d6bf05c5 remains untracked in the owning coder03 worktree. Designated release owner coder-mba-l-ca is offline; active ARO PM has been asked to assign an available shipping lane. PROD runtime and both final audits PASS.
-
Repository preservation completed by assigned shipping lane; independently verifying exact commit before closure.
-
Frozen applied migration preserved exactly in commit f872859ab06d9f53373d4c31e02520694e3229fa on branch movilba-97-modification-subtype. Independent git-object verification: commit changes only docs/migrations/2026-09-19-movilba-516-reconciliar-snapshot-origen-agnostico-DEV-Y-PROD.sql; committed blob 951a69c7099cc2e045748a51df50286131f931a2; SHA256 from git show is 87a4e54dfc6dbee746925bcdcbfa07b180dc6dd68f23ec7c7547b196d6bf05c5, byte-identical to the audited PROD migration.
-
Completed. Exact origin-agnostic reconciler migration SHA256 87a4e54dfc6dbee746925bcdcbfa07b180dc6dd68f23ec7c7547b196d6bf05c5 committed as f872859ab06d9f53373d4c31e02520694e3229fa and independently verified from the git object. PROD committed run /data-lezama/movilba/migration-evidence/runs/2026-09-19T173900Z-movilba-516-prod-apply-s5-2801835 passed fresh postcheck and both independent audits: snapshot 5, raw/latest/normalized 5528, usable 2413, open_without_state 0, target reconciler MD5 2b7e946f835170839b0f75d950c85f23 installed, obsolete helper absent, AC098EJ/AG202SZ stable Alta/116, and zero reconciliation mutations.
-
Independent evidence measurement PASS for DEV prerequisite apply. Evidence /data-lezama/movilba-web/evidence/2026-09-20-movilba-516-dev-apply-db02-mba-l-ca.md SHA256 b7d7091d8704d73c181ccfe08a1180c522b3c26755d33c2c4510e2c83234b5bd. Exact artifact f872859ab06d9f53373d4c31e02520694e3229fa / blob 951a69c7099cc2e045748a51df50286131f931a2 / SHA256 87a4e54dfc6dbee746925bcdcbfa07b180dc6dd68f23ec7c7547b196d6bf05c5; rollback restored b5b83c40, apply committed 2b7e946f, fresh owner movilba_user, retired helper 0; PROD untouched.
bug
3w ago by wi-cli-venus
3w ago
2026-09-19 17:48