stop-hook-false-positive-on-agent-waiting-state

The Stop hook fires repeatedly when the agent sends a minimal message (e.g., ’.’, ‘Holding.’, ‘Paused.’) while awaiting user input mid-skill. The hook evaluates session completion criteria even though no stop() call was initiated — it cannot distinguish ‘agent finished and stopped’ from ‘agent sent a short acknowledgment and is idle’. This caused 30+ false-positive evaluations in a single brainstorming session.

Related

• stop-hook-false-positive-during-active-waiting-state
• stop-hook-false-positive-on-minimal-agent-responses
• stop-hook-fires-on-agent-wait-state-not-just-stop
• stop-hook-false-positive-during-waiting-state
• stop-hook-false-positive-during-agent-waiting-state
• stop-hook-must-check-for-actual-stop-event-not-message-conte
• stop-hook-fires-on-agent-waiting-state-not-only-stop
• stop-hook-fires-false-positives-on-agent-waiting-state
• stop-hook-needs-agent-stop-intent-detection-not-just-event-n
• stop-hook-fires-on-agent-waiting-state-not-just-stop