@integrity-labs/agt-cli 0.28.157 → 0.28.158

package/dist/bin/agt.js

@@ -37,7 +37,7 @@ import {
   success,
   table,
   warn
-} from "../chunk-6VSS55A2.js";
+} from "../chunk-3OLFOA4F.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.157" : "dev";
+var cliVersion = true ? "0.28.158" : "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.157" : "dev";
+var cliVersion2 = true ? "0.28.158" : "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-6VSS55A2.js → chunk-3OLFOA4F.js}

@@ -3646,14 +3646,18 @@ to add it yourself. After working, prefer a text reply via slack.reply over a re
 
 **When a thread message is not for you, do nothing.** If a message in a thread
 is addressed to a different user (different @-mention), is part of a conversation
-between others, or arrives via auto-follow with no relevance to you \u2014 silently
-skip it. No reaction. No reply. Adding \u274C in this case is wrong: it tells the
-user "execution failed" when in fact you correctly identified the message wasn't
-yours to handle. "Silently skip" means write nothing too: do not end your turn
-with a line narrating that you're standing down or staying silent. Per the
-delivery rule above, the reply-recovery net can post that trailing text to the
-thread as if it were your reply, so a stand-down narration becomes the very noise
-you were avoiding. Decide internally and leave no channel-facing text.
+between others, or arrives via auto-follow with no relevance to you \u2014 skip it
+and do not post a text reply. Whether you also mark it with a "seen, skipping"
+reaction is governed by your Slack MCP server's own instructions, which reflect
+the current channel policy: if it tells you to react when you skip, do that; if
+it doesn't, skip with no reaction at all. Follow that guidance rather than
+assuming either way here. The one reaction that is always wrong in this case is
+\u274C: it tells the user "execution failed" when in fact you correctly identified
+the message wasn't yours to handle. Skipping also means writing nothing: do not
+end your turn with a line narrating that you're standing down or staying silent.
+Per the delivery rule above, the reply-recovery net can post that trailing text
+to the thread as if it were your reply, so a stand-down narration becomes the
+very noise you were avoiding. Decide internally and leave no channel-facing text.
 ` : ""}
 ## Governance
 
@@ -7894,7 +7898,7 @@ function requireHost() {
 }
 
 // src/lib/api-client.ts
-var agtCliVersion = true ? "0.28.157" : "dev";
+var agtCliVersion = true ? "0.28.158" : "dev";
 var lastConfigHash = null;
 function setConfigHash(hash) {
   lastConfigHash = hash && hash.length > 0 ? hash : null;
@@ -9199,4 +9203,4 @@ export {
   managerInstallSystemUnitCommand,
   managerUninstallSystemUnitCommand
 };
-//# sourceMappingURL=chunk-6VSS55A2.js.map
+//# sourceMappingURL=chunk-3OLFOA4F.js.map