fix: force-clear WebSocket session from memory on disconnect

[nyarumyaro]

Summary

Fixes #294 — corrupted WebSocket room cleanup logic.

When an admin closes or refreshes the dashboard browser tab abruptly, the backend was entering a 60-second grace period before removing the dead socket session from memory. This caused stale disconnected-pending entries to accumulate in the sessions map, creating unnecessary memory overhead.

Changes

src/lib/socket.ts — handleDisconnect

• Removed the 60-second grace period / disconnectTimer timeout on disconnect.
• Session is now immediately deleted from the sessions map when a disconnect event fires.
• Any previously scheduled disconnectTimer is cancelled before deletion to avoid dangling timers.

Before / After

// Before: session entered grace period for 60s
session.status = "disconnected-pending";
session.disconnectTimer = setTimeout(() => sessions.delete(sessionId), 60000);

// After: session is force-cleared immediately
if (session.disconnectTimer) clearTimeout(session.disconnectTimer);
sessions.delete(sessionId);

Testing

• Connect a Socket.IO client, then abruptly close the connection.
• Verify the session is removed from the sessions map immediately (no 60s wait).
• Verify no memory growth from repeated abrupt disconnects.

[drips-wave]

@nyarumyaro Great news! 🎉 Based on an automated assessment of this PR, the linked Wave issue(s) no longer count against your application limits.

You can now already apply to more issues while waiting for a review of this PR. Keep up the great work! 🚀

Learn more about application limits