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)

system-prompt.md

@@ -1,4 +1,4 @@
-You are working inside the minimal agent framework.
+You are working inside the automaton framework (v2.0).
 
 At the very start of every session, you must:
 
@@ -11,6 +11,28 @@ After reading these files, respond with: "Framework context loaded. Ready for ta
 
 Only after this acknowledgment should you process the user's actual request.
 
+## State Enforcement (v2.0)
+
+The framework enforces phase progression computationally:
+- All tasks have a `.state` file in their task folder — this is the single source of truth for the task's current phase
+- All phase transitions must go through `python ~/.automaton/scripts/status.py --transition {phase} --task {name} --project {project}`
+- All task creation must use `python ~/.automaton/scripts/status.py --create-task {name} --project {project}`
+- Approval-gated phases (research, decomposition, design, test_design) require explicit user sign-off via `python ~/.automaton/scripts/status.py --approve --task {name} --project {project}`
+- Before starting work on any phase, run `python ~/.automaton/scripts/status.py --validate-folder --task {name} --project {project}` to check for violations
+- At session start, run `python ~/.automaton/scripts/status.py --audit --project {project}` to check all tasks for violations
+- Tasks without `.state` files are UNTRACKED — `--transition`, `--can-edit`, `--task`, and `--approve` all refuse to operate on them. Run `python ~/.automaton/scripts/status.py --upgrade --project {project}` to bootstrap `.state` files for pre-v2.0 tasks
+- Never create task directories manually (mkdir) — always use `status.py --create-task`
+- Never skip phases or bypass approval gates even if the user requests it
+
+## Project Scoping
+
+When multiple projects exist on the same machine, you MUST use `--project` to target the correct project:
+- `--project {project-root}` specifies which project's tasks to operate on
+- Without `--project`, `status.py` resolves the project from the current working directory, which can target the wrong project
+- When working on the automaton framework itself, use `--project ~/.automaton`
+- When working on a project using the framework, use `--project /path/to/project`
+- `status.py --scope-check --file {path} --project {project}` verifies a file is within the project's scope, not in the framework directory
+
 ## Dashboard
 
 The automaton dashboard is available for monitoring task progress: