stop-hook-blocks-pure-planning-sessions-pathological-loop

The session-close stop hook incorrectly blocks termination on pure planning/brainstorming sessions when the agent is awaiting user input mid-workflow. The hook treats ‘structurally incomplete brainstorming step’ as a blocking condition even when zero file modifications occurred. This creates an infinite loop: agent waits → hook fires → hook blocks → agent waits. The hook condition should APPROVE all pure planning sessions with no file changes, regardless of brainstorming workflow state — workflow incompleteness is not the hook’s concern.

Related

• stop-hook-loop-on-mid-workflow-user-silence
• stop-hook-infinite-loop-on-pure-planning-sessions
• stop-hook-blocks-pure-planning-sessions-in-brainstorm-loop
• stop-hook-blocks-indefinitely-on-brainstorming-user-absence
• stop-hook-infinite-loop-during-brainstorming-await
• session-close-phase-1-6-disposition-is-not-resolution
• security-hook-blocks-exec-eval-tokens-in-prose
• subagent-grep-operations-leave-temp-files-in-tmp
• doc-sync-deferral-to-post-checkpoint-is-invalid
• stop-hook-false-positive-during-active-waiting-state
• stop-hook-false-positive-during-waiting-state
• stop-hook-false-positive-loop-on-waiting-state
• stop-hook-false-positive-loop-on-agent-waiting-state