fix: respect enabled flag in useArcadeGuard WebSocket redirects

The useArcadeGuard hook was ignoring the enabled flag for WebSocket
redirects, causing unwanted navigation from /arcade-rooms to /arcade/room.

When enabled=false (used by PageWithNav), the hook should only track
session state without triggering redirects.

Changes:
- Check enabled flag before redirecting in WebSocket onSessionState
- Check enabled flag before redirecting in HTTP checkSession
- Allows room management pages to use PageWithNav without redirects

Fixes the issue where visiting /arcade-rooms with an active game
session would immediately redirect to /arcade/room.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>

apps/web/src/hooks/useArcadeGuard.ts

@@ -73,8 +73,8 @@ export function useArcadeGuard(options: UseArcadeGuardOptions = {}): UseArcadeGu
         currentGame: data.currentGame,
       })
 
-      // Redirect if we're not already on the active game page
-      if (pathname !== data.gameUrl) {
+      // Redirect if we're not already on the active game page (only if enabled)
+      if (enabled && pathname !== data.gameUrl) {
         console.log('[ArcadeGuard] Redirecting to active session:', data.gameUrl)
         onRedirect?.(data.gameUrl)
         router.push(data.gameUrl)
@@ -126,8 +126,8 @@ export function useArcadeGuard(options: UseArcadeGuardOptions = {}): UseArcadeGu
             currentGame: session.currentGame,
           })
 
-          // Redirect if we're not already on the active game page
-          if (pathname !== session.gameUrl) {
+          // Redirect if we're not already on the active game page (only if enabled)
+          if (enabled && pathname !== session.gameUrl) {
             console.log('[ArcadeGuard] Redirecting to active session:', session.gameUrl)
             onRedirect?.(session.gameUrl)
             router.push(session.gameUrl)