L13-08 — Qualify correction breadth across Editor, PdfTool, and Action List #134

Outcome

Every L13 operation behaves the same from the Editor, PdfTool, and Action Lists.

Parent and boundary

Parent: #109. Owner: LoopLibCore correction subsystem. This issue owns one bounded slice of Correction Catalog Breadth; consume accepted upstream contracts and keep PDF/verdict/publication authority with Core.

Grounding

• L04-08 (L04-08 — Implement forward rollback and cross-surface parity #40) provides the cross-surface parity harness.

Acceptance

• Every new operation appears in the generated correction catalog with an overlay row.
• The three surfaces produce equivalent plans and outputs for the same input and parameters.
• The round-trip corpus runs green, and python scripts/generate-architecture-catalogs.py --check passes.
• Execution goes only through the L04 gateway with a versioned registry entry, save policy, impact set, and generated catalog overlay.
• Failure case: an operation that is reachable from only one surface cannot be admitted.

Required proof

Parity harness report and round-trip corpus. 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 · Gap review of the issue suite against the approved roadmap, 2026-09-27.