diff --git a/lib/templates.ts b/lib/templates.ts
index 19d6d9f..cd5647d 100644
--- a/lib/templates.ts
+++ b/lib/templates.ts
@@ -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) |
 | \`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_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
 
@@ -171,14 +171,14 @@ Evaluate each task and pass the appropriate developer level to \`work_start\`:
 
 ### 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
 - QA "fail" → issue moves to "To Improve" → scheduler dispatches DEV
 - QA "pass" → Done, no further dispatch
 - 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