gitea
05c76852a2
CI / build (push) Has been cancelled
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)
1.0 KiB
1.0 KiB
Bug Report: State File Enforcement
Methodology
Reviewed status.py implementation of .state file format, approval sub-states, atomic writes, forbidden artifacts per phase, task creation gate, and state transition rules.
Acceptance Criteria
| # | Criterion | Result |
|---|---|---|
| 1 | .state file format with approval sub-states |
✅ |
| 2 | Atomic write mechanism (tmp+rename) | ✅ |
| 3 | Forbidden artifacts per phase enforced | ✅ |
| 4 | --validate-folder flags folders without .state |
✅ |
| 5 | --audit flags manually created task folders |
✅ |
| 6 | Task creation gate (--create-task) |
✅ |
| 7 | Approval sub-states for research/design/decompose/test_design | ✅ |
| 8 | :awaiting_approval → :approved only via --approve |
✅ |
| 9 | .state excluded from artifact heuristics |
✅ |
Findings
- Minor: The
.gitignorepattern for.statewas not explicitly added to a project-level gitignore — it's documented as metadata but not enforced in version control.