Remote Control disconnects now explain the cause, like another device taking over or the session being archived.
What's wrong with this entry?
Code 4090 disconnects now carry a distinct reason each: a newer worker took over, the session is not active, the session was not found, or the client's view of the session is out of date. Each has plain-language text, for example that a session was ended or archived from another device or app.
- The epoch-mismatch handler emits a session-not-active event alongside the existing stale and mismatch events, each now carrying a reason.
- The diagnostic line was reformatted to
worker epoch mismatch (409) reason=....
this session was ended or archived from another device or app (code 4090)
Strings lifted out of the shipped bundle, so the claim above can be checked against them.