Fix completion-consumption gap in agent workflow

skills/agent-workflow/SKILL.md

@@ -97,6 +97,20 @@ When a worker reports milestone/completion/blocker:
 
 If there is no evidence point yet, do not claim the work has already started; say it is about to start.
 
+## Completion-consumption rule
+If a worker completion/milestone/blocker has already been emitted by runtime or is visible in session history, main must treat that as a consumed-state obligation immediately.
+
+Main must not remain in a "still waiting" posture after worker completion is already visible.
+
+Required steps:
+1. read/confirm the worker result
+2. update task state / CURRENT_STATE
+3. send the user a normal main-authored update (`who / status / output / next`)
+
+Important:
+- runtime auto-announce does not replace main's supervisory duty
+- user seeing the worker result before main summarizes it is a main-process failure, not an acceptable steady state
+
 ## Blocked reasons
 Prefer a short blocked reason label:
 - `launch failure`

skills/execution-agent-dispatch/CHECKLIST.md

@@ -58,3 +58,10 @@ Before main says the task is done:
 - [ ] Basic verification happened when relevant
 - [ ] Caveats/blockers are disclosed
 - [ ] Tao has been updated
+
+## H. Completion-consumption gate
+If worker completion/milestone/blocker already exists in runtime/session history:
+- [ ] Main has explicitly read/confirmed the worker result
+- [ ] CURRENT_STATE reflects the new state
+- [ ] Tao has received a main-authored summary (`who / status / output / next`)
+- [ ] Main is no longer behaving as if it is still waiting for a reply

skills/project-heartbeat/SKILL.md

@@ -97,6 +97,8 @@ If multiple sub-tasks belong to the same project, keep the heartbeat open until
 - Do not keep the heartbeat alive after project closure.
 - Do not claim progress without evidence.
 - Silence is a process problem, not a neutral state.
+- If the latest check finds no new evidence since the previous user-visible update, do not dress that up as `in_progress`; report `blocked`, `launch failure`, or `no change` plainly.
+- Do not keep re-broadcasting stale `CURRENT_STATE` text as if it were fresh execution progress.
 
 ## References
 - For task-state rules and evidence gates: read `../agent-workflow/references/state-machine.md`