When another session takes over remotely, this one now closes down as superseded properly.
What's wrong with this entry?
When a remote session's connection closed with a code indicating another session took over, teardown now acts on it: codes 4090 with an epoch conflict, 403 and 404 mark the session superseded and suppress the archive, with a log line recording the decision.
- Where the specific cause is unclear, the session is marked superseded with an unknown reason rather than archived.
[remote-bridge] Teardown latched a stashed supersession close (
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.