@integrity-labs/agt-cli 0.28.509 → 0.28.511

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

@@ -34995,6 +34995,22 @@ var FLAG_REGISTRY = [
     // safe: `since` is excluded from projectDefinition, so it does not roll
     // FLAGS_SCHEMA_VERSION.
   },
+  {
+    key: "agt-version-drift-alarm",
+    description: "Arms the ENG-8341 agt CLI version-drift alert. When a host has fallen behind its EFFECTIVE target (env pin > DB pin > release channel) across two or more of its OWN maintenance windows, the monitor opens a host_agt_version_drift alert. OBSERVE-FIRST rollout gate: the cron computes and LOGS the drift for every host on every run regardless of this flag, so the real fleet spread is measurable before anyone is paged - the ticket asks for the threshold to be set from observed data rather than a guess. Off = compute and log, open nothing. Boolean gate; ships dark. Evaluated API-side, in the cron.",
+    flagType: "boolean",
+    // Declared safe value is `false`. Fail-safe direction for a NEW alerting
+    // cron is silence: ~21 hosts with no prior drift signal means the first
+    // armed pass could open an alert for every host that is behind at once.
+    // The cron also carries a bootstrap floor (agent-stall-monitor.ts's
+    // precedent) so arming it does not retroactively page for drift that
+    // started before the monitor existed.
+    defaultValue: false,
+    // Arming this makes a previously-invisible backlog visible all at once, in
+    // the same shape ENG-8204's never-spawned-session-metric warned about - so
+    // the flip is a deliberate, confirmed one (ADR-0022 sensitive-flag confirm).
+    sensitive: true
+  },
   {
     key: "memory-extraction",
     description: "Host-side durable-memory extraction (ENG-6200): the manager extracts candidate memories from completed conversations and POSTs them to /host/memories/candidates, which writes dream_log via promoteCandidates. Post persistent-session cutover this is the ONLY live consolidation path. Boolean gate; ships dark \u2014 when off the manager runs no extraction, so 0 dream_log rows fleet-wide is the expected steady state until it is armed.",

package/dist/mcp/index.js

@@ -21500,6 +21500,16 @@ function describeReconnectRequestResult(resp) {
         text: "A reconnect request for this integration was already sent recently, so no new notification went out. Stop retrying the failing tool and wait for the reconnect.",
         isError: false
       };
+    case "notified_disputed":
+      return {
+        text: "Reconnect request sent. Note that the platform still shows this integration as connected, so your report and the stored status disagree \u2014 your manager has been notified with both, and with the error you reported. Stop retrying the failing tool; a human has to resolve the disagreement.",
+        isError: false
+      };
+    // CS-1542: retained for older API stages that still return it. The route no
+    // longer emits `healthy` - a stored status is not a probe, so it is not
+    // allowed to end the request - but a host can run a newer CLI than the API
+    // it talks to, and the previous copy ("no reconnect request was sent") is
+    // the honest thing to say if this ever does come back.
     case "healthy":
       return {
         text: "The platform shows this integration as connected, so no reconnect request was sent. If the tool is still failing, tell your operator exactly what error you saw instead of retrying.",

package/dist/mcp/origami.js

@@ -40886,6 +40886,22 @@ var FLAG_REGISTRY = [
     // safe: `since` is excluded from projectDefinition, so it does not roll
     // FLAGS_SCHEMA_VERSION.
   },
+  {
+    key: "agt-version-drift-alarm",
+    description: "Arms the ENG-8341 agt CLI version-drift alert. When a host has fallen behind its EFFECTIVE target (env pin > DB pin > release channel) across two or more of its OWN maintenance windows, the monitor opens a host_agt_version_drift alert. OBSERVE-FIRST rollout gate: the cron computes and LOGS the drift for every host on every run regardless of this flag, so the real fleet spread is measurable before anyone is paged - the ticket asks for the threshold to be set from observed data rather than a guess. Off = compute and log, open nothing. Boolean gate; ships dark. Evaluated API-side, in the cron.",
+    flagType: "boolean",
+    // Declared safe value is `false`. Fail-safe direction for a NEW alerting
+    // cron is silence: ~21 hosts with no prior drift signal means the first
+    // armed pass could open an alert for every host that is behind at once.
+    // The cron also carries a bootstrap floor (agent-stall-monitor.ts's
+    // precedent) so arming it does not retroactively page for drift that
+    // started before the monitor existed.
+    defaultValue: false,
+    // Arming this makes a previously-invisible backlog visible all at once, in
+    // the same shape ENG-8204's never-spawned-session-metric warned about - so
+    // the flip is a deliberate, confirmed one (ADR-0022 sensitive-flag confirm).
+    sensitive: true
+  },
   {
     key: "memory-extraction",
     description: "Host-side durable-memory extraction (ENG-6200): the manager extracts candidate memories from completed conversations and POSTs them to /host/memories/candidates, which writes dream_log via promoteCandidates. Post persistent-session cutover this is the ONLY live consolidation path. Boolean gate; ships dark \u2014 when off the manager runs no extraction, so 0 dream_log rows fleet-wide is the expected steady state until it is armed.",

package/dist/mcp/slack-channel.js

@@ -35164,6 +35164,22 @@ var FLAG_REGISTRY = [
     // safe: `since` is excluded from projectDefinition, so it does not roll
     // FLAGS_SCHEMA_VERSION.
   },
+  {
+    key: "agt-version-drift-alarm",
+    description: "Arms the ENG-8341 agt CLI version-drift alert. When a host has fallen behind its EFFECTIVE target (env pin > DB pin > release channel) across two or more of its OWN maintenance windows, the monitor opens a host_agt_version_drift alert. OBSERVE-FIRST rollout gate: the cron computes and LOGS the drift for every host on every run regardless of this flag, so the real fleet spread is measurable before anyone is paged - the ticket asks for the threshold to be set from observed data rather than a guess. Off = compute and log, open nothing. Boolean gate; ships dark. Evaluated API-side, in the cron.",
+    flagType: "boolean",
+    // Declared safe value is `false`. Fail-safe direction for a NEW alerting
+    // cron is silence: ~21 hosts with no prior drift signal means the first
+    // armed pass could open an alert for every host that is behind at once.
+    // The cron also carries a bootstrap floor (agent-stall-monitor.ts's
+    // precedent) so arming it does not retroactively page for drift that
+    // started before the monitor existed.
+    defaultValue: false,
+    // Arming this makes a previously-invisible backlog visible all at once, in
+    // the same shape ENG-8204's never-spawned-session-metric warned about - so
+    // the flip is a deliberate, confirmed one (ADR-0022 sensitive-flag confirm).
+    sensitive: true
+  },
   {
     key: "memory-extraction",
     description: "Host-side durable-memory extraction (ENG-6200): the manager extracts candidate memories from completed conversations and POSTs them to /host/memories/candidates, which writes dream_log via promoteCandidates. Post persistent-session cutover this is the ONLY live consolidation path. Boolean gate; ships dark \u2014 when off the manager runs no extraction, so 0 dream_log rows fleet-wide is the expected steady state until it is armed.",

package/dist/mcp/telegram-channel.js

@@ -35490,6 +35490,22 @@ var FLAG_REGISTRY = [
     // safe: `since` is excluded from projectDefinition, so it does not roll
     // FLAGS_SCHEMA_VERSION.
   },
+  {
+    key: "agt-version-drift-alarm",
+    description: "Arms the ENG-8341 agt CLI version-drift alert. When a host has fallen behind its EFFECTIVE target (env pin > DB pin > release channel) across two or more of its OWN maintenance windows, the monitor opens a host_agt_version_drift alert. OBSERVE-FIRST rollout gate: the cron computes and LOGS the drift for every host on every run regardless of this flag, so the real fleet spread is measurable before anyone is paged - the ticket asks for the threshold to be set from observed data rather than a guess. Off = compute and log, open nothing. Boolean gate; ships dark. Evaluated API-side, in the cron.",
+    flagType: "boolean",
+    // Declared safe value is `false`. Fail-safe direction for a NEW alerting
+    // cron is silence: ~21 hosts with no prior drift signal means the first
+    // armed pass could open an alert for every host that is behind at once.
+    // The cron also carries a bootstrap floor (agent-stall-monitor.ts's
+    // precedent) so arming it does not retroactively page for drift that
+    // started before the monitor existed.
+    defaultValue: false,
+    // Arming this makes a previously-invisible backlog visible all at once, in
+    // the same shape ENG-8204's never-spawned-session-metric warned about - so
+    // the flip is a deliberate, confirmed one (ADR-0022 sensitive-flag confirm).
+    sensitive: true
+  },
   {
     key: "memory-extraction",
     description: "Host-side durable-memory extraction (ENG-6200): the manager extracts candidate memories from completed conversations and POSTs them to /host/memories/candidates, which writes dream_log via promoteCandidates. Post persistent-session cutover this is the ONLY live consolidation path. Boolean gate; ships dark \u2014 when off the manager runs no extraction, so 0 dream_log rows fleet-wide is the expected steady state until it is armed.",

package/dist/{persistent-session-BDNW4K6M.js → persistent-session-CMG4VWT6.js}

@@ -37,7 +37,7 @@ import {
   writeDirectChatSessionState,
   writeEgressAllowlist,
   writePersistentClaudeWrapper
-} from "./chunk-7U63M5R6.js";
+} from "./chunk-OQBHTDWK.js";
 import "./chunk-XWVM4KPK.js";
 export {
   EGRESS_BASELINE_DOMAINS,
@@ -79,4 +79,4 @@ export {
   writeEgressAllowlist,
   writePersistentClaudeWrapper
 };
-//# sourceMappingURL=persistent-session-BDNW4K6M.js.map
+//# sourceMappingURL=persistent-session-CMG4VWT6.js.map

package/dist/{responsiveness-probe-KR73VA2S.js → responsiveness-probe-COMUJVPF.js}

@@ -1,6 +1,6 @@
 import {
   paneLogPath
-} from "./chunk-7U63M5R6.js";
+} from "./chunk-OQBHTDWK.js";
 import "./chunk-XWVM4KPK.js";
 
 // src/lib/responsiveness-probe.ts
@@ -662,4 +662,4 @@ export {
   readAndResetSlackReplyBindingClassifications,
   readAndResetSlackReplyTargetClassifications
 };
-//# sourceMappingURL=responsiveness-probe-KR73VA2S.js.map
+//# sourceMappingURL=responsiveness-probe-COMUJVPF.js.map

package/package.json

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