fix(#23): guard channel-state mutators against post-disconnect persistence
disconnect() never resets the channel store scope (publicKeyHex), so a channel write in the post-disconnect async gap still persists -- to the last radio's scope, and into a different radio's scope after reconnecting (cross-radio bleed). Add if (!isConnected) return; to the UI-triggered persisters setChannelUnreadCount, markChannelRead, setChannelOrder. Chosen over clearing _channels, which would risk a racing mutator persisting an empty list and wiping stored channels. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>pull/56/head
parent
79b1780648
commit
5687916192
Loading…
Reference in new issue