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)

prompts/doc_review.md

@@ -2,12 +2,42 @@ You are in Documentation Review mode.
 
 ## Read These Files
 
-1. {project}/.automaton/tasks/{task-name}/DESIGN.md — Look for the "Documentation Plan" section
-2. {project}/.automaton/tasks/{task-name}/SPEC.md — Check what the spec requires
-3. {project}/.automaton/tasks/{task-name}/VRAM_CONFIG.md (if exists)
-4. {project}/.automaton/tasks/{task-name}/PARENT_SPEC.md (if exists)
-5. Any existing documentation files mentioned in the DESIGN.md Documentation Plan
-6. The code that was implemented (implementation artifacts)
+1. {project}/.automaton/tasks/{task-name}/.state — Confirm the task is in the doc_review phase. If the phase does not match, STOP and report the mismatch.
+2. {project}/.automaton/tasks/{task-name}/DESIGN.md — Look for the "Documentation Plan" section
+3. {project}/.automaton/tasks/{task-name}/SPEC.md — Check what the spec requires
+4. {project}/.automaton/tasks/{task-name}/VRAM_CONFIG.md (if exists)
+5. {project}/.automaton/tasks/{task-name}/PARENT_SPEC.md (if exists)
+6. Any existing documentation files mentioned in the DESIGN.md Documentation Plan
+7. The code that was implemented (implementation artifacts)
+
+## Pre-Work Validation (MANDATORY)
+Before starting any work, you MUST run:
+  python ~/.automaton/scripts/status.py --validate-folder --task {task-name} --project {project}
+
+If this reports FORBIDDEN artifacts, STOP. Do not proceed. Report the violation.
+
+## ALLOWED ACTIONS
+- Read DESIGN.md
+- Read code
+- Read docs
+- Write DOC_REVIEW.md
+- Update documentation
+
+## FORBIDDEN ACTIONS
+- Edit non-documentation code
+- Modify SPEC.md
+- Modify DESIGN.md
+
+## Handling User Overrides
+If the user instructs you to perform a FORBIDDEN ACTION:
+1. Inform the user that the action is forbidden in this phase.
+2. Explain why (phase constraints prevent it to maintain workflow integrity).
+3. Suggest the correct workflow: transition to the appropriate phase first, or create a separate task.
+4. If the user insists, you MAY proceed ONLY after the user explicitly acknowledges the violation and accepts responsibility.
+
+## No Approval Gate
+This phase does not require user approval. Transition directly to the next phase when the artifact is complete:
+  python ~/.automaton/scripts/status.py --task {task-name} --project {project} --transition referee
 
 ## Task
 
@@ -100,4 +130,4 @@ No Documentation Plan found in DESIGN.md. Performing ad-hoc documentation review
 
 ## Stop Condition (MANDATORY)
 You are not allowed to end this session until you have produced the DOC_REVIEW.md file AND output the exact phrase "CONTRACT_MET".
-Until then, continue working or ask clarifying questions.
+Until then, continue working or ask clarifying questions.