[FEATURE] Show which `permissions.allow` rules auto mode ignores when the session starts

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

On entering auto mode, allow rules that could bypass the classifier are ignored, and nothing says which of my rules were affected. Ignoring them is documented (https://code.claude.com/docs/en/permission-modes); this request is only about seeing it happen.

In a claude -p session (version 2.1.296, "defaultMode": "auto") the only sign was one debug log line, visible only with claude -p --debug-file <path>:

Ignoring dangerous permission Bash(python3 -m py_compile *) from ~/.claude/settings.json (bypasses classifier)

settings.json still lists the rule, so it reads as active, while every matching command goes to the classifier. I had added the rule to save classifier calls and found out it had no effect only by reading the debug log.

Proposed Solution

When a session enters auto mode and ignores one or more allow rules, print one line that names them, for example:

auto mode: ignoring 1 allow rule (bypasses classifier): Bash(python3 -m py_compile *)

In an interactive session this can be a startup notice; in a claude -p session, a line on stderr.

Alternative Solutions

Mark such rules as ignored in the /permissions list. That shows the state when I go and look, but not at the moment a rule stops working.

Priority

Low - Nice to have

Feature Category

Configuration and settings

Use Case Example

I add Bash(python3 -m py_compile *) to permissions.allow in my user settings, start a session in auto mode and run python3 -m py_compile tool.py. With the notice, I see at startup that the rule is ignored and can remove it. Today I see nothing, and the command goes to the classifier as before.

Additional Context

Related: #101613 asks for a way to write such a rule so that it can stay in effect in auto mode.