fix(realtime): gate isReady() on loaded script SHAs, not just connection

Follow-up to the prior isConnected change, which was incomplete: the redis client's
'ready' event flips isConnected=true on connect — before initialize() loads the Lua
scripts — so a bare isConnected check reports ready while removeUserFromRoom /
updateUserActivity would silently no-op on a null SHA. Gate isReady() on the SHAs
too, so the POST endpoints return a retryable 503 during that startup window instead
of proceeding against unloaded scripts. Standard readiness-probe discipline.

Author: waleedlatif1

apps/realtime/src/rooms/redis-manager.ts

@@ -160,7 +160,14 @@ export class RedisRoomManager implements IRoomManager {
   }
 
   isReady(): boolean {
-    return this.isConnected
+    // Gate on the loaded script SHAs, not just the connection: the `ready` event flips
+    // `isConnected` true as soon as the socket connects — before `initialize()` loads the Lua
+    // scripts — so a bare `isConnected` check would report ready while `removeUserFromRoom` /
+    // `updateUserActivity` would silently no-op on a null SHA. Reporting not-ready here makes the
+    // POST endpoints return a retryable 503 during that startup window instead.
+    return (
+      this.isConnected && this.removeRoomScriptSha !== null && this.updateActivityScriptSha !== null
+    )
   }
 
   async initialize(): Promise<void> {