wizard: fixed resumability banner is unsafe for stateful cutovers

## Skill wizard ## Harness and version Codex desktop 26.1013.40934, GPT-6.1 Sol at high effort. The skill was installed as a local skills.sh-style copy on 2026-10-15; the exact package version was not exposed. This occurred in a long production-maintenance task after one context compaction. ## What happened A real wizard was generated for a production cleanup that moved exact filesystem entries into quarantine, verified the application, and then either rolled back or deleted quarantine after a second confirmation. The required unchanged template banner printed that the operator could stop with Ctrl-C and rerun later because saved values would be remembered. That was false for this workflow: move state existed only in process-local arrays, and a rerun after some or all moves could see no original warning and leave quarantine stranded. A read-only production-safety review flagged this as a high-severity interruption and recovery defect before execution. Because SKILL.md says the library above STAGES must never be edited, the generated wizard had to avoid calling banner, print a separate non-resumable opening, and add state-aware EXIT, HUP, INT, and TERM handling below the marker. No production mutation occurred before the issue was corrected. ## What I expected The shared template should not make an unconditional resumability claim. The skill explicitly covers one-off migrations and cutovers, where partial state can make blind reruns unsafe. A small fix would be: 1. Replace the fixed banner copy with neutral guidance that does not promise rerun safety. 2. Add a migration and cutover authoring rule in SKILL.md: define interruption, partial-state reporting, rollback, and rerun behavior before an irreversible stage; if state is not durably recorded, explicitly forbid blind reruns. 3. Keep the library consistent across wizards without requiring authors to bypass banner. Observable completion: a stateful cutover wizard generated from the stock template makes no universal rerun claim, and static verification requires explicit interruption semantics for irreversible stages. ## Scope evidence This is an observed failure from a real session, not a hypothetical feature request. It affects the promoted engineering wizard and does not request a harness-specific branch or a new configuration option. Searches for wizard template, resumable, Ctrl-C, migration, and saved-values issues found no existing duplicate.