M12.4: define explicit boundary-accounting checkpoint upgrades
Foundation / checks (deploy) (push) Successful in 4s
Foundation / checks (ecs) (push) Successful in 2m38s
Foundation / checks (network) (push) Successful in 22m52s
Foundation / checks (client) (push) Successful in 23m48s
Foundation / checks (tsan) (push) Successful in 23m38s
Foundation / checks (postgres) (push) Successful in 53m31s
Foundation / checks (checks) (push) Successful in 1h9m6s
Foundation / postgres-tools (push) Successful in 2m0s
Foundation / server-image (push) Successful in 4m2s
Foundation / image (push) Successful in 4m40s
Foundation / checks (deploy) (push) Successful in 4s
Foundation / checks (ecs) (push) Successful in 2m38s
Foundation / checks (network) (push) Successful in 22m52s
Foundation / checks (client) (push) Successful in 23m48s
Foundation / checks (tsan) (push) Successful in 23m38s
Foundation / checks (postgres) (push) Successful in 53m31s
Foundation / checks (checks) (push) Successful in 1h9m6s
Foundation / postgres-tools (push) Successful in 2m0s
Foundation / server-image (push) Successful in 4m2s
Foundation / image (push) Successful in 4m40s
This commit is contained in:
@@ -83,3 +83,17 @@ after cohort transfer, comparing the complete continued destination snapshot.
|
||||
This closes the portable continuation format boundary needed by a future durable
|
||||
adapter. It does not add a durable bundle or SQL admission: both the current C++
|
||||
prepared validator and SQL checker continue to admit only population batch 1.
|
||||
|
||||
## M12.4f portable checkpoint upgrade boundary
|
||||
|
||||
[ADR-0145](../adr/0145-boundary-accounting-checkpoint-upgrade.md) declares bundle
|
||||
10 for owner 7 and supplies an explicit bundle-9 no-tick upgrade candidate for
|
||||
both existing profiles. The manifest advances its commit sequence and retains
|
||||
the exact source digest while preserving profile, history and biological tick.
|
||||
Complete payload restoration/upgrade retains biology, opening stock and cohort
|
||||
policy/membership/sequence. There is no bundle-10 genesis or repeated upgrade.
|
||||
Ordinary continuation and profile changes preserve the tuple; new/old payload
|
||||
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.
|
||||
|
||||
@@ -54,6 +54,10 @@ Population batch 2 continues owner-7 biology and conversions with retained flows
|
||||
cross-version replay is refused and a new process reproduces a post-transfer
|
||||
64-tick interval. Its durable admission/upgrade remains intentionally unsupported
|
||||
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.
|
||||
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
|
||||
|
||||
@@ -1,5 +1,15 @@
|
||||
# Validation strategy
|
||||
|
||||
M12.4f's checkpoint contract exercises explicit portable bundle-9 to 10 upgrades
|
||||
for raw owners and a real nonempty cohort with retained policy/sequence. It
|
||||
requires complete candidate equality, canonical restore, continued batch-2
|
||||
biology and bundle-preserving representation changes. Negative cases cover
|
||||
old/new payload confusion, malformed source/lease/digest bindings, exhaustion,
|
||||
repeated upgrade and new genesis. The private PostgreSQL population suite must
|
||||
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.
|
||||
|
||||
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
|
||||
|
||||
@@ -1,5 +1,36 @@
|
||||
# Validation report
|
||||
|
||||
## 2026-10-17 - M12.4f portable boundary-accounting checkpoint upgrade
|
||||
|
||||
ADR-0145 adds portable bundle 10, explicit bundle-9 no-tick upgrade candidates
|
||||
for raw and population owners, exact source-payload restoration, and
|
||||
bundle-preserving continuation/profile transitions. Bundle-10 genesis and
|
||||
repeated upgrade are refused. No SQL migration, biological rule, worker default,
|
||||
golden, dependency, live state or deployment changed.
|
||||
|
||||
Executed locally:
|
||||
|
||||
- Native MSVC Release **78/78 passed**, 12.56 s, including the new contract cases.
|
||||
The first sandboxed invocation passed 76/78; its two existing hard-link
|
||||
filesystem fixtures were denied access. The full permitted rerun passed.
|
||||
- Linux Clang 19 analysis checkpoint upgrade **1/1 passed**, 5.12 s; retained
|
||||
checkpoint/migration/restart checks **3/3 passed**, 14.71 s. Repository
|
||||
clang-format 19 gate passed. An initial missing-default fixture warning was
|
||||
corrected before this successful analysis run.
|
||||
- Linux Clang 19 ASan/UBSan checkpoint contracts **2/2 passed**, 16.76 s,
|
||||
with no reports.
|
||||
- Actual GCC 14 optional server/PostgreSQL targets rebuilt; private schema-45
|
||||
population suite passed, 6 s total. A SHA-bound portable bundle-10 upgrade is
|
||||
refused by prepared retry/resolution, direct SQL profile transition and the
|
||||
generic publisher; the committed head stays exact. The retained batch-2 under
|
||||
bundle-9 refusal also remains covered.
|
||||
|
||||
These results qualify the portable declaration and fail-closed admission
|
||||
boundary. They do not qualify durable bundle-10 publication, immutable upgrade
|
||||
evidence/recovery, paired escrow, a coupled atlas/environment, multigeneration
|
||||
ecology or elapsed multi-day stability. Build errors supplied by the maintainer
|
||||
remain preserved in untracked `Build_Errors.txt`.
|
||||
|
||||
## 2026-10-17 - captured M12 CI execution failures
|
||||
|
||||
Reviewed the maintainer's local `Build_Errors.txt`. Repeated checks/TSan runs hit
|
||||
|
||||
Reference in New Issue
Block a user