Non-allowlisted Bash commands silently rejected instead of prompting user

Bug Description

When Bash commands are not in the permissions.allow list in settings.json, they are silently rejected with an exit code (1 or 2) and no output, instead of prompting the user for approval.

Expected Behavior

Non-allowlisted Bash commands should prompt the user to approve or deny execution, as described in the documentation:

"When you attempt to call a tool that is not automatically allowed by the user's permission mode or permission settings, the user will be prompted so that they can approve or deny the execution."

Actual Behavior

Commands not matching any Bash(...) pattern in the allow list return exit code 1 (or exit code 2) with no output and no prompt. The user is never asked to approve or deny.

Steps to Reproduce

1. Configure ~/.claude/settings.json with specific Bash(...) allow patterns (e.g., Bash(git *), Bash(ls *), etc.)
2. Start a Claude Code session
3. Have Claude run a Bash command not in the allow list (e.g., echo "hello", pwd, whoami)
4. Observe: command silently fails with exit code 1, user is never prompted

Environment

• OS: Windows 11 Enterprise 10.0.22631
• Shell: bash (Git Bash)
• Claude Code: latest channel

Additional Context

Commands that do match the allow list work fine (e.g., git --version succeeds). The issue is specifically that non-matching commands are silently swallowed rather than triggering a permission prompt.