hermes/automaton
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Add update mechanism: update.sh script, project upgrade option in onboarding, update instructions in README, Bug 12

Browse Source
This commit is contained in:
gitea
2026-06-10 23:48:43 -04:00
parent 3ac1b0858b
commit a17cbbe304
5 changed files with 104 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files
BUG_REPORT.md
+10 -2
View File
@@ -2,7 +2,7 @@
## Summary
A comprehensive review of the agent-framework project identified **11 bugs** (after removing the visualize*.html files, which eliminated 8 visualization-related bugs). Remaining issues range from critical (Orchestrator is not a real state machine) to low (unused placeholders).
A comprehensive review of the agent-framework project identified **12 bugs** (after removing the visualize*.html files, which eliminated 8 visualization-related bugs). Remaining issues range from critical (Orchestrator is not a real state machine) to low (unused placeholders).
---
@@ -103,6 +103,13 @@ A comprehensive review of the agent-framework project identified **11 bugs** (af
- **Reproduction**: Read `prompts/orchestrate.md`; the "Tasks from bug verdicts" section says "MUST also create new tasks and drive them" in Autopilot mode, but the note says "the Orchestrator should NOT create fix/review/tiebreak tasks from FAIL/NEEDS_REVIEW verdicts — it should pause and let the user decide".
- **Suggested Fix**: **RESOLVED** — Split the section into Manual Mode (create tasks) and Autopilot Mode (pause and report human intervention required).
### Bug 12: No update mechanism for existing projects
- **Severity**: Medium
- **Location**: `README.md`, `install.sh`, `prompts/onboarding.md`
- **Description**: There is no mechanism to update an existing project's framework files when the global framework is updated. The README mentions "Upgrade" as a project type in the onboarding section but has no implementation. The install.sh only mentions `git pull` as a vague update hint. When the framework adds new phases (e.g., Doc Review), existing projects won't have the new prompt files and won't know about them.
- **Reproduction**: User updates the global framework with new phases. Existing projects still only have the old prompt files. The agent doesn't know about the new phases for those projects.
- **Suggested Fix**: **RESOLVED** — Added `update.sh` script for updating the global framework, added "Upgrade" option in onboarding prompt for existing projects, updated README with update instructions.
---
## Score
@@ -120,4 +127,5 @@ A comprehensive review of the agent-framework project identified **11 bugs** (af
| 9 | High | +5 | **RESOLVED** — Dedicated Doc Review phase added between Adversarial Bug Find and Referee |
| 10 | High | +5 | **RESOLVED** — Research and Design phases now interactive with user |
| 11 | Medium | +5 | **RESOLVED** — Split Orchestrator verdict task creation into Manual/Autopilot modes |
| **Total** | | **47** | |
| 12 | Medium | +5 | **RESOLVED** — Added `update.sh` script, upgrade option in onboarding, update instructions in README |
| **Total** | | **52** | |