plans/prompts/wave_6/pr_c2_image_generation.md
Implement the image_generation wave of C2 in plans/cleanup-state-machines.md. The plan wins. Prereqs: a prior C2 wave landed (pattern reuse); the B0 ADR resolved this machine's app-quit policy and app-restart persistence decision — those calls are binding here.
Pre-code artifacts: lifecycle matrix row per the ADR; serializability audit (job payloads and attachments — decide what crosses the wire vs stays referenced); safe projection (job list is the read model — A3 already shaped the manager's snapshot/subscribe surface as exactly this; publishing it remotely should be nearly mechanical); deletion budget (renderer per-job dispatcher controllers, the provider's toast orchestration moves to presentation events routed per decision 5 with first-window semantics from the ADR).
Semantics to preserve: cancellation is best-effort with the main IPC promise as terminal authority (this simplifies under main-hosting — the authority and the machine are finally in the same process; note the deletion of the late-cancel projection guard if it becomes structural); lateAfterCancel exclusion from chat projection; cancelling presentation state; terminal-job retention/pruning policy moves to the actor's lifecycle policy. dismissedImageGenerationJobIdsAtom stays per-window UI state composing with the remote read model.
Tests: existing image_generation suites ported to drive the actor; job visible from a second window; window close mid-job (continues per decision 2); chat-strip auto-attach behavior unchanged (the lateAfterCancel regression class); quit/restart per the ADR decisions. Golden suite green. /deep-review. Branch c2-image-generation; /pr-push; update plan status + matrix.
Trailing deletion (part of this wave, per the plan's rolling Phase D): land the wave's adapter/channel deletion as a SEPARATE PR immediately behind the cutover (same day is fine — no bake, no soak; per the plan's recorded corrections: no update window, no runtime toggle, stragglers are compile-time-detectable, and dead-code deletion cannot regress runtime once typecheck/CI pass). The separation exists ONLY to keep the high-scrutiny cutover diff pure for review; a later cutover revert simply reverts both PRs. The wave is not complete until it lands.
Rebatch note (see DEPENDENCIES.md): after github_ops sets the pattern, version_preview and image_generation PREP runs in parallel (disjoint domains); only the cutovers stagger through the single cutover slot.