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.4 KiB
1.4 KiB
Bug Report: Multi-Agent Support
Methodology
Reviewed claim/release/next-available/available commands, .state.lock files, Agent Configuration in .agent.md, and single-agent zero-overhead guarantee.
Acceptance Criteria
| # | Criterion | Result |
|---|---|---|
| 1 | Single-agent mode has zero behavioral change | ✅ |
| 2 | --claim creates .state.lock atomically |
✅ |
| 3 | --claim refuses if already claimed (non-expired) |
✅ |
| 4 | --claim overclaims if expired |
✅ |
| 5 | --release removes .state.lock |
✅ |
| 6 | --release refuses if wrong agent |
✅ |
| 7 | --next-available finds highest-priority unclaimed task |
✅ |
| 8 | --available lists all unclaimed tasks for agent role |
✅ |
| 9 | Agent Configuration in .agent.md activates multi-agent |
✅ |
| 10 | .state.lock excluded from --validate-folder |
✅ |
| 11 | Completed tasks auto-release locks | ✅ |
Findings
-
Minor: Lock timeout defaults to 30 minutes. The configurable timeout parsing (
5m,10m, etc.) from.agent.mdworks but is case-sensitive —30Mwould not be parsed correctly. Minor UX issue. -
Minor: The
--as-coordinatorflag and--forceflag for coordinator override are parsed but the coordinator role validation is limited — any agent can potentially pass--agent orchestratorwithout verification. This is acceptable since agent identity is self-reported in the current design.