Prisma Jobs

Bug fix in a real-time chat application. Context: chat messages are stored as generic ChatEvent rows in Postgres, with no dedicated flag distinguishing a private message from a public one — private messages currently arrive with a text-based marker prefixed to the message body (e.g. a bracketed tag at the start of the string). The frontend chat component already has a fully built, distinct rendering path for private messages (different visual treatment) — it just never gets used, because the API route that serves chat events to the frontend maps every single row to the generic "chat" type regardless of content, so the private-message type the frontend already knows how to render is never actually emitted. Task: update the API route so it correctly detects the priv...