A new branch in the API-error handler can emit "grant_refused" telemetry under a "safeguards_skip" event with a message built from the error, but the checks that would trigger it currently always return false and an empty string, so the branch is unreachable in this build.
New "safeguards" grant-refused error path (currently inert)
A 'grant refused' safeguards error path exists but its triggering checks always return false.
Nothing to try yetTier: how much it should matter to you
2Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
ElsewhereArea: what it touches
In DevelopmentKind: in v2.1.261,
In DevelopmentSection of the release