Feature: Voice input support in permission/approval prompts

Summary

When Claude Code is in voice mode (/voice) and a permission prompt appears (e.g., "Allow this tool? [y/n]", the approval dialog for tool use), voice input is completely inactive. The user must type their response, even though voice mode is enabled and working for the main chat input.

Current Behavior

1. Enable voice mode with /voice
2. Voice works for sending messages to Claude (hold Space to record)
3. Claude proposes a tool use that requires approval
4. The permission/approval prompt appears (e.g., "Do you want to allow Bash?")
5. Voice is not available in this prompt - only keyboard input works
6. User must type y, n, or select an option manually

Expected Behavior

Voice mode should remain active in the permission prompt. The user should be able to hold Space (or their configured PTT key) and say "yes", "allow", "deny", etc. to respond to the approval dialog without switching to the keyboard.

Why This Matters

Voice mode is designed for hands-free interaction. Having to reach for the keyboard every time a tool approval prompt appears breaks the flow. This is especially disruptive because tool approvals happen frequently during normal usage (running bash commands, editing files, etc.), making the keyboard fallback a constant interruption.

Possible Approach

• Detect simple voice responses ("yes", "no", "allow", "deny", "always allow") and map them to the corresponding prompt actions
• Keep the PTT keybinding active when the approval prompt is focused