@integrity-labs/agt-cli 0.28.451 → 0.28.453

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

@@ -35119,15 +35119,24 @@ var FLAG_REGISTRY = [
     // a deliberate availability trade (the refusal is free, but it is still a
     // dispatch the operator previously suppressed), so flipping toward it is an
     // audited change (ADR-0022 sensitive-flag confirm).
-    sensitive: true
-    // ENG-8149: `since` is the agt-cli version that first carries
-    // resolveUsageLimitReactiveMode + the MCP watcher. It cannot be known before
-    // this lands (the auto-publish patch-bumps on merge), and an undefined
-    // `since` makes the flip-reach modal claim FULL reach - true for flags that
-    // predate the reach work, wrong for a NEW host-read flag whose reader older
-    // hosts simply do not have. Backfilled by a follow-up commit once the
-    // publishing run reports the version. Excluded from projectDefinition, so
+    sensitive: true,
+    // ENG-8149 / ENG-8229: the agt-cli that first carries
+    // resolveUsageLimitReactiveMode in ALL THREE channel servers - published from
+    // the ENG-8207 merge 0294fa1a8. Without this the flip-reach modal reports FULL
+    // reach, because an undefined `since` means "every host can honour it" - true
+    // for flags that predate the reach work, wrong for a NEW host-read flag whose
+    // reader older hosts simply do not have. Excluded from projectDefinition, so
     // setting it does not roll FLAGS_SCHEMA_VERSION.
+    //
+    // Deliberately the LATER of the two versions this flag's reader shipped in.
+    // Unlike its siblings, this reader landed in two stages: direct-chat at the
+    // ENG-8201 Slice 2 publish, slack + telegram only at 0.28.450 (ENG-8207) - and
+    // `since` is one version per flag, so it cannot express "partially honoured".
+    // A host in between genuinely honours the flag for direct-chat and is still
+    // classified `stale`. That understates reach rather than overstating it, which
+    // is the safe direction, and it is the useful one while the flag sits at
+    // enforce and slack/telegram adoption is what an operator needs to track.
+    since: "0.28.450"
   },
   {
     key: "slack-hot-thread-guard",
@@ -35796,6 +35805,14 @@ function computeFlagsSchemaVersion() {
 }
 var FLAGS_SCHEMA_VERSION = computeFlagsSchemaVersion();
 
+// ../core/dist/restart/breaker-thresholds.js
+var RESTART_BREAKER_PROVISIONING_MAX = 5;
+var BIND_FAILURE_QUARANTINE_THRESHOLD = deriveBindFailureQuarantineThreshold(RESTART_BREAKER_PROVISIONING_MAX);
+function deriveBindFailureQuarantineThreshold(provisioningMax) {
+  return Math.max(2, provisioningMax - 2);
+}
+var MIN_PROVISIONING_MAX_FOR_QUARANTINE_ORDERING = BIND_FAILURE_QUARANTINE_THRESHOLD + 1;
+
 // src/usage-limit-notice.ts
 function usageLimitMarkerPath(codeName) {
   if (!codeName) return null;

package/dist/mcp/origami.js

@@ -40464,15 +40464,24 @@ var FLAG_REGISTRY = [
     // a deliberate availability trade (the refusal is free, but it is still a
     // dispatch the operator previously suppressed), so flipping toward it is an
     // audited change (ADR-0022 sensitive-flag confirm).
-    sensitive: true
-    // ENG-8149: `since` is the agt-cli version that first carries
-    // resolveUsageLimitReactiveMode + the MCP watcher. It cannot be known before
-    // this lands (the auto-publish patch-bumps on merge), and an undefined
-    // `since` makes the flip-reach modal claim FULL reach - true for flags that
-    // predate the reach work, wrong for a NEW host-read flag whose reader older
-    // hosts simply do not have. Backfilled by a follow-up commit once the
-    // publishing run reports the version. Excluded from projectDefinition, so
+    sensitive: true,
+    // ENG-8149 / ENG-8229: the agt-cli that first carries
+    // resolveUsageLimitReactiveMode in ALL THREE channel servers - published from
+    // the ENG-8207 merge 0294fa1a8. Without this the flip-reach modal reports FULL
+    // reach, because an undefined `since` means "every host can honour it" - true
+    // for flags that predate the reach work, wrong for a NEW host-read flag whose
+    // reader older hosts simply do not have. Excluded from projectDefinition, so
     // setting it does not roll FLAGS_SCHEMA_VERSION.
+    //
+    // Deliberately the LATER of the two versions this flag's reader shipped in.
+    // Unlike its siblings, this reader landed in two stages: direct-chat at the
+    // ENG-8201 Slice 2 publish, slack + telegram only at 0.28.450 (ENG-8207) - and
+    // `since` is one version per flag, so it cannot express "partially honoured".
+    // A host in between genuinely honours the flag for direct-chat and is still
+    // classified `stale`. That understates reach rather than overstating it, which
+    // is the safe direction, and it is the useful one while the flag sits at
+    // enforce and slack/telegram adoption is what an operator needs to track.
+    since: "0.28.450"
   },
   {
     key: "slack-hot-thread-guard",
@@ -41141,6 +41150,14 @@ function computeFlagsSchemaVersion() {
 }
 var FLAGS_SCHEMA_VERSION = computeFlagsSchemaVersion();
 
+// ../core/dist/restart/breaker-thresholds.js
+var RESTART_BREAKER_PROVISIONING_MAX = 5;
+var BIND_FAILURE_QUARANTINE_THRESHOLD = deriveBindFailureQuarantineThreshold(RESTART_BREAKER_PROVISIONING_MAX);
+function deriveBindFailureQuarantineThreshold(provisioningMax) {
+  return Math.max(2, provisioningMax - 2);
+}
+var MIN_PROVISIONING_MAX_FOR_QUARANTINE_ORDERING = BIND_FAILURE_QUARANTINE_THRESHOLD + 1;
+
 // src/identity.ts
 var IdentityError = class extends Error {
   status;

package/dist/mcp/slack-channel.js

@@ -34688,15 +34688,24 @@ var FLAG_REGISTRY = [
     // a deliberate availability trade (the refusal is free, but it is still a
     // dispatch the operator previously suppressed), so flipping toward it is an
     // audited change (ADR-0022 sensitive-flag confirm).
-    sensitive: true
-    // ENG-8149: `since` is the agt-cli version that first carries
-    // resolveUsageLimitReactiveMode + the MCP watcher. It cannot be known before
-    // this lands (the auto-publish patch-bumps on merge), and an undefined
-    // `since` makes the flip-reach modal claim FULL reach - true for flags that
-    // predate the reach work, wrong for a NEW host-read flag whose reader older
-    // hosts simply do not have. Backfilled by a follow-up commit once the
-    // publishing run reports the version. Excluded from projectDefinition, so
+    sensitive: true,
+    // ENG-8149 / ENG-8229: the agt-cli that first carries
+    // resolveUsageLimitReactiveMode in ALL THREE channel servers - published from
+    // the ENG-8207 merge 0294fa1a8. Without this the flip-reach modal reports FULL
+    // reach, because an undefined `since` means "every host can honour it" - true
+    // for flags that predate the reach work, wrong for a NEW host-read flag whose
+    // reader older hosts simply do not have. Excluded from projectDefinition, so
     // setting it does not roll FLAGS_SCHEMA_VERSION.
+    //
+    // Deliberately the LATER of the two versions this flag's reader shipped in.
+    // Unlike its siblings, this reader landed in two stages: direct-chat at the
+    // ENG-8201 Slice 2 publish, slack + telegram only at 0.28.450 (ENG-8207) - and
+    // `since` is one version per flag, so it cannot express "partially honoured".
+    // A host in between genuinely honours the flag for direct-chat and is still
+    // classified `stale`. That understates reach rather than overstating it, which
+    // is the safe direction, and it is the useful one while the flag sits at
+    // enforce and slack/telegram adoption is what an operator needs to track.
+    since: "0.28.450"
   },
   {
     key: "slack-hot-thread-guard",
@@ -35365,6 +35374,14 @@ function computeFlagsSchemaVersion() {
 }
 var FLAGS_SCHEMA_VERSION = computeFlagsSchemaVersion();
 
+// ../core/dist/restart/breaker-thresholds.js
+var RESTART_BREAKER_PROVISIONING_MAX = 5;
+var BIND_FAILURE_QUARANTINE_THRESHOLD = deriveBindFailureQuarantineThreshold(RESTART_BREAKER_PROVISIONING_MAX);
+function deriveBindFailureQuarantineThreshold(provisioningMax) {
+  return Math.max(2, provisioningMax - 2);
+}
+var MIN_PROVISIONING_MAX_FOR_QUARANTINE_ORDERING = BIND_FAILURE_QUARANTINE_THRESHOLD + 1;
+
 // src/usage-limit-notice.ts
 function usageLimitMarkerPath(codeName) {
   if (!codeName) return null;

package/dist/mcp/telegram-channel.js

@@ -34990,15 +34990,24 @@ var FLAG_REGISTRY = [
     // a deliberate availability trade (the refusal is free, but it is still a
     // dispatch the operator previously suppressed), so flipping toward it is an
     // audited change (ADR-0022 sensitive-flag confirm).
-    sensitive: true
-    // ENG-8149: `since` is the agt-cli version that first carries
-    // resolveUsageLimitReactiveMode + the MCP watcher. It cannot be known before
-    // this lands (the auto-publish patch-bumps on merge), and an undefined
-    // `since` makes the flip-reach modal claim FULL reach - true for flags that
-    // predate the reach work, wrong for a NEW host-read flag whose reader older
-    // hosts simply do not have. Backfilled by a follow-up commit once the
-    // publishing run reports the version. Excluded from projectDefinition, so
+    sensitive: true,
+    // ENG-8149 / ENG-8229: the agt-cli that first carries
+    // resolveUsageLimitReactiveMode in ALL THREE channel servers - published from
+    // the ENG-8207 merge 0294fa1a8. Without this the flip-reach modal reports FULL
+    // reach, because an undefined `since` means "every host can honour it" - true
+    // for flags that predate the reach work, wrong for a NEW host-read flag whose
+    // reader older hosts simply do not have. Excluded from projectDefinition, so
     // setting it does not roll FLAGS_SCHEMA_VERSION.
+    //
+    // Deliberately the LATER of the two versions this flag's reader shipped in.
+    // Unlike its siblings, this reader landed in two stages: direct-chat at the
+    // ENG-8201 Slice 2 publish, slack + telegram only at 0.28.450 (ENG-8207) - and
+    // `since` is one version per flag, so it cannot express "partially honoured".
+    // A host in between genuinely honours the flag for direct-chat and is still
+    // classified `stale`. That understates reach rather than overstating it, which
+    // is the safe direction, and it is the useful one while the flag sits at
+    // enforce and slack/telegram adoption is what an operator needs to track.
+    since: "0.28.450"
   },
   {
     key: "slack-hot-thread-guard",
@@ -35667,6 +35676,14 @@ function computeFlagsSchemaVersion() {
 }
 var FLAGS_SCHEMA_VERSION = computeFlagsSchemaVersion();
 
+// ../core/dist/restart/breaker-thresholds.js
+var RESTART_BREAKER_PROVISIONING_MAX = 5;
+var BIND_FAILURE_QUARANTINE_THRESHOLD = deriveBindFailureQuarantineThreshold(RESTART_BREAKER_PROVISIONING_MAX);
+function deriveBindFailureQuarantineThreshold(provisioningMax) {
+  return Math.max(2, provisioningMax - 2);
+}
+var MIN_PROVISIONING_MAX_FOR_QUARANTINE_ORDERING = BIND_FAILURE_QUARANTINE_THRESHOLD + 1;
+
 // src/usage-limit-notice.ts
 function usageLimitMarkerPath(codeName) {
   if (!codeName) return null;

package/dist/{persistent-session-7HZXY56P.js → persistent-session-X5N7UFEF.js}

@@ -36,7 +36,7 @@ import {
   writeDirectChatSessionState,
   writeEgressAllowlist,
   writePersistentClaudeWrapper
-} from "./chunk-ESZRW7A3.js";
+} from "./chunk-3NJHNIO3.js";
 import "./chunk-XWVM4KPK.js";
 export {
   EGRESS_BASELINE_DOMAINS,
@@ -77,4 +77,4 @@ export {
   writeEgressAllowlist,
   writePersistentClaudeWrapper
 };
-//# sourceMappingURL=persistent-session-7HZXY56P.js.map
+//# sourceMappingURL=persistent-session-X5N7UFEF.js.map

package/dist/{responsiveness-probe-AIA7ZEBW.js → responsiveness-probe-OAZ55KPC.js}

@@ -1,6 +1,6 @@
 import {
   paneLogPath
-} from "./chunk-ESZRW7A3.js";
+} from "./chunk-3NJHNIO3.js";
 import "./chunk-XWVM4KPK.js";
 
 // src/lib/responsiveness-probe.ts
@@ -528,4 +528,4 @@ export {
   readAndResetSlackReplyBindingClassifications,
   readAndResetSlackReplyTargetClassifications
 };
-//# sourceMappingURL=responsiveness-probe-AIA7ZEBW.js.map
+//# sourceMappingURL=responsiveness-probe-OAZ55KPC.js.map

package/package.json

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