@integrity-labs/agt-cli 0.28.1005 → 0.28.1006

package/dist/{chunk-6U4NB3LJ.js → chunk-Z5UDL4AB.js}

@@ -15,7 +15,7 @@ import {
   parseEnvFileEntries,
   parseEnvIntegrations,
   shellQuote
-} from "./chunk-TGTUE7Y2.js";
+} from "./chunk-O6R6HS2Z.js";
 import {
   BIND_FAILURE_QUARANTINE_THRESHOLD,
   INTEGRATIONS_SECTION_END,
@@ -75,7 +75,7 @@ import {
   sessionTranscriptDir,
   worseConnectivityOutcome,
   wrapScheduledTaskPrompt
-} from "./chunk-DVSYT4MU.js";
+} from "./chunk-XWMUQR65.js";
 import {
   classifyUnanswerablePane,
   summarizeUnanswerablePane
@@ -6974,7 +6974,7 @@ function exchangeFailureKind(err) {
 }
 
 // src/lib/api-client.ts
-var agtCliVersion = true ? "0.28.1005" : "dev";
+var agtCliVersion = true ? "0.28.1006" : "dev";
 var lastConfigHash = null;
 function setConfigHash(hash) {
   lastConfigHash = hash && hash.length > 0 ? hash : null;
@@ -8533,7 +8533,32 @@ var PROVISIONING_RELOAD_REASONS = /* @__PURE__ */ new Set([
   // ENG-9861: and again for standing rules. The fail-closed first-poll restart
   // has exactly the same shape, so it needs the same protection from a host
   // whose sidecar write keeps failing.
-  "agent-rules-change"
+  "agent-rules-change",
+  // ENG-10510 (Obi-Wan on #6313): a channel-set ADD is a config reload, not a
+  // crash, and it was landing on the crash tally purely by falling through.
+  // It is 'integration-change's exact sibling - both are "a channel or server
+  // was added, re-render .mcp.json and respawn" - and it was never argued for
+  // the crash class, it simply was not in this set.
+  //
+  // This is the ENG-9138 / ENG-10066 species verbatim: a PLATFORM-MANUFACTURED
+  // restart counted as though the agent had crashed. ENG-9138 cost katie 8h16m
+  // when day-rollover fell through the same way; ENG-10066 cost an operator an
+  // auto-pause when a channel /restart did. Both were fixed by naming the
+  // reason rather than leaving it to the catch-all, and this is the third.
+  //
+  // WHY NOW. Until ENG-10510 this restart only ever followed a human adding a
+  // channel, so the crash tally was wrong but rarely reached: a person adding
+  // two channels inside ten minutes is uncommon and self-limiting. Channel
+  // auto-resume is the first thing that fires it UNATTENDED, on a timer, on
+  // any agent with a quarantined channel. An agent with a second crash-class
+  // restart in the same ten minutes (the presence reaper's
+  // 'mcp-presence-reaper', for one) would cross DEFAULT_MAX and auto-pause
+  // with no human anywhere in the loop - which is precisely the ENG-8215 harm
+  // that feature's 2h floor exists to prevent.
+  //
+  // Counted, not exempt: provisioning is a LOOSER tally, not an absent one, so
+  // sustained channel-set thrash still trips and still pages.
+  "channel-set-change"
 ]);
 function isProvisioningReloadReason(reason) {
   return PROVISIONING_RELOAD_REASONS.has(reason);
@@ -8568,7 +8593,11 @@ var OPERATOR_CONFIG_REASONS = /* @__PURE__ */ new Set([
 function isOperatorConfigReason(reason) {
   return OPERATOR_CONFIG_REASONS.has(reason);
 }
+var NEVER_INTEGRATION_BUCKETED = /* @__PURE__ */ new Set([
+  "channel-set-change"
+]);
 function isIntegrationBucketedReason(reason) {
+  if (NEVER_INTEGRATION_BUCKETED.has(reason)) return false;
   return isProvisioningReloadReason(reason) || isOperatorConfigReason(reason);
 }
 function restartReasonClass(reason) {
@@ -11683,6 +11712,7 @@ export {
   liveProxyExtraHeaderVars,
   liveProxyTokenVars,
   reapStaleMcpChildren,
+  DEAD_CHANNEL_MS,
   clearPresenceReaperState,
   clearPresenceReaperStateForKeys,
   givenUpMcpServerKeys,
@@ -11725,4 +11755,4 @@ export {
   managerInstallSystemUnitCommand,
   managerUninstallSystemUnitCommand
 };
-//# sourceMappingURL=chunk-6U4NB3LJ.js.map
+//# sourceMappingURL=chunk-Z5UDL4AB.js.map