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)

tasks/multi-agent-support/VERDICT.md

@@ -0,0 +1,26 @@
+# VERDICT: Multi-Agent Support
+
+## Summary
+Implemented claim/release/next-available/available commands in status.py, .state.lock files for agent coordination, Agent Configuration section in .agent.md, and single-agent zero-overhead guarantee (no locks or claiming in single-agent mode).
+
+## Phase Results
+| Phase | Result |
+|-------|--------|
+| Implementation | ✅ PASS |
+| Bug Find | ✅ PASS (2 minor findings) |
+| Adversarial Bug Find | ✅ PASS |
+| Doc Review | ✅ PASS |
+
+## Findings
+- Single-agent mode has zero behavioral overhead (no locks created)
+- Claim/release with atomic writes and lock expiry
+- Work discovery with priority ordering (tasks closer to completion first)
+- Agent Configuration validates phases are covered by at least one agent
+- Completed/human_intervention tasks auto-release locks
+- Minor: Lock timeout parsing is case-sensitive
+- Minor: Agent identity is self-reported (acceptable in trusted environment)
+
+## Final Verdict
+**PASS** — All acceptance criteria met. Multi-agent support is opt-in and adds zero overhead to single-agent mode.
+
+Score: +10