When another device takes over your remote session, you're no longer told to reconnect to it.
What's wrong with this entry?
When a remote session ends because another device claimed it, the disconnect notice no longer suggests running /remote-control to reconnect. That advice was pointing you back at a session that had legitimately moved elsewhere.
- The new end reason is raised when the transport closes with a superseded code, or when another connection wins the race to own the session.
another connection took over this session while it was being restored — this device is standing down
Strings lifted out of the shipped bundle, so the claim above can be checked against them.