fix: implement socket room isolation for realtime events

[ash1shkumar]

🚀 Description

Implemented socket room isolation for realtime events to prevent cross-project event leakage between connected clients.

✅ Changes Made

• Added room-based socket joining for connected users
• Scoped realtime task events to project-specific rooms
• Updated frontend socket emits to include room metadata
• Isolated Kanban realtime updates per project workspace
• Improved scalability and multi-project realtime handling

🔧 Backend Changes

• Updated join socket event to support room joining
• Added socket.join(room) support
• Scoped task-moved broadcasts using io.to(room).emit(...)

🎨 Frontend Changes

• Updated chat socket join payload to include room
• Updated Kanban realtime emits to send room metadata
• Ensured realtime sync only affects clients in the same room

📌 Result

Realtime events are now isolated by room/project instead of being globally broadcasted to all connected users.

Fixes #125

Expected labels:
level3 NSoC'26

[vercel]

@ash1shkumar is attempting to deploy a commit to the shreemp194-gmailcom's projects Team on Vercel.

A member of the Team first needs to authorize it.

[github-actions]

👋 Thank you for opening this pull request! I will review your changes and assist you soon.

[ash1shkumar]

@Shriii19 This PR is ready for review. I’ve completed the implementation, tested the changes locally, and addressed the issue requirements. Please review when available. Thanks!

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
flow-forge	Ready	Preview, Comment	May 30, 2026 4:19pm