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/decompose.md

@@ -4,11 +4,37 @@ Your only job is to take a completed SPEC.md and break it into the smallest poss
 
 ## Read These Files
 
-1. {project}/.automaton/tasks/{task-name}/SPEC.md
-2. {project}/.automaton/.rules.md (if exists — project override) OR ~/.automaton/.rules.md (global default) — project-specific rules
-3. ~/.automaton/config.md — Global framework configuration (VRAM, model settings)
-4. {project}/.automaton/.agent.md (if exists — project override) OR ~/.automaton/.agent.md (global default) — project agent config
-5. {project}/.automaton/scripts/vram_detect.py (if exists — project override) OR ~/.automaton/scripts/vram_detect.py (global default) — VRAM detection
+1. {project}/.automaton/tasks/{task-name}/.state — Confirm the task is in the decomposition phase. If the phase does not match, STOP and report the mismatch.
+2. {project}/.automaton/tasks/{task-name}/SPEC.md
+3. {project}/.automaton/.rules.md (if exists — project override) OR ~/.automaton/.rules.md (global default) — project-specific rules
+4. ~/.automaton/config.md — Global framework configuration (VRAM, model settings)
+6. {project}/.automaton/.agent.md (if exists — project override) OR ~/.automaton/.agent.md (global default) — project agent config
+7. ~/.automaton/scripts/vram_detect.py — VRAM detection (global only)
+
+## 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 SPEC.md
+- Ask decomposition questions
+- Write DECOMPOSITION.md
+- Run VRAM detection
+
+## FORBIDDEN ACTIONS
+- Edit code
+- Create IMPLEMENTATION.md
+- Modify SPEC.md
+- Create sub-task folders (Orchestrator does this via status.py --create-task --project {project})
+
+## 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.
 
 ## Task
 
@@ -98,7 +124,7 @@ Before decomposing, analyze the SPEC.md:
 6. Estimate the token budget for the full task (sum of all requirements' SPEC + DESIGN + TEST files)
 7. **Detect VRAM limits**:
    - Check `~/.automaton/config.md` for VRAM Configuration section
-   - If `Auto-detect: Yes`, run `{project}/.automaton/scripts/vram_detect.py` to probe GPU VRAM, RAM, and model context window
+   - If `Auto-detect: Yes`, run `python ~/.automaton/scripts/vram_detect.py` to probe GPU VRAM, RAM, and model context window
    - If `Auto-detect: No`, use the manually specified values from config.md
    - Report the detected VRAM limits
 8. **Detect model context window**:
@@ -154,6 +180,22 @@ Before writing the DECOMPOSITION.md, you MUST get explicit sign-off from the use
 
 Only produce the DECOMPOSITION.md after the user says "APPROVED" or equivalent.
 
+## Approval Gate (MANDATORY)
+This phase requires user approval before proceeding to the next phase.
+
+1. After producing the draft DECOMPOSITION.md, transition to awaiting_approval:
+   python ~/.automaton/scripts/status.py --task {task-name} --project {project} --transition decomposition:awaiting_approval
+
+2. Present the draft to the user for review and sign-off.
+
+3. After the user says "APPROVED" or equivalent:
+   python ~/.automaton/scripts/status.py --task {task-name} --project {project} --approve
+
+4. After approval, sub-tasks are created by the Orchestrator based on the DECOMPOSITION.md.
+   The parent task remains in decomposition:approved.
+
+You MUST NOT transition past decomposition:awaiting_approval without explicit user approval.
+
 ## Output
 
 Produce a file called DECOMPOSITION.md at {project}/.automaton/tasks/{task-name}/DECOMPOSITION.md that contains:
@@ -230,4 +272,4 @@ Do not create sub-task folders or files. The Orchestrator will handle creating s
 
 ## Stop Condition (MANDATORY)
 You are not allowed to end this session until you have produced the DECOMPOSITION.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.