Under the hood
Useful2 Signal3
Remote bridge disconnects now use distinct close codes for session problems versus expired tokens.
What's wrong with this entry?
Anonymous. No account, no email.
What
When the remote-control connection hits a terminal request-path condition, the close code now reflects the cause: session or epoch problems close with 4090, expired or exhausted tokens with 4094.
Details
- Both places that build the client opt into typed close codes, so the mapping is what runs; the untyped path still closes with 4090 for everything.
Evidence
terminal request-path condition
Strings lifted out of the shipped bundle, so the claim above can be checked against them.