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)
21 lines
1.1 KiB
Markdown
21 lines
1.1 KiB
Markdown
# Bug Report: Inflight Upgrade Path
|
|
|
|
## Methodology
|
|
Reviewed upgrade.sh script, bootstrap .state from artifacts, version marker in config.md, and README/CHANGELOG updates.
|
|
|
|
## Acceptance Criteria
|
|
| # | Criterion | Result |
|
|
|---|-----------|--------|
|
|
| 1 | `status.py` bootstraps `.state` for tasks without it | ✅ |
|
|
| 2 | `upgrade.sh` scans all tasks and bootstraps missing `.state` | ✅ |
|
|
| 3 | `upgrade.sh` runs `--audit` and reports violations | ✅ |
|
|
| 4 | `upgrade.sh` produces human-readable summary | ✅ |
|
|
| 5 | Phase prompts work with or without `.state` | ✅ |
|
|
| 6 | `README.md` updated with new features | ✅ |
|
|
| 7 | `CHANGELOG.md` updated under `[unreleased]` | ✅ |
|
|
| 8 | Version marker added to `config.md` | ✅ |
|
|
|
|
## Findings
|
|
1. **Minor**: `migrate-project.sh` does not explicitly handle `.state` files that may already exist in migrated project task folders. The spec mentions "not delete `.state` files during migration" but the migration script currently skips task folders silently if they have `.state`. This is correct behavior but not explicitly tested.
|
|
|
|
## Verdict: PASS |