CLI shows busy state after response completion, blocking input without ESC interrupt

Preflight Checklist

• [x] I have searched existing issues and this hasn't been reported yet
• [x] This is a single bug report (please file separate reports for different bugs)
• [x] I am using the latest version of Claude Code

What's Wrong?

Title:
CLI shows busy state after response completion, blocking input without ESC interrupt

Body:
## Bug Description

Claude Code CLI continues showing busy state (e.g., "Burrowing... (running stop hooks... 4/6)") after Claude has completed its response and is idle, waiting for the next input.

## Impact

• User cannot type follow-up prompts without pressing ESC
• Pressing ESC cancels/interrupts Claude
• This breaks the core "respond while busy" feature

## Reproduction

1. Send a simple prompt like "hey"
2. Claude responds immediately
3. CLI continues showing busy state with "Burrowing... (running stop hooks...)"
4. User must press ESC to type, which interrupts Claude

## Expected Behavior

Once Claude completes its response and is idle, the CLI should immediately allow user input without showing busy state.

## Environment

• Platform: darwin (macOS)
• Remote: Mac Mini via Tailscale
• Session hooks active (stop hooks running after response)

What Should Happen?

CLI shows busy state after response completion, blocking input without ESC interrupt

Error Messages/Logs

Steps to Reproduce

any prompt sent

Claude Model

None

Is this a regression?

Yes, this worked in a previous version

Last Working Version

_No response_

Claude Code Version

2.1.34

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

Terminal.app (macOS)

Additional Information

_No response_