[BUG] Custom slash command allowed-tools not bypassing authorization prompts for Bash commands

Environment

• Platform (select one):
• [ ] Anthropic API
• [ ] AWS Bedrock
• [ ] Google Vertex AI
• [x] Other: Max Plan
• Claude CLI version: 1.0.73 (Claude Code)
• Operating System: macOS (Darwin 24.5.0)
• Terminal: VS Code integrated terminal

Bug Description

<!-- A clear and concise description of the bug -->
Custom slash command with allowed-tools configuration still prompts for user authorization when executing Bash commands that should be pre-authorized.

<img width="739" height="821" alt="Image" src="https://github.com/user-attachments/assets/c89d4eb1-80f6-4108-969d-3237e51f2484" />

Steps to Reproduce

1. Create a custom slash command at _~/.claude/commands/git-commit.md_ with allowed-tools: Bash(git commit:*) in the frontmatter
2. Run the slash command with /git-commit
3. When the command attempts to execute git commit, it prompts for user authorization despite being in the allowed-tools list

Expected Behavior

<!-- What you expected to happen -->
Commands matching the pattern Bash(git commit:*) should execute without requiring user authorization since they are explicitly listed in the allowed-tools configuration.

Actual Behavior

<!-- What actually happened -->
The system still prompts "Do you want to proceed?" with options to approve or deny the Bash command execution, even though Bash(git commit:*) is in the allowed-tools list.

Additional Context

<!-- Add any other context about the problem here, such as screenshots, logs, etc. -->

• The slash command configuration file is available at: https://github.com/liby/dotfiles/blob/main/.claude/commands/git-commit.md
• The allowed-tools configuration includes: Bash(git commit:*) along with other git-related commands
• This was working correctly in previous versions (exact last working version unknown)
• The issue appears to have started in recent versions