Registered repository migration — fleet ledger

Runtime discovery fixed the effective 12-project registry at SHA-256 ce521fc435f51c893ccf7a334cdfdedf13d1452ca987c3b5cb3bd820d4616034. Every row has a content-bearing snapshot and a terminal state.

Coverage

ProjectBefore resourcesStateEvidence or required action
L2G1 legacyDeferredCreate the missing project index, then authorise a reviewed wave.
hanney21 legacyDeferredPreflight clean; explicit external repository write authority required.
helix3 legacyDeferredPreflight clean; explicit external repository write authority required.
imas-ambix162 legacy, 1 typedDeferredFour active alternate worktrees must finish or stand down.
imas-codex112 legacy, 37 typedDeferredThree active worktrees and a nested research path violate the canonical resolver contract.
imas-efit458 legacy, 439 typedDeferredA nested research path violates the canonical resolver contract.
imas-standard-names48 legacyDeferredOne active worktree; mounted branch is two commits behind its upstream.
norma11 legacyDeferredPreflight clean; explicit external repository write authority required.
nova49 legacyDeferredTwo active alternate worktrees must finish or stand down.
reckon26 legacy, 9 typedVerified157f1c8 pushed to origin/main; 0 legacy and 35 typed after.
tessera5 legacyDeferredPreflight clean; explicit external repository write authority required.
vv4 legacyDeferredPreflight clean; explicit external repository write authority required.

Snapshot and promotion guarantees

The next reviewed wave can start with helix and hanney after explicit cross-repository write authority. Blocked repositories remain independently resumable after their named conditions clear.