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,11 +0,0 @@
|
||||
# Adversarial Bug Report: Additive Extension Model
|
||||
|
||||
## Deep Review
|
||||
The global-first read order in orchestrate.md is correct. The extension loading order (after global for prompts/contracts, before global for scripts) makes sense — scripts need pre-processing hooks.
|
||||
|
||||
## Potential Issues
|
||||
1. **Extension conflict**: If two extensions define the same file, the later one silently wins. No merge logic exists. This is by design (additive overrides), but could confuse users.
|
||||
|
||||
2. **Script ordering**: Extensions loaded before global scripts (`pre-processing`). If a global script evolves and the extension was written for an older version, behavior could break silently.
|
||||
|
||||
## Verdict: PASS — no security or logic flaws.
|
||||
@@ -1,21 +0,0 @@
|
||||
# Bug Report: Additive Extension Model
|
||||
|
||||
## Methodology
|
||||
Reviewed all modified files against SPEC requirements.
|
||||
|
||||
## Acceptance Criteria
|
||||
| # | Criterion | Result |
|
||||
|---|-----------|--------|
|
||||
| 1 | orchestrate.md reads from global first | ✅ |
|
||||
| 2 | orchestrate.md checks extensions/ | ✅ |
|
||||
| 3 | onboarding.md no diff/merge upgrade | ✅ |
|
||||
| 4 | onboarding.md creates minimal files | ✅ |
|
||||
| 5 | onboarding.md documents extensions/ | ✅ |
|
||||
| 6 | update.sh does simple git pull | ✅ |
|
||||
| 7 | README.md describes new model | ✅ |
|
||||
| 8 | No regression in prompt/contract/script behavior | ✅ |
|
||||
|
||||
## Findings
|
||||
1. **Minor**: `references/extensions.md` noted in SPEC but not created — no functional impact, documented elsewhere.
|
||||
|
||||
## Verdict: PASS
|
||||
@@ -1,15 +0,0 @@
|
||||
# Doc Review: Additive Extension Model
|
||||
|
||||
## Documents Checked
|
||||
| Doc | Status |
|
||||
|-----|--------|
|
||||
| README.md | ✅ Updated (lines 33-41) |
|
||||
| prompts/onboarding.md | ✅ Updated (migration check, extensions doc) |
|
||||
| prompts/orchestrate.md | ✅ Updated (global-first precedence) |
|
||||
| scripts/update.sh | ✅ Simplified to git pull |
|
||||
| CHANGELOG.md | ✅ Entry added |
|
||||
|
||||
## Findings
|
||||
None — extension model documented in 3 places with consistent messaging.
|
||||
|
||||
## Verdict: PASS
|
||||
@@ -1,34 +0,0 @@
|
||||
# Implementation: Additive Extension Model
|
||||
|
||||
## Summary
|
||||
|
||||
Replaced the diff/merge upgrade process with an additive extension model. Projects no longer copy framework files — they provide overrides via `.agent.md`, `.rules.md`, and an optional `extensions/` directory.
|
||||
|
||||
## Changes Made
|
||||
|
||||
### `prompts/orchestrate.md`
|
||||
- Base framework files (prompts, contracts, scripts) now always read from `~/.automaton/`
|
||||
- Projects provide additive extensions under `{project}/.automaton/extensions/`
|
||||
- Extension read order: project extensions loaded after (or before for scripts) corresponding global files
|
||||
- `.agent.md` and `.rules.md` remain layered (project override first)
|
||||
|
||||
### `prompts/onboarding.md`
|
||||
- Removed the diff/merge "Project Upgrade" section
|
||||
- Simplified to create minimal `.agent.md` and `.rules.md` if missing
|
||||
- Documents the `extensions/` directory pattern
|
||||
- Explicitly states projects should never copy framework files
|
||||
|
||||
### `scripts/update.sh`
|
||||
- Simplified to plain `git pull origin main`
|
||||
- Removed `reset hard HEAD` step — never touches project directories
|
||||
|
||||
### `README.md`
|
||||
- Updated "Upgrading existing projects" section for the additive model
|
||||
- Documents the `extensions/` directory pattern
|
||||
- Migration path for old-model projects
|
||||
|
||||
## Files Modified
|
||||
- `prompts/orchestrate.md` — reordered read precedence, added extension checks
|
||||
- `prompts/onboarding.md` — removed diff/merge section, simplified setup
|
||||
- `scripts/update.sh` — simplified to plain git pull
|
||||
- `README.md` — documented new upgrade model
|
||||
@@ -1,3 +0,0 @@
|
||||
# Review
|
||||
- **Status**: approved
|
||||
- **Timestamp**: 2026-06-13T18:13:50.828495
|
||||
@@ -1,69 +0,0 @@
|
||||
# SPEC: Additive Extension Model for Project Upgrades
|
||||
|
||||
## Overview
|
||||
|
||||
Replace the current diff/merge upgrade process with a simpler additive extension model. Projects should never copy framework files. Instead, they provide overrides via `.agent.md`, `.rules.md`, and an optional `extensions/` directory. Updating the framework becomes a simple `git pull` with no project-level file comparison.
|
||||
|
||||
## Motivation
|
||||
|
||||
The current design has a design-vs-reality gap:
|
||||
|
||||
| Design Intent | Reality |
|
||||
|---|---|
|
||||
| Projects only have `.agent.md` + `.rules.md` | Projects have full copies of framework files |
|
||||
| Additive overrides only | Diff/merge required on upgrade |
|
||||
| Simple `git pull` update | Complex file-by-file comparison |
|
||||
|
||||
The root cause: `orchestrate.md` reads prompts/contracts/scripts from the **project first**, then falls back to global. This encourages copying files into the project, which breaks the clean separation.
|
||||
|
||||
## Required Changes
|
||||
|
||||
### 1. `prompts/orchestrate.md`
|
||||
|
||||
Remove the project-first fallback for prompts, contracts, and scripts. The Orchestrator should:
|
||||
- Always read base prompts/contracts/scripts from `~/.automaton/` (global)
|
||||
- Check `{project}/.automaton/extensions/` for additive extensions (not replacements)
|
||||
- Specific extension files to check:
|
||||
- `{project}/.automaton/extensions/prompts/*.md` - loaded after the corresponding global prompt
|
||||
- `{project}/.automaton/extensions/contracts/*.md` - loaded after global contracts
|
||||
- `{project}/.automaton/extensions/scripts/*.sh` - loaded before global scripts (to allow pre-processing)
|
||||
- The read order for `.agent.md` stays layered (project override is correct for routing)
|
||||
|
||||
### 2. `prompts/onboarding.md`
|
||||
|
||||
- Remove the "Project Upgrade" section (lines 99-155) that performs diff/merge
|
||||
- Simplify to: if `.agent.md` or `.rules.md` are missing, create minimal defaults
|
||||
- Add documentation for the `extensions/` directory pattern
|
||||
- Remove any instructions that copy framework files into the project
|
||||
|
||||
### 3. `scripts/update.sh`
|
||||
|
||||
- Simplify: remove the reset hard HEAD step. Just `git pull` with a clean working tree check.
|
||||
- Ensure it only touches `~/.automaton/`, never project directories
|
||||
|
||||
### 4. `README.md`
|
||||
|
||||
- Update the "Upgrading existing projects" section to describe the new additive model
|
||||
- Document the `extensions/` directory pattern
|
||||
|
||||
## Acceptance Criteria
|
||||
|
||||
- [ ] `prompts/orchestrate.md` reads prompts/contracts/scripts from `~/.automaton/` first, not from project
|
||||
- [ ] `prompts/orchestrate.md` checks `{project}/.automaton/extensions/` for additive extensions
|
||||
- [ ] `prompts/onboarding.md` no longer has diff/merge upgrade logic
|
||||
- [ ] `prompts/onboarding.md` creates minimal `.agent.md` and `.rules.md` if missing
|
||||
- [ ] `prompts/onboarding.md` documents the `extensions/` directory
|
||||
- [ ] `scripts/update.sh` does a simple `git pull` without resetting local changes
|
||||
- [ ] `README.md` describes the new upgrade model
|
||||
- [ ] No existing prompt/contract/script behavior is broken (regression check)
|
||||
|
||||
## Non-Goals
|
||||
|
||||
- Moving the dashboard (`automaton/dashboard/`) - it already reads from `~/.automaton/` at runtime
|
||||
- Changing how `config.md` is read (already always global per `orchestrate.md` line 15)
|
||||
- Changing the task directory structure
|
||||
|
||||
## Notes
|
||||
|
||||
- The `invest-copilot` project has a full copy of the framework in its `.automaton/` - this task should include a migration path to clean it up
|
||||
- The extension model should be documented in `references/extensions.md` as well
|
||||
@@ -1,17 +0,0 @@
|
||||
# VERDICT: Additive Extension Model
|
||||
|
||||
|
||||
## Status: PASS
|
||||
## Summary
|
||||
Replaced diff/merge upgrade with additive extension model. Projects never copy framework files; they extend via `.agent.md`, `.rules.md`, and `extensions/`.
|
||||
|
||||
## Phase Results
|
||||
| Phase | Result |
|
||||
|-------|--------|
|
||||
| Implementation | ✅ PASS |
|
||||
| Bug Find | ✅ PASS (1 minor finding) |
|
||||
| Adversarial Bug Find | ✅ PASS |
|
||||
| Doc Review | ✅ PASS |
|
||||
|
||||
## Final Verdict
|
||||
**PASS** — All acceptance criteria met. The extensions model is consistently documented across orchestrate.md, onboarding.md, and README.md.
|
||||
Reference in New Issue
Block a user