stop-hook-loop-on-mid-workflow-user-silence
The stop hook’s ‘structural incompleteness’ criterion (brainstorming step awaiting user input = BLOCK) conflicts with its ‘pure planning sessions APPROVE’ criterion, creating an infinite blocking loop when users are unresponsive mid-workflow. The hook fired 30+ times in a single session with no escape path. Stop hook logic needs an override: if the session has zero file modifications AND user has not responded for N cycles, APPROVE regardless of workflow step.
Related
- stop-hook-brainstorming-skill-deadlock-loop
- stop-hook-brainstorm-workflow-infinite-block-pattern
- stop-hook-blocks-indefinitely-on-brainstorming-user-absence
- brainstorming-hardgate-blocks-stop-hook-creating-loop
- brainstorming-skill-hardgate-overrides-stop-hook-pure-planni
- pine-script-vps-deployment-impossible
- stop-hook-infinite-loop-when-brainstorming-awaits-user-input
- stop-hook-blocks-pure-planning-sessions-infinite-loop
- pine-script-default-rr-ratio-is-negative
- stop-hook-blocks-pure-planning-sessions-in-brainstorm-loop
- stop-hook-infinite-loop-on-pure-planning-sessions
- stop-hook-infinite-loop-during-brainstorming-await
- stop-hook-blocks-mid-stream-brainstorming-sessions
- stop-hook-blocks-on-brainstorming-mid-flow
- stop-hook-brainstorming-workflow-infinite-loop
- stop-hook-blocks-pure-planning-sessions-pathological-loop
- session-close-phase-1-6-disposition-is-not-resolution
helix-repository-at-arj999-helix-private(archived)- parallel-subagent-temp-artifacts-require-explicit-cleanup
- ucg-must-be-explicitly-invoked-not-implied