- Shipped
- 10 ஆகஸ்ட், 2026 அன்று 7:47 PM UTC
- Author
- Kamo
- Commit
- 4ebfa45
The unread/ACTIVITY broadcast is published for every session type and carried no indication of which. The chats list, having nothing to go on, typed an unseen session as a plain chat — so a support ticket's first activity arrived as a chat row: wrong sub-tab, the ticket's system-event JSON as its preview, and opening it fell through to the direct-message window instead of the ticket. Same field and same reason as the incoming-message notification; this was the second broadcast carrying the same blind spot.