fix(room): ensure WS connect before subscribe; reactions load for IDB path

- setup() now awaits client.connect() before subscribeRoom and loadMore,
  ensuring the connection is truly open so WS is used for both
- subscribeRoom / reactionListBatch: already WS-first via RoomWsClient.request()
- IDB paths (initial + loadMore) now call thisLoadReactions to batch-fetch
  reactions via WS with HTTP fallback, fixing the missing reactions bug

src/contexts/room-context.tsx

@@ -241,19 +241,19 @@ export function RoomProvider({
     if (!activeRoomId || !client) return;
 
     const setup = async () => {
-      if (client.getStatus() !== 'open') {
+      // Ensure WS is open before subscribing. connect() is idempotent — if already
-        await client.connect();
+      // connecting/open, it returns immediately. While connecting, messages load from
-      }
+      // IDB (instant) and reactions batch-fetch via WS-first request().
-      // Re-check: activeRoomId may have changed while we were waiting for connect.
+      await client.connect();
-      // Use activeRoomIdRef to get the *current* room, not the stale closure value.
+      // Guard: room may have changed while we were waiting for connect.
-      const roomId = activeRoomIdRef.current;
+      if (activeRoomIdRef.current !== activeRoomId) return;
-      if (!roomId) return;
+      // subscribeRoom is WS-first with HTTP fallback; failure is non-fatal.
-      await client.subscribeRoom(roomId);
+      client.subscribeRoom(activeRoomId).catch(() => {});
-      // loadMoreRef.current is null on first mount (set later in render order).
+      // loadMore checks IDB first (no WS needed), then batch-fetches reactions
-      // Call loadMore directly to ensure initial message fetch always runs.
+      // via WS with HTTP fallback. Safe to call without awaiting.
       loadMore(null);
     };
-    setup();
+    setup().catch(() => {});
 
     return () => {
       client.unsubscribeRoom(activeRoomId).catch(() => {});