Declare removedByMemberId, or the relay drops it in silence

Shipped

August 30, 2026 at 2:44 AM UTC

Author

Kamo

Commit

e86c161

The NATS payload for MEMBER_REMOVED carries who did the removing, but the NATS→STOMP relay projects every frame through ChatMessageDto — so a field this class does not declare never reaches a browser at all. Subscribers read it as empty, with nothing anywhere reporting a problem. The same trap already caught ATTACHMENT_REVOKED once, which is why that event carries its id twice.