# M12.4l migration storage fault qualification This extends the ADR-0147–0149 private PostgreSQL migration matrix. It changes tests and documentation only, with the existing ADR-0061 filesystem adapter and its test-only directory-sync seam. No SQL, production API, biological rule, format, dependency, deployment or live world changes. ## Matrix and command ```sh bash tools/ci/postgres-check.sh --population-only "$PWD/build/m97-postgres/evo-postgres-tests" ``` The full, sanitizer and TLS qualification paths also run these cases as part of the population suite. Both raw/profile-4 and cohort/profile-5 cases use real player-origin wildlife and outbound/return transfers. - Failure of the source capsule's directory sync refuses preparation without a pending source pointer. A subsequent ordinary preparation verifies and syncs the retained object before using it. - Failure of the destination capsule's directory sync refuses staging. The source remains frozen and no destination pending pointer appears. - Failure of either result object's directory sync refuses paired publication. Independent database observations prove both heads unchanged and both pending roles retained. A visible object alone never grants ownership; later retries verify and sync identical bytes again. - After a real paired commit, the unprivileged fixture user loses read permission on both current result objects (outbound) or both local counterpart predecessor capsules (return). Direct adapter reads must report actual I/O errors. Paused owners refuse advancement while independent database observation proves the committed heads remain unchanged. Current-payload I/O failure is retriable and increments the store-failure counter; unavailable paired replay evidence is a tail-verification failure and quarantines. Pointer settlement cannot resume stale source stock or activate an unverified destination. - A scope guard restores original permissions without changing immutable bytes. Temporary current-payload I/O failures reconcile the complete pair under the same epochs. Tail-verification quarantine remains sticky: the test coordinator explicitly retires the captured current database leases, then replacement hosts obtain strictly newer epochs and recover the exact committed payloads. Exact paired retries return the original receipt without a second transfer. The read-permission fixture requires an unprivileged Linux user, as does the disposable PostgreSQL cluster. It fails if permissions do not actually deny reads; it does not silently skip under elevated filesystem privileges. ## Limits Directory-sync failures use the existing adapter test seam; they are not physical disk failure, a power-loss durability experiment or a filesystem remount. Read denial is a real filesystem permission failure on selected retained objects, without deleting, corrupting or rewriting their contents. It does not establish remote object-storage availability, multi-host failover, capacity/performance or orchestrator recovery. Explicit lease retirement in the test is a coordinator action under current captured authority, not an automatic quarantine policy. Multi-host/kernel-network faults, storage-host failure, orchestrator drills, linked ecology, maturation, world census/cuts, target-host costs and actual elapsed-day ecology remain open. Executed checks are recorded in [VALIDATION](VALIDATION.md); this document alone is not a passing result.