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/task-status-reason/SPEC.md

@@ -0,0 +1,40 @@
+# Add Status Reason to Task Display
+
+## Goal
+Show a human-readable explanation of *why* a task is in its current state, fix the pending review count to exclude terminal-state tasks, and replace approve/request-changes buttons with revoke buttons when a review is already submitted.
+
+## Requirements
+
+### R1. Add `status_reason` property to Task
+Add a `status_reason` property on the `Task` dataclass that derives a human-readable explanation from the task's state, artifacts, and verdict status. For example:
+- DONE → "Verdict: PASS"
+- BLOCKED → "Verdict: FAIL — changes required before re-review"
+- BUG_FIND (with IMPLEMENTATION.md) → "Implementation complete — awaiting bug finding"
+- BACKLOG → "No artifacts yet — not started"
+
+### R2. Expose `status_reason` in API responses
+Include `status_reason` in the JSON response for both `/api/tasks` and `/api/task/{name}`.
+
+### R3. Display status reason prominently
+- Show `status_reason` below the status badge in the task detail panel
+- Show `status_reason` on task cards for blocked/bug_find/adv_bug_find states
+
+### R4. Fix pending review count
+The pending review counter in the header currently counts all tasks without a review, including DONE tasks. Fix it to exclude terminal states (done, blocked) so only active tasks count toward pending.
+
+### R5. Replace review buttons with revoke on submitted reviews
+When a task already has an approved review, replace the approve button with "Revoke Approval". When changes are requested, replace with "Revoke Changes". Both send status="pending" to reset the review.
+
+## Acceptance Criteria
+- [ ] `status_reason` property works for all task states
+- [ ] `/api/tasks` responses include `status_reason`
+- [ ] Detail panel shows status reason below the status badge
+- [ ] Task cards show status reason for blocked/bug_find/adv_bug_find tasks
+- [ ] Pending review count excludes done/blocked tasks
+- [ ] Approved tasks show "Revoke Approval" instead of "Approve"
+- [ ] Backend accepts "pending" as a review status
+- [ ] All tests pass
+
+## Non-Goals
+- Not changing the task state machine — revoking a review only resets the review metadata, not the task state
+- Not adding buttons to change task state directly (e.g., send back to planning) — that's a larger feature