M12.4: qualify migration storage failures and exact recovery
Foundation / checks (client) (push) Successful in 5s
Foundation / checks (network) (push) Successful in 5s
Foundation / checks (deploy) (push) Successful in 5s
Foundation / checks (ecs) (push) Successful in 2m12s
Foundation / postgres-tools (push) Canceled after 0s
Foundation / server-image (push) Canceled after 0s
Foundation / image (push) Canceled after 0s
Foundation / checks (postgres) (push) Canceled after 19m42s
Foundation / checks (checks) (push) Canceled after 19m48s
Foundation / checks (tsan) (push) Canceled after 19m49s

This commit is contained in:
dingo
2026-10-18 13:38:05 -04:00
parent e0a7c13f6b
commit df680810af
9 changed files with 313 additions and 4 deletions
+50
View File
@@ -1,5 +1,55 @@
# Validation report
## 2026-10-18 - M12.4l migration object sync/read failures
Test-only qualification extends ADR-0147–0149 using the existing filesystem
adapter's directory-sync fault seam and actual read-permission denial under the
unprivileged disposable-cluster user. Both raw and cohort representations use
real player-origin wildlife, outbound and return transfers, unchanged complete
payload oracles and independent database head/pointer observations. See
[storage fixture and limits](M12_MIGRATION_STORAGE_FAULTS.md).
Executed locally:
- GCC 14 optional persistence/process targets rebuilt. The final private
population/migration suite passed **17 s** (15 s population phase).
- Linux Clang 19 **ASan/UBSan** storage and TLS fault matrix passed **64 s**
(60 s population phase), with no sanitizer reports.
- Explicit clang-tidy 19 on the changed publication tests passed with no owned
warnings. Repository clang-format 19 passed.
- Complete frozen-binary private PostgreSQL qualification passed with **exit 0**,
**546 s**: C++ integration/process/load/history (434 s), combined TLS/storage
fault matrix (38 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.
Failed source capsule sync cannot prepare a freeze; failed destination capsule
sync cannot stage a ghost. Failure of either result sync leaves both heads and
both pending roles unchanged. Existing identical objects are reverified and
synced on retry; visible bytes do not grant ownership.
Post-commit direct reads report actual I/O errors while the database retains
both exact result heads. Current-payload I/O failure pauses complete recovery and
retries under the same epochs after access returns. Unavailable counterpart
replay evidence quarantines both owners; restoring access leaves quarantine
sticky. Explicit current-lease retirement and replacement recover exact bytes
under strictly newer epochs. The original paired receipt survives both paths.
The first test draft incorrectly expected current-payload I/O failure to
quarantine. Inspection confirmed the existing retriable `RecoveryError::store`
contract. The test now distinguishes this from unavailable paired replay evidence
(`RecoveryError::tail`) and verifies both behaviors without changing production
error handling or weakening readiness checks.
Limits: sync failure uses an existing test seam; permission denial affects
selected local objects, not a storage-host or physical media/power failure. Test
coordinator lease retirement is explicit, not a new automatic quarantine policy.
No new production/thread behavior, SQL, dependency, biological rule/format,
golden, live database, World0 or deployment changed. Native/TSan results from
M12.4k remain separate; this test-only segment does not claim new runs of those
checks or a Docker image build/remote CI result. Linked ecology and later M12
integration/soak gates remain open.
## 2026-10-18 - M12.4k TLS migration request/receipt and owner partitions
Test-only qualification extends ADR-0147–0149 with opaque loopback TCP relays and