💬 Messages

MES-01: Enable ack reactions by setting messages.ackReactionScope

Review my OpenClaw config and enable ack reactions by setting `messages.ackReactionScope` explicitly.

Do all of the following:

1. Find my OpenClaw config file.
2. Check whether `messages.ackReactionScope` is already set.
3. If it is missing, explain the available values:
   - `group-mentions`
   - `group-all`
   - `direct`
   - `all`
   - `off`
   - `none`
4. Unless I want a narrower behavior, recommend `messages.ackReactionScope = "all"`.
5. After I choose, update the config carefully.

Then show me:
- which config file you changed
- the exact `messages` block before and after
- what `messages.ackReactionScope` is set to now
- what the selected scope means
- any assumptions you made

📨 Telegram

TEL-01: Use Telegram inline buttons for recurring actions

Review my OpenClaw Telegram setup and enable inline buttons for recurring actions where taps are better than typed replies.

Do all of the following:

1. Find the active OpenClaw config file actually used by this runtime.
2. Check whether Telegram is configured and currently active.
3. Identify which Telegram account is being used for this chat/test.
4. Check whether channels.telegram.capabilities.inlineButtons is already set.
5. Unless there is a clear reason to limit scope, set: `channels.telegram.capabilities.inlineButtons = "all"`
6. Preserve any existing Telegram settings that are unrelated.
7. Do not treat plain-text option lists as buttons.
8. For real clickable Telegram buttons, send a message using an actual inline keyboard payload.
9. Use OpenClaw CLI in this form: `openclaw message send --channel telegram --account <accountId> --target <chatId> --message "<text>" --buttons '<json>'`
10. Ensure the --buttons payload is:
  - valid JSON
  - top-level array of rows
  - each row an array of button objects
  - each callback button includes text and callback_data
11. If a style field is supported by tooling, treat it only as a hint. Do not rely on Telegram per-button colors.
12. After configuration, send a real test message with clickable inline buttons.
13. Wait for at least one button click if possible, or clearly state if callback verification could not be completed.
14. Do not claim success unless the buttons were actually rendered as Telegram inline buttons.
15. Add this information in learnings/memory.

Then report back with:
- the exact config file changed
- the exact config value before and after for channels.telegram.capabilities.inlineButtons
- whether Telegram was already active
- which Telegram account was used
- which chat ID / target was tested
- the exact command used to send the test message
- whether the buttons rendered