Files
automaton/tasks/complete/project-scoping-enforcement/SPEC.md
T
Lap Tran 4a2301b077
CI / build (push) Has been cancelled
Archive completed tasks, add cleanup commands, self-documenting dashboard UI
- Archive 79 completed framework-dev tasks from tasks/ -> tasks/complete/
- status.py: add --cleanup-done and --install-cleanup-schedule commands
- Add scripts/automaton-cleanup.sh for periodic task archiving
- Dashboard: rename 'Background' tab -> 'Agent', 'Cleanup' agent -> 'Completed Task Archiver', remove redundant group headers and pill badges, dim inactive agent placeholders
- .rules.md: add Self-Documenting UI Names rule
- New tests: test_cleanup_done.py, expanded test_app.py and test_task.py
2026-06-24 22:43:33 -04:00

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

  1. status.py must error (not silently fall back) when no project is detected and --project is not specified
  2. status.py --scope-check must mark framework files as OUT_OF_SCOPE when working on a project (not IN_SCOPE)
  3. Dashboard handler methods must use stored project_root instead of re-detecting from CWD
  4. All status.py command invocations in prompts and config files must include --project {project}
  5. _infer_state_from_artifacts must NOT be used as a silent fallback in operational commands — only --upgrade, --audit, and --validate-folder may use it
  6. All operational commands (--transition, --can-edit, --task, --approve, --claim) must refuse tasks without .state files
  7. --list must show tasks without .state as UNTRACKED, not silently bootstrap them
  8. New --upgrade command must bootstrap .state files for pre-v2.0 tasks
  9. upgrade.sh must call status.py --upgrade instead of manual shell heuristic bootstrapping
  10. All documentation and prompts must reference --upgrade for pre-v2.0 tasks

Acceptance Criteria

  • status.py errors when run from /tmp/ without --project
  • Framework files are OUT_OF_SCOPE when --project points to a project
  • Dashboard uses stored project_root for all handler methods
  • Every status.py command reference in prompts includes --project {project}
  • _find_project_dir no longer has cwd.name == ".automaton" false positive
  • _find_project_dir errors instead of silently falling back
  • --transition, --can-edit, --task, --claim refuse untracked tasks
  • --list shows UNTRACKED for tasks without .state
  • --upgrade --task {name} bootstraps .state for a single task
  • --upgrade (no --task) bootstraps all tasks missing .state
  • All 192 tests pass