What happened?

While looking into #16387 I noticed the reply metadata never actually reaches the UI — not because the feature isn't implemented, but because of a gap in the middleware.
XEP-0461 support was added to lib-jitsi-meet in #2922, so LJM already parses reply stanzas and passes replyToId as the last argument on MESSAGE_RECEIVED and PRIVATE_MESSAGE_RECEIVED. The problem is that the callbacks in _addChatMsgListener() (react/features/chat/middleware.ts) don't declare that argument — so it gets silently dropped before it ever reaches Redux or the UI.
Expected
replyToId forwarded through to Redux as replyToMessageId on the chat message object.

Actual -
replyToMessageId is always missing, even when LJM resolved it from the stanza.

Notes -
Scoped to the receiving side in jitsi-meet only — send/parse stays in LJM.
Two plain jitsi-meet tabs won't trigger this path; you need a reply-capable client or a test that injects .

Platform

• Chrome (or Chromium based)
• Firefox
• Safari
• Other desktop browser
• Android browser
• iOS browser
• Electron app
• Android mobile app
• iOS mobile app
• Custom app using a mobile SDK

Browser / app / sdk version

Brave v1.87.192

Relevant log output

Reproducibility

• The problem is reproducible on meet.jit.si

More details?

No response