@integrity-labs/agt-cli 0.28.394 → 0.28.396

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

@@ -34888,6 +34888,18 @@ var FLAG_REGISTRY = [
     sensitive: true
     // No envVar - net-new API-side control with no pre-flags env gate to migrate (ADR-0022).
   },
+  {
+    key: "mcp-auto-resume-mode",
+    description: "MCP auto-resume of a bind-failure quarantine (ENG-8036, follow-up to ENG-7916): off = disabled, shadow = log only (would-resume without acting), enforce = flip an ENG-7916-quarantined integration (status=unhealthy) back to status=active after DEFAULT_AUTO_RESUME_OK_CYCLES consecutive healthy connectivity-probe cycles. Recovery is observed via the connectivity-probe path, not the session-tool-bind probe (a quarantined row is excluded from the bind probe by the ENG-5292 writer). Only rows this quarantine system marked are auto-resumed - the reaper/oauth-refresh error/unhealthy states are never stomped. Declared safe value is off (fully dark): a flag-DB read error must never auto-un-quarantine on its own. Flip to shadow to observe, then enforce once the cycle threshold is tuned.",
+    flagType: "enum",
+    allowedValues: ["off", "shadow", "enforce"],
+    // off = fully dark. See comment block above for the fail-safe direction.
+    defaultValue: "off",
+    // Enforcement-mode control, like its ENG-7916 sibling mcp-quarantine-mode:
+    // masked on public surfaces and mutations require explicit confirmation.
+    sensitive: true
+    // No envVar - net-new API-side control with no pre-flags env gate to migrate (ADR-0022).
+  },
   {
     key: "channel-quarantine-mode",
     description: "Optional-channel quarantine (ENG-5932): off = disabled, shadow = log matches only, enforce = quarantine.",

package/dist/mcp/origami.js

@@ -40552,6 +40552,18 @@ var FLAG_REGISTRY = [
     sensitive: true
     // No envVar - net-new API-side control with no pre-flags env gate to migrate (ADR-0022).
   },
+  {
+    key: "mcp-auto-resume-mode",
+    description: "MCP auto-resume of a bind-failure quarantine (ENG-8036, follow-up to ENG-7916): off = disabled, shadow = log only (would-resume without acting), enforce = flip an ENG-7916-quarantined integration (status=unhealthy) back to status=active after DEFAULT_AUTO_RESUME_OK_CYCLES consecutive healthy connectivity-probe cycles. Recovery is observed via the connectivity-probe path, not the session-tool-bind probe (a quarantined row is excluded from the bind probe by the ENG-5292 writer). Only rows this quarantine system marked are auto-resumed - the reaper/oauth-refresh error/unhealthy states are never stomped. Declared safe value is off (fully dark): a flag-DB read error must never auto-un-quarantine on its own. Flip to shadow to observe, then enforce once the cycle threshold is tuned.",
+    flagType: "enum",
+    allowedValues: ["off", "shadow", "enforce"],
+    // off = fully dark. See comment block above for the fail-safe direction.
+    defaultValue: "off",
+    // Enforcement-mode control, like its ENG-7916 sibling mcp-quarantine-mode:
+    // masked on public surfaces and mutations require explicit confirmation.
+    sensitive: true
+    // No envVar - net-new API-side control with no pre-flags env gate to migrate (ADR-0022).
+  },
   {
     key: "channel-quarantine-mode",
     description: "Optional-channel quarantine (ENG-5932): off = disabled, shadow = log matches only, enforce = quarantine.",

package/dist/mcp/slack-channel.js

@@ -34471,6 +34471,18 @@ var FLAG_REGISTRY = [
     sensitive: true
     // No envVar - net-new API-side control with no pre-flags env gate to migrate (ADR-0022).
   },
+  {
+    key: "mcp-auto-resume-mode",
+    description: "MCP auto-resume of a bind-failure quarantine (ENG-8036, follow-up to ENG-7916): off = disabled, shadow = log only (would-resume without acting), enforce = flip an ENG-7916-quarantined integration (status=unhealthy) back to status=active after DEFAULT_AUTO_RESUME_OK_CYCLES consecutive healthy connectivity-probe cycles. Recovery is observed via the connectivity-probe path, not the session-tool-bind probe (a quarantined row is excluded from the bind probe by the ENG-5292 writer). Only rows this quarantine system marked are auto-resumed - the reaper/oauth-refresh error/unhealthy states are never stomped. Declared safe value is off (fully dark): a flag-DB read error must never auto-un-quarantine on its own. Flip to shadow to observe, then enforce once the cycle threshold is tuned.",
+    flagType: "enum",
+    allowedValues: ["off", "shadow", "enforce"],
+    // off = fully dark. See comment block above for the fail-safe direction.
+    defaultValue: "off",
+    // Enforcement-mode control, like its ENG-7916 sibling mcp-quarantine-mode:
+    // masked on public surfaces and mutations require explicit confirmation.
+    sensitive: true
+    // No envVar - net-new API-side control with no pre-flags env gate to migrate (ADR-0022).
+  },
   {
     key: "channel-quarantine-mode",
     description: "Optional-channel quarantine (ENG-5932): off = disabled, shadow = log matches only, enforce = quarantine.",

package/dist/mcp/telegram-channel.js

@@ -34821,6 +34821,18 @@ var FLAG_REGISTRY = [
     sensitive: true
     // No envVar - net-new API-side control with no pre-flags env gate to migrate (ADR-0022).
   },
+  {
+    key: "mcp-auto-resume-mode",
+    description: "MCP auto-resume of a bind-failure quarantine (ENG-8036, follow-up to ENG-7916): off = disabled, shadow = log only (would-resume without acting), enforce = flip an ENG-7916-quarantined integration (status=unhealthy) back to status=active after DEFAULT_AUTO_RESUME_OK_CYCLES consecutive healthy connectivity-probe cycles. Recovery is observed via the connectivity-probe path, not the session-tool-bind probe (a quarantined row is excluded from the bind probe by the ENG-5292 writer). Only rows this quarantine system marked are auto-resumed - the reaper/oauth-refresh error/unhealthy states are never stomped. Declared safe value is off (fully dark): a flag-DB read error must never auto-un-quarantine on its own. Flip to shadow to observe, then enforce once the cycle threshold is tuned.",
+    flagType: "enum",
+    allowedValues: ["off", "shadow", "enforce"],
+    // off = fully dark. See comment block above for the fail-safe direction.
+    defaultValue: "off",
+    // Enforcement-mode control, like its ENG-7916 sibling mcp-quarantine-mode:
+    // masked on public surfaces and mutations require explicit confirmation.
+    sensitive: true
+    // No envVar - net-new API-side control with no pre-flags env gate to migrate (ADR-0022).
+  },
   {
     key: "channel-quarantine-mode",
     description: "Optional-channel quarantine (ENG-5932): off = disabled, shadow = log matches only, enforce = quarantine.",

package/dist/{persistent-session-QRUINHGI.js → persistent-session-34CDP2I3.js}

@@ -36,7 +36,7 @@ import {
   writeDirectChatSessionState,
   writeEgressAllowlist,
   writePersistentClaudeWrapper
-} from "./chunk-7HONFACG.js";
+} from "./chunk-4LZBDTFJ.js";
 import "./chunk-XWVM4KPK.js";
 export {
   EGRESS_BASELINE_DOMAINS,
@@ -77,4 +77,4 @@ export {
   writeEgressAllowlist,
   writePersistentClaudeWrapper
 };
-//# sourceMappingURL=persistent-session-QRUINHGI.js.map
+//# sourceMappingURL=persistent-session-34CDP2I3.js.map

package/dist/{responsiveness-probe-IHKBNMSQ.js → responsiveness-probe-T7WBF4FX.js}

@@ -1,6 +1,6 @@
 import {
   paneLogPath
-} from "./chunk-7HONFACG.js";
+} from "./chunk-4LZBDTFJ.js";
 import "./chunk-XWVM4KPK.js";
 
 // src/lib/responsiveness-probe.ts
@@ -437,4 +437,4 @@ export {
   readAndResetSlackReplyBindingClassifications,
   readAndResetSlackReplyTargetClassifications
 };
-//# sourceMappingURL=responsiveness-probe-IHKBNMSQ.js.map
+//# sourceMappingURL=responsiveness-probe-T7WBF4FX.js.map

package/package.json

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