L04-01 — Reconcile registry and canonical plan contract #33

Outcome

Inventory current repair entry points; define one versioned operation registry, deterministic plan serialization, digest, scope, save policy, and impact metadata.

Parent and boundary

Parent: #5. Owner: LoopLibCore correction subsystem. This issue owns one bounded slice of Governed Operation Engine; consume accepted upstream contracts and keep PDF/verdict/publication authority with Core.

Acceptance

• All supported operations resolve one unambiguous registration and stable cross-platform plan digest.
• Failure case: Duplicate registration, unknown operation, ambiguous parameter, or stale revision fails before candidate computation.

Required proof

Golden vectors, schema tests, and migration decision. Record the exact source SHA, test command or hosted run, fixture/artifact identity, and any skipped or unavailable lane. Run the repository's mapped proof and check-change gate for a PR.

Handoff

Record changed files, observed result, remaining risk, and a 1–3 sentence anti-slop review. Completion means acceptance evidence, not merely a merged implementation.

Sources

Approved master roadmap · Legacy/research input (legacy #587).