Haven v2.0.2
release notes.

The presence indicator for users other than self in voice channels would rapidly flash. subscribe run fired forever and the trigger [person] write looped back into the effect. This was fixed by untracking the subscribe.

Presence indicators became stale for self upon joining of a voice channel due to being ignored from presence subscriptions for currently joined voice channels. Client stopped listening for presence changes, leaving orphaned presence indicators and no response to the leave from the removed user. The fix for this was to re-order participents to ensure the LiveKit presence wins the race for the active channel.

OccupantRow's wrapper was a plain <span> meaning the ring-2 that draws around the taller box looked oblong. Fix was making the wrapper class="inline-flex rounded-full".

Speaking toggled applyParticipants -> core.voice.setParticipants(newRoster). Nexus setParticipants does this.setState("participants", participants) which as a full replace with new objects. <For each={occupants()}> keyed by object reference -> new object -> tears down and rebuilds OccupantRow -> the open DropdownMenu inside it gets destroyed. Fix was reconciling by userId so existing rows keep the reference and only the changed field updates.

The moment you click join, startConnect sets activeChannel/currentChannelId immediately (phase "connecting"). The reordered memo now says "active channel → use LiveKit participants but LiveKit is empty until the room actually connects. Presence for that channel is simultaneously being excluded/cleared. So for a very brief window, both sources are empty → the roster blinks out visually to users. Fix is to seed LiveKit from presence at connect time so there's no empty gap.