@integrity-labs/agt-cli 0.28.727 → 0.28.729

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

@@ -36105,6 +36105,22 @@ var FLAG_REGISTRY = [
     // safe: `since` is excluded from projectDefinition, so it does not roll
     // FLAGS_SCHEMA_VERSION.
   },
+  {
+    key: "host-poll-rate-alarm",
+    description: "Arms the ENG-9637 per-agent poll-rate alert. The HostPollRateMonitor cron counts /host/refresh requests per agent from CloudWatch Logs Insights each hour and opens an agent_poll_rate_runaway alert when an agent is far above its OWN trailing baseline, or far above the fleet median. OBSERVE-FIRST rollout gate, on the agt-version-drift-alarm precedent: the cron measures, PERSISTS and LOGS every agent on every run regardless of this flag, so the real fleet spread is measurable before anyone is paged. Off = measure, persist and log, open nothing. It gates OPENING only - the recovery pass runs regardless, because arming decides whether we may assert a condition and has no bearing on whether an assertion already made is still true; gating the close would make disarming this flag freeze every open alert permanently. Boolean gate; ships dark. Evaluated API-side, in the cron.",
+    flagType: "boolean",
+    // Declared safe value is `false`, and the reason is specific rather than
+    // habitual. The self-baseline rule needs several hours of persisted history
+    // per agent before it can say anything, so arming this on the same deploy
+    // that creates the table would run the fleet rule alone against a fleet
+    // that is still mid-rollout of the ENG-9637 poll ceiling - i.e. against the
+    // widest poll-rate spread the fleet will ever have. That is a page for
+    // every host still carrying the old CLI.
+    defaultValue: false,
+    // Arming it makes a previously-invisible condition visible all at once,
+    // which is the ADR-0022 sensitive-flag shape.
+    sensitive: true
+  },
   {
     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.",

package/dist/mcp/index.js

@@ -43066,6 +43066,22 @@ var FLAG_REGISTRY = [
     // safe: `since` is excluded from projectDefinition, so it does not roll
     // FLAGS_SCHEMA_VERSION.
   },
+  {
+    key: "host-poll-rate-alarm",
+    description: "Arms the ENG-9637 per-agent poll-rate alert. The HostPollRateMonitor cron counts /host/refresh requests per agent from CloudWatch Logs Insights each hour and opens an agent_poll_rate_runaway alert when an agent is far above its OWN trailing baseline, or far above the fleet median. OBSERVE-FIRST rollout gate, on the agt-version-drift-alarm precedent: the cron measures, PERSISTS and LOGS every agent on every run regardless of this flag, so the real fleet spread is measurable before anyone is paged. Off = measure, persist and log, open nothing. It gates OPENING only - the recovery pass runs regardless, because arming decides whether we may assert a condition and has no bearing on whether an assertion already made is still true; gating the close would make disarming this flag freeze every open alert permanently. Boolean gate; ships dark. Evaluated API-side, in the cron.",
+    flagType: "boolean",
+    // Declared safe value is `false`, and the reason is specific rather than
+    // habitual. The self-baseline rule needs several hours of persisted history
+    // per agent before it can say anything, so arming this on the same deploy
+    // that creates the table would run the fleet rule alone against a fleet
+    // that is still mid-rollout of the ENG-9637 poll ceiling - i.e. against the
+    // widest poll-rate spread the fleet will ever have. That is a page for
+    // every host still carrying the old CLI.
+    defaultValue: false,
+    // Arming it makes a previously-invisible condition visible all at once,
+    // which is the ADR-0022 sensitive-flag shape.
+    sensitive: true
+  },
   {
     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.",

package/dist/mcp/origami.js

@@ -41837,6 +41837,22 @@ var FLAG_REGISTRY = [
     // safe: `since` is excluded from projectDefinition, so it does not roll
     // FLAGS_SCHEMA_VERSION.
   },
+  {
+    key: "host-poll-rate-alarm",
+    description: "Arms the ENG-9637 per-agent poll-rate alert. The HostPollRateMonitor cron counts /host/refresh requests per agent from CloudWatch Logs Insights each hour and opens an agent_poll_rate_runaway alert when an agent is far above its OWN trailing baseline, or far above the fleet median. OBSERVE-FIRST rollout gate, on the agt-version-drift-alarm precedent: the cron measures, PERSISTS and LOGS every agent on every run regardless of this flag, so the real fleet spread is measurable before anyone is paged. Off = measure, persist and log, open nothing. It gates OPENING only - the recovery pass runs regardless, because arming decides whether we may assert a condition and has no bearing on whether an assertion already made is still true; gating the close would make disarming this flag freeze every open alert permanently. Boolean gate; ships dark. Evaluated API-side, in the cron.",
+    flagType: "boolean",
+    // Declared safe value is `false`, and the reason is specific rather than
+    // habitual. The self-baseline rule needs several hours of persisted history
+    // per agent before it can say anything, so arming this on the same deploy
+    // that creates the table would run the fleet rule alone against a fleet
+    // that is still mid-rollout of the ENG-9637 poll ceiling - i.e. against the
+    // widest poll-rate spread the fleet will ever have. That is a page for
+    // every host still carrying the old CLI.
+    defaultValue: false,
+    // Arming it makes a previously-invisible condition visible all at once,
+    // which is the ADR-0022 sensitive-flag shape.
+    sensitive: true
+  },
   {
     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.",

package/dist/mcp/slack-channel.js

@@ -36357,6 +36357,22 @@ var FLAG_REGISTRY = [
     // safe: `since` is excluded from projectDefinition, so it does not roll
     // FLAGS_SCHEMA_VERSION.
   },
+  {
+    key: "host-poll-rate-alarm",
+    description: "Arms the ENG-9637 per-agent poll-rate alert. The HostPollRateMonitor cron counts /host/refresh requests per agent from CloudWatch Logs Insights each hour and opens an agent_poll_rate_runaway alert when an agent is far above its OWN trailing baseline, or far above the fleet median. OBSERVE-FIRST rollout gate, on the agt-version-drift-alarm precedent: the cron measures, PERSISTS and LOGS every agent on every run regardless of this flag, so the real fleet spread is measurable before anyone is paged. Off = measure, persist and log, open nothing. It gates OPENING only - the recovery pass runs regardless, because arming decides whether we may assert a condition and has no bearing on whether an assertion already made is still true; gating the close would make disarming this flag freeze every open alert permanently. Boolean gate; ships dark. Evaluated API-side, in the cron.",
+    flagType: "boolean",
+    // Declared safe value is `false`, and the reason is specific rather than
+    // habitual. The self-baseline rule needs several hours of persisted history
+    // per agent before it can say anything, so arming this on the same deploy
+    // that creates the table would run the fleet rule alone against a fleet
+    // that is still mid-rollout of the ENG-9637 poll ceiling - i.e. against the
+    // widest poll-rate spread the fleet will ever have. That is a page for
+    // every host still carrying the old CLI.
+    defaultValue: false,
+    // Arming it makes a previously-invisible condition visible all at once,
+    // which is the ADR-0022 sensitive-flag shape.
+    sensitive: true
+  },
   {
     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.",

package/dist/mcp/telegram-channel.js

@@ -36513,6 +36513,22 @@ var FLAG_REGISTRY = [
     // safe: `since` is excluded from projectDefinition, so it does not roll
     // FLAGS_SCHEMA_VERSION.
   },
+  {
+    key: "host-poll-rate-alarm",
+    description: "Arms the ENG-9637 per-agent poll-rate alert. The HostPollRateMonitor cron counts /host/refresh requests per agent from CloudWatch Logs Insights each hour and opens an agent_poll_rate_runaway alert when an agent is far above its OWN trailing baseline, or far above the fleet median. OBSERVE-FIRST rollout gate, on the agt-version-drift-alarm precedent: the cron measures, PERSISTS and LOGS every agent on every run regardless of this flag, so the real fleet spread is measurable before anyone is paged. Off = measure, persist and log, open nothing. It gates OPENING only - the recovery pass runs regardless, because arming decides whether we may assert a condition and has no bearing on whether an assertion already made is still true; gating the close would make disarming this flag freeze every open alert permanently. Boolean gate; ships dark. Evaluated API-side, in the cron.",
+    flagType: "boolean",
+    // Declared safe value is `false`, and the reason is specific rather than
+    // habitual. The self-baseline rule needs several hours of persisted history
+    // per agent before it can say anything, so arming this on the same deploy
+    // that creates the table would run the fleet rule alone against a fleet
+    // that is still mid-rollout of the ENG-9637 poll ceiling - i.e. against the
+    // widest poll-rate spread the fleet will ever have. That is a page for
+    // every host still carrying the old CLI.
+    defaultValue: false,
+    // Arming it makes a previously-invisible condition visible all at once,
+    // which is the ADR-0022 sensitive-flag shape.
+    sensitive: true
+  },
   {
     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.",

package/dist/{persistent-session-LP7JOGZ5.js → persistent-session-KHGH6UKC.js}

@@ -46,8 +46,8 @@ import {
   writeDirectChatSessionState,
   writeEgressAllowlist,
   writePersistentClaudeWrapper
-} from "./chunk-ZCTFF4PA.js";
-import "./chunk-IXGIGDJG.js";
+} from "./chunk-KF3IFJVV.js";
+import "./chunk-WVYNQJRS.js";
 import "./chunk-XWVM4KPK.js";
 export {
   EGRESS_BASELINE_DOMAINS,
@@ -98,4 +98,4 @@ export {
   writeEgressAllowlist,
   writePersistentClaudeWrapper
 };
-//# sourceMappingURL=persistent-session-LP7JOGZ5.js.map
+//# sourceMappingURL=persistent-session-KHGH6UKC.js.map

package/dist/{responsiveness-probe-TTHNHBBS.js → responsiveness-probe-ASAPVDUQ.js}

@@ -1,7 +1,7 @@
 import {
   paneLogPath
-} from "./chunk-ZCTFF4PA.js";
-import "./chunk-IXGIGDJG.js";
+} from "./chunk-KF3IFJVV.js";
+import "./chunk-WVYNQJRS.js";
 import "./chunk-XWVM4KPK.js";
 
 // src/lib/responsiveness-probe.ts
@@ -745,4 +745,4 @@ export {
   readAndResetSlackReplyBindingClassifications,
   readAndResetSlackReplyTargetClassifications
 };
-//# sourceMappingURL=responsiveness-probe-TTHNHBBS.js.map
+//# sourceMappingURL=responsiveness-probe-ASAPVDUQ.js.map

package/dist/{session-auth-dead-YQHE3WKV.js → session-auth-dead-ABEYQHK3.js}

@@ -1,6 +1,6 @@
 import {
   sessionTranscriptDir
-} from "./chunk-IXGIGDJG.js";
+} from "./chunk-WVYNQJRS.js";
 
 // src/lib/session-auth-dead.ts
 import { closeSync, openSync, readSync, readdirSync, statSync } from "fs";
@@ -203,4 +203,4 @@ export {
   decideSessionAuthState,
   probeSessionAuth
 };
-//# sourceMappingURL=session-auth-dead-YQHE3WKV.js.map
+//# sourceMappingURL=session-auth-dead-ABEYQHK3.js.map

package/package.json

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