@integrity-labs/agt-cli 0.28.297 → 0.28.299

package/dist/mcp/index.js

@@ -21784,7 +21784,7 @@ server.tool(
   }
 );
 var kanbanMoveStatuses = AGT_KANBAN_WAITING_ENABLED ? ["backlog", "todo", "in_progress", "waiting", "done", "failed"] : ["backlog", "todo", "in_progress", "done", "failed"];
-var kanbanMoveDescription = AGT_KANBAN_WAITING_ENABLED ? 'Move a kanban item to a different status column. Use status="failed" for a task attempted but not completable. Use status="waiting" when you have COMPLETED your part and cannot proceed until one specific external action happens (a person approves/answers/decides, or a dependency like a PR merge or deploy completes). status="waiting" REQUIRES waiting_kind - classify the wait as "pr-review", "pr-merged", "human", "external", or "other" (the catch-all when none fit). For a PR wait ("pr-review"/"pr-merged") set waiting_repo ("owner/repo") and waiting_pr (the number) INSTEAD of waiting_on - the card then links straight to the PR and can auto-resume when it lands. For "human"/"external"/"other" set waiting_on to the single concrete action, phrased as an instruction ("Approve the budget", "Answer my question"). Do NOT use waiting to offload hard work, and do NOT confuse it with a failure. (matches the hosted kanban_move enum).' : 'Move a kanban item to a different status column. Use status="failed" to mark a task that was attempted but could not complete (matches the hosted kanban_move enum).';
+var kanbanMoveDescription = AGT_KANBAN_WAITING_ENABLED ? 'Move a kanban item to a different status column. Use status="failed" for a task attempted but not completable. Use status="waiting" when you have COMPLETED your part and cannot proceed until one specific external action happens (a person approves/answers/decides, or a dependency like a PR merge or deploy completes). status="waiting" REQUIRES waiting_kind - classify the wait as "pr-review", "pr-merged", "human", "external", or "other" (the catch-all when none fit). For a PR wait ("pr-review"/"pr-merged") set waiting_repo ("owner/repo") and waiting_pr (the number) INSTEAD of waiting_on - the card then links straight to the PR and can auto-resume when it lands. For "human"/"external"/"other" set waiting_on to a one-line ask ("Answer my 5 scoping questions") AND put the full context the person needs to decide - the actual questions, options, links - in waiting_details, so they can answer from the card without opening a ticket. Do NOT use waiting to offload hard work, and do NOT confuse it with a failure. (matches the hosted kanban_move enum).' : 'Move a kanban item to a different status column. Use status="failed" to mark a task that was attempted but could not complete (matches the hosted kanban_move enum).';
 var kanbanMoveStatusDescribe = AGT_KANBAN_WAITING_ENABLED ? 'Target status. "waiting" parks the card until one external action happens; it REQUIRES waiting_kind - use "pr-review"/"pr-merged" with waiting_repo + waiting_pr, or "human"/"external"/"other" with a concrete waiting_on. "failed" closes the row as a failed attempt; there is no "cancelled" status, close no-longer-needed work via kanban_done with an explanatory result.' : 'Target status. "failed" closes the row as a failed attempt; there is no "cancelled" status, close no-longer-needed work via kanban_done with an explanatory result.';
 server.tool(
   "kanban_move",
@@ -21796,10 +21796,13 @@ server.tool(
     notes: external_exports.string().optional().describe("Progress notes"),
     ...AGT_KANBAN_WAITING_ENABLED ? {
       waiting_on: external_exports.string().optional().describe(
-        'Only with status="waiting", for a NON-PR wait: the single concrete action you are parked on, phrased as an instruction ("Approve the budget", "Answer my question"). Shown as the card headline. For a PR wait use waiting_kind/waiting_repo/waiting_pr instead.'
+        'Only with status="waiting", for a NON-PR wait: a ONE-LINE headline of what you are parked on, phrased as an instruction ("Approve the budget", "Answer my 5 scoping questions"). Keep it short - it is the card headline. Put the FULL context the person needs to decide in waiting_details, not here. For a PR wait use waiting_kind/waiting_repo/waiting_pr instead.'
+      ),
+      waiting_details: external_exports.string().optional().describe(
+        `Only with status="waiting" on a "human"/"external"/"other" wait: the FULL context the person needs to make the decision, inline - the actual questions, the options, the specifics, any links. Put everything here so they can answer from the card alone; NEVER just point at a ticket ("see ENG-1234"). waiting_on stays the one-line headline; this is the body. Shown in full in the card's Respond panel; the card preview and chat notifications may show a truncated preview (kept within their limits).`
       ),
       waiting_kind: external_exports.enum(["pr-review", "pr-merged", "human", "external", "other"]).optional().describe(
-        'REQUIRED with status="waiting": classify what you are waiting on. "pr-review" = a pull request awaiting review, "pr-merged" = a reviewed PR awaiting merge (both require waiting_repo + waiting_pr and let the card link to the PR and auto-resume). "human" = a specific person must decide/answer, "external" = a non-PR system/process must complete (a deploy, CI, a third party); for those two, describe it in waiting_on. "other" = none of the above / unsure - the generic catch-all, also described in waiting_on. Always pick the most specific kind that fits; fall back to "other" rather than leaving it unset.'
+        'REQUIRED with status="waiting": classify what you are waiting on. "pr-review" = a pull request awaiting review, "pr-merged" = a reviewed PR awaiting merge (both require waiting_repo + waiting_pr and let the card link to the PR and auto-resume). "human" = a specific person must decide/answer, "external" = a non-PR system/process must complete (a deploy, CI, a third party); for those two put a one-line ask in waiting_on and the full decision context in waiting_details. "other" = none of the above / unsure - the generic catch-all, same waiting_on + waiting_details. Always pick the most specific kind that fits; fall back to "other" rather than leaving it unset.'
       ),
       waiting_repo: external_exports.string().optional().describe(
         'Only with a pr-* waiting_kind: the "owner/repo" the pull request lives in (e.g. "Integrity-Labs/augmented").'
@@ -21844,8 +21847,11 @@ server.tool(
     let waitingContext;
     if (isPrKind) {
       waitingContext = { repo: p.waiting_repo, pr_number: p.waiting_pr };
-    } else if (p.waiting_choices && p.waiting_choices.length > 0) {
-      waitingContext = { choices: p.waiting_choices };
+    } else {
+      const ctx = {};
+      if (p.waiting_choices && p.waiting_choices.length > 0) ctx.choices = p.waiting_choices;
+      if (p.waiting_details && p.waiting_details.trim().length > 0) ctx.details = p.waiting_details;
+      if (Object.keys(ctx).length > 0) waitingContext = ctx;
     }
     const data = await apiPost("/host/kanban", {
       agent_id: AGT_AGENT_ID,
@@ -22533,6 +22539,9 @@ server.tool(
       "Short form title (max 24 chars - the Slack modal title limit), shown on the button and as the modal heading. Put longer context in intro."
     ),
     intro: external_exports.string().max(1e3).optional().describe("Optional context shown above the button and inside the modal (what you are asking and why)."),
+    button_label: external_exports.string().min(1).max(75).optional().describe(
+      'Optional label for the button that opens the form (max 75 chars). Defaults to "Fill out form". Use a specific call-to-action so the person knows what they are opening, e.g. "Start intake", "Give feedback", "Book a slot", "Submit your update".'
+    ),
     schema: external_exports.record(external_exports.unknown()).describe(
       'The form definition as a constrained JSON Schema: { "type": "object", "properties": { "<field>": { "type": "string|number|integer|boolean|array", "enum"?: [...], "format"?: "date|time|date-time|email|uri", ... } }, "required": ["..."] }. Flat only - no nested objects or oneOf/anyOf/allOf.'
     ),
@@ -22555,6 +22564,7 @@ server.tool(
         ...params.thread_ts ? { thread_ts: params.thread_ts } : {},
         title: params.title,
         ...params.intro ? { intro: params.intro } : {},
+        ...params.button_label ? { button_label: params.button_label } : {},
         schema: params.schema,
         ...params.request_id ? { request_id: params.request_id } : {}
       });

package/dist/mcp/origami.js

@@ -38842,7 +38842,10 @@ var INTEGRATION_REGISTRY = [
       note: "Billed per second of generated video; the rate depends on the resolution.",
       meters: [
         { event_type: "grok_imagine_video_1_5_480p", unit: "second" },
-        { event_type: "grok_imagine_video_1_5_720p", unit: "second" }
+        { event_type: "grok_imagine_video_1_5_720p", unit: "second" },
+        // 1080p is image-to-video only (xAI restriction); metered when the
+        // agent supplies image_url (ENG-7675).
+        { event_type: "grok_imagine_video_1_5_1080p", unit: "second" }
       ]
     }
   },
@@ -40115,6 +40118,41 @@ var FLAG_REGISTRY = [
     // safety control, so mutations require explicit confirmation.
     sensitive: true
   },
+  {
+    key: "composio-hitl-mode",
+    description: "Composio managed-toolkits HITL gate (ENG-6027): off = kill switch, shadow = resolve + audit the tier decision but never block, enforce = block write_high_risk+ calls (routed to approval when hitl-approval-routing is on). Per-org rollout from the admin Feature Flags page; ENG-7672 migrated this off the fleet-wide COMPOSIO_HITL_MODE env var.",
+    flagType: "enum",
+    allowedValues: ["off", "shadow", "enforce"],
+    // Declared safe value is `shadow` (resolve + audit, never block) — NOT `off`.
+    // shadow keeps the control evaluating + producing enforce-flip evidence while
+    // staying non-blocking, and matches the pre-flag compiled default so migrating
+    // onto the flag (ENG-7672) preserves fleet behaviour. A flag-DB read error
+    // degrades here. `enforce` is the deliberate, audited flip.
+    defaultValue: "shadow",
+    // Migration override (ADR-0022): the pre-flags env gate stays the
+    // highest-precedence operator override. It is only injected onto the Lambdas
+    // when an operator explicitly sets it (sst.config.ts) — otherwise this flag governs.
+    envVar: "COMPOSIO_HITL_MODE",
+    // enforce blocks prod tool calls, so weakening it (enforce → shadow/off) drops a
+    // safety control — mutations require explicit confirmation.
+    sensitive: true
+  },
+  {
+    key: "hitl-approval-routing",
+    description: "Routing for HITL-blocked integration calls (ENG-6028): off = blocked calls return the terminal block, on = route them into the approval-core flow (approval_requests row + Slack approval card). Needs a block first (composio-hitl-mode=enforce, or the always-on Direct-HTTP lane). Per-org rollout; ENG-7672 migrated this off the fleet-wide HITL_APPROVAL_ROUTING env var.",
+    flagType: "enum",
+    allowedValues: ["off", "on"],
+    // Declared safe value is `off` (terminal block, no new side effects) — the
+    // most-restrictive-known state, matching the pre-flag default. A flag-DB read
+    // error degrades here.
+    defaultValue: "off",
+    // Migration override (ADR-0022): only injected onto the Lambdas when an operator
+    // explicitly sets it (sst.config.ts) — otherwise this flag governs.
+    envVar: "HITL_APPROVAL_ROUTING",
+    // Turning routing on starts minting approval cards / approval_requests rows — an
+    // egress + workflow change worth an explicit confirm.
+    sensitive: true
+  },
   {
     key: "slack-reply-binding",
     description: "Slack reply-target binding (ENG-7396 / WS2, cross-thread reply routing): the model names which inbound it answers (inbound_id) and the server resolves the destination from its own verified record. shadow = classify + count only, routing unchanged; warn = same routing plus a tool-result note so the model self-corrects; enforce = route a bound reply to the registry thread and REJECT a reply whose target matches no inbound this process delivered. The channel server can't evaluate flags, so the manager materializes the resolved value into the AGT_SLACK_REPLY_BINDING spawn env (the operator/canary override, ADR-0022). Ships shadow.",

package/dist/mcp/slack-channel.js

@@ -15629,7 +15629,8 @@ var SLACK_EGRESS_TOOLS = /* @__PURE__ */ new Set([
   "slack.react",
   "slack.send_structured",
   "slack.ask_user",
-  "slack.upload_file"
+  "slack.upload_file",
+  "slack.update"
 ]);
 
 // src/strip-repost-preamble.ts
@@ -20417,6 +20418,25 @@ mcp.setRequestHandler(ListToolsRequestSchema, async () => ({
         required: ["channel", "timestamp", "emoji"]
       }
     },
+    {
+      name: "slack.update",
+      description: 'Edit the text of a Slack message YOU already sent (Slack chat.update). Pass the channel and the message\'s ts (slack.reply returns it as `(ts=\u2026)` on a successful send) plus the new text. You can only edit your OWN messages. This REPLACES the message text - any block layout on the original is cleared - so use it to correct a typo or update a message in place instead of posting a new one. NOTE: editing an interim "On it\u2026" into the final answer does NOT clear the pending-reply obligation - your final answer must still be a separate slack.reply (interim omitted). Common Slack errors: message_not_found (wrong ts/channel), cant_update_message (not your message), edit_window_closed.',
+      inputSchema: {
+        type: "object",
+        properties: {
+          channel: {
+            type: "string",
+            description: "Slack channel ID the message is in (the same channel you sent it to)."
+          },
+          ts: {
+            type: "string",
+            description: 'Timestamp of the message to edit - the `ts` value slack.reply returned when you sent it (e.g. "1783902864.258519"). Must be a message the bot itself sent.'
+          },
+          text: { type: "string", description: "The new message text. Replaces the existing text." }
+        },
+        required: ["channel", "ts", "text"]
+      }
+    },
     {
       name: "slack.read_thread",
       description: "Read the full message history of a Slack thread. Inbound thread replies already carry the surrounding thread inline as the <channel> tag's thread_context attribute \u2014 ground your reply in that first, and only call this tool when you need MORE history than thread_context shows (it is capped to recent messages) or to catch up on an auto-followed thread.",
@@ -20820,8 +20840,10 @@ mcp.setRequestHandler(CallToolRequestSchema, async (req) => {
           }
         })();
       }
+      const base = bindingFeedback ? `sent. ${bindingFeedback}` : "sent";
+      const sentTs = typeof data.ts === "string" ? data.ts : void 0;
       return {
-        content: [{ type: "text", text: bindingFeedback ? `sent. ${bindingFeedback}` : "sent" }]
+        content: [{ type: "text", text: sentTs ? `${base} (ts=${sentTs})` : base }]
       };
     } catch (err) {
       return {
@@ -20868,6 +20890,40 @@ mcp.setRequestHandler(CallToolRequestSchema, async (req) => {
       };
     }
   }
+  if (name === "slack.update") {
+    const { channel, ts, text } = args;
+    if (!channel || !ts || typeof text !== "string") {
+      return {
+        content: [{ type: "text", text: "slack.update requires channel, ts and text" }],
+        isError: true
+      };
+    }
+    try {
+      const res = await fetch("https://slack.com/api/chat.update", {
+        method: "POST",
+        headers: {
+          "Content-Type": "application/json; charset=utf-8",
+          Authorization: `Bearer ${BOT_TOKEN}`
+        },
+        // text only: chat.update replaces the message, clearing any prior blocks.
+        body: JSON.stringify({ channel, ts, text }),
+        signal: AbortSignal.timeout(8e3)
+      });
+      const data = await res.json();
+      if (!data.ok) {
+        return {
+          content: [{ type: "text", text: `Slack error: ${data.error}` }],
+          isError: true
+        };
+      }
+      return { content: [{ type: "text", text: "updated" }] };
+    } catch (err) {
+      return {
+        content: [{ type: "text", text: `Failed: ${err.message}` }],
+        isError: true
+      };
+    }
+  }
   if (name === "slack.read_thread") {
     const { channel, thread_ts, limit: rawLimit } = args;
     const limit = Math.min(Math.max(rawLimit ?? 50, 1), 200);

package/dist/{persistent-session-A5N7BYS3.js → persistent-session-RSM62IW7.js}

@@ -36,7 +36,7 @@ import {
   writeDirectChatSessionState,
   writeEgressAllowlist,
   writePersistentClaudeWrapper
-} from "./chunk-QXU5FMXN.js";
+} from "./chunk-KMJHNKPQ.js";
 import "./chunk-XWVM4KPK.js";
 export {
   EGRESS_BASELINE_DOMAINS,
@@ -77,4 +77,4 @@ export {
   writeEgressAllowlist,
   writePersistentClaudeWrapper
 };
-//# sourceMappingURL=persistent-session-A5N7BYS3.js.map
+//# sourceMappingURL=persistent-session-RSM62IW7.js.map

package/dist/{responsiveness-probe-OZP2HO2F.js → responsiveness-probe-DAKU7GSN.js}

@@ -1,6 +1,6 @@
 import {
   paneLogPath
-} from "./chunk-QXU5FMXN.js";
+} from "./chunk-KMJHNKPQ.js";
 import "./chunk-XWVM4KPK.js";
 
 // src/lib/responsiveness-probe.ts
@@ -418,4 +418,4 @@ export {
   readAndResetSlackReplyBindingClassifications,
   readAndResetSlackReplyTargetClassifications
 };
-//# sourceMappingURL=responsiveness-probe-OZP2HO2F.js.map
+//# sourceMappingURL=responsiveness-probe-DAKU7GSN.js.map

package/package.json

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