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)

scripts/git-hooks/pre-commit

@@ -0,0 +1,41 @@
+#!/usr/bin/env bash
+# pre-commit hook — blocks commits when no task is in an edit-allowed phase.
+#
+# Install: cp this file to .git/hooks/pre-commit && chmod +x .git/hooks/pre-commit
+# Or:      ln -s ~/.automaton/scripts/git-hooks/pre-commit .git/hooks/pre-commit
+#
+# This is a safety net. The primary enforcement is the harness pre-edit hook.
+# Pre-commit catches changes that bypassed the harness (e.g., manual edits).
+
+set -euo pipefail
+
+STATUS_SCRIPT="$HOME/.automaton/scripts/status.py"
+
+if [ ! -f "$STATUS_SCRIPT" ]; then
+    exit 0
+fi
+
+PROJECT_ROOT="$(git rev-parse --show-toplevel 2>/dev/null || pwd)"
+
+python3 "$STATUS_SCRIPT" --can-edit --project "$PROJECT_ROOT" --json 2>/dev/null
+EXIT_CODE=$?
+
+if [ $EXIT_CODE -ne 0 ]; then
+    echo ""
+    echo "=== COMMIT BLOCKED ==="
+    echo "No task is in an implement or doc_review phase."
+    echo "Create a task and transition it to implement before committing:"
+    echo ""
+    echo "  python ~/.automaton/scripts/status.py --create-task my-feature --project $PROJECT_ROOT"
+    echo "  python ~/.automaton/scripts/status.py --transition research --task my-feature --project $PROJECT_ROOT"
+    echo "  python ~/.automaton/scripts/status.py --transition implement --task my-feature --project $PROJECT_ROOT"
+    echo ""
+    echo "Or use --upgrade to bootstrap .state files for existing tasks:"
+    echo "  python ~/.automaton/scripts/status.py --upgrade --project $PROJECT_ROOT"
+    echo ""
+    echo "To bypass this hook (NOT RECOMMENDED): git commit --no-verify"
+    echo "====================="
+    exit 1
+fi
+
+exit 0

scripts/upgrade.sh

@@ -0,0 +1,57 @@
+#!/usr/bin/env bash
+# upgrade.sh — Upgrade existing Automaton projects to support .state files and status.py
+# Usage: ./upgrade.sh [project-path]
+
+set -euo pipefail
+
+SCRIPT_DIR="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"
+STATUS_SCRIPT="$SCRIPT_DIR/status.py"
+
+if [ -n "${1:-}" ]; then
+    PROJECT_DIR="$(cd "$1" && pwd)"
+else
+    PROJECT_DIR="$(pwd)"
+fi
+
+TASKS_DIR="$PROJECT_DIR/.automaton/tasks"
+FRAMEWORK_DIR="$HOME/.automaton"
+
+echo "=== Automaton Upgrade ==="
+echo "Project: $PROJECT_DIR"
+echo ""
+
+# Bootstrap .state files for tasks using status.py --upgrade
+if [ -f "$STATUS_SCRIPT" ]; then
+    echo "Step 1: Bootstrapping .state files for existing tasks..."
+    python3 "$STATUS_SCRIPT" --upgrade --project "$PROJECT_DIR" || true
+    echo ""
+fi
+
+# Add version marker to config.md if not present
+CONFIG_FILE="$FRAMEWORK_DIR/config.md"
+if [ -f "$CONFIG_FILE" ]; then
+    if ! grep -q "Framework Version" "$CONFIG_FILE"; then
+        echo "" >> "$CONFIG_FILE"
+        echo "## Framework Version" >> "$CONFIG_FILE"
+        echo "- **Version**: 2.0" >> "$CONFIG_FILE"
+        echo "- **State enforcement**: enabled (.state file + status.py)" >> "$CONFIG_FILE"
+        echo "" >> "$CONFIG_FILE"
+        echo "Added version marker to $CONFIG_FILE"
+    else
+        echo "Version marker already present in $CONFIG_FILE"
+    fi
+else
+    echo "WARNING: $CONFIG_FILE not found. Creating with version marker."
+    cat > "$CONFIG_FILE" << 'EOF'
+# Framework Configuration
+
+## Framework Version
+- **Version**: 2.0
+- **State enforcement**: enabled (.state file + status.py)
+EOF
+fi
+
+echo ""
+echo "=== Upgrade Complete ==="
+echo "Run 'python ~/.automaton/scripts/status.py --list --project $PROJECT_DIR' to verify task states."
+echo "Run 'python ~/.automaton/scripts/status.py --audit --project $PROJECT_DIR' to check for violations."