You'll noticeTier: how much it should matter to you
2Useful: my rating, 1 to 5
0Signal: worth watching, 1 to 5
Remote ControlArea: what it touches
ImprovementsKind: in v2.1.225,
ImprovementsSection of the release
What
Reconnect recovery no longer forces an OAuth refresh for every handled close code, cutting unnecessary token work on non-auth disconnects.
Details
The per-close-code recovery table (401, 4091, 4093, 4094) gains needsOAuthRefresh, true for 401 and 4094 only.
The flag decides whether to force an OAuth refresh up front, whether to enter the retry loop that prompts for a fresh login, and whether to do a late refresh instead.
The CCR client gained an onRequestAuthOk callback fired on a successful heartbeat, wired through the bridge so the session can mark auth as proven.
Evidence
needsOAuthRefresh
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
