Registered repository migration — Reckon canary

The canonical repository completed the real transaction and was pushed to origin/main at 157f1c8.

The Reckon canary passes through snapshot, staged migration, verification, installation, commit and push. — The content-bearing snapshot remains outside the repository under the immutable registry run.

Before and after

Measure	Before	After	Verdict
Legacy resource paths	26	0	Pass
Typed resource paths	9	35	Pass
Legacy capability records	33	0	Pass
Plan/research/evidence resources	30	30	Parity
Sprint/blocker/timeline/project resources	7	7	Parity
Project-state format	distributed	distributed	Preserved

The typed manifest records 26 moves and 16 link rewrites. The source snapshot is SHA-256 23f82116d059bfd4bd01103bab5491867ac4ff00fe853bbddc457170c163d67d.

Verification

Gate	Result
Document audit	0 errors
Schema audit	17 checked, 17 conformant, 0 violations
Relationship and project-state audit	0 errors
Progressive discovery	34 resources returned through the bounded summary stream
Legacy capability audit	0 findings
Isolated static build	Pass; 30 plans and 4 sprints projected
Post-install repository suite	1,378 passed in 33.03 seconds
Commit and push	`157f1c8` equals `origin/main`

The canary found one stale flat-directory assumption in the repository's byte-identity test. It was changed to use the shared typed resolver, then the failing test and full suite passed.