@integrity-labs/agt-cli 0.28.975 → 0.28.976

package/dist/{chunk-YBDGTOXI.js → chunk-KTFN2AIB.js}

@@ -20,7 +20,7 @@ import {
   rotateDailySession,
   sessionFileExists,
   todayLocalIso
-} from "./chunk-VRYNZ3G5.js";
+} from "./chunk-VF5BT7BP.js";
 import {
   classifyUnanswerablePane,
   findUsageLimitResetHint,
@@ -5575,4 +5575,4 @@ export {
   stopAllSessionsAndWait,
   getProjectDir
 };
-//# sourceMappingURL=chunk-YBDGTOXI.js.map
+//# sourceMappingURL=chunk-KTFN2AIB.js.map

package/dist/{chunk-VRYNZ3G5.js → chunk-VF5BT7BP.js}

@@ -1303,8 +1303,8 @@ ${desc}
 
 **The delivery rule, true of every reply below:** the ONLY way a channel user
 (Slack, Telegram, Microsoft Teams, Direct Chat) receives anything from you is a
-channel reply tool call - \`slack.reply\`, \`telegram.reply\`, \`teams.reply\`,
-or \`direct_chat.reply\`. Plain text you write in your turn is NOT delivered to
+channel reply tool call - \`slack_reply\`, \`telegram_reply\`, \`teams_reply\`,
+or \`direct_chat_reply\`. Plain text you write in your turn is NOT delivered to
 the user; it goes only to your local session log. So always reply on the channel
 the message arrived on, and never answer a channel message with plain text
 alone: if you did not call a reply tool, the user received nothing.
@@ -1412,17 +1412,17 @@ ${resolvedChannels?.includes("slack") ? `
 ## Slack
 
 Slack MCP server connected. Triage per \xA7 FIRST ACTION on
-every channel message; acknowledge before slow work. Only a \`slack.reply\`
+every channel message; acknowledge before slow work. Only a \`slack_reply\`
 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_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 (\xA7 Reading a conversation back)
 
 Inbound gets an automatic \u{1F440}; don't duplicate it. Prefer a reply to a reaction.
 
-**Reaction taxonomy (the only emoji for slack.react):**
+**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
   "skipped", "disagree", "not addressed to me", "n/a" or "noted".
@@ -1641,7 +1641,7 @@ When you reply to a user via any channel (Slack, Telegram, direct chat, schedule
 - **Match the scope of the request.** A yes/no question gets a one-line answer; a "quick summary" gets a summary, not a dissertation. Cut any section, caveat, or restatement that doesn't directly answer what was asked.
 - **Never reference internal state.** Memory files, \`/tmp/\` paths, kanban task IDs, filesystem locations, "saved to \u2026" / "logged to \u2026" notes \u2014 these are invisible to the recipient and waste their attention. Only the deliverable content belongs in your reply.
 - **Put the full deliverable in the reply itself.** Don't tease ("I've prepared a detailed brief"), don't point "above" or "attached", and don't assume the recipient can see intermediate tool output. If they asked for a brief, the brief goes verbatim into your reply.
-- **If the deliverable is a file** (PDF, CSV, screenshot, export, report), upload it with the channel's file-upload tool (e.g. \`slack.upload_file\`) rather than describing its path. The recipient cannot access your filesystem.
+- **If the deliverable is a file** (PDF, CSV, screenshot, export, report), upload it with the channel's file-upload tool (e.g. \`slack_upload_file\`) rather than describing its path. The recipient cannot access your filesystem.
 
 ## Standards
 
@@ -15200,4 +15200,4 @@ export {
   peekCurrentSession,
   readDailySessionPin
 };
-//# sourceMappingURL=chunk-VRYNZ3G5.js.map
+//# sourceMappingURL=chunk-VF5BT7BP.js.map