A session taken over on another device is now reported as such instead of a generic disconnect.
What's wrong with this entry?
Close codes from the remote session connection now map to named outcomes in a shared table, so a session that was taken over elsewhere is reported as ended elsewhere rather than as a generic transport close.
- Taken over by a worker maps to superseded; an inactive session maps to archived; epoch conflicts, missing causes, 403 and 404 map to an unknown supersession.
session_not_active
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.