L03-10 — Present undo and redo as governed revision history #124

Outcome

Undo and redo in Quick are revision navigation over governed history: a published correction is reversed by a forward rollback, never by rewriting bytes.

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.

Grounding

• docs/QUICK_PDF_PARITY.md excludes undo and redo from the Quick shell.
• Completed drags are discarded: EditorHost::onDragCompleted drops the DragSession #104 asks how a committed drag would interact with actionUndo and actionRedo; L04-08 (L04-08 — Implement forward rollback and cross-surface parity #40) defines forward rollback.

Acceptance

• Undo of a published correction creates a forward-rollback artifact through the L04 gateway.
• View and selection state is separate from document history.
• A history panel shows revision identities, approvals, and receipts.
• Failure case: undo must not remove an approved, published revision or its receipt.

Required proof

History fixtures across publish, rollback, and reopen; mapped interaction and quick lanes. 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.