Under the hood
The internal 401 (unauthorized) recovery routine can now report its result back to the caller
What
The internal routine that tries to recover when a request fails with a 401 (unauthorized) error can now take an optional callback function that is told the actual outcome of the refresh attempt, instead of only returning a simple true/false. This is intended for callers such as SDK-style, non-interactive consumers that need to know the specific result rather than just whether recovery succeeded.
Why
This lets programmatic integrations react more precisely to authentication failures instead of only learning that something went wrong.