[BUG] /status slash command freezes terminal UI on macOS — requires process kill to recover

Description

Running the /status slash command inside an active Claude Code session causes the terminal UI to freeze completely. The prompt becomes unresponsive to all input including Ctrl+C and Ctrl+Q. The only recovery is killing the process externally (e.g., tmux respawn-pane -k or kill <pid>).

Environment

• Claude Code version: 2.1.74
• OS: macOS Darwin 25.3.0 (Apple Silicon)
• Terminal: iTerm2 + tmux
• Shell: fish
• Model: claude-opus-4-6

Steps to Reproduce

1. Start a Claude Code session (claude or claude -c)
2. Have an active conversation with some context loaded (MCP servers, memory files, etc.)
3. Run /context to check token usage (works fine)
4. Run /status
5. Terminal freezes -- no response to any input

Expected Behavior

/status should display status information and return to the prompt.

Actual Behavior

• Terminal UI freezes completely
• No response to Ctrl+C, Ctrl+Q, or any keystrokes
• Process remains running (visible via ps aux) but unresponsive
• Must be killed externally

Additional Context

• 4 custom MCP servers were connected at the time
• Context usage was ~28% (56k/200k tokens) at freeze time
• This matches the pattern in #22032 (/plan slash command freeze on macOS) and #17165 (stale status message freeze)
• The freeze appears to be at the Node.js event loop level, not the shell level, which explains why terminal signals don't propagate

Workaround

Kill the process from another terminal/pane:

tmux respawn-pane -t <session>:<window>.<pane> -k