After a network drop, sessions re-register automatically, but only a limited number of times per hour.
What's wrong with this entry?
After a network interruption, a bridge session that comes back to a conflict now re-registers instead of giving up, but no more than a fixed number of times per hour. Past that it stops with an explicit message.
- Worker registration uses compare-and-swap fencing so a stale connection cannot overwrite a newer one.
- If another connection has genuinely taken the session over, this device stands down and says so rather than retrying.
another connection took over this session while it was being restored \u2014 this device is standing down
Strings lifted out of the shipped bundle, so the claim above can be checked against them.