v2.0: state enforcement, project scoping, harness integration

State Enforcement (v2.0):
- .state file as single source of truth for task phase
- Approval gates for research, decomposition, design, test_design
- status.py --transition refuses illegal phase transitions
- status.py --validate-folder detects out-of-order artifacts
- status.py --audit checks all tasks for violations
- status.py --create-task is the only valid way to create tasks
- Pre-v2.0 tasks without .state are UNTRACKED -- all commands refuse them
- New --upgrade command bootstraps .state files for existing tasks

Project Scoping:
- --project flag added to all status.py commands across 16+ files
- _find_project_dir errors instead of silently falling back to ~/.automaton/
- --scope-check marks framework files OUT_OF_SCOPE when working on a project
- Dashboard handlers use stored project_root instead of re-detecting from CWD
- Prompts reference ~/.automaton/scripts/vram_detect.py (not {project}/.automaton/)

Harness Integration:
- status.py --can-edit now supports project-level checks (no --task required)
- --can-edit --file checks file scope without --task
- --json output for machine-readable harness integration
- opencode plugin (plugins/automaton-guard/plugin.ts) intercepts edit/write
- Git pre-commit hook (scripts/git-hooks/pre-commit) blocks commits without task
- Formal integration contract (contracts/harness-integration.md)

Other:
- upgrade.sh delegates to status.py --upgrade instead of manual heuristics
- Phase prompts reference --project {project} for multi-project scoping
- 200 tests passing (14 new)

.agent.md

@@ -20,3 +20,39 @@ IF task type = orchestrate  → load prompts/orchestrate.md + project structure
 IF task type = compaction   → load prompts/compaction.md
 
 Always start by reading this file to determine mode.
+
+## State Enforcement (v2.0)
+
+All phase transitions must go through `status.py`:
+- Create tasks: `python ~/.automaton/scripts/status.py --create-task {name} --project {project}`
+- Transition phases: `python ~/.automaton/scripts/status.py --transition {phase} --task {name} --project {project}`
+- Approve phases: `python ~/.automaton/scripts/status.py --approve --task {name} --project {project}`
+- Validate folders: `python ~/.automaton/scripts/status.py --validate-folder --task {name} --project {project}`
+- Audit all tasks: `python ~/.automaton/scripts/status.py --audit --project {project}`
+- Upgrade pre-v2.0 tasks: `python ~/.automaton/scripts/status.py --upgrade --project {project}`
+
+**Important**: Always pass `--project {project}` to ensure correct scoping. Without it, `status.py` resolves the project from the current working directory, which can target the wrong project when multiple projects exist on the same machine.
+
+## Agent Configuration (Optional — Multi-Agent Mode)
+
+To enable multi-agent mode, add the following section:
+
+```markdown
+## Agent Configuration
+Mode: multi-agent
+Agents:
+  - id: researcher
+    phases: [research, decomposition, design, test_design]
+  - id: implementer
+    phases: [implement]
+  - id: bug-hunter
+    phases: [bug_find, adversarial_bug_find]
+  - id: referee
+    phases: [referee]
+  - id: orchestrator
+    phases: [new, complete, human_intervention]
+    role: coordinator
+Lock timeout: 30m
+```
+
+When `Mode: multi-agent` is present, agents can claim tasks (`--claim`), release them (`--release`), and discover work (`--next-available`). When absent (default), all multi-agent commands are no-ops.