Under the hood
Useful2 Signal2
The fast-path check now records why it declined; the decisions are unchanged.
What's wrong with this entry?
Anonymous. No account, no email.
What
The check that decides whether a request can use the fast gateway path now returns a reason along with its yes/no answer, so refusals can be reported in diagnostics. The answers themselves are unchanged.
Details
- Reasons:
unpinned_gateway,third_party_provider,custom_base_url,sandboxed_entrypoint,unsupported_subscription,no_auth.
Evidence
sandboxed_entrypoint
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.232
Cache-break diagnostics kept in a per-session file
Both mention diagnostic
-
v2.1.232
One-shot warnings share a single claim registry
Both mention diagnostic
-
v2.1.232
One registry now backs every "warn about this once" case
Both mention diagnostic