Beta.3 mutation guard breaks message(action=react) for DM reactions

Summary

resolveTelegramMessageMutationChatId() in action-runtime-BmXKtFG6.js rejects message(action=react) calls when the target chat doesn't match the session's conversation context. In DMs, the matchesChat check fails — likely a format mismatch between how the session identifies itself and how the target is addressed.

React calls are idempotent and low-risk. The mutation guard is appropriate for sends/deletes/edits but unnecessarily restrictive for reactions.

Reproduction

1. Agent session bound to a Telegram DM conversation
2. Call message(action=react) with the DM's chat_id and a valid messageId
3. Result: "Reaction failed. Do not retry." — the catch block on the thrown TOPIC_BINDING_ERROR

Workaround

Patched dist locally to skip resolveTelegramMessageMutationChatId for react calls and use chatId directly. Sends/deletes/edits still go through the full guard.

Expected behavior

message(action=react) should succeed when actions.reactions: true and reactionLevel permits it, without requiring the mutation guard's chat-matching logic.

Version

OpenClaw 2026.8.1-beta.3

Start in action-runtime-BmXKtFG6.js at resolveTelegramMessageMutationChatId() and trace the message(action=react) path, including the TOPIC_BINDING_ERROR catch. Reproduce with a Telegram DM chat_id and valid messageId. Done means permitted reactions succeed without the mutation guard while sends, deletes, and edits retain the guard.