Files
automaton/tasks/autopilot-gate-integration/BUG_REPORT.md
T
gitea 05c76852a2
CI / build (push) Has been cancelled
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)
2026-06-15 14:16:46 -04:00

1011 B

Bug Report: Autopilot Gate Integration

Methodology

Reviewed orchestrate.md autopilot section for gate-check loop, approval pauses, persona switching via .state, and session break recovery.

Acceptance Criteria

# Criterion Result
1 Orchestrator uses status.py --transition between phases ✅
2 Orchestrator calls --validate-folder before each transition ✅
3 Orchestrator STOPS on validation violations ✅
4 Approval gates pause autopilot (research/decomposition/design/test_design) ✅
5 --transition {phase}:awaiting_approval before user sign-off ✅
6 --approve only after user says "APPROVED" ✅
7 Non-approval phases transition automatically ✅
8 .state used for resumption ✅
9 Persona switching via phase prompt loading ✅
10 Session break recovery via .state ✅

Findings

None — gate-check loop is correctly implemented in orchestrate.md.

Verdict: PASS