@integrity-labs/agt-cli 0.28.354 → 0.28.356

package/dist/mcp/slack-channel.js

@@ -37368,6 +37368,15 @@ function buildSlackMcpInstructions(opts) {
 // src/slack-react-taxonomy.ts
 var SLACK_REACT_TOOL_DESCRIPTION = "Add an emoji reaction to a Slack message. Use sparingly \u2014 prefer a text reply. Reaction taxonomy: \u2705 = action completed successfully. \u{1F4DD} (:memo:) and \u26A0\uFE0F (:warning:) are blessed for explicit multi-state STATUS pipelines only \u2014 e.g. marking a run/parent \u2705 done / \u{1F4DD} waiting / \u26A0\uFE0F failed for at-a-glance status. That exception is narrow: never use a reaction to tell a user that YOUR reply failed \u2014 NEVER react to signal failure of your own work; on failure call slack.reply with one sentence explaining what went wrong instead (no stack traces, no secrets). \u{1F440} (eyes) is already auto-applied on inbound; do not duplicate. \u23F3 (:hourglass_flowing_sand:) is reserved for the system to mark an inbound that arrived while the agent couldn't reply \u2014 never add \u23F3 or \u274C yourself. (A \u{1F512} you may see on a thread is the server's reply-throttle marker, not a coerced reaction \u2014 slack.react passes your emoji straight through to Slack and never rewrites it to \u{1F512}.)";
 
+// src/slack-routed-to-note.ts
+function describeChannelRedirect(input) {
+  const { requestedChannel, effectiveChannel, reason = null } = input;
+  if (!requestedChannel) return null;
+  if (requestedChannel === effectiveChannel) return null;
+  const why = reason === "scheduled-task" ? " (routed to the scheduled task's configured destination)" : reason === "dm-channel-guard" ? " (redirected by the DM-channel guard because those coordinates belong to a DM)" : "";
+  return `Heads up: this was delivered to ${effectiveChannel}, NOT the ${requestedChannel} you named${why}. routed_to=${effectiveChannel}. If ${effectiveChannel} is not where you intended this to go, the destination is misconfigured; do not assume it posted to ${requestedChannel}.`;
+}
+
 // src/slack-reply-binding-telemetry.ts
 import { readFileSync as readFileSync13, writeFileSync as writeFileSync10 } from "fs";
 import { join as join13 } from "path";
@@ -41451,6 +41460,12 @@ mcp.setRequestHandler(CallToolRequestSchema, async (req) => {
       if (hotThreadRedirected) {
         base += ". Note: this was threaded into the conversation you are actively working in rather than posted at the channel root. If you genuinely meant to start a NEW top-level topic, resend with to_channel_root:true.";
       }
+      const redirectNote = describeChannelRedirect({
+        requestedChannel: channel,
+        effectiveChannel,
+        reason: scheduledDest?.retargeted ? "scheduled-task" : channelGuard.corrected ? "dm-channel-guard" : null
+      });
+      if (redirectNote) base += `. ${redirectNote}`;
       const sentTs = typeof data.ts === "string" ? data.ts : void 0;
       return {
         content: [{ type: "text", text: sentTs ? `${base} (ts=${sentTs})` : base }]

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@integrity-labs/agt-cli",
-  "version": "0.28.354",
+  "version": "0.28.356",
   "description": "Augmented Team CLI — agent provisioning and management",
   "type": "module",
   "engines": {