@integrity-labs/agt-cli 0.28.815 → 0.28.817

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

@@ -36676,6 +36676,29 @@ var FLAG_REGISTRY = [
     // which is the ADR-0022 sensitive-flag shape.
     sensitive: true
   },
+  {
+    key: "host-alarm-reconciler-repair",
+    description: "Arms the CREATE and DRIFT-REPAIR halves of the ENG-8325 host-alarm reconciler. The cron computes and LOGS the full diff for every host on every run regardless of this flag, on the host-poll-rate-alarm precedent, so the fleet diff is measurable before anything mutates. Off = measure and log, create nothing and re-put nothing. Evaluated PER ORGANIZATION from the host row, so arming can be staged one org at a time and watched. It does NOT gate the reap - see host-alarm-reconciler-reap, which is deliberately fleet-wide because an orphan alarm whose host row is gone has no organization to scope by. AGT_HOST_ALARM_RECONCILER_APPLY outranks this flag and forces BOTH gates on fleet-wide; it is deliberately not declared as this flag's envVar, because it is a master override of two flags rather than the operator override of this one. Boolean gate; ships dark. Evaluated API-side, in the cron.",
+    flagType: "boolean",
+    // Safe value is `false` for a specific reason, not a habitual one: the
+    // first applying run creates one alarm per host that lacks one, and a
+    // PutMetricAlarm on a fleet whose expected set is wrong is not a no-op you
+    // can shrug off - it is monitoring that now exists and will page.
+    defaultValue: false,
+    // It mutates CloudWatch for every host in the armed org, which is the
+    // ADR-0022 sensitive-flag shape.
+    sensitive: true
+  },
+  {
+    key: "host-alarm-reconciler-reap",
+    description: "Arms the REAP half of the ENG-8325 host-alarm reconciler: deleting alarms under augmented/{env}/host/ whose parsed host id is not in the live set. Off = count and name the orphan candidates, delete nothing. DELIBERATELY EVALUATED GLOBALLY, with no organization scope, and that is not an oversight to be tidied up later. An orphan is defined as an alarm whose host id resolves to no live host; where the host row is gone entirely there is no organization to scope by, so the property that makes an alarm an orphan is the same one that makes it unattributable. A per-org gate here would silently reap other orgs' orphans the moment any one org was armed, which is staged creates with an unstaged reap - the more dangerous half. AGT_HOST_ALARM_RECONCILER_APPLY outranks this flag and forces both gates on. Boolean gate; ships dark. Evaluated API-side, in the cron.",
+    flagType: "boolean",
+    // The destructive half. Measured on prod 2026-09-03: a first applying run
+    // deletes 84 alarms across 33 dead instance ids. Nothing about that is
+    // recoverable by re-running, so the safe value is not a formality.
+    defaultValue: false,
+    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.",
@@ -36707,6 +36730,12 @@ var FLAG_REGISTRY = [
     // flip wants a deliberate confirm rather than a casual toggle. Before flipping,
     // check which orgs sit at the `enforce` / `require_approval` email-guard stage:
     // those are the ones where a newly-effective policy can reach a real block.
+    //
+    // Run that pre-flight per `docs/runbooks/org-email-domain-derivation-rollout.md`,
+    // and read it before acting on the result: the dry run reports `would-derive`
+    // for orgs where arming is provably inert (an unverified row for the candidate
+    // domain makes the insert collide and write nothing), so the report reads as
+    // riskier than it is and invites per-org overrides that are not needed.
     sensitive: true
   },
   {

package/dist/mcp/index.js

@@ -28447,6 +28447,29 @@ var FLAG_REGISTRY = [
     // which is the ADR-0022 sensitive-flag shape.
     sensitive: true
   },
+  {
+    key: "host-alarm-reconciler-repair",
+    description: "Arms the CREATE and DRIFT-REPAIR halves of the ENG-8325 host-alarm reconciler. The cron computes and LOGS the full diff for every host on every run regardless of this flag, on the host-poll-rate-alarm precedent, so the fleet diff is measurable before anything mutates. Off = measure and log, create nothing and re-put nothing. Evaluated PER ORGANIZATION from the host row, so arming can be staged one org at a time and watched. It does NOT gate the reap - see host-alarm-reconciler-reap, which is deliberately fleet-wide because an orphan alarm whose host row is gone has no organization to scope by. AGT_HOST_ALARM_RECONCILER_APPLY outranks this flag and forces BOTH gates on fleet-wide; it is deliberately not declared as this flag's envVar, because it is a master override of two flags rather than the operator override of this one. Boolean gate; ships dark. Evaluated API-side, in the cron.",
+    flagType: "boolean",
+    // Safe value is `false` for a specific reason, not a habitual one: the
+    // first applying run creates one alarm per host that lacks one, and a
+    // PutMetricAlarm on a fleet whose expected set is wrong is not a no-op you
+    // can shrug off - it is monitoring that now exists and will page.
+    defaultValue: false,
+    // It mutates CloudWatch for every host in the armed org, which is the
+    // ADR-0022 sensitive-flag shape.
+    sensitive: true
+  },
+  {
+    key: "host-alarm-reconciler-reap",
+    description: "Arms the REAP half of the ENG-8325 host-alarm reconciler: deleting alarms under augmented/{env}/host/ whose parsed host id is not in the live set. Off = count and name the orphan candidates, delete nothing. DELIBERATELY EVALUATED GLOBALLY, with no organization scope, and that is not an oversight to be tidied up later. An orphan is defined as an alarm whose host id resolves to no live host; where the host row is gone entirely there is no organization to scope by, so the property that makes an alarm an orphan is the same one that makes it unattributable. A per-org gate here would silently reap other orgs' orphans the moment any one org was armed, which is staged creates with an unstaged reap - the more dangerous half. AGT_HOST_ALARM_RECONCILER_APPLY outranks this flag and forces both gates on. Boolean gate; ships dark. Evaluated API-side, in the cron.",
+    flagType: "boolean",
+    // The destructive half. Measured on prod 2026-09-03: a first applying run
+    // deletes 84 alarms across 33 dead instance ids. Nothing about that is
+    // recoverable by re-running, so the safe value is not a formality.
+    defaultValue: false,
+    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.",
@@ -28478,6 +28501,12 @@ var FLAG_REGISTRY = [
     // flip wants a deliberate confirm rather than a casual toggle. Before flipping,
     // check which orgs sit at the `enforce` / `require_approval` email-guard stage:
     // those are the ones where a newly-effective policy can reach a real block.
+    //
+    // Run that pre-flight per `docs/runbooks/org-email-domain-derivation-rollout.md`,
+    // and read it before acting on the result: the dry run reports `would-derive`
+    // for orgs where arming is provably inert (an unverified row for the candidate
+    // domain makes the insert collide and write nothing), so the report reads as
+    // riskier than it is and invites per-org overrides that are not needed.
     sensitive: true
   },
   {

package/dist/mcp/origami.js

@@ -42400,6 +42400,29 @@ var FLAG_REGISTRY = [
     // which is the ADR-0022 sensitive-flag shape.
     sensitive: true
   },
+  {
+    key: "host-alarm-reconciler-repair",
+    description: "Arms the CREATE and DRIFT-REPAIR halves of the ENG-8325 host-alarm reconciler. The cron computes and LOGS the full diff for every host on every run regardless of this flag, on the host-poll-rate-alarm precedent, so the fleet diff is measurable before anything mutates. Off = measure and log, create nothing and re-put nothing. Evaluated PER ORGANIZATION from the host row, so arming can be staged one org at a time and watched. It does NOT gate the reap - see host-alarm-reconciler-reap, which is deliberately fleet-wide because an orphan alarm whose host row is gone has no organization to scope by. AGT_HOST_ALARM_RECONCILER_APPLY outranks this flag and forces BOTH gates on fleet-wide; it is deliberately not declared as this flag's envVar, because it is a master override of two flags rather than the operator override of this one. Boolean gate; ships dark. Evaluated API-side, in the cron.",
+    flagType: "boolean",
+    // Safe value is `false` for a specific reason, not a habitual one: the
+    // first applying run creates one alarm per host that lacks one, and a
+    // PutMetricAlarm on a fleet whose expected set is wrong is not a no-op you
+    // can shrug off - it is monitoring that now exists and will page.
+    defaultValue: false,
+    // It mutates CloudWatch for every host in the armed org, which is the
+    // ADR-0022 sensitive-flag shape.
+    sensitive: true
+  },
+  {
+    key: "host-alarm-reconciler-reap",
+    description: "Arms the REAP half of the ENG-8325 host-alarm reconciler: deleting alarms under augmented/{env}/host/ whose parsed host id is not in the live set. Off = count and name the orphan candidates, delete nothing. DELIBERATELY EVALUATED GLOBALLY, with no organization scope, and that is not an oversight to be tidied up later. An orphan is defined as an alarm whose host id resolves to no live host; where the host row is gone entirely there is no organization to scope by, so the property that makes an alarm an orphan is the same one that makes it unattributable. A per-org gate here would silently reap other orgs' orphans the moment any one org was armed, which is staged creates with an unstaged reap - the more dangerous half. AGT_HOST_ALARM_RECONCILER_APPLY outranks this flag and forces both gates on. Boolean gate; ships dark. Evaluated API-side, in the cron.",
+    flagType: "boolean",
+    // The destructive half. Measured on prod 2026-09-03: a first applying run
+    // deletes 84 alarms across 33 dead instance ids. Nothing about that is
+    // recoverable by re-running, so the safe value is not a formality.
+    defaultValue: false,
+    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.",
@@ -42431,6 +42454,12 @@ var FLAG_REGISTRY = [
     // flip wants a deliberate confirm rather than a casual toggle. Before flipping,
     // check which orgs sit at the `enforce` / `require_approval` email-guard stage:
     // those are the ones where a newly-effective policy can reach a real block.
+    //
+    // Run that pre-flight per `docs/runbooks/org-email-domain-derivation-rollout.md`,
+    // and read it before acting on the result: the dry run reports `would-derive`
+    // for orgs where arming is provably inert (an unverified row for the candidate
+    // domain makes the insert collide and write nothing), so the report reads as
+    // riskier than it is and invites per-org overrides that are not needed.
     sensitive: true
   },
   {

package/dist/mcp/slack-channel.js

@@ -36955,6 +36955,29 @@ var FLAG_REGISTRY = [
     // which is the ADR-0022 sensitive-flag shape.
     sensitive: true
   },
+  {
+    key: "host-alarm-reconciler-repair",
+    description: "Arms the CREATE and DRIFT-REPAIR halves of the ENG-8325 host-alarm reconciler. The cron computes and LOGS the full diff for every host on every run regardless of this flag, on the host-poll-rate-alarm precedent, so the fleet diff is measurable before anything mutates. Off = measure and log, create nothing and re-put nothing. Evaluated PER ORGANIZATION from the host row, so arming can be staged one org at a time and watched. It does NOT gate the reap - see host-alarm-reconciler-reap, which is deliberately fleet-wide because an orphan alarm whose host row is gone has no organization to scope by. AGT_HOST_ALARM_RECONCILER_APPLY outranks this flag and forces BOTH gates on fleet-wide; it is deliberately not declared as this flag's envVar, because it is a master override of two flags rather than the operator override of this one. Boolean gate; ships dark. Evaluated API-side, in the cron.",
+    flagType: "boolean",
+    // Safe value is `false` for a specific reason, not a habitual one: the
+    // first applying run creates one alarm per host that lacks one, and a
+    // PutMetricAlarm on a fleet whose expected set is wrong is not a no-op you
+    // can shrug off - it is monitoring that now exists and will page.
+    defaultValue: false,
+    // It mutates CloudWatch for every host in the armed org, which is the
+    // ADR-0022 sensitive-flag shape.
+    sensitive: true
+  },
+  {
+    key: "host-alarm-reconciler-reap",
+    description: "Arms the REAP half of the ENG-8325 host-alarm reconciler: deleting alarms under augmented/{env}/host/ whose parsed host id is not in the live set. Off = count and name the orphan candidates, delete nothing. DELIBERATELY EVALUATED GLOBALLY, with no organization scope, and that is not an oversight to be tidied up later. An orphan is defined as an alarm whose host id resolves to no live host; where the host row is gone entirely there is no organization to scope by, so the property that makes an alarm an orphan is the same one that makes it unattributable. A per-org gate here would silently reap other orgs' orphans the moment any one org was armed, which is staged creates with an unstaged reap - the more dangerous half. AGT_HOST_ALARM_RECONCILER_APPLY outranks this flag and forces both gates on. Boolean gate; ships dark. Evaluated API-side, in the cron.",
+    flagType: "boolean",
+    // The destructive half. Measured on prod 2026-09-03: a first applying run
+    // deletes 84 alarms across 33 dead instance ids. Nothing about that is
+    // recoverable by re-running, so the safe value is not a formality.
+    defaultValue: false,
+    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.",
@@ -36986,6 +37009,12 @@ var FLAG_REGISTRY = [
     // flip wants a deliberate confirm rather than a casual toggle. Before flipping,
     // check which orgs sit at the `enforce` / `require_approval` email-guard stage:
     // those are the ones where a newly-effective policy can reach a real block.
+    //
+    // Run that pre-flight per `docs/runbooks/org-email-domain-derivation-rollout.md`,
+    // and read it before acting on the result: the dry run reports `would-derive`
+    // for orgs where arming is provably inert (an unverified row for the candidate
+    // domain makes the insert collide and write nothing), so the report reads as
+    // riskier than it is and invites per-org overrides that are not needed.
     sensitive: true
   },
   {

package/dist/mcp/telegram-channel.js

@@ -37087,6 +37087,29 @@ var FLAG_REGISTRY = [
     // which is the ADR-0022 sensitive-flag shape.
     sensitive: true
   },
+  {
+    key: "host-alarm-reconciler-repair",
+    description: "Arms the CREATE and DRIFT-REPAIR halves of the ENG-8325 host-alarm reconciler. The cron computes and LOGS the full diff for every host on every run regardless of this flag, on the host-poll-rate-alarm precedent, so the fleet diff is measurable before anything mutates. Off = measure and log, create nothing and re-put nothing. Evaluated PER ORGANIZATION from the host row, so arming can be staged one org at a time and watched. It does NOT gate the reap - see host-alarm-reconciler-reap, which is deliberately fleet-wide because an orphan alarm whose host row is gone has no organization to scope by. AGT_HOST_ALARM_RECONCILER_APPLY outranks this flag and forces BOTH gates on fleet-wide; it is deliberately not declared as this flag's envVar, because it is a master override of two flags rather than the operator override of this one. Boolean gate; ships dark. Evaluated API-side, in the cron.",
+    flagType: "boolean",
+    // Safe value is `false` for a specific reason, not a habitual one: the
+    // first applying run creates one alarm per host that lacks one, and a
+    // PutMetricAlarm on a fleet whose expected set is wrong is not a no-op you
+    // can shrug off - it is monitoring that now exists and will page.
+    defaultValue: false,
+    // It mutates CloudWatch for every host in the armed org, which is the
+    // ADR-0022 sensitive-flag shape.
+    sensitive: true
+  },
+  {
+    key: "host-alarm-reconciler-reap",
+    description: "Arms the REAP half of the ENG-8325 host-alarm reconciler: deleting alarms under augmented/{env}/host/ whose parsed host id is not in the live set. Off = count and name the orphan candidates, delete nothing. DELIBERATELY EVALUATED GLOBALLY, with no organization scope, and that is not an oversight to be tidied up later. An orphan is defined as an alarm whose host id resolves to no live host; where the host row is gone entirely there is no organization to scope by, so the property that makes an alarm an orphan is the same one that makes it unattributable. A per-org gate here would silently reap other orgs' orphans the moment any one org was armed, which is staged creates with an unstaged reap - the more dangerous half. AGT_HOST_ALARM_RECONCILER_APPLY outranks this flag and forces both gates on. Boolean gate; ships dark. Evaluated API-side, in the cron.",
+    flagType: "boolean",
+    // The destructive half. Measured on prod 2026-09-03: a first applying run
+    // deletes 84 alarms across 33 dead instance ids. Nothing about that is
+    // recoverable by re-running, so the safe value is not a formality.
+    defaultValue: false,
+    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.",
@@ -37118,6 +37141,12 @@ var FLAG_REGISTRY = [
     // flip wants a deliberate confirm rather than a casual toggle. Before flipping,
     // check which orgs sit at the `enforce` / `require_approval` email-guard stage:
     // those are the ones where a newly-effective policy can reach a real block.
+    //
+    // Run that pre-flight per `docs/runbooks/org-email-domain-derivation-rollout.md`,
+    // and read it before acting on the result: the dry run reports `would-derive`
+    // for orgs where arming is provably inert (an unverified row for the candidate
+    // domain makes the insert collide and write nothing), so the report reads as
+    // riskier than it is and invites per-org overrides that are not needed.
     sensitive: true
   },
   {

package/dist/{persistent-session-IZXPZFYT.js → persistent-session-YX4JTHMC.js}

@@ -49,8 +49,8 @@ import {
   writeDirectChatSessionState,
   writeEgressAllowlist,
   writePersistentClaudeWrapper
-} from "./chunk-UQKTHEYS.js";
-import "./chunk-7DTMJSAF.js";
+} from "./chunk-5RZBTMBD.js";
+import "./chunk-SZ47B4KO.js";
 import "./chunk-XWVM4KPK.js";
 export {
   EGRESS_BASELINE_DOMAINS,
@@ -104,4 +104,4 @@ export {
   writeEgressAllowlist,
   writePersistentClaudeWrapper
 };
-//# sourceMappingURL=persistent-session-IZXPZFYT.js.map
+//# sourceMappingURL=persistent-session-YX4JTHMC.js.map

package/dist/{responsiveness-probe-HPPMYMSN.js → responsiveness-probe-63R3PUAU.js}

@@ -1,7 +1,7 @@
 import {
   paneLogPath
-} from "./chunk-UQKTHEYS.js";
-import "./chunk-7DTMJSAF.js";
+} from "./chunk-5RZBTMBD.js";
+import "./chunk-SZ47B4KO.js";
 import "./chunk-XWVM4KPK.js";
 
 // src/lib/responsiveness-probe.ts
@@ -745,4 +745,4 @@ export {
   readAndResetSlackReplyBindingClassifications,
   readAndResetSlackReplyTargetClassifications
 };
-//# sourceMappingURL=responsiveness-probe-HPPMYMSN.js.map
+//# sourceMappingURL=responsiveness-probe-63R3PUAU.js.map

package/dist/{session-auth-dead-42GBGDNA.js → session-auth-dead-2NFR7OFR.js}

@@ -1,6 +1,6 @@
 import {
   sessionTranscriptDir
-} from "./chunk-7DTMJSAF.js";
+} from "./chunk-SZ47B4KO.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-42GBGDNA.js.map
+//# sourceMappingURL=session-auth-dead-2NFR7OFR.js.map

package/package.json

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