peter/devclaw-gitea
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs: remove outdated scheduler tick references from AGENTS.md template (#177) (#178)

Browse Source
This commit is contained in:
Lauren ten Hoor
2026-02-13 21:04:16 +08:00
committed by GitHub
parent be3095bbe9
commit 64138b04bf
1 changed files with 3 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
lib/templates.ts
View File

@@ -138,7 +138,7 @@ All orchestration goes through these tools. You do NOT manually manage sessions,
| \`status\` | Task queue and worker state per project (lightweight dashboard) | | \`status\` | Task queue and worker state per project (lightweight dashboard) |
| \`health\` | Scan worker health: zombies, stale workers, orphaned state. Pass fix=true to auto-fix | | \`health\` | Scan worker health: zombies, stale workers, orphaned state. Pass fix=true to auto-fix |
| \`work_start\` | End-to-end: label transition, level assignment, session create/reuse, dispatch with role instructions | | \`work_start\` | End-to-end: label transition, level assignment, session create/reuse, dispatch with role instructions |
| \`work_finish\` | End-to-end: label transition, state update, issue close/reopen. Ticks scheduler after completion. | | \`work_finish\` | End-to-end: label transition, state update, issue close/reopen |
### Pipeline Flow ### Pipeline Flow
@@ -171,14 +171,14 @@ Evaluate each task and pass the appropriate developer level to \`work_start\`:
### When Work Completes ### When Work Completes
Workers call \`work_finish\` themselves — the label transition, state update, and audit log happen atomically. After completion, \`work_finish\` ticks the scheduler to fill free slots: Workers call \`work_finish\` themselves — the label transition, state update, and audit log happen atomically. The heartbeat service will pick up the next task on its next cycle:
- DEV "done" → issue moves to "To Test" → scheduler dispatches QA - DEV "done" → issue moves to "To Test" → scheduler dispatches QA
- QA "fail" → issue moves to "To Improve" → scheduler dispatches DEV - QA "fail" → issue moves to "To Improve" → scheduler dispatches DEV
- QA "pass" → Done, no further dispatch - QA "pass" → Done, no further dispatch
- QA "refine" / blocked → needs human input - QA "refine" / blocked → needs human input
The response includes \`tickPickups\` showing any tasks that were auto-dispatched. **Always include issue URLs** in your response — these are in the \`announcement\` fields. **Always include issue URLs** in your response — these are in the \`announcement\` fields.
### Prompt Instructions ### Prompt Instructions