L03-04 — Present plan and approval journey #30

Outcome

Show operation scope, parameters, candidate impact, preview, approver decision, and terminal result.

Parent and boundary

Parent: #4. Owner: LoopEditor. This issue owns one bounded slice of Quick Workspace; consume accepted upstream contracts and keep PDF/verdict/publication authority with Core.

Acceptance

• Approval binds the displayed exact plan and input identity; completion displays published/revalidated artifact.
• Failure case: QML cannot call a mutation bypass or approve a changed plan.

Required proof

End-to-end GUI fixture using L04 gateway and denied/stale cases. 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.