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/fix-verdict-parsing/IMPLEMENTATION.md

@@ -0,0 +1,24 @@
+# Implementation: Fix Verdict Parsing and State Machine Alignment
+
+## Summary
+- Added `parse_verdict_status()` function to `task.py` that uses structured status-line parsing (`## Status:`, `- **Status**:`) before falling back to substring search
+- Fixed `determine_task_state()` to use structured verdict parsing, eliminating false-BLOCKED classification when PASS verdicts discuss failures
+- Aligned state machine with orchestrator spec: IMPLEMENTATION.md alone → BUG_FIND (not IMPLEMENT), ADVERSARIAL_BUG_REPORT alone → BUG_FIND (not ADV_BUG_FIND)
+- Added filesystem-sourced task name validation in `discover_tasks()` and `parse_sub_tasks()` — directories with characters outside `[A-Za-z0-9_-]` are skipped
+- Added comprehensive test classes: `TestVerdictParsing`, `TestStateMachineAlignment`, `TestTaskNameValidation`
+- Updated existing `test_implementation_state` to reflect new state machine behavior
+
+## Changes
+- `automaton/dashboard/core/task.py`: Added `parse_verdict_status()`, `_VALID_TASK_NAME_CHARS`, rewrote `determine_task_state()`, added name validation to `discover_tasks()` and `parse_sub_tasks()`
+- `tests/test_task.py`: Added 16 new tests, updated 1 existing test
+
+## Test Results
+90 passed in 0.06s (full suite)
+
+## Decisions
+- Kept substring fallback for unstructured verdicts for backward compatibility
+- ADVERSARIAL_BUG_REPORT alone now maps to BUG_FIND (not ADV_BUG_FIND) per orchestrator spec clarification
+- State machine checks are: DOC_REVIEW → both bug reports → BUG_REPORT alone → ADV alone → IMPLEMENTATION alone → TEST_PLAN → DESIGN → DECOMPOSITION → SPEC → BACKLOG
+
+## Blockers
+None