M12.4: retain read-only destination migration stages
Foundation / checks (deploy) (push) Successful in 5s
Foundation / checks (ecs) (push) Successful in 2m25s
Foundation / checks (network) (push) Successful in 20m44s
Foundation / checks (client) (push) Successful in 21m57s
Foundation / checks (tsan) (push) Successful in 22m46s
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 30m2s
Foundation / checks (postgres) (push) Canceled after 29m56s

This commit is contained in:
dingo
2026-10-18 09:32:50 -04:00
parent c625a4cb68
commit 0515702964
21 changed files with 1023 additions and 21 deletions
+48
View File
@@ -1,5 +1,53 @@
# Validation report
## 2026-10-18 - M12.4i durable read-only destination staging
ADR-0148/schema 48 retains a destination-authorized staging record and bounded
pending pointer at the exact captured head. The adapter verifies both cuts,
replays the trace and retains a source capsule plus verified destination ghost
in the destination namespace. The source owns all outgoing stock; neither head
moves. Source abort releases both pending pointers atomically, and exact stage
retries retain their original outcome. Both migration roles are exclusive.
Executed locally:
- Native MSVC Release **78/78 passed**, 12.62 s.
- Actual GCC 14 optional server/persistence targets rebuilt; final private
PostgreSQL population/staging suite passed, **11 s** (8 s test phase).
- Linux Clang 19 ASan/UBSan private population/staging suite passed, **33 s**
(30 s test phase), with no sanitizer reports.
- Explicit clang-tidy 19 on the adapter, owning host and PostgreSQL population
tests passed with no owned warnings. Repository clang-format 19 and both
changed shell scripts' syntax checks passed.
- Complete frozen-binary private PostgreSQL qualification passed with **exit 0**,
**501 s**: C++ integration/process/load/history (426 s), life reservations,
backup/restore, host-loss DR, upgrade, migration history/rollback, runtime
permission audit and checksum/future-version rejection. The detached runner
recorded its completion code.
Both representations use real funded player-origin wildlife and unchanged cuts.
Cases cover exact/conflicting retries, a moved destination, pending destination
intervals, source/destination role exclusivity, blocked publication/profile/life
reservations and stale destination authority. Replacement epochs retain staging.
Missing source capsules, missing and same-length corrupt ghosts fail strong
binding. An existing valid object with false destination biology fails complete
replay. Real lock-timeout ambiguity retains exact requests; SIGKILL before/after
stage commit leaves absence/a retained pause respectively. Independent database
connections race stage against source abort without stranded destination work.
The owning destination host pauses on unknown staging, survives drain/recreation
without adopting the ghost and resumes its identical original state after source
abort. The existing fixed freeze metric covers either role without new labels.
Limits: this is staging evidence, not a migration result or activation receipt.
Atomic paired publication, its common immutable outcome, commit/abort races and
recovery/activation remain open. Backup retains all immutable namespace objects;
existing backup/DR fixtures do not qualify cellular cloning or a new cellular
restore procedure. No elapsed-day, linked-geometry or multigeneration claim
follows. No live database, World0, deployment, dependency, biological rule, format
or golden changed. The earlier captured `Build_Errors.txt` and unrelated local
work remain untracked; remote CI confirmation of the previous runner repair
remains separate.
## 2026-10-18 - M12.4h durable migration source freeze and explicit abort
ADR-0147/schema 47 retains exact source-authorized preparation, both predecessor