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
@@ -97,3 +97,26 @@ confusion is refused in both directions. Portable reader support does not imply
database admission: schema 45 and the population prepared validator still reject
the tuple. Dedicated upgrade publication/evidence/recovery is the next segment;
paired escrow, geometry and remaining biological gates stay open.
## M12.4g durable accounting upgrade admission
[ADR-0146](../adr/0146-durable-boundary-accounting-upgrade.md)/schema 46 extends
the existing immutable version-upgrade journal to an explicit same-profile
bundle-9 to 10 publication. Both profiles retain complete source/result manifests,
payload digests and exact version tuples under the current lease and head fence.
An unsettled population interval blocks a new upgrade. The adapter restores the
verified source, derives the exact candidate, uploads/reads back its object and
retains the same prepared bytes after ambiguity. No worker upgrades automatically.
Recovery selects the recorded no-tick operation: a version upgrade is rederived
from its full retained source; a representation change uses its separate journal.
Both require full byte equality. Matching aggregate inventory cannot admit a
different cohort policy or membership. Bundle 10 requires envelope/batch 2;
bundle 9 retains envelope/batch 1. Raw biological trace 3 and rules 8 are unchanged.
Representation changes preserve either tuple and interval/player-operation
guards remain in place.
This admits the accounting format and its ordinary continuation. Paired migration
trace 1 still has no SQL publisher, source freeze, staged ghost or activation
rights. Durable two-head escrow, abort/partition/duplicate settlement, linked
geometry and ecology remain open. No deployment, live upgrade or golden changed.
+5 -2
View File
@@ -56,8 +56,11 @@ cross-version replay is refused and a new process reproduces a post-transfer
by bundle 9 and schema 45.
ADR-0145 now defines the portable bundle-10 declaration and explicit same-profile,
no-tick source upgrade, with complete payload preservation and no new genesis.
SQL admission, immutable upgrade evidence and replayed recovery remain required
before those candidates can become durable region heads.
ADR-0146/schema 46 supplies SQL admission through the existing immutable
version-upgrade evidence and complete replayed recovery. Both profile upgrades,
population batch 2 and bundle-preserving profile changes are explicit; no worker
upgrades automatically. This format admission does not publish a migration pair
or close source-freeze/destination-activation and escrow qualification.
The transfer tests also expose the current rules-8 maturation gap: buds retain
their subadult realization while reproduction requires a fully realized parent.
Finite extra food alone does not close repeated wildlife generations. A versioned
+10
View File
@@ -10,6 +10,16 @@ continue refusing these portable candidates through schema 45 and existing
prepared/generic publication paths without advancing the head. Durable admission
and upgrade crash/retry recovery remain separate gates.
M12.4g's private PostgreSQL suite upgrades raw/profile-5 bundle-9 sources using
schema 46. It rehearses raw upgrade/trace-3 continuation and rollback, retains a
nonempty cohort, refuses pending-interval upgrades and wrong publication paths,
and recovers after a pre-transaction SIGKILL and an ambiguous exact retry. Changed
requests and stale writers fail. Missing/corrupt objects quarantine; a canonical
but unequal cohort with matching biological totals fails full upgrade replay.
Batch-1/2 cross-binding is refused in both directions. The process-loss and
host-recreation/materialization matrix also runs with batch 2. Full historical
migration/backup/DR/permission regression remains required for schema admission.
Tests defend contracts, not directory coverage. All checks remain active in
Release builds. Current proof has no actual network, biology or distributed
recovery, so those categories below are milestone gates rather than passing
+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