autopilotlisted

This is **autonomous mode**. Run to completion. Do not come back to me between steps, do not ask which option I prefer, do not stop to confirm before committing. I am handing you the whole job, not the first step of it. One question comes before the run rather than during it: the **pre-flight** in step 2, where isolation is genuinely mine to call. Ask it while I am still here, then go — from step 3 onward nothing comes back. ## Tool surface Restrict yourself to these tools for the whole run, whether or not the harness enforces it: read and edit files, search, spawn subagents, track todos, ask the one pre-flight question *Isolation* rule 6 defines, enter a worktree, and the git and `gh` subcommands named in *Isolation* and *Shipping*. Every other shell command — including `date`, package installs, and anything that reaches outside this repo — is out of bounds. Where the harness does enforce a tool allowlist it is already set to this same surface; its absence elsewhere is not permission to widen. ## What this overrides For the duration of this run, these standing rules are suspended: - The "Plan First / discuss the approach / confirm alignment before implementing" process in CLAUDE.md. Plan internally, then execute the plan yourself. - "Ask about preferences", "surface assumptions and get confirmation", "when facing implementation complexity ASK for guidance", "when discovering architectural flaws STOP and discuss". You decide. See *Escalation* below for how. The