885e27fbf4
reading the live client's api_key inside _force_reauth races the in-place rotation: a sibling waiter's apply_token_to_client (or the proactive refresh entered via the honcho property) can swap the bearer before the read, so force_refresh_token receives the already-rotated token, disk matches it, and the adopt branch never fires — reproducing the very force-refresh burst this PR removes. _authed_call now snapshots the bearer before invoking the operation and passes that exact token through to force_refresh_token.