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:
@@ -1 +0,0 @@
|
||||
complete
|
||||
@@ -1,9 +0,0 @@
|
||||
# Adversarial Bug Report: SPEC.md Content in Task Detail Panel
|
||||
|
||||
## Deep Review
|
||||
spec_content is read from the task's SPEC.md file and rendered in a `<pre>` tag via `escapeHtml()`.
|
||||
|
||||
## Potential Issues
|
||||
1. **XSS**: content is escaped via `escapeHtml()` before innerHTML assignment. Safe.
|
||||
|
||||
## Verdict: PASS
|
||||
@@ -1,15 +0,0 @@
|
||||
# Bug Report: SPEC.md Content in Task Detail Panel
|
||||
|
||||
## Methodology
|
||||
Reviewed app.py API and dashboard.js renderDetail().
|
||||
|
||||
## Acceptance Criteria
|
||||
| # | Criterion | Result |
|
||||
|---|-----------|--------|
|
||||
| 1 | SPEC.md content in detail panel | ✅ |
|
||||
| 2 | API serves spec_content | ✅ |
|
||||
|
||||
## Findings
|
||||
None.
|
||||
|
||||
## Verdict: PASS
|
||||
@@ -1,11 +0,0 @@
|
||||
# Doc Review: SPEC.md Content in Task Detail Panel
|
||||
|
||||
## Documents Checked
|
||||
| Doc | Status |
|
||||
|-----|--------|
|
||||
| automaton/dashboard/README.md | ❌ Missing — no spec display mention |
|
||||
|
||||
## Findings
|
||||
1. **Missing**: Dashboard README could mention specification viewing.
|
||||
|
||||
## Verdict: PASS (finding noted)
|
||||
@@ -1,17 +0,0 @@
|
||||
# Implementation: SPEC.md Content in Task Detail Panel
|
||||
|
||||
## Summary
|
||||
|
||||
Added SPEC.md content display in the task detail panel so reviewers can see the specification when reviewing a task.
|
||||
|
||||
## Changes Made
|
||||
|
||||
### Backend (`app.py`)
|
||||
- `_serve_tasks()` and `_serve_task()` now include `spec_content` field from the task's SPEC.md
|
||||
|
||||
### Frontend (`dashboard.js`)
|
||||
- `renderDetail()` renders SPEC.md content in a "Specification" section using `<pre class="detail-content-text">`
|
||||
|
||||
## Files Modified
|
||||
- `automaton/dashboard/ui/app.py` — added spec_content to API responses
|
||||
- `automaton/dashboard/html/dashboard.js` — renders specification section in detail panel
|
||||
@@ -1,3 +0,0 @@
|
||||
# Review
|
||||
- **Status**: approved
|
||||
- **Timestamp**: 2026-06-13T18:04:55.062654
|
||||
@@ -1,19 +0,0 @@
|
||||
# SPEC: Display SPEC.md Content in Task Detail Panel
|
||||
|
||||
## Overview
|
||||
|
||||
The task detail panel shows verdict and bug report content but not the task's SPEC.md. Users need to see the specification when reviewing a task.
|
||||
|
||||
## Changes
|
||||
|
||||
- Add `spec_content` field to API responses (`_serve_tasks`, `_serve_task`)
|
||||
- Display SPEC.md content in the detail panel under a "Specification" section
|
||||
|
||||
## Acceptance Criteria
|
||||
|
||||
- [ ] SPEC.md content appears in detail panel
|
||||
- [ ] API serves `spec_content` for all tasks
|
||||
|
||||
## VERDICT
|
||||
|
||||
PASS — implemented in commit 01d8451
|
||||
@@ -1,17 +0,0 @@
|
||||
# VERDICT: SPEC.md Content in Task Detail Panel
|
||||
|
||||
|
||||
## Status: PASS
|
||||
## Summary
|
||||
Added SPEC.md content display in the task detail panel so reviewers can see the specification inline.
|
||||
|
||||
## Phase Results
|
||||
| Phase | Result |
|
||||
|-------|--------|
|
||||
| Implementation | ✅ PASS |
|
||||
| Bug Find | ✅ PASS |
|
||||
| Adversarial Bug Find | ✅ PASS |
|
||||
| Doc Review | ✅ PASS (1 doc finding) |
|
||||
|
||||
## Final Verdict
|
||||
**PASS** — All acceptance criteria met.
|
||||
Reference in New Issue
Block a user