M12.4: admit and replay durable boundary-accounting upgrades
Foundation / checks (deploy) (push) Successful in 5s
Foundation / checks (ecs) (push) Successful in 2m23s
Foundation / checks (network) (push) Successful in 21m4s
Foundation / checks (client) (push) Successful in 22m15s
Foundation / checks (tsan) (push) Successful in 23m3s
Foundation / checks (postgres) (push) Successful in 51m33s
Foundation / postgres-tools (push) Canceled after 0s
Foundation / server-image (push) Canceled after 0s
Foundation / image (push) Canceled after 0s
Foundation / checks (checks) (push) Canceled after 55m18s

This commit is contained in:
dingo
2026-10-18 08:13:36 -04:00
parent 2416735e2b
commit 1b5c0cdf7c
21 changed files with 812 additions and 98 deletions
+46
View File
@@ -1,5 +1,51 @@
# Validation report
## 2026-10-18 - M12.4g durable boundary-accounting upgrade
ADR-0146/schema 46 admits the explicit same-profile bundle-9 to 10 upgrade through
the existing immutable version-upgrade journal. Recovery rederives the complete
source/result transformation; representation changes retain separate evidence.
Both profiles preserve their exact tuple through ordinary continuation; bundle
10 requires population batch 2 while bundle 9 retains batch 1. No worker performs
an automatic upgrade. Biology/rules 8, goldens, dependencies and live state are
unchanged.
Executed locally:
- Native MSVC Release **78/78 passed**, 12.30 s.
- Actual GCC 14 optional server/PostgreSQL targets rebuilt; final focused private
PostgreSQL population/upgrade suite passed, 6 s total.
- Linux Clang 19 ASan/UBSan final private population/upgrade suite passed, 26 s
total (22 s test phase), with no reports.
- Explicit clang-tidy 19 on both affected adapters and both PostgreSQL test
sources passed, with no owned warnings. Repository clang-format 19 and shell
syntax checks passed.
- Complete frozen-binary private PostgreSQL qualification passed with **exit 0**,
**503 s**: C++ integration/process/load/history (423 s), life reservations,
backup, DR, upgrade, migration history/rollback, runtime permission audit and
checksum/future-version rejection. Earlier interrupted runs are not counted.
New cases exercise raw upgrade/trace-3 continuation and rollback, nonempty cohort
policy/sequence retention, pending-interval refusal, wrong publication paths,
pre-transaction SIGKILL, ambiguous exact retry, conflicting bytes and stale
writers. Missing/corrupt objects quarantine. A canonical cohort object with equal
biological totals but different policy/membership fails complete upgrade replay.
Batch-1/2 cross-binding is refused in both directions. The publication process
kill and actual host-recreation/materialization matrix also runs with batch 2.
An initial new-migration CASE expression failed parsing and was corrected before
the successful runs. The first full fixture omitted sibling load/session-probe
tools; a corrected run was then interrupted by a hangup. The final detached run
used every required frozen sibling executable and recorded its completion code.
Limits: these backup/DR/clone checks retain their existing supported fixtures;
they do not qualify cellular cloning or a new world-wide migration cut. Paired
biological transfer trace 1 remains unadmitted; no durable source freeze, staged
ghost activation, two-head escrow, linked atlas/environment or multi-generation/
elapsed-day ecological claim follows. No live database, World0 or deployment was
touched. Remote CI/container confirmation of the earlier build-runner repair
remains separate; `Build_Errors.txt` and unrelated local work remain untracked.
## 2026-10-17 - M12.4f portable boundary-accounting checkpoint upgrade
ADR-0145 adds portable bundle 10, explicit bundle-9 no-tick upgrade candidates