- Ya
- 10 Agosti 2026, 19:43 UTC
- Mwandishi
- kamo
- Ahadi ya
- 87a7d92
Two faults, one symptom. Assignment makes the agent a member of the ticket's media session, so the incoming-message notification reached them and ChatNotificationListener opened a direct-message window for a support conversation — the wrong surface, with none of the ticket's controls. And that window rendered the ticket's system events as raw `{"systemEvent":true,...}`, because only the support chat's renderer knows how to read them. The listener now ignores SUPPORT_TICKET notifications; support has its own window, opened by the accept popup or by AssignedTicketOpener. Absent sessionType is treated as an ordinary chat, so a client running ahead of MediaService behaves as before. MessageList also routes a system-event body to the support renderer rather than the text bubble. Support conversations should not reach that list at all now, but "a renderer never shows a user a JSON blob" is worth guaranteeing outright.