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
+17
View File
@@ -1,5 +1,22 @@
# Project status and next steps
## M12.4l local migration storage failures - 2026-10-18
The private matrix now refuses preparation, staging or paired publication after
capsule/result directory-sync failures. Real read-permission denial after commit
pauses current-payload recovery for retry or quarantines unavailable counterpart
replay evidence. Both paths preserve the exact database heads and receipt; full
recovery restores exact biology, with newer authority after quarantine.
GCC private population/migration checks pass in 17 s, ASan/UBSan storage/TLS
checks in 64 s, and Clang analysis/format checks pass.
Complete private persistence/process/backup/DR and migration/permission
qualification, including the combined fault matrix, passes in 546 s.
[Evidence and limits](engineering/VALIDATION.md) distinguish local sync/read
failures from physical media, storage-host and orchestrator drills. Linked ecology,
maturation and later M12 integration/soak gates remain open. This segment changes
tests/documentation only.
## M12.4k independent migration TLS path faults - 2026-10-18
Test-only relays now exercise real loopback TCP/end-to-end TLS request/receipt