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)
2.1 KiB
2.1 KiB
Project Scoping Enforcement
Goal
Fix scoping issues that arise when working on the automaton framework and another project using the framework simultaneously on the same machine. Also close the gap where pre-v2.0 tasks (without .state files) could be operated on by all commands, bypassing state enforcement entirely.
Requirements
status.pymust error (not silently fall back) when no project is detected and--projectis not specifiedstatus.py --scope-checkmust mark framework files as OUT_OF_SCOPE when working on a project (not IN_SCOPE)- Dashboard handler methods must use stored
project_rootinstead of re-detecting from CWD - All status.py command invocations in prompts and config files must include
--project {project} _infer_state_from_artifactsmust NOT be used as a silent fallback in operational commands — only--upgrade,--audit, and--validate-foldermay use it- All operational commands (
--transition,--can-edit,--task,--approve,--claim) must refuse tasks without.statefiles --listmust show tasks without.stateas UNTRACKED, not silently bootstrap them- New
--upgradecommand must bootstrap.statefiles for pre-v2.0 tasks upgrade.shmust callstatus.py --upgradeinstead of manual shell heuristic bootstrapping- All documentation and prompts must reference
--upgradefor pre-v2.0 tasks
Acceptance Criteria
status.pyerrors when run from/tmp/without--project- Framework files are OUT_OF_SCOPE when
--projectpoints to a project - Dashboard uses stored
project_rootfor all handler methods - Every status.py command reference in prompts includes
--project {project} _find_project_dirno longer hascwd.name == ".automaton"false positive_find_project_direrrors instead of silently falling back--transition,--can-edit,--task,--claimrefuse untracked tasks--listshows UNTRACKED for tasks without.state--upgrade --task {name}bootstraps.statefor a single task--upgrade(no --task) bootstraps all tasks missing.state- All 192 tests pass