You'll notice
Useful3 Signal0
When the auto-mode classifier can't decide, you no longer get a bogus denial message or permission-rule hint.
What's wrong with this entry?
Anonymous. No account, no email.
What
A permission decision that the classifier could not produce a verdict for is now tracked separately from a real denial, so telemetry and UI stop treating a classifier failure as a refusal.
Details
- The decision reason carries a new
noVerdictflag. - Denial-reason bucketing keys off the flag instead of matching a message prefix; telemetry labels are assembled at runtime as
classifier:${e.classifier}:no-verdictaround the literal:no-verdict. - The UI denial kind
automode-parsing-erroris now chosen byt.noVerdict. - The 'add a Bash permission rule' hint and the post-denial hook message are both skipped for no-verdict cases.
Evidence
noVerdict
Strings lifted out of the shipped bundle, so the claim above can be checked against them.