Lap Tran
4a2301b077
- 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
1.3 KiB
Adversarial Bug Report: Autopilot Gate Integration
Deep Review
The gate-check loop in orchestrate.md replaces the previous drive_all() pseudocode with an explicit phase-by-phase process. Each phase is validated before and after. Approval gates are hard stops, not soft suggestions.
Potential Issues
-
Self-approval risk: In autopilot mode, the orchestrator prompt says "STOP and wait for user approval" at approval gates. However, the orchestrator is the same agent that completes the phase. A non-compliant orchestrator could skip the approval gate and call
--approveitself. Mitigation:--approveis designed to require explicit user action, but the enforcement is prompt-based within a single agent session. -
Session context loss at approval pause: When autopilot pauses for user approval and the user returns in a new session, the orchestrator must re-read
.stateto know where it left off. This works correctly but depends on the.statefile being written before the pause. -
No timeout on approval pauses: If the user never returns to approve a phase, the task is stuck in
:awaiting_approvalindefinitely. This is by design (user must approve), but there's no notification mechanism.