fix: remove ack reactions after reply (#633) (thanks @levifig)

docs/providers/discord.md

@@ -225,7 +225,8 @@ Outbound Discord API calls retry on rate limits (429) using Discord `retry_after
 ```
 
 Ack reactions are controlled globally via `messages.ackReaction` +
-`messages.ackReactionScope`.
+`messages.ackReactionScope`. Use `messages.removeAckAfterReply` to clear the
+ack reaction after the bot replies.
 
 - `dm.enabled`: set `false` to ignore all DMs (default `true`).
 - `dm.policy`: DM access control (`pairing` recommended). `"open"` requires `dm.allowFrom=["*"]`.

docs/providers/slack.md

@@ -192,7 +192,8 @@ Tokens can also be supplied via env vars:
 - `SLACK_APP_TOKEN`
 
 Ack reactions are controlled globally via `messages.ackReaction` +
-`messages.ackReactionScope`.
+`messages.ackReactionScope`. Use `messages.removeAckAfterReply` to clear the
+ack reaction after the bot replies.
 
 ## Limits
 - Outbound text is chunked to `slack.textChunkLimit` (default 4000).

docs/providers/telegram.md

@@ -287,4 +287,4 @@ Related global options:
 - `agents.list[].groupChat.mentionPatterns` (mention gating patterns).
 - `messages.groupChat.mentionPatterns` (global fallback).
 - `commands.native`, `commands.text`, `commands.useAccessGroups` (command behavior).
-- `messages.responsePrefix`, `messages.ackReaction`, `messages.ackReactionScope`.
+- `messages.responsePrefix`, `messages.ackReaction`, `messages.ackReactionScope`, `messages.removeAckAfterReply`.