A successful Remote Control heartbeat now clears stored auth failures, so you get fewer spurious re-login prompts.
What's wrong with this entry?
A successful bridge heartbeat clears accumulated authentication-failure state instead of leaving the counter to age out on its own.
- the CCR client gained an
onRequestAuthOkoption, invoked next toresetHeartbeatStreak()on each successful heartbeat - the bridge supplies a callback that resets its auth-failure counter and calls the existing
onAuthProvenhook
onRequestAuthOk
Strings lifted out of the shipped bundle, so the claim above can be checked against them.