Rivet currently allows a client to present the same resume token again while the preious transport is still being torn down. In normal recconects this is harmless, but during a fast network handoff two transports can briefly race to restore the same subscription state. This affects Northstar because its client reconnect flow can open the replacemnet transport before the previous one has fully disappeared. I'd like to agree on the contract at the Rivet boundary rather than relying on client-side timing.

ight now the reconnect path assumes the remote document still exists. I think a local draft should survive deletion as a recoverable copy instead of disappearing when synchronization resumes.

Extensions currently have no reliable way to distinguish an active connection from reconnecting or offline state. Exposing a small connection-state API would let integrations defer network-dependent actions instead of guessing from failed requests.