Registered repository migration tooling evidence
The transaction runner passed its focused and integration gates before the live canary.
Evidence
| Requirement | Proof | Verdict |
|---|---|---|
| Runtime fleet boundary | Registry names and paths are loaded from the effective mounts file; tests use arbitrary project identities. | Pass |
| Recoverable snapshots | Every discovered mount receives a content-bearing ZIP and SHA-256 before preflight promotion. | Pass |
| Preserve user changes | Dirty migration paths defer with exact names; unrelated source dirt remains outside the install set. | Pass |
| Transaction safety | Migration stages outside the checkout, verifies fully, rechecks source hashes, and installs exact paths. | Pass |
| Rollback | An injected second-write failure restored the original Git worktree with no residual tracked or untracked files. | Pass |
| Resumability | Ledger transitions are atomic; a completed run returns idempotently without rewriting migrated resources. | Pass |
| Regression scope | 93 affected tests and all 1,378 repository tests passed; Ruff was clean. | Pass |