L03-13d — Wire Production color modes, bitonal conversion, render-to-images, and bleed fixup in Quick #235

Outcome

The Production group's display color modes and production commands work in Quick.

Parent and boundary

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

Grounding

• No handler: actionColorInvert, actionColorGrayscale, actionColorHighContrast, actionColorBitonal, actionColorCustom, actionCreateBitonalDocument, actionRender_to_Images, actionBleedFixup.
• All are ABSORB/Production in docs/loop-shell-actions.json.

Acceptance

• Display color modes change presentation only, are marked as non-authoritative in the fidelity indicator, and never reach Production Preview evidence.
• actionBleedFixup and actionCreateBitonalDocument open the governed Fix flow (plan, preview, approve) instead of writing directly.
• Render-to-images writes through the atomic writer with the render identity recorded.
• Failure case: a display color mode is never mistaken for a production render in Compare or sign-off.

Required proof

Render-identity tests for each color mode; governed-flow test for bleed fixup and bitonal; atomic-write test for render-to-images. 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 docs/loop-shell-actions.json against Quick command handlers, 2026-10-06.