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/inflight-upgrade-path/ADVERSARIAL_BUG_REPORT.md

@@ -0,0 +1,13 @@
+# Adversarial Bug Report: Inflight Upgrade Path
+
+## Deep Review
+The upgrade path is designed for backward compatibility. Existing tasks without `.state` get bootstrapped via the artifact heuristic. The version marker in config.md enables future version detection.
+
+## Potential Issues
+1. **Bootstrap phase inference may be wrong**: The artifact heuristic determines phase based on which artifacts exist, but this can be ambiguous. For example, if a task has both SPEC.md and IMPLEMENTATION.md (because it was in early implement phase), the heuristic must infer "implement" correctly. The heuristic uses a priority order (latest phase with all required artifacts), which is reasonable but could misidentify tasks that were abandoned mid-phase.
+
+2. **upgrade.sh has no rollback**: If the upgrade script bootstraps a `.state` with an incorrect inferred phase, there's no automatic rollback. The user must manually correct the `.state` file. The script reports inferred phases for review, but doesn't provide a `--dry-run` flag.
+
+3. **Version marker parsing**: `config.md` is a markdown file, so parsing the version marker requires string matching rather than structured format. If someone reformats config.md, the version detection could fail.
+
+## Verdict: PASS — the bootstrap heuristic is reasonable and upgrade.sh reports results for manual review. No critical bugs.