feat(persistence): define retained-plan checkpoint upgrade candidates
Foundation / checks (ecs) (push) Successful in 2m51s
Foundation / checks (deploy) (push) Successful in 5m18s
Foundation / checks (network) (push) Successful in 25m49s
Foundation / checks (client) (push) Successful in 26m34s
Foundation / checks (tsan) (push) Successful in 37m12s
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 47m59s
Foundation / checks (postgres) (push) Canceled after 47m53s

This commit is contained in:
dingo
2026-10-19 14:17:41 -04:00
parent c0c66fa11a
commit 39509ecd40
17 changed files with 629 additions and 11 deletions
+3 -1
View File
@@ -19,7 +19,9 @@ closure. [ADR-0165](../adr/0165-retained-cellular-offspring-plans.md) adds porta
retained plans and earned selections, unchanged expressed parents and repeated
funded births. [ADR-0166](../adr/0166-retained-plan-replay-traces.md) adds portable
raw trace-4 replay, action matching and exact process restart. Existing same-genome
behavior remains. Durable plan/trace/bundle,
behavior remains. [ADR-0167](../adr/0167-retained-plan-checkpoint-upgrade.md) defines
the portable raw checkpoint tuple and exact retained-source upgrade. Durable
plan/trace/bundle admission,
population/migration/census admission, the in-life expression catalog, authority
handoff and NPC/UI integration are still required.
+53
View File
@@ -1,5 +1,58 @@
# Validation report
## 2026-10-19 - Portable retained-plan checkpoint upgrade
[ADR-0167](../adr/0167-retained-plan-checkpoint-upgrade.md) adds raw-only bundle
12 and the exact bundle-11 -> 12 manifest/payload candidate. The new tuple has
portable reader support, no genesis or population mapping, and no SQL admission.
Legacy revision/trace admission helpers remain unchanged. The payload operation
restores the whole source before invoking the detached owner upgrade; an ordinary
successor preserves bundle 12 and biological continuation requires trace 4.
Executed locally:
- MSVC 19.44 Release full CTest **89/89 passed, 22.32 s**, with NDEBUG.
- GCC 14.2 Release full CTest **89/89 passed, 17.33 s**, with NDEBUG.
- Clang 19.1 Debug new checkpoint/actual process-restart tests **2/2 passed,
2.28 s**, built with clang-tidy 19 enabled. Both changed implementations and
the test compiled under analysis; repository clang-format 19 and diff checks
pass. No golden or existing biological rule was changed.
- Clang 19.1 ASan/UBSan region checkpoints, inherited checkpoint upgrade, upgrade
process restart and population checkpoints **4/4 passed, 26.86 s**, without
reports.
- Optional GCC persistence and session consumers rebuilt; the session adapter
test passed **1/1, 0.14 s**. No new durable admission was enabled.
The finite-food fixture acquires an actual legacy expressed mutation, produces
funded offspring and suspends its parent before the upgrade. It checks unchanged
source bytes/manifests, equality with the full owner-upgrade oracle, retained
archive/stock/identities/presence and initial plans matching current expressed
genomes rather than immutable birth genomes. Continuation resumes the parent,
earns/consumes a real plan offer, compares direct execution to trace-4 replay,
and restores each resulting bundle-12 checkpoint. No state is replenished.
Tests refuse skipped/repeated upgrades, unknown history, sequence exhaustion,
zero/reused commit or digest/build bindings, invalid holder/epoch/frame, payload
bounds, corrupt/truncated source bytes, genesis, population admission and old/new
payload mislabeling. Manifest fields and the complete target re-encode exactly.
The process test saves a source owner and manifest, then a fresh process derives
the complete target manifest plus payload. MSVC and GCC proof bytes share SHA-256
`ee8fdf41a4fc132581cea2c74788f6517414a9444bb36efeda763beccafb1f11`.
That concatenation is a test comparison artifact, not a new production codec.
These tests use opaque nonzero digest inputs to exercise the storage-free API.
They do not verify cryptographic source binding, a committed database chain or
publication authority. The caller must independently hash/verify both immutable
manifests/objects and enforce the current head/lease. SQL schema, durable upgrade
and publication adapters are unchanged. No private database fault suite, live
deployment, target-host, TSan, actual-days, client/UI or M12 completion evidence
is claimed. Fenced admission/recovery and plan viability remain subsequent work.
The refreshed DEV window expires **2026-10-19 22:17:08 UTC**. Rendered deployment
policy passes: 75 objects in 74 files, 138 rendered objects in 17 overlays, zero
failures. The unchanged policy self-test matrix was not repeated. No deployment
or World0 operation occurred; unrelated untracked work was preserved.
## 2026-10-19 - Portable retained-plan trace replay
[ADR-0166](../adr/0166-retained-plan-replay-traces.md) adds explicit raw trace 4