@integrity-labs/agt-cli 0.28.118 → 0.28.119

package/dist/bin/agt.js

@@ -37,7 +37,7 @@ import {
   success,
   table,
   warn
-} from "../chunk-P7FAMLC4.js";
+} from "../chunk-HOSOEXRD.js";
 import {
   CHANNEL_REGISTRY,
   DEPLOYMENT_TEMPLATES,
@@ -4777,7 +4777,7 @@ import { execFileSync, execSync } from "child_process";
 import { existsSync as existsSync10, realpathSync as realpathSync2 } from "fs";
 import chalk18 from "chalk";
 import ora16 from "ora";
-var cliVersion = true ? "0.28.118" : "dev";
+var cliVersion = true ? "0.28.119" : "dev";
 async function fetchLatestVersion() {
   const host2 = getHost();
   if (!host2) return null;
@@ -5791,7 +5791,7 @@ function handleError(err) {
 }
 
 // src/bin/agt.ts
-var cliVersion2 = true ? "0.28.118" : "dev";
+var cliVersion2 = true ? "0.28.119" : "dev";
 var program = new Command();
 program.name("agt").description("Augmented CLI \u2014 agent provisioning and management").version(cliVersion2).option("--json", "Emit machine-readable JSON output (suppress spinners and colors)").option("--skip-update-check", "Skip the automatic update check on startup");
 program.hook("preAction", async (thisCommand, actionCommand) => {

package/dist/{chunk-P7FAMLC4.js → chunk-HOSOEXRD.js}

@@ -3401,6 +3401,14 @@ ${desc}
 
 ## \u26A0\uFE0F FIRST ACTION on every channel message: triage
 
+**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
+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.
+
 This is the highest-priority instruction in this document. Before anything
 else when you receive an inbound \`<channel>\` tag (Slack/Telegram/Direct
 Chat), decide:
@@ -3412,7 +3420,7 @@ refreshes, multi-skill activations, or anything you'd reasonably want to
 acknowledge before you start.
 
 - **FAST (< 60s):** handle inline. Reply via the channel tool
-  (slack.reply / telegram.reply / directchat.reply) and end your turn.
+  (slack.reply / telegram.reply / direct_chat.reply) and end your turn.
 
 - **SLOW (\u2265 60s):** acknowledge first, then handle inline.
   1. Send a one-line acknowledgement via the channel tool \u2014 short, warm,
@@ -3423,7 +3431,7 @@ acknowledge before you start.
      need (MCP, skills, file reads, etc.) \u2014 your parent session has the
      full MCP surface bound.
   3. Reply with the result via the channel tool (\`slack.reply\` /
-     \`telegram.reply\` / \`directchat.reply\`), addressing the same thread
+     \`telegram.reply\` / \`direct_chat.reply\`), addressing the same thread
      / chat / conversation you acknowledged in step 1.
 
 > **Why inline and not sub-agent dispatch right now:** there is an
@@ -3539,8 +3547,9 @@ diving into slow work (sub-agent dispatch for channel replies is
 currently disabled due to an upstream Claude Code bug; see the FIRST
 ACTION section for the full rationale).
 
-For fast requests, respond directly in the conversation. You can also
-proactively use:
+For fast requests, reply with \`slack.reply\` (see the delivery rule in the
+FIRST ACTION section: a plain-text turn does NOT reach Slack - only a
+\`slack.reply\` call does). You can also proactively use:
 
 - **slack.reply** \u2014 reply to a message in a channel/thread
 - **slack.react** \u2014 add an emoji reaction to a message (use sparingly \u2014 see taxonomy below)
@@ -7632,7 +7641,7 @@ function requireHost() {
 }
 
 // src/lib/api-client.ts
-var agtCliVersion = true ? "0.28.118" : "dev";
+var agtCliVersion = true ? "0.28.119" : "dev";
 var lastConfigHash = null;
 function setConfigHash(hash) {
   lastConfigHash = hash && hash.length > 0 ? hash : null;
@@ -8929,4 +8938,4 @@ export {
   managerInstallSystemUnitCommand,
   managerUninstallSystemUnitCommand
 };
-//# sourceMappingURL=chunk-P7FAMLC4.js.map
+//# sourceMappingURL=chunk-HOSOEXRD.js.map