stop-hook-fires-on-waiting-state-not-only-stop-events
The Stop hook fires repeatedly when the agent is in an active waiting state (awaiting user input mid-session), not only on actual stop() calls. This produces floods of hook evaluations — 25+ consecutive triggers — with no corresponding agent-initiated termination event in the transcript. The hook’s evaluation criteria (‘Before allowing the agent to stop’) cannot be satisfied when no stop action has occurred, making all those invocations false-positives that pollute context.