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)
975 B
975 B
VERDICT: Inflight Upgrade Path
Summary
Created upgrade.sh script that bootstraps .state from existing artifacts, added version marker to config.md, updated README.md and CHANGELOG.md with new features and upgrade instructions. Phase prompts gracefully degrade when .state is absent.
Phase Results
| Phase | Result |
|---|---|
| Implementation | ✅ PASS |
| Bug Find | ✅ PASS (1 minor finding) |
| Adversarial Bug Find | ✅ PASS |
| Doc Review | ✅ PASS |
Findings
- upgrade.sh bootstraps .state for all existing tasks
- Version 2.0 marker in config.md enables version detection
- Phase prompts warn but continue when .state is missing
- README and CHANGELOG updated with upgrade instructions
- Minor: No --dry-run flag on upgrade.sh
- Minor: migrate-project.sh handling of .state is implicit, not explicitly tested
Final Verdict
PASS — All acceptance criteria met. The upgrade path is backward-compatible and well-documented.
Score: +10