openclaw/extensions/whatsapp
Marcus Castro 34648235a3
WhatsApp: use shared resolveReactionMessageId for context-aware reactions (#57226)
Wire the shared resolveReactionMessageId helper into the WhatsApp
channel adapter, matching the pattern already used by Telegram, Signal,
and Discord. The model can now react to the current inbound message
without explicitly providing a messageId.

Safety guards:
- Only falls back to context when the source is WhatsApp
- Suppresses fallback when targeting a different chat (normalized comparison)
- Throws ToolInputError (400) instead of plain Error (500) when messageId
  is missing, preserving gateway error mapping
2026-03-29 15:42:19 -03:00
..
src WhatsApp: use shared resolveReactionMessageId for context-aware reactions (#57226) 2026-03-29 15:42:19 -03:00
action-runtime-api.ts
action-runtime.runtime.ts
api.ts refactor: route channel contract tests through public barrels 2026-03-27 13:46:16 +00:00
auth-presence.ts
channel-catalog.contract.test.ts refactor: move extension-owned tests to extensions 2026-03-27 21:37:09 +00:00
channel-config-api.ts refactor: move channel config metadata into plugin-owned manifests 2026-03-27 01:59:30 +00:00
constants.ts refactor(plugins): decouple bundled plugin runtime loading 2026-03-29 09:10:38 +01:00
index.ts
light-runtime-api.ts
login-qr-api.ts refactor: continue plugin seam cleanup 2026-03-27 13:46:16 +00:00
openclaw.plugin.json
package-manifest.contract.test.ts refactor(plugins): decouple bundled plugin runtime loading 2026-03-29 09:10:38 +01:00
package.json chore: bump version to 2026.3.29 2026-03-29 14:33:12 +01:00
runtime-api.ts refactor: continue plugin seam cleanup 2026-03-27 13:46:16 +00:00
setup-entry.ts
test-api.ts refactor: route plugin runtime through bundled seams 2026-03-27 16:40:27 +00:00