Add socket.io realtime infrastructure backed by Redis

[VectoDE]

Summary

• add a Socket.IO API route and client provider so the UI refreshes when realtime events arrive
• integrate Redis/BullMQ queues with a Prisma middleware to broadcast database mutations
• expose helpers for publishing realtime events from server code

Testing

• pnpm lint

---

https://chatgpt.com/codex/tasks/task_e_6908c14c86ac832ca53a61044f630ab9

[vercel]

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

Project	Deployment	Preview	Comments	Updated (UTC)
portfolio	Ready	Preview	Comment	Nov 3, 2025 5:08pm

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Avoid hanging Prisma writes when Redis is down

Each Prisma mutation awaits enqueueRealtimeEvent, and the Redis clients created in lib/redis.ts set maxRetriesPerRequest: null (infinite retries). When Redis is unavailable or misconfigured, queue.add never resolves nor rejects, so every database write waits forever before the middleware returns. This change effectively makes all writes dependent on Redis uptime even though the realtime queue is optional. Consider not awaiting the enqueue call or adding a bounded timeout/retry so mutations can complete even when Redis is offline.

Useful? React with 👍 / 👎.