fix: propagate WhatsApp reply context

[tkwong]

Summary

• extract quoted message id and text from Baileys contextInfo in the WhatsApp bridge
• pass quoted reply metadata through the WhatsApp adapter into MessageEvent.reply_to_message_id / reply_to_text
• add regression tests covering event construction and gateway reply-context injection

Test Plan

• /opt/homebrew/bin/node --check scripts/whatsapp-bridge/bridge.js
• pytest tests/gateway/test_whatsapp_reply_context.py tests/gateway/test_whatsapp_group_gating.py -q

[anand-agastya]

We've been running this fix locally (both bridge.js + whatsapp.py changes) and it works correctly. When a user replies to a WhatsApp message, the agent sees [Replying to: "the quoted text"] prepended.

Tested with conversation, extendedText, image caption, and video caption quoted messages.

Would be great to see this merged — reply context is lost without it, and it's been open since April.

[teknium1]

Thanks for the focused WhatsApp reply-context fix. This is now implemented on current main; automated hermes-sweeper review found that the PR is superseded by a later WhatsApp refactor.

• scripts/whatsapp-bridge/bridge_helpers.js:311-317 extracts Baileys contextInfo, including quoted message ID and text, and returns it at :480-484.
• plugins/platforms/whatsapp/adapter.py:1439-1455 maps that metadata into structured reply fields, passed to MessageEvent at :1514-1517.
• gateway/run.py:10572-10586 renders the agent-visible [Replying to: "…"] pointer.
• Commit 11627fdcb92a0ad57c9b637538f8fbea39142272 introduced this implementation and is contained in release tag v2026.7.7.

The original gateway/platforms/whatsapp.py target was subsequently migrated to the bundled plugin adapter, so this branch's patch is no longer needed.