[FEATURE] Title: Permission prompt should indicate which settings file to edit

Preflight Checklist

• [x] I have searched existing requests and this feature hasn't been requested yet
• [x] This is a single feature request (not multiple features)

Problem Statement

Title: Permission prompt should indicate which settings file to edit

Description:

When Claude prompts for bash permission approval, there's no indication of:

1. Which settings file would satisfy this permission (local vs global, .json vs .local.json)
2. The correct syntax to add to that file
3. Whether an existing rule almost-matched but failed

Current behavior:
Prompt just says "Allow [command]? (y/n)"

Suggested improvement:
Allow "git commit -m ..."?
[y] Yes, this time
[a] Always (add to .claude/settings.local.json)
[t] Always for team (add to .claude/settings.json)
[n] No

To allow manually, add to settings.json:
"Bash(git commit *)"

Impact: Users can't easily build up their permission config without trial-and-error or reading docs.

Proposed Solution

Title: Permission prompt should indicate which settings file to edit

Description:

When Claude prompts for bash permission approval, there's no indication of:

1. Which settings file would satisfy this permission (local vs global, .json vs .local.json)
2. The correct syntax to add to that file
3. Whether an existing rule almost-matched but failed

Current behavior:
Prompt just says "Allow [command]? (y/n)"

Suggested improvement:
Allow "git commit -m ..."?
[y] Yes, this time
[a] Always (add to .claude/settings.local.json)
[t] Always for team (add to .claude/settings.json)
[n] No

To allow manually, add to settings.json:
"Bash(git commit *)"

Impact: Users can't easily build up their permission config without trial-and-error or reading docs.

Alternative Solutions

_No response_

Priority

Low - Nice to have

Feature Category

CLI commands and flags

Use Case Example

_No response_

Additional Context

_No response_