Archive completed tasks, add cleanup commands, self-documenting dashboard UI
CI / build (push) Has been cancelled
CI / build (push) Has been cancelled
- 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
This commit is contained in:
Lap Tran
@@ -1 +0,0 @@
|
||||
complete
|
||||
@@ -1,13 +0,0 @@
|
||||
# Adversarial Bug Report: State File Enforcement
|
||||
|
||||
## Deep Review
|
||||
The .state file format and transition rules are robust. Approval sub-states create a hard gate that cannot be bypassed via `--transition`. Atomic writes via tmp+rename prevent corruption on crash.
|
||||
|
||||
## Potential Issues
|
||||
1. **Race condition on create**: Two concurrent `--create-task` calls for the same name could both pass the "doesn't exist" check before one creates the directory. The atomic rename pattern mitigates this for .state writes but not for `mkdir`.
|
||||
|
||||
2. **Manual .state tampering**: A user or agent could directly edit `.state` to write an invalid phase name. `status.py` handles this ("Unknown phase" error), but the error path could be clearer about what phases are valid.
|
||||
|
||||
3. **Stale .state after crash**: If an agent crashes after producing an artifact but before transitioning `.state`, the `.state` lags behind artifacts. The artifact heuristic fallback in `--audit` Category 2 catches this, but it's a recovery scenario not a normal path.
|
||||
|
||||
## Verdict: PASS — no security or logic flaws that would compromise enforcement.
|
||||
@@ -1,22 +0,0 @@
|
||||
# Bug Report: State File Enforcement
|
||||
|
||||
## Methodology
|
||||
Reviewed status.py implementation of .state file format, approval sub-states, atomic writes, forbidden artifacts per phase, task creation gate, and state transition rules.
|
||||
|
||||
## Acceptance Criteria
|
||||
| # | Criterion | Result |
|
||||
|---|-----------|--------|
|
||||
| 1 | `.state` file format with approval sub-states | ✅ |
|
||||
| 2 | Atomic write mechanism (tmp+rename) | ✅ |
|
||||
| 3 | Forbidden artifacts per phase enforced | ✅ |
|
||||
| 4 | `--validate-folder` flags folders without `.state` | ✅ |
|
||||
| 5 | `--audit` flags manually created task folders | ✅ |
|
||||
| 6 | Task creation gate (`--create-task`) | ✅ |
|
||||
| 7 | Approval sub-states for research/design/decompose/test_design | ✅ |
|
||||
| 8 | `:awaiting_approval` → `:approved` only via `--approve` | ✅ |
|
||||
| 9 | `.state` excluded from artifact heuristics | ✅ |
|
||||
|
||||
## Findings
|
||||
1. **Minor**: The `.gitignore` pattern for `.state` was not explicitly added to a project-level gitignore — it's documented as metadata but not enforced in version control.
|
||||
|
||||
## Verdict: PASS
|
||||
@@ -1,15 +0,0 @@
|
||||
# Doc Review: State File Enforcement
|
||||
|
||||
## Documents Checked
|
||||
| Doc | Status |
|
||||
|-----|--------|
|
||||
| SPEC.md | ✅ Complete — all acceptance criteria defined |
|
||||
| IMPLEMENTATION.md | ✅ Implementation documented |
|
||||
| prompts/orchestrate.md | ✅ Updated to read/write .state |
|
||||
| prompts/workflow.md | ✅ References .state as canonical |
|
||||
| scripts/status.py | ✅ All .state commands implemented |
|
||||
|
||||
## Findings
|
||||
None — .state enforcement is consistently documented across spec, implementation, and prompts.
|
||||
|
||||
## Verdict: PASS
|
||||
@@ -1,50 +0,0 @@
|
||||
# Implementation: State File Enforcement
|
||||
|
||||
## Changes Made
|
||||
|
||||
### 1. `.state` file format (implemented in `scripts/status.py`)
|
||||
- `.state` file contains a single phase name (e.g., `research`, `research:awaiting_approval`, `implement`)
|
||||
- Written atomically via `.state.tmp` → `.state` rename
|
||||
- `.state.approvals` append-only log records all approvals with timestamp and approver
|
||||
- `.state.lock` for multi-agent claiming (optional, only in multi-agent mode)
|
||||
- Non-artifact metadata files (`.state`, `.state.approvals`, `.state.lock`, `.state.tmp`, `VRAM_CONFIG.md`, `PARENT_SPEC.md`, `REVIEW.md`) are excluded from artifact checks
|
||||
|
||||
### 2. State transitions with approval sub-states
|
||||
- Approval-gated phases: research, decomposition, design, test_design now have `:awaiting_approval` → `:approved` sub-states
|
||||
- Non-approval phases: implement, bug_find, adversarial_bug_find, doc_review, referee have no sub-states
|
||||
- `status.py --transition` refuses transitions past `:awaiting_approval` without `--approve`
|
||||
- `status.py --approve` transitions `:awaiting_approval` → `:approved` and records approval in `.state.approvals`
|
||||
|
||||
### 3. Backward compatibility
|
||||
- If `.state` doesn't exist, `status.py` infers phase from artifacts and writes `.state`
|
||||
- `upgrade.sh` bootstraps `.state` for all existing tasks
|
||||
- Phase prompts work with or without `.state` (warns if missing)
|
||||
|
||||
### 4. Forbidden artifacts per phase (implemented in `status.py --validate-folder`)
|
||||
- Each phase has a defined set of artifacts that must NOT exist (artifacts from future phases)
|
||||
- `--validate-folder` checks and reports violations
|
||||
- `--transition` refuses to proceed if forbidden artifacts exist
|
||||
|
||||
### 5. Task creation gate (implemented in `status.py --create-task`)
|
||||
- `--create-task` creates task folder with `.state` = `new` and empty `.state.approvals`
|
||||
- Validates kebab-case task names
|
||||
- Refuses if task already exists
|
||||
- `--audit` Category 4 flags manually created task folders
|
||||
|
||||
### 6. Orchestrator and workflow updates
|
||||
- `prompts/workflow.md` rewritten: `.state` is canonical, approval sub-states documented, `status.py` commands referenced
|
||||
- `prompts/orchestrate.md` reduced from 493 to 143 lines, references `workflow.md` and `subtask_management.md`
|
||||
- All phase prompts include `.state` precondition check
|
||||
|
||||
## Files Modified
|
||||
- `scripts/status.py` (new, 980 lines)
|
||||
- `prompts/workflow.md` (rewritten)
|
||||
- `prompts/orchestrate.md` (rewritten, 143 lines)
|
||||
- `prompts/subtask_management.md` (new, extracted from orchestrate.md)
|
||||
- `tests/test_status.py` (new, 25 tests)
|
||||
- `scripts/upgrade.sh` (new)
|
||||
|
||||
## Test Results
|
||||
- 183 tests passing (including 25 new status.py tests)
|
||||
- Python compilation clean
|
||||
- Shell script syntax clean
|
||||
@@ -1,146 +0,0 @@
|
||||
# SPEC: State File Enforcement
|
||||
|
||||
## Goal
|
||||
Replace the fragile "check which artifacts exist" heuristic for determining task phase with an explicit `.state` file that is the single source of truth for a task's current phase.
|
||||
|
||||
## Background
|
||||
Currently, `orchestrate.md` and `workflow.md` determine a task's phase by checking which artifact files exist in the task folder (e.g., "if SPEC.md exists but not DESIGN.md, the task is in research phase"). This is unreliable because:
|
||||
- Any agent can create any artifact file at any time, bypassing phase ordering
|
||||
- File-existence checks are ambiguous (e.g., overlapping conditions when multiple artifacts exist)
|
||||
- There's no authoritative record of what phase a task is in — every agent has to re-derive it
|
||||
|
||||
## Requirements
|
||||
|
||||
### 1. `.state` file format
|
||||
- Location: `tasks/{task-name}/.state`
|
||||
- Content: a phase name (and optional approval status), one of:
|
||||
- `new`
|
||||
- `research` / `research:awaiting_approval` / `research:approved`
|
||||
- `decomposition` / `decomposition:awaiting_approval` / `decomposition:approved`
|
||||
- `design` / `design:awaiting_approval` / `design:approved`
|
||||
- `test_design` / `test_design:awaiting_approval` / `test_design:approved`
|
||||
- `implement`
|
||||
- `bug_find`
|
||||
- `adversarial_bug_find`
|
||||
- `doc_review`
|
||||
- `referee`
|
||||
- `complete`
|
||||
- `human_intervention`
|
||||
- The base phase name (e.g., `research`) is used for backward compatibility and when approval is not applicable
|
||||
- The `:awaiting_approval` sub-state means the phase artifact has been produced but not yet approved by the user
|
||||
- The `:approved` sub-state means the user has given explicit approval to proceed
|
||||
- Only phases with interactive sign-off requirements use sub-states: research, decomposition, design, test_design
|
||||
- Phases without sign-off (implement, bug_find, adversarial_bug_find, doc_review, referee) use only the base name
|
||||
- The file must be written atomically (write to `.state.tmp`, then rename to `.state`) to prevent partial reads
|
||||
- The file must NOT be listed in task artifact checks — it is metadata, not a deliverable
|
||||
|
||||
### 2. State transitions
|
||||
- Only the Orchestrator (or `status.py`) may write to `.state`
|
||||
- Phase prompts must READ `.state` to confirm they are in the correct phase before acting
|
||||
- Transition rules match the existing state machine in `workflow.md`:
|
||||
- `new` → `research` (when task folder is created)
|
||||
- `research` → `research:awaiting_approval` (when SPEC.md draft is presented for sign-off)
|
||||
- `research:awaiting_approval` → `research:approved` (when user says APPROVED)
|
||||
- `research:approved` → `decomposition` or `design` or `implement` (when SPEC.md is finalized)
|
||||
- `decomposition` → `decomposition:awaiting_approval` (when DECOMPOSITION.md draft is presented)
|
||||
- `decomposition:awaiting_approval` → `decomposition:approved` (when user says APPROVED)
|
||||
- `decomposition:approved` → sub-task research (when DECOMPOSITION.md is finalized)
|
||||
- `design` → `design:awaiting_approval` (when DESIGN.md draft is presented)
|
||||
- `design:awaiting_approval` → `design:approved` (when user says APPROVED)
|
||||
- `design:approved` → `test_design` or `implement` (when DESIGN.md is finalized)
|
||||
- `test_design` → `test_design:awaiting_approval` (when TEST_PLAN.md draft is presented)
|
||||
- `test_design:awaiting_approval` → `test_design:approved` (when user says APPROVED)
|
||||
- `test_design:approved` → `implement` (when TEST_PLAN.md is finalized)
|
||||
- `implement` → `bug_find` (when IMPLEMENTATION.md is produced — no approval needed)
|
||||
- `bug_find` → `adversarial_bug_find` (when BUG_REPORT.md is produced — no approval needed)
|
||||
- `adversarial_bug_find` → `doc_review` (when ADVERSARIAL_BUG_REPORT.md is produced — no approval needed)
|
||||
- `doc_review` → `referee` (when DOC_REVIEW.md is produced — no approval needed)
|
||||
- `referee` → `complete` (when VERDICT.md has PASS)
|
||||
- `referee` → `human_intervention` (when VERDICT.md has FAIL or NEEDS_REVIEW)
|
||||
|
||||
**Approval gate enforcement:**
|
||||
- `status.py --transition` MUST REFUSE to transition past an `:awaiting_approval` sub-state
|
||||
- Only `status.py --approve` can move from `:awaiting_approval` to `:approved`
|
||||
- Only `status.py --transition` from `:approved` can move to the next phase
|
||||
- This makes sign-off enforceable — an agent cannot skip approval and proceed
|
||||
|
||||
### 3. Backward compatibility
|
||||
- If `.state` exists, it is authoritative
|
||||
- If `.state` does not exist, fall back to the artifact-based heuristic (current behavior) and write `.state` with the inferred phase
|
||||
- This ensures existing tasks without `.state` continue to work and get migrated on first access
|
||||
|
||||
### 4. Artifact validation rules (enforced by `status.py`)
|
||||
Each phase has a defined set of artifacts that are ALLOWED and FORBIDDEN in the task folder. These rules are enforced by `status.py --validate-folder` and `status.py --transition`:
|
||||
|
||||
**Forbidden artifacts per phase** (artifacts from future phases — must NOT exist):
|
||||
|
||||
| Phase | Forbidden artifacts |
|
||||
|---|---|
|
||||
| `new` | SPEC.md, DESIGN.md, DECOMPOSITION.md, TEST_PLAN.md, IMPLEMENTATION.md, BUG_REPORT.md, ADVERSARIAL_BUG_REPORT.md, DOC_REVIEW.md, VERDICT.md |
|
||||
| `research` | DESIGN.md, DECOMPOSITION.md, TEST_PLAN.md, IMPLEMENTATION.md, BUG_REPORT.md, ADVERSARIAL_BUG_REPORT.md, DOC_REVIEW.md, VERDICT.md |
|
||||
| `decomposition` | DESIGN.md, TEST_PLAN.md, IMPLEMENTATION.md, BUG_REPORT.md, ADVERSARIAL_BUG_REPORT.md, DOC_REVIEW.md, VERDICT.md |
|
||||
| `design` | DECOMPOSITION.md, TEST_PLAN.md, IMPLEMENTATION.md, BUG_REPORT.md, ADVERSARIAL_BUG_REPORT.md, DOC_REVIEW.md, VERDICT.md |
|
||||
| `test_design` | DECOMPOSITION.md, IMPLEMENTATION.md, BUG_REPORT.md, ADVERSARIAL_BUG_REPORT.md, DOC_REVIEW.md, VERDICT.md |
|
||||
| `implement` | BUG_REPORT.md, ADVERSARIAL_BUG_REPORT.md, DOC_REVIEW.md, VERDICT.md |
|
||||
| `bug_find` | ADVERSARIAL_BUG_REPORT.md, DOC_REVIEW.md, VERDICT.md |
|
||||
| `adversarial_bug_find` | DOC_REVIEW.md, VERDICT.md |
|
||||
| `doc_review` | VERDICT.md |
|
||||
| `referee` | (none) |
|
||||
| `complete` | (none) |
|
||||
| `human_intervention` | (none) |
|
||||
|
||||
**Non-artifact files** are never forbidden: `.state`, `VRAM_CONFIG.md`, `PARENT_SPEC.md`, `REVIEW.md`, `.state.tmp`. These are metadata and can exist at any phase.
|
||||
|
||||
**Enforcement**: When `status.py --transition` is called, it must check for forbidden artifacts BEFORE allowing the transition. If forbidden artifacts exist, the transition is refused with a clear error identifying the offending artifacts.
|
||||
|
||||
### 5. Orchestrator updates
|
||||
- Update `prompts/orchestrate.md`:
|
||||
- State determination section must read `.state` first, falling back to artifact heuristic
|
||||
- After each phase transition, the Orchestrator must write `.state` with the new phase name
|
||||
- The `.state` file must be written BEFORE the orchestrator begins executing the next phase
|
||||
- Update `prompts/workflow.md`:
|
||||
- Add `.state` as the canonical phase indicator
|
||||
- Note that artifact-based heuristic is a fallback only
|
||||
|
||||
### 5. Phase prompt updates
|
||||
- Every phase prompt must include a precondition check:
|
||||
```
|
||||
Read tasks/{task}/.state. If the phase does not match this prompt's phase, STOP and report.
|
||||
```
|
||||
- This is a 2-line addition to each prompt's "Read These Files" section
|
||||
|
||||
### 6. Task creation gate
|
||||
- Task folders MUST be created via `status.py --create-task` (defined in status-script spec)
|
||||
- A valid task folder has a `.state` file with `new` as the initial phase
|
||||
- `--validate-folder` checks that task folders have a `.state` file; folders without `.state` were created manually and should be flagged
|
||||
- `--audit` flags task folders without `.state` as violations: "Task '{task-name}' was created manually (no .state file). Use 'python ~/.automaton/scripts/status.py --create-task' to create tasks properly."
|
||||
|
||||
### 7. Artifact integrity
|
||||
- `.state` is NOT an artifact — it should NOT appear in state determination logic that checks artifact files
|
||||
- `.state` should be added to `.gitignore` patterns (or documented that it's transient metadata)
|
||||
|
||||
## Acceptance Criteria
|
||||
- [ ] `.state` file format is specified and documented (including approval sub-states)
|
||||
- [ ] Approval sub-states defined for research, decomposition, design, test_design
|
||||
- [ ] Approval transition rules defined (`:awaiting_approval` → `:approved` only via `--approve`)
|
||||
- [ ] Transition past `:awaiting_approval` without approval is REFUSED by `--transition`
|
||||
- [ ] Phases without sign-off (implement, bug_find, etc.) use base names only
|
||||
- [ ] Atomic write mechanism is defined (write-to-tmp-then-rename)
|
||||
- [ ] Fallback to artifact heuristic when `.state` doesn't exist is specified
|
||||
- [ ] Forbidden artifacts per phase are defined and documented
|
||||
- [ ] `status.py --validate-folder` enforces forbidden artifacts
|
||||
- [ ] `status.py --transition` refuses transitions when forbidden artifacts exist
|
||||
- [ ] `status.py --validate-folder` flags task folders without `.state` as manually created
|
||||
- [ ] `status.py --audit` flags manually created task folders
|
||||
- [ ] `status.py --create-task` is the only valid way to create task folders
|
||||
- [ ] `orchestrate.md` updated to read/write `.state`
|
||||
- [ ] `workflow.md` updated to reference `.state` as canonical
|
||||
- [ ] All phase prompts include `.state` precondition check
|
||||
- [ ] State transition rules match existing state machine
|
||||
- [ ] `.state` is excluded from artifact-based state determination
|
||||
- [ ] Sub-task `.state` files are scoped to sub-task folders
|
||||
|
||||
## Non-Goals
|
||||
- This spec does not cover the `status.py` script (separate task)
|
||||
- This spec does not cover prompt restructuring with FORBIDDEN sections (separate task)
|
||||
- This spec does not cover autopilot integration (separate task)
|
||||
@@ -1,24 +0,0 @@
|
||||
# VERDICT: State File Enforcement
|
||||
|
||||
|
||||
## Status: PASS
|
||||
## Summary
|
||||
Implemented `.state` file as single source of truth for task phase, with approval sub-states (awaiting_approval/approved), atomic writes, forbidden artifacts per phase, task creation gate, and full transition validation in status.py.
|
||||
|
||||
## Phase Results
|
||||
| Phase | Result |
|
||||
|-------|--------|
|
||||
| Implementation | ✅ PASS |
|
||||
| Bug Find | ✅ PASS (1 minor finding) |
|
||||
| Adversarial Bug Find | ✅ PASS |
|
||||
| Doc Review | ✅ PASS |
|
||||
|
||||
## Findings
|
||||
- All acceptance criteria met
|
||||
- Minor: `.gitignore` pattern for `.state` not explicitly enforced at project level (documented as metadata only)
|
||||
- Minor: Concurrent `--create-task` race condition is theoretically possible but unlikely in practice
|
||||
|
||||
## Final Verdict
|
||||
**PASS** — All acceptance criteria met. The .state file enforcement mechanism is complete and working. All tests pass.
|
||||
|
||||
Score: +10
|
||||
Reference in New Issue
Block a user