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.5 KiB
1.5 KiB
Bug Report: Status Script
Methodology
Reviewed the 980-line status.py implementation and 25 passing tests. Verified all commands, state transitions, validation logic, and error handling.
Acceptance Criteria
| # | Criterion | Result |
|---|---|---|
| 1 | --task shows current phase, allowed/forbidden actions |
✅ |
| 2 | --transition validates and writes .state |
✅ |
| 3 | --transition refuses past :awaiting_approval |
✅ |
| 4 | --approve transitions awaiting → approved |
✅ |
| 5 | --approve refuses if not awaiting approval |
✅ |
| 6 | --create-task creates folder with .state = new |
✅ |
| 7 | --list shows all tasks with phase and approval status |
✅ |
| 8 | --validate-folder checks out-of-order artifacts |
✅ |
| 9 | --audit runs all check categories |
⚠️ See finding 1 |
| 10 | --claim/--release/--next-available/--available |
✅ |
| 11 | --can-edit/--scope-check/--same-session |
✅ |
| 12 | Atomic writes (tmp+rename) | ✅ |
| 13 | .state.approvals log maintained |
✅ |
| 14 | 25 tests passing | ✅ |
Findings
- Minor:
--auditCategory 3 (git modification check) is stubbed — it checks whether the project is a git repo and reports "Skipped: not a git repository" or falls back to a simplified check. Full git-log-based timestamp comparison is not implemented. This is documented as part of the spec's "graceful skip" clause but the implementation is simpler than the spec describes.