M12.6: capture consistent regional census snapshots
Foundation / checks (deploy) (push) Successful in 5s
Foundation / checks (ecs) (push) Successful in 2m20s
Foundation / checks (network) (push) Successful in 21m3s
Foundation / checks (client) (push) Successful in 22m14s
Foundation / checks (tsan) (push) Successful in 24m52s
Foundation / checks (postgres) (push) Failing after 36m19s
Foundation / checks (checks) (push) Successful in 1h10m25s
Foundation / postgres-tools (push) Skipped
Foundation / server-image (push) Skipped
Foundation / image (push) Skipped

This commit is contained in:
dingo
2026-10-18 15:56:58 -04:00
parent 82568da9cd
commit 7631f9d2e2
17 changed files with 648 additions and 3 deletions
+68
View File
@@ -1,5 +1,73 @@
# Validation report
## 2026-10-18 - M12.6d consistent scoped census snapshots
[ADR-0153](../adr/0153-consistent-cellular-census-snapshots.md) captures the current
heads of 1..64 declared regions in one owned read-only repeatable-read database
transaction. It completes that short metadata transaction before fully replaying
each immutable selected cut through the existing history reader. Exact cut binding
and the scoped census-set checks remain mandatory. Failed capture rolls back;
failed completion/cleanup or a capture exception disconnects the session. No
partial result or older-head fallback. See
[the contract](../../schemas/ecology/consistent-cellular-census-snapshot-v1.md).
Executed locally:
- Native MSVC **19.44.35217.0** default Release build/CTest **79/79 passed**,
**13.76 s**, with optional Linux persistence disabled.
- GCC 14 Release private population/history integration passed **17 s** (15 s
population phase). Final combined snapshot/history/migration **TLS and storage
fault qualification passed, exit 0, 39 s** (38 s population phase).
- Clang 19 Linux **ASan/UBSan** private population integration passed **46 s**;
the final combined TLS/storage/snapshot matrix passed **exit 0, 70 s** (66 s
population phase), without sanitizer reports.
- Explicit clang-tidy 19 covered the libpq owner, snapshot adapter and integration
tests, then rechecked the final TLS assertions; no owned warnings. Repository
clang-format 19 and `git diff --check` passed.
Each raw/cohort migration race uses an independent publishing connection after
the first captured head read. Actual database settings are checked as repeatable
read and read-only. Both captured heads remain before the atomic pair; a later
snapshot sees both new heads. Earlier cuts fully replay after publication, retain
identical complete regional rows, and preserve exact/descendant resident counts,
body and reserve in both migration directions. The metadata transaction is closed
before the existing idle-only historical reader runs.
Tests also retain exact head/manifest binding on repeated reads, direct biology
oracles, request bounds/order/null validation, missing regions, incompatible
current ticks/owner versions, stale grants, unretained builds, missing/unreadable
payloads and unchanged current heads. Caller-owned read-only transactions and a
writer's pending publication are refused without taking over its transaction.
Capture failure rolls back; throwing hooks and failed completion close the
connection. Disconnect is idempotent and later queries return `closed`.
Actual loopback TCP with end-to-end TLS independently drops requests and replies
at both BEGIN and COMMIT. Every uncertain outcome returns no census, closes the
query session and preserves observed heads. Existing migration owner expiry,
replacement/heal, exact recovery and local object-failure checks still pass.
All database runners used fresh private temporary clusters and stopped them on
exit; no live database, deployment or World0 action.
The test allowlist initially needed an explicit nested digest-array type; analysis
also required consuming the expected result in the throwing-hook test. Both were
corrected and the final matrix rebuilt. No checks/goldens were suppressed or
rewritten. No SQL schema, biological rule/codec, dependency or ownership change.
Limits: this is a consistent cut of a caller-declared set in one connected
database, not durable world coverage or external branch identity. Outside-region
transfers, reserve viability and complete global freshness/reconciliation remain
open. SQL deadlines do not preempt local object reads or promise whole-query
latency. Existing replay evidence calls retain their per-call lease locks. No
deployment-host capacity claim, new TSan, complete SQL/backup/DR rerun, remote CI,
multi-host drill or actual multi-day soak. Prior full persistence regression is
retained in M12.6b. No terminal-extinction acceptance or client endpoint.
Logs: `build/m126d-native.log`, `build/m126d-postgres.log`,
`build/m126d-asan.log`, `build/m126d-final-postgres-build.log`,
`build/m126d-final-postgres.log`, `build/m126d-final-asan-build.log`,
`build/m126d-final-asan.log`, `build/m126d-final-tidy.log`,
`build/m126d-final-integration-tidy.log`, `build/m126d-final-format.log`.
## 2026-10-18 - M12.6c scoped multi-region census queries
[ADR-0152](../adr/0152-scoped-cellular-census-sets.md) adds a portable detached