Implement Autopilot mode: state machine, adversarial bug finding, and proactive orchestration

prompts/workflow.md

@@ -0,0 +1,21 @@
+# Workflow State Machine
+
+This file defines the linear progression of a task in the agent-framework. The Orchestrator uses this to determine the next phase.
+
+## Task Lifecycle
+
+| Current State | Signal (Artifact) | Next Phase | Action |
+| :--- | :--- | :--- | :--- |
+| **New Task** | No `SPEC.md` | Research | Generate `SPEC.md` |
+| **Research** | Has `SPEC.md` | Implement | Generate code and tests |
+| **Implementation** | Has `IMPLEMENTATION.md` | Bug Find | Generate `BUG_REPORT.md` |
+| **Bug Find** | Has `BUG_REPORT.md` | Adversarial Bug Find | Generate `ADVERSARIAL_BUG_REPORT.md` |
+| **Adversarial Bug Find** | Has `ADVERSARIAL_BUG_REPORT.md` | Referee | Generate `VERDICT.md` |
+| **Referee** | Has `VERDICT.md` | Complete / Review | Finalize or request user intervention |
+
+## Autopilot Rules
+
+1. **Linear Progression**: Never skip a phase.
+2. **Artifact Check**: A phase is only considered "complete" if its corresponding artifact exists and is non-empty.
+3. **Automatic Transition**: Upon completion of an artifact, the Orchestrator must immediately identify and propose the next phase in the lifecycle.
+4. **Human Intervention**: If the Referee marks a task as `NEEDS_REVIEW` or identifies "Tie-Breaks", the Autopilot pauses and waits for user input.