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:
@@ -0,0 +1 @@
|
||||
complete
|
||||
@@ -0,0 +1 @@
|
||||
# ADVERSARIAL_BUG_REPORT\n\nNo adversarial issues found.
|
||||
@@ -0,0 +1 @@
|
||||
# BUG_REPORT\n\nNo bugs found.
|
||||
@@ -0,0 +1 @@
|
||||
# DOC_REVIEW\n\nChanges are minimal and well-understood.
|
||||
@@ -0,0 +1,10 @@
|
||||
# IMPLEMENTATION.md — Fix Guard Plugin Derailment
|
||||
|
||||
## Changes Made
|
||||
- `plugins/automaton-guard/plugin.ts:60-65`: Replaced `client.chat()` injection with `throw new Error()`
|
||||
|
||||
## How It Works
|
||||
- When an edit is blocked, the guard now throws an error instead of injecting synthetic user messages
|
||||
- This prevents derailing the agent's context mid-operation
|
||||
- The harness handles the error cleanly without contaminating message history
|
||||
- The error message still includes actionable instructions for creating/transitioning tasks
|
||||
@@ -0,0 +1,4 @@
|
||||
# Review
|
||||
- **Status**: approved
|
||||
- **Timestamp**: 2026-06-15T17:33:42.956856
|
||||
- **Comment**:
|
||||
@@ -0,0 +1,11 @@
|
||||
# Fix Guard Plugin Derailment
|
||||
|
||||
## Problem
|
||||
The automaton-guard plugin (`plugins/automaton-guard/plugin.ts:61-64`) calls `client.chat()` with `role: "user"` when an edit is blocked. This injects synthetic user messages that can derail agent context mid-operation.
|
||||
|
||||
## Fix
|
||||
Replace the `client.chat()` call with returning an error through the output mechanism, using `throw new Error()` or equivalent so the harness handles the rejection cleanly without contaminating the agent's message history.
|
||||
|
||||
## Verification
|
||||
- Guard plugin rejects blocked edits without injecting user messages
|
||||
- Agent context is not contaminated
|
||||
@@ -0,0 +1,3 @@
|
||||
VERDICT: PASS
|
||||
|
||||
All fixes verified. 206 tests pass.
|
||||
Reference in New Issue
Block a user