@integrity-labs/agt-cli 0.28.282 → 0.28.283

package/dist/mcp/index.js

@@ -21525,6 +21525,10 @@ function readRunId() {
 }
 var AGT_RUN_ID = readRunId();
 var AGT_TOKEN = process.env.AGT_TOKEN ?? "";
+var AGT_KANBAN_WAITING_ENABLED = (() => {
+  const raw = (process.env.AGT_KANBAN_WAITING_ENABLED ?? "").trim().toLowerCase();
+  return raw === "true" || raw === "1";
+})();
 if (!AGT_HOST || !AGT_AGENT_ID || !AGT_TOKEN && !AGT_API_KEY && !AGT_AGENT_SESSION_TOKEN) {
   console.error(
     "augmented-mcp: Missing required env vars. Need AGT_HOST, AGT_AGENT_ID, and one of AGT_AGENT_SESSION_TOKEN, AGT_TOKEN, or AGT_API_KEY"
@@ -21775,14 +21779,22 @@ 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) - set waiting_on to that single concrete action, phrased as an instruction ("Merge PR #3120", "Approve the budget"). 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 (blocked on a human decision or an external dependency); pair it with 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",
-  '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).',
+  kanbanMoveDescription,
   {
     id: external_exports.string().optional().describe("Item UUID (preferred)"),
     title: external_exports.string().optional().describe("Item title for fuzzy match (if no id)"),
-    status: external_exports.enum(["backlog", "todo", "in_progress", "done", "failed"]).describe('Target status. "failed" closes the row as a failed attempt; there is no "cancelled" status \u2014 close no-longer-needed work via kanban_done with an explanatory result.'),
-    notes: external_exports.string().optional().describe("Progress notes")
+    status: external_exports.enum(kanbanMoveStatuses).describe(kanbanMoveStatusDescribe),
+    notes: external_exports.string().optional().describe("Progress notes"),
+    ...AGT_KANBAN_WAITING_ENABLED ? {
+      waiting_on: external_exports.string().optional().describe(
+        'Only with status="waiting": the single concrete action you are parked on, phrased as an instruction ("Merge PR #3120", "Approve the budget"). Shown as the card headline.'
+      )
+    } : {}
   },
   async (params) => {
     if (!params.id && !params.title) {
@@ -21798,7 +21810,8 @@ server.tool(
           id: params.id,
           title: params.title,
           status: params.status,
-          notes: params.notes
+          notes: params.notes,
+          waiting_on: params.waiting_on
         }
       ]
     });
@@ -23473,8 +23486,11 @@ function statusLabel(status) {
     backlog: "Backlog",
     todo: "To Do",
     in_progress: "In Progress",
+    waiting: "Waiting",
     done: "Done",
-    failed: "Failed"
+    failed: "Failed",
+    // ENG-5723: reaper-only state; render it if the board carries one.
+    needs_attention: "Needs attention"
   };
   return labels[status] ?? status;
 }

package/dist/mcp/origami.js

@@ -39322,7 +39322,8 @@ var KANBAN_STATUSES = [
   "done",
   "failed",
   "cancelled",
-  "needs_attention"
+  "needs_attention",
+  "waiting"
 ];
 var KANBAN_STATUS_SET = new Set(KANBAN_STATUSES);
 
@@ -40174,6 +40175,21 @@ var FLAG_REGISTRY = [
     // current behaviour (single-slot injection). Turning it ON only makes the
     // fallback MORE conservative (injects less), so it removes no control.
     defaultValue: false
+  },
+  {
+    key: "kanban-waiting-status",
+    description: "Let managed agents set the 'waiting' kanban status via POST /host/kanban (ADR-0044 / ENG-7493) - work that has started but is parked on a human decision or an external dependency (a PR review, an approval). This is the DEPLOY-ORDER gate (ADR-0044 section 8): the status value + its migration (20260709000003), the webapp Waiting column, and the ~7-day reaper backstop all ship first, and this flag is flipped ON per org LAST, once they are live - the moment agents are allowed to emit `waiting`. Off (default) = the API rejects an agent `waiting` write with the existing 400, exactly as today. The API gate (evaluated per-org in POST /host/kanban via getEvaluatedFlags()) is the authoritative boundary. It is ALSO materialized host-side into AGT_KANBAN_WAITING_ENABLED (ENG-7591) so the kanban_move MCP tool only exposes `waiting` to agents once the host resolves the flag on - a host-grained UX hint, not the security boundary (the per-org API gate still decides). Ships dark.",
+    flagType: "boolean",
+    // Declared safe value is `false`: agents cannot emit `waiting` until an operator
+    // flips it on for the org, after the migration + webapp column + reaper backstop
+    // are deployed. Turning it ON grants a new capability, so it is not sensitive in
+    // the "relaxing a control" sense, but it MUST stay off until the deploy order is met.
+    defaultValue: false,
+    // Host-side materialization vehicle (ENG-7591): the manager writes this into the
+    // agent's spawn env from the resolved flag so the stdio MCP server (which cannot
+    // call the flag evaluator) can gate the kanban_move `waiting` option. Also the
+    // highest-precedence operator override, per ADR-0022.
+    envVar: "AGT_KANBAN_WAITING_ENABLED"
   }
 ];
 var REGISTRY_BY_KEY = new Map(FLAG_REGISTRY.map((definition) => [definition.key, definition]));

package/dist/{persistent-session-7H3IYXXP.js → persistent-session-WRL7JV3G.js}

@@ -36,7 +36,7 @@ import {
   writeDirectChatSessionState,
   writeEgressAllowlist,
   writePersistentClaudeWrapper
-} from "./chunk-C4QMCOAN.js";
+} from "./chunk-CUQUOIPW.js";
 import "./chunk-XWVM4KPK.js";
 export {
   EGRESS_BASELINE_DOMAINS,
@@ -77,4 +77,4 @@ export {
   writeEgressAllowlist,
   writePersistentClaudeWrapper
 };
-//# sourceMappingURL=persistent-session-7H3IYXXP.js.map
+//# sourceMappingURL=persistent-session-WRL7JV3G.js.map

package/dist/{responsiveness-probe-PFJM4QMQ.js → responsiveness-probe-LSRBQ5OJ.js}

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

package/package.json

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