@integrity-labs/agt-cli 0.28.558 → 0.28.560

package/dist/mcp/direct-chat-channel.js

@@ -34975,6 +34975,12 @@ var FLAG_REGISTRY = [
     // operational decision with blast radius, so mutations require confirmation.
     sensitive: true
   },
+  {
+    key: "frozen-customer-waiting-page",
+    description: "Frozen-prompt-with-a-customer-waiting PAGE (ENG-8683): when ON, the responsiveness-probe route opens a `warning` `agent_frozen_customer_waiting` alert for an agent whose input watchdog gave up on the session AFTER a message was queued, and whose message is still unanswered past the window. Both halves were already measured in the same request and both were `info` (agent_input_stuck, agent_pending_inbound), which alert-pager drops before routing \u2014 so the condition was detected twice a minute and paged nobody. Defaults ON, unlike the usual ships-dark posture for anything that pages, because both inputs have been in observe mode for months (the input-stuck alarm has defaulted ON since ENG-6055, the pending-inbound metric has been written since ENG-6017) and the conjunction is strictly narrower than either \u2014 shipping it dark would make the fix a fleet-wide no-op and leave the ticket open in everything but name. Flip OFF from the admin Feature Flags page to disarm stage-wide; the wait window is tuned with the AUGMENTED_FROZEN_CUSTOMER_WAITING_SECONDS API tunable (default 300). No envVar: an API-evaluated flag with a declared envVar risks the ENG-8303 sst.config.ts pin, and a new AUGMENTED_*_ENABLED gate is what check-new-env-gates.sh rejects.",
+    flagType: "boolean",
+    defaultValue: true
+  },
   {
     key: "promise-outstanding-alarm",
     description: 'Outstanding-interim-promise alarm (ENG-8265): when ON, the responsiveness-probe route creates a per-agent CloudWatch alarm on `PromiseOutstandingOldestAgeSeconds` \u2014 an inbound the agent acknowledged with an interim reply ("on it") and never answered substantively. Closes the blind spot where an ack satisfied channel-silent-loss, refreshed pending-inbound, and left agent_stall with no in_progress card to see, so a broken promise looked like a served request. Defaults ON (armed on deploy) because the alert it opens is `info` severity \u2014 dashboard-only, never paged \u2014 so a day-one false positive costs a visible row, not a woken human. Flip OFF from the admin Feature Flags page to disarm stage-wide; the window itself is tuned with the AUGMENTED_PROMISE_OUTSTANDING_THRESHOLD_SECONDS API tunable (default 1800).',

package/dist/mcp/index.js

@@ -21083,14 +21083,47 @@ function groupKanbanByStatus(items) {
   }
   return groups;
 }
-function renderKanbanItemLine(item) {
+function formatWaitingAge(since, nowMs) {
+  if (!since) return null;
+  const ms = nowMs - Date.parse(since);
+  if (!Number.isFinite(ms)) return null;
+  const mins = Math.max(0, Math.floor(ms / 6e4));
+  if (mins < 1) return "<1m";
+  if (mins < 60) return `${mins}m`;
+  const hours = Math.floor(mins / 60);
+  if (hours < 24) return `${hours}h`;
+  return `${Math.floor(hours / 24)}d`;
+}
+function renderPrWaitTarget(item) {
+  if (item.waiting_kind !== "pr-review" && item.waiting_kind !== "pr-merged") return null;
+  const pr = item.waiting_context?.pr_number;
+  if (!Number.isSafeInteger(pr) || pr <= 0) return null;
+  const verb = item.waiting_kind === "pr-review" ? "Review" : "Merge";
+  const repo = item.waiting_context?.repo;
+  const where = repo && repo !== "Integrity-Labs/augmented" ? ` in ${repo}` : "";
+  return `${verb} PR #${pr}${where}`;
+}
+function renderWaitingClause(item, nowMs) {
+  if (item.status !== "waiting") return "";
+  const parts = [];
+  if (item.waiting_kind) parts.push(item.waiting_kind);
+  const age = formatWaitingAge(item.waiting_since, nowMs);
+  if (age) parts.push(`${age}`);
+  const head = parts.length ? ` \u23F8 ${parts.join(", ")}` : "";
+  const prTarget = renderPrWaitTarget(item);
+  if (prTarget) return head ? `${head}: ${prTarget}` : ` \u23F8 ${prTarget}`;
+  const ask = item.waiting_on ? `: ${item.waiting_on.length > 80 ? `${item.waiting_on.slice(0, 77)}...` : item.waiting_on}` : "";
+  return head ? `${head}${ask}` : "";
+}
+function renderKanbanItemLine(item, nowMs) {
   const pri = kanbanPriorityLabel(item.priority);
   const est = item.estimated_minutes ? ` ~${item.estimated_minutes}min` : "";
   const del = item.deliverable ? ` \u2192 ${item.deliverable}` : "";
   const res = item.result ? ` \u2713 ${item.result}` : "";
-  return `- [${pri}] ${item.title}${est}${del}${res} (id: ${item.id})`;
+  const wait = renderWaitingClause(item, nowMs);
+  return `- [${pri}] ${item.title}${wait}${est}${del}${res} (id: ${item.id})`;
 }
-function renderKanbanList(items) {
+function renderKanbanList(items, nowMs = Date.now()) {
   if (!items.length) return "Board is empty.";
   const humanAssigned = items.filter(isHumanAssigned);
   const mine = items.filter((i) => !isHumanAssigned(i));
@@ -21104,7 +21137,7 @@ function renderKanbanList(items) {
     if (!group?.length) continue;
     lines.push(`
 ## ${kanbanStatusLabel(status)} (${group.length})`);
-    for (const item of group) lines.push(renderKanbanItemLine(item));
+    for (const item of group) lines.push(renderKanbanItemLine(item, nowMs));
   }
   if (humanAssigned.length) {
     lines.push(`
@@ -21112,7 +21145,7 @@ function renderKanbanList(items) {
     lines.push(HUMAN_ASSIGNED_SECTION_NOTE);
     for (const item of humanAssigned) {
       const who = item.assignee_name ? ` [with ${item.assignee_name}]` : "";
-      lines.push(`${renderKanbanItemLine(item)}${who}`);
+      lines.push(`${renderKanbanItemLine(item, nowMs)}${who}`);
     }
   }
   return lines.join("\n");

package/dist/mcp/origami.js

@@ -40866,6 +40866,12 @@ var FLAG_REGISTRY = [
     // operational decision with blast radius, so mutations require confirmation.
     sensitive: true
   },
+  {
+    key: "frozen-customer-waiting-page",
+    description: "Frozen-prompt-with-a-customer-waiting PAGE (ENG-8683): when ON, the responsiveness-probe route opens a `warning` `agent_frozen_customer_waiting` alert for an agent whose input watchdog gave up on the session AFTER a message was queued, and whose message is still unanswered past the window. Both halves were already measured in the same request and both were `info` (agent_input_stuck, agent_pending_inbound), which alert-pager drops before routing \u2014 so the condition was detected twice a minute and paged nobody. Defaults ON, unlike the usual ships-dark posture for anything that pages, because both inputs have been in observe mode for months (the input-stuck alarm has defaulted ON since ENG-6055, the pending-inbound metric has been written since ENG-6017) and the conjunction is strictly narrower than either \u2014 shipping it dark would make the fix a fleet-wide no-op and leave the ticket open in everything but name. Flip OFF from the admin Feature Flags page to disarm stage-wide; the wait window is tuned with the AUGMENTED_FROZEN_CUSTOMER_WAITING_SECONDS API tunable (default 300). No envVar: an API-evaluated flag with a declared envVar risks the ENG-8303 sst.config.ts pin, and a new AUGMENTED_*_ENABLED gate is what check-new-env-gates.sh rejects.",
+    flagType: "boolean",
+    defaultValue: true
+  },
   {
     key: "promise-outstanding-alarm",
     description: 'Outstanding-interim-promise alarm (ENG-8265): when ON, the responsiveness-probe route creates a per-agent CloudWatch alarm on `PromiseOutstandingOldestAgeSeconds` \u2014 an inbound the agent acknowledged with an interim reply ("on it") and never answered substantively. Closes the blind spot where an ack satisfied channel-silent-loss, refreshed pending-inbound, and left agent_stall with no in_progress card to see, so a broken promise looked like a served request. Defaults ON (armed on deploy) because the alert it opens is `info` severity \u2014 dashboard-only, never paged \u2014 so a day-one false positive costs a visible row, not a woken human. Flip OFF from the admin Feature Flags page to disarm stage-wide; the window itself is tuned with the AUGMENTED_PROMISE_OUTSTANDING_THRESHOLD_SECONDS API tunable (default 1800).',

package/dist/mcp/slack-channel.js

@@ -35311,6 +35311,12 @@ var FLAG_REGISTRY = [
     // operational decision with blast radius, so mutations require confirmation.
     sensitive: true
   },
+  {
+    key: "frozen-customer-waiting-page",
+    description: "Frozen-prompt-with-a-customer-waiting PAGE (ENG-8683): when ON, the responsiveness-probe route opens a `warning` `agent_frozen_customer_waiting` alert for an agent whose input watchdog gave up on the session AFTER a message was queued, and whose message is still unanswered past the window. Both halves were already measured in the same request and both were `info` (agent_input_stuck, agent_pending_inbound), which alert-pager drops before routing \u2014 so the condition was detected twice a minute and paged nobody. Defaults ON, unlike the usual ships-dark posture for anything that pages, because both inputs have been in observe mode for months (the input-stuck alarm has defaulted ON since ENG-6055, the pending-inbound metric has been written since ENG-6017) and the conjunction is strictly narrower than either \u2014 shipping it dark would make the fix a fleet-wide no-op and leave the ticket open in everything but name. Flip OFF from the admin Feature Flags page to disarm stage-wide; the wait window is tuned with the AUGMENTED_FROZEN_CUSTOMER_WAITING_SECONDS API tunable (default 300). No envVar: an API-evaluated flag with a declared envVar risks the ENG-8303 sst.config.ts pin, and a new AUGMENTED_*_ENABLED gate is what check-new-env-gates.sh rejects.",
+    flagType: "boolean",
+    defaultValue: true
+  },
   {
     key: "promise-outstanding-alarm",
     description: 'Outstanding-interim-promise alarm (ENG-8265): when ON, the responsiveness-probe route creates a per-agent CloudWatch alarm on `PromiseOutstandingOldestAgeSeconds` \u2014 an inbound the agent acknowledged with an interim reply ("on it") and never answered substantively. Closes the blind spot where an ack satisfied channel-silent-loss, refreshed pending-inbound, and left agent_stall with no in_progress card to see, so a broken promise looked like a served request. Defaults ON (armed on deploy) because the alert it opens is `info` severity \u2014 dashboard-only, never paged \u2014 so a day-one false positive costs a visible row, not a woken human. Flip OFF from the admin Feature Flags page to disarm stage-wide; the window itself is tuned with the AUGMENTED_PROMISE_OUTSTANDING_THRESHOLD_SECONDS API tunable (default 1800).',

package/dist/mcp/telegram-channel.js

@@ -35470,6 +35470,12 @@ var FLAG_REGISTRY = [
     // operational decision with blast radius, so mutations require confirmation.
     sensitive: true
   },
+  {
+    key: "frozen-customer-waiting-page",
+    description: "Frozen-prompt-with-a-customer-waiting PAGE (ENG-8683): when ON, the responsiveness-probe route opens a `warning` `agent_frozen_customer_waiting` alert for an agent whose input watchdog gave up on the session AFTER a message was queued, and whose message is still unanswered past the window. Both halves were already measured in the same request and both were `info` (agent_input_stuck, agent_pending_inbound), which alert-pager drops before routing \u2014 so the condition was detected twice a minute and paged nobody. Defaults ON, unlike the usual ships-dark posture for anything that pages, because both inputs have been in observe mode for months (the input-stuck alarm has defaulted ON since ENG-6055, the pending-inbound metric has been written since ENG-6017) and the conjunction is strictly narrower than either \u2014 shipping it dark would make the fix a fleet-wide no-op and leave the ticket open in everything but name. Flip OFF from the admin Feature Flags page to disarm stage-wide; the wait window is tuned with the AUGMENTED_FROZEN_CUSTOMER_WAITING_SECONDS API tunable (default 300). No envVar: an API-evaluated flag with a declared envVar risks the ENG-8303 sst.config.ts pin, and a new AUGMENTED_*_ENABLED gate is what check-new-env-gates.sh rejects.",
+    flagType: "boolean",
+    defaultValue: true
+  },
   {
     key: "promise-outstanding-alarm",
     description: 'Outstanding-interim-promise alarm (ENG-8265): when ON, the responsiveness-probe route creates a per-agent CloudWatch alarm on `PromiseOutstandingOldestAgeSeconds` \u2014 an inbound the agent acknowledged with an interim reply ("on it") and never answered substantively. Closes the blind spot where an ack satisfied channel-silent-loss, refreshed pending-inbound, and left agent_stall with no in_progress card to see, so a broken promise looked like a served request. Defaults ON (armed on deploy) because the alert it opens is `info` severity \u2014 dashboard-only, never paged \u2014 so a day-one false positive costs a visible row, not a woken human. Flip OFF from the admin Feature Flags page to disarm stage-wide; the window itself is tuned with the AUGMENTED_PROMISE_OUTSTANDING_THRESHOLD_SECONDS API tunable (default 1800).',

package/dist/{persistent-session-WX4ILTCF.js → persistent-session-7P5B6Z4M.js}

@@ -41,7 +41,7 @@ import {
   writeDirectChatSessionState,
   writeEgressAllowlist,
   writePersistentClaudeWrapper
-} from "./chunk-TBP245GG.js";
+} from "./chunk-AN7V4OG6.js";
 import "./chunk-XWVM4KPK.js";
 export {
   EGRESS_BASELINE_DOMAINS,
@@ -87,4 +87,4 @@ export {
   writeEgressAllowlist,
   writePersistentClaudeWrapper
 };
-//# sourceMappingURL=persistent-session-WX4ILTCF.js.map
+//# sourceMappingURL=persistent-session-7P5B6Z4M.js.map

package/dist/{responsiveness-probe-FKJBQ6PQ.js → responsiveness-probe-AALUPZKZ.js}

@@ -1,6 +1,6 @@
 import {
   paneLogPath
-} from "./chunk-TBP245GG.js";
+} from "./chunk-AN7V4OG6.js";
 import "./chunk-XWVM4KPK.js";
 
 // src/lib/responsiveness-probe.ts
@@ -689,4 +689,4 @@ export {
   readAndResetSlackReplyBindingClassifications,
   readAndResetSlackReplyTargetClassifications
 };
-//# sourceMappingURL=responsiveness-probe-FKJBQ6PQ.js.map
+//# sourceMappingURL=responsiveness-probe-AALUPZKZ.js.map

package/package.json

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