@integrity-labs/agt-cli 0.28.559 → 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/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.559",
+  "version": "0.28.560",
   "description": "Augmented Team CLI — agent provisioning and management",
   "type": "module",
   "engines": {