Files

T

CI / build (push) Has been cancelled

Details

Archive completed tasks, add cleanup commands, self-documenting dashboard UI

- 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

2026-06-24 22:43:33 -04:00

1.2 KiB

Raw Blame History

BUG_REPORT: add-self-improvement-loop

Findings

Bug 1 (LOW): install.sh loop bootstrap is inside the `else` block

The loop creation commands are inside the else block of if [ -d "$FRAMEWORK_DIR" ], which means they only run on fresh installs. If a user previously installed the framework before this change and runs install.sh again, they get "already installed" and the loop is NOT created. This is correct behavior -- update.sh handles the existing-user case.

Severity: LOW (by design) Fix: None needed.

Bug 2 (INFO): No `--project` flag consistency check

install.sh uses --project "$FRAMEWORK_DIR" while update.sh also uses --project "$FRAMEWORK_DIR". Both are consistent. The work_source.project in the template is "~/.automaton/" (a string), but --create-loop doesn't use work_source.project -- it uses the --project flag. The runner reads work_source.project at tick time. No mismatch because --project "$FRAMEWORK_DIR" (which is $HOME/.automaton) and work_source.project: "~/.automaton/" resolve to the same path.

Severity: INFO (no bug) Fix: None needed.

Summary

No correctness bugs found. One LOW (by design) and one INFO.

Verdict: CLEAN

1.2 KiB Raw Blame History