Confirmed that refreshing the page does not reproduce it. It only happens when the transport changes underneath the existing client state, so this looks specific to reconnect rather than initial join.

The important part is that reconnect must not silently clear the editor before the deletion state is surfaced. Recovery can be simple as long as the content survives.

I strongly prefer preserving the draft locally. Remote deletion should remove the shared document, not destroy text the user still has in an unsynchronized editor.

I can reproduce this when switching from Wi-Fi to Ethernet with the tab in the background. The new socket joins immediately, but the old presence entry survives until its timeout expires.

I can reproduce this after leaving a tab suspended for about ten minutes. The reconnect loop starts immediately after subscriptions are restored. Disabling session restoration prevents it.