User-installed mods can no longer lift ask rules from user settings since 2.1.299 (docs and changelog say otherwise)

What happened

Since 2.1.299, a user-installed mod's tool.check allow no longer lifts an ask rule from my own user settings. Worked in 2.1.294; still the case in 2.1.300.

Setup: auto mode, a bare Bash entry in permissions.ask in ~/.claude/settings.json (so every shell command comes to me instead of the auto-mode classifier), and a small user mod loaded via CLAUDE_CODE_PLUGIN_DIRS that answers tool.check with allow for a narrow allowlist of read-only commands (git status/log/diff, gh pr view, grep/cat/ls inside a few folders). Everything else is meant to keep prompting.

Now every Bash call prompts. Debug log:

<mod>: tool.check bypassed by cc-plugin-sec-default (tier user); beneath runs
<mod> tried to lift an ask rule in your settings from a Bash call (Bash); the ask rule holds over the plugins you install (allowModsToOverrideDenyRules)

The mod loads and is admitted (plugin.register: <mod> (user, …), judged by cc-plugin-sec-default: admitted), and its own tests pass.

Why this looks unintended, or at least undocumented

• Changelog 2.1.299 says: "Improved enforcement of managed permission rules, managed hooks and organization MCP tool names against user-installed mods". The rule held here is in user settings, not managed settings.
• Docs ("Manage mods for your organization") say a user's mod can approve a call an ask rule would prompt for, and that allowModsToOverrideDenyRules governs deny rules.
• The only switch named in the log, allowModsToOverrideDenyRules, is managed-only and also loosens deny rules.

Impact

With auto mode, an ask rule is the only way to get a dialog for a tool instead of the classifier. So "this tool always asks me, except what my mod allowlists" has no configuration left:

• keep the ask rule: the mod can't make exceptions;
• drop it: everything not allowlisted goes to the classifier instead of me;
• switch to default mode: every tool without a rule prompts, and the classifier is gone.

Request

Either let a user's mod lift ask rules from the user's own settings again (deny rules keep holding), or add a user-settable option for exactly that, separate from allowModsToOverrideDenyRules. And update the docs and changelog to match whichever behavior is intended.

Version: 2.1.300 (regression from 2.1.294), Linux