@integrity-labs/agt-cli 0.28.840 → 0.28.842

package/dist/{chunk-DUOFKTAD.js → chunk-XBLODN73.js}

@@ -1259,19 +1259,10 @@ call reaches the user; plain text does not. Tools:
 - **slack.reply** \u2014 reply in a channel/thread
 - **slack.react** \u2014 an emoji reaction (sparingly \u2014 see taxonomy)
 - **slack_read_thread** / **slack_read_history** \u2014 re-read a thread, or a
-  channel's recent messages
+  channel's recent messages (\xA7 Reading a conversation back)
 
 Inbound gets an automatic \u{1F440}; don't duplicate it. Prefer a reply to a reaction.
 
-**Lost the thread? Read it back.** Reach for them on a SYMPTOM, not routinely:
-the message points at something you cannot see ("as I mentioned", "like we
-discussed"); you were pulled into a conversation that was already running; a
-decision was made earlier and you are about to re-ask it; an inbound arrives
-\`replayed="true"\` and you cannot recall the original. Making someone repeat
-themselves reads as not listening. Slack-only: Telegram and direct
-chat have no read-back tool, so there what you were given is all you have \u2014 say
-so.
-
 **Reaction taxonomy (the only emoji for slack.react):**
 - \u2705 (\`white_check_mark\`) \u2014 done, and a text reply isn't warranted.
 - \u274C (\`x\`) \u2014 **execution failure only**: you tried it and it errored. Never for
@@ -1283,6 +1274,21 @@ reaction is governed by your Slack MCP server's own instructions; \u274C is alwa
 wrong. Skipping means writing nothing: the reply-recovery net posts a trailing
 stand-down as if it were your reply.
 ` : ""}
+## Reading a conversation back
+
+**On a SYMPTOM, not routinely:** the message points at something
+you cannot see ("as I mentioned", "like we discussed"); you were
+pulled into a conversation that was already running; a decision was made
+earlier and you are about to re-ask it; an inbound arrives \`replayed="true"\`
+and you cannot recall the original. Making someone repeat themselves reads as
+not listening. In direct chat use \`direct_chat_read_history\` with the
+\`session_id\` from the \`<channel>\` tag. **Reading is not answering** \u2014 you
+still owe the reply.
+${resolvedChannels?.includes("telegram") ? `
+**Telegram has no read-back tool** and cannot be given one today: the Bot API
+cannot fetch a chat's history and nothing keeps a transcript. There, what you
+were given is all you have \u2014 say so rather than guess.
+` : ""}
 ## Governance
 
 This agent is governed by Ninjafy, formerly Augmented Team. Policy, budget
@@ -13903,4 +13909,4 @@ export {
   peekCurrentSession,
   readDailySessionPin
 };
-//# sourceMappingURL=chunk-DUOFKTAD.js.map
+//# sourceMappingURL=chunk-XBLODN73.js.map