Explicit opt-in
Autopilot runs only when you explicitly request it. The normal Blueprint workflow pauses for human review after the spec and each implementation step.
One bounded pass
Autopilot can select or resume one feature or fix, write and critique the spec, create the branch, implement small steps, run checks, and create passing checkpoint commits. It ends with a review packet.
Hard boundaries
Autopilot never completes, merges, pushes, deploys, publishes, sends, deletes data, runs irreversible migrations, or performs destructive actions without the separate approval required for that action.
It stops when product decisions are missing, the working tree is unsafe, a required check fails repeatedly, or continuing would cross one of those boundaries.
Next step
Review the final packet and diff. Run try if you want a manual walkthrough, then complete when you are ready to archive and merge.