Repository navigation
L04-05 — Centralize approved Core execution #37
Description
Outcome
Route Editor, PdfTool, PageMaster and Action List through one cancellation-safe mutation gateway.
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
- One plan produces one published candidate or a terminal nonpublication receipt; no adapter owns alternate mutation.
- Failure case: Unauthorized, stale, already-terminal, or malformed requests stop before partial publication.
Required proof
Gateway fault-injection and per-surface parity tests. 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.
Activity
feat(core): refuse duplicate registration and bind registry identity …
feat(core): thread approval authorization contexts through surfaces (#36
feat(core): add one cancellation-safe governed mutation gateway (#37)
feat(core): route approved execution through the mutation gateway (#37)
feat(core): thread approval authorization contexts through surfaces (#36
feat(core): add one cancellation-safe governed mutation gateway (#37)
feat(core): route approved execution through the mutation gateway (#37)
feat(core): thread approval authorization contexts through surfaces (#36
feat(core): add one cancellation-safe governed mutation gateway (#37)
feat(core): route approved execution through the mutation gateway (#37)