fix(love): allow rejoining a room the client is still recorded in

[nigad]

Description of the issue

ParticipantInfo (who is in which Love room) is written only by the person's own client, on join and on leave, and dropped by the server only when the person goes fully offline. If the client goes away mid-call — page reload, crash, laptop lid, network loss — the LiveKit participant is dropped but the record keeps pointing at the room.

The person then reloads and sees themselves "in" the room with no audio/video. RoomPopup hides Enter room because $myInfo.room === room._id, and the microphone/camera controls need $lkSessionConnected, so there is no way to get the call back. Everyone else keeps seeing them as a member of the room.

Steps to reproduce

1. Join a video room (e.g. All hands) from the office view; confirm audio works.
2. Reload the page (or kill the tab) while in the call.
3. Open the room popup after the reload.

Expected behaviour

The person can re-establish the call (or leave the room).

Actual behaviour

The popup shows the person as a member, offers only Leave, and no media is connected. Server side, the LiveKit log shows participant closing … CLIENT_REQUEST_LEAVE while the ParticipantInfo still has room set to the video room.

Fix

• RoomPopup.svelte: show Enter room whenever no LiveKit session is connected, not only when the record says the person is out.
• meetings.ts: new exported reconnectMeeting(room), which connects directly when the record already places the person in that room. joinMeeting is not used for this case because it would send a knock/join request again for Knock rooms and offices. connectToMeeting's moveToMeetingRoom already returns early when the room is unchanged, so rejoining is only a fresh token and LiveKit connect.

Deliberately no automatic reset on startup: a second tab of the same user would reset the first tab's live call, and the record's sessionId cannot identify the owning tab (it is refreshed on every transactor Reconnected).

A companion PR makes the Love service reset stale records on LiveKit participant_left / room_finished webhooks, so other members stop seeing the ghost without the person doing anything.

Testing

Reproduced on a self-hosted v0.7.432 instance (LiveKit self-hosted). Verified the failure mode from the transactor and livekit-server logs and the transactor REST API; verified that the same ParticipantInfo update the client's own kick() sends clears the state.

Developed with AI assistance; reviewed and tested by the author.

[nigad]

Closing; will be resubmitted from the correct account.