What
Remote Control no longer decides reconnection correctness by comparing registration epochs with a retry budget. It now watches for the session owner changing and re-checks ownership before proceeding.
Details
- Removed: the compare-and-set epoch fence, the worker epoch tracker, the 4090
epoch_staleconflict handler with its per-hour re-registration budget, and the messages about a registration going stale or another connection taking over during restore. - Added: an owner-change subscription, plus an owner-changed check before connect, before handling incoming data, and on token refresh.
- Inbound frames are buffered while an owner check is in flight and drained afterwards; the drain is abandoned if the connection was superseded in the meantime.
- The owner-change path only runs when the owner check reports it applies.
Evidence
owner_changed_recovery
Strings lifted out of the shipped bundle, so the claim above can be checked against them.