stop-hook-fires-on-idle-wait-not-just-agent-stop

The Stop hook fires repeatedly during active waiting states (agent mid-brainstorm waiting for user input) — not only when the agent explicitly initiates a stop() call. This causes a false-positive loop where the hook evaluates session completion criteria against a non-existent stop event, flooding the transcript with feedback messages. The hook condition ‘before allowing the agent to stop’ is being triggered by idle/yield states rather than true agent termination requests.

Related

• stop-hook-false-positive-during-waiting-state
• stop-hook-false-positive-during-active-wait-state
• stop-hook-fires-false-positives-on-agent-waiting-state
• stop-hook-false-positive-on-waiting-state
• stop-hook-false-positive-loop-on-waiting-state
• stop-hook-fires-on-waiting-state-not-just-on-stop
• stop-hook-fires-during-active-waiting-state-false-positive-l