@integrity-labs/agt-cli 0.28.480 → 0.28.481

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

@@ -34852,17 +34852,25 @@ var FLAG_REGISTRY = [
   },
   {
     key: "synthetic-probe-enabled",
-    description: 'Global gate for the agent synthetic-liveness cron (ENG-8074). When OFF, the cron exits after reading the flag \u2014 no probes sent, no metrics emitted, no CloudWatch alarms fired, near-zero DB footprint. Ships dark (OFF) because the probe cron was generating false positives (probe_timeout on angie for 7+ days while healthy, ENG-8048) and had open cron_invocation_errors alarms (since 2026-07-23). Flip ON per-environment via the admin Feature Flags page once the reliability issues are resolved. The existing AUGMENTED_SYNTHETIC_PROBE_ENABLED env var is the declared envVar for this flag (ADR-0022): set it to "true"/"1" to force-enable (env takes precedence over the DB stage value), or "false"/"0" to force-disable without a DB lookup. Evaluated as a global stage value by the central cron (no per-org targeting). Boolean gate.',
+    description: 'Global gate for the agent synthetic-liveness cron (ENG-8074). When OFF, the cron exits after reading the flag \u2014 no probes sent, no metrics emitted, no CloudWatch alarms fired, near-zero DB footprint. This is the fleet-wide kill switch for synthetic probing, flippable per-environment from the admin Feature Flags page. The AUGMENTED_SYNTHETIC_PROBE_ENABLED env var is the declared envVar for this flag (ADR-0022): set it in the deploy environment to "true"/"1" to force-enable or "false"/"0" to force-disable without a DB lookup. Leave it UNSET (the default on every stage since ENG-8303) so this flag governs. Evaluated as a global stage value by the central cron (no per-org targeting). Boolean gate.',
     flagType: "boolean",
-    // Safe/dark default: false = probe off. This encodes the ENG-8074 intent (disable
-    // in prod until reliability issues are resolved) and is the fail-safe direction for
-    // a flag-DB read error — a hiccup degrades to keeping the cron dormant rather than
-    // silently re-arming a broken probe fleet-wide.
-    // The env var AUGMENTED_SYNTHETIC_PROBE_ENABLED was the pre-flag emergency kill switch
-    // (read as `!== 'false'`, so unset = probe ON). The flag inverts this: unset env var
-    // now resolves to the flag default (OFF). Set AUGMENTED_SYNTHETIC_PROBE_ENABLED=true to
-    // explicitly re-arm the probe via env, or flip the flag ON from the admin UI.
-    defaultValue: false,
+    // ON by default — this deliberately matches the fleet's live behaviour rather than the
+    // dark default ENG-8074 declared, and the history is worth keeping straight:
+    //
+    // ENG-8074 set `false` to hold the probe dark until its reliability issues were fixed
+    // (probe_timeout false positives, ENG-8048; open cron_invocation_errors alarms). That
+    // default was never reachable: sst.config.ts pinned the declared envVar to the literal
+    // 'true' on every deployed stage, and a declared envVar outranks the DB value, so the
+    // probe ran throughout (ENG-8303). ENG-8303 un-pinned the env var, which hands this flag
+    // real authority for the first time — so its value must now be chosen for the fleet it
+    // actually controls, not inherited from an intent that never took effect.
+    //
+    // `true` keeps prod exactly as it has been running. Flipping to `false` here instead
+    // would have silently switched agent liveness probing off at the next deploy — including
+    // the prod verification of ENG-8302's PutMetricAlarm quota fix, which needs the cron
+    // alive to observe. The reliability concern behind ENG-8074 is addressed by ENG-8302;
+    // if it recurs, the kill switch is now a genuine admin-UI flip rather than a redeploy.
+    defaultValue: true,
     envVar: "AUGMENTED_SYNTHETIC_PROBE_ENABLED"
   },
   {

package/dist/mcp/origami.js

@@ -40799,17 +40799,25 @@ var FLAG_REGISTRY = [
   },
   {
     key: "synthetic-probe-enabled",
-    description: 'Global gate for the agent synthetic-liveness cron (ENG-8074). When OFF, the cron exits after reading the flag \u2014 no probes sent, no metrics emitted, no CloudWatch alarms fired, near-zero DB footprint. Ships dark (OFF) because the probe cron was generating false positives (probe_timeout on angie for 7+ days while healthy, ENG-8048) and had open cron_invocation_errors alarms (since 2026-07-23). Flip ON per-environment via the admin Feature Flags page once the reliability issues are resolved. The existing AUGMENTED_SYNTHETIC_PROBE_ENABLED env var is the declared envVar for this flag (ADR-0022): set it to "true"/"1" to force-enable (env takes precedence over the DB stage value), or "false"/"0" to force-disable without a DB lookup. Evaluated as a global stage value by the central cron (no per-org targeting). Boolean gate.',
+    description: 'Global gate for the agent synthetic-liveness cron (ENG-8074). When OFF, the cron exits after reading the flag \u2014 no probes sent, no metrics emitted, no CloudWatch alarms fired, near-zero DB footprint. This is the fleet-wide kill switch for synthetic probing, flippable per-environment from the admin Feature Flags page. The AUGMENTED_SYNTHETIC_PROBE_ENABLED env var is the declared envVar for this flag (ADR-0022): set it in the deploy environment to "true"/"1" to force-enable or "false"/"0" to force-disable without a DB lookup. Leave it UNSET (the default on every stage since ENG-8303) so this flag governs. Evaluated as a global stage value by the central cron (no per-org targeting). Boolean gate.',
     flagType: "boolean",
-    // Safe/dark default: false = probe off. This encodes the ENG-8074 intent (disable
-    // in prod until reliability issues are resolved) and is the fail-safe direction for
-    // a flag-DB read error — a hiccup degrades to keeping the cron dormant rather than
-    // silently re-arming a broken probe fleet-wide.
-    // The env var AUGMENTED_SYNTHETIC_PROBE_ENABLED was the pre-flag emergency kill switch
-    // (read as `!== 'false'`, so unset = probe ON). The flag inverts this: unset env var
-    // now resolves to the flag default (OFF). Set AUGMENTED_SYNTHETIC_PROBE_ENABLED=true to
-    // explicitly re-arm the probe via env, or flip the flag ON from the admin UI.
-    defaultValue: false,
+    // ON by default — this deliberately matches the fleet's live behaviour rather than the
+    // dark default ENG-8074 declared, and the history is worth keeping straight:
+    //
+    // ENG-8074 set `false` to hold the probe dark until its reliability issues were fixed
+    // (probe_timeout false positives, ENG-8048; open cron_invocation_errors alarms). That
+    // default was never reachable: sst.config.ts pinned the declared envVar to the literal
+    // 'true' on every deployed stage, and a declared envVar outranks the DB value, so the
+    // probe ran throughout (ENG-8303). ENG-8303 un-pinned the env var, which hands this flag
+    // real authority for the first time — so its value must now be chosen for the fleet it
+    // actually controls, not inherited from an intent that never took effect.
+    //
+    // `true` keeps prod exactly as it has been running. Flipping to `false` here instead
+    // would have silently switched agent liveness probing off at the next deploy — including
+    // the prod verification of ENG-8302's PutMetricAlarm quota fix, which needs the cron
+    // alive to observe. The reliability concern behind ENG-8074 is addressed by ENG-8302;
+    // if it recurs, the kill switch is now a genuine admin-UI flip rather than a redeploy.
+    defaultValue: true,
     envVar: "AUGMENTED_SYNTHETIC_PROBE_ENABLED"
   },
   {

package/dist/mcp/slack-channel.js

@@ -35077,17 +35077,25 @@ var FLAG_REGISTRY = [
   },
   {
     key: "synthetic-probe-enabled",
-    description: 'Global gate for the agent synthetic-liveness cron (ENG-8074). When OFF, the cron exits after reading the flag \u2014 no probes sent, no metrics emitted, no CloudWatch alarms fired, near-zero DB footprint. Ships dark (OFF) because the probe cron was generating false positives (probe_timeout on angie for 7+ days while healthy, ENG-8048) and had open cron_invocation_errors alarms (since 2026-07-23). Flip ON per-environment via the admin Feature Flags page once the reliability issues are resolved. The existing AUGMENTED_SYNTHETIC_PROBE_ENABLED env var is the declared envVar for this flag (ADR-0022): set it to "true"/"1" to force-enable (env takes precedence over the DB stage value), or "false"/"0" to force-disable without a DB lookup. Evaluated as a global stage value by the central cron (no per-org targeting). Boolean gate.',
+    description: 'Global gate for the agent synthetic-liveness cron (ENG-8074). When OFF, the cron exits after reading the flag \u2014 no probes sent, no metrics emitted, no CloudWatch alarms fired, near-zero DB footprint. This is the fleet-wide kill switch for synthetic probing, flippable per-environment from the admin Feature Flags page. The AUGMENTED_SYNTHETIC_PROBE_ENABLED env var is the declared envVar for this flag (ADR-0022): set it in the deploy environment to "true"/"1" to force-enable or "false"/"0" to force-disable without a DB lookup. Leave it UNSET (the default on every stage since ENG-8303) so this flag governs. Evaluated as a global stage value by the central cron (no per-org targeting). Boolean gate.',
     flagType: "boolean",
-    // Safe/dark default: false = probe off. This encodes the ENG-8074 intent (disable
-    // in prod until reliability issues are resolved) and is the fail-safe direction for
-    // a flag-DB read error — a hiccup degrades to keeping the cron dormant rather than
-    // silently re-arming a broken probe fleet-wide.
-    // The env var AUGMENTED_SYNTHETIC_PROBE_ENABLED was the pre-flag emergency kill switch
-    // (read as `!== 'false'`, so unset = probe ON). The flag inverts this: unset env var
-    // now resolves to the flag default (OFF). Set AUGMENTED_SYNTHETIC_PROBE_ENABLED=true to
-    // explicitly re-arm the probe via env, or flip the flag ON from the admin UI.
-    defaultValue: false,
+    // ON by default — this deliberately matches the fleet's live behaviour rather than the
+    // dark default ENG-8074 declared, and the history is worth keeping straight:
+    //
+    // ENG-8074 set `false` to hold the probe dark until its reliability issues were fixed
+    // (probe_timeout false positives, ENG-8048; open cron_invocation_errors alarms). That
+    // default was never reachable: sst.config.ts pinned the declared envVar to the literal
+    // 'true' on every deployed stage, and a declared envVar outranks the DB value, so the
+    // probe ran throughout (ENG-8303). ENG-8303 un-pinned the env var, which hands this flag
+    // real authority for the first time — so its value must now be chosen for the fleet it
+    // actually controls, not inherited from an intent that never took effect.
+    //
+    // `true` keeps prod exactly as it has been running. Flipping to `false` here instead
+    // would have silently switched agent liveness probing off at the next deploy — including
+    // the prod verification of ENG-8302's PutMetricAlarm quota fix, which needs the cron
+    // alive to observe. The reliability concern behind ENG-8074 is addressed by ENG-8302;
+    // if it recurs, the kill switch is now a genuine admin-UI flip rather than a redeploy.
+    defaultValue: true,
     envVar: "AUGMENTED_SYNTHETIC_PROBE_ENABLED"
   },
   {

package/dist/mcp/telegram-channel.js

@@ -35403,17 +35403,25 @@ var FLAG_REGISTRY = [
   },
   {
     key: "synthetic-probe-enabled",
-    description: 'Global gate for the agent synthetic-liveness cron (ENG-8074). When OFF, the cron exits after reading the flag \u2014 no probes sent, no metrics emitted, no CloudWatch alarms fired, near-zero DB footprint. Ships dark (OFF) because the probe cron was generating false positives (probe_timeout on angie for 7+ days while healthy, ENG-8048) and had open cron_invocation_errors alarms (since 2026-07-23). Flip ON per-environment via the admin Feature Flags page once the reliability issues are resolved. The existing AUGMENTED_SYNTHETIC_PROBE_ENABLED env var is the declared envVar for this flag (ADR-0022): set it to "true"/"1" to force-enable (env takes precedence over the DB stage value), or "false"/"0" to force-disable without a DB lookup. Evaluated as a global stage value by the central cron (no per-org targeting). Boolean gate.',
+    description: 'Global gate for the agent synthetic-liveness cron (ENG-8074). When OFF, the cron exits after reading the flag \u2014 no probes sent, no metrics emitted, no CloudWatch alarms fired, near-zero DB footprint. This is the fleet-wide kill switch for synthetic probing, flippable per-environment from the admin Feature Flags page. The AUGMENTED_SYNTHETIC_PROBE_ENABLED env var is the declared envVar for this flag (ADR-0022): set it in the deploy environment to "true"/"1" to force-enable or "false"/"0" to force-disable without a DB lookup. Leave it UNSET (the default on every stage since ENG-8303) so this flag governs. Evaluated as a global stage value by the central cron (no per-org targeting). Boolean gate.',
     flagType: "boolean",
-    // Safe/dark default: false = probe off. This encodes the ENG-8074 intent (disable
-    // in prod until reliability issues are resolved) and is the fail-safe direction for
-    // a flag-DB read error — a hiccup degrades to keeping the cron dormant rather than
-    // silently re-arming a broken probe fleet-wide.
-    // The env var AUGMENTED_SYNTHETIC_PROBE_ENABLED was the pre-flag emergency kill switch
-    // (read as `!== 'false'`, so unset = probe ON). The flag inverts this: unset env var
-    // now resolves to the flag default (OFF). Set AUGMENTED_SYNTHETIC_PROBE_ENABLED=true to
-    // explicitly re-arm the probe via env, or flip the flag ON from the admin UI.
-    defaultValue: false,
+    // ON by default — this deliberately matches the fleet's live behaviour rather than the
+    // dark default ENG-8074 declared, and the history is worth keeping straight:
+    //
+    // ENG-8074 set `false` to hold the probe dark until its reliability issues were fixed
+    // (probe_timeout false positives, ENG-8048; open cron_invocation_errors alarms). That
+    // default was never reachable: sst.config.ts pinned the declared envVar to the literal
+    // 'true' on every deployed stage, and a declared envVar outranks the DB value, so the
+    // probe ran throughout (ENG-8303). ENG-8303 un-pinned the env var, which hands this flag
+    // real authority for the first time — so its value must now be chosen for the fleet it
+    // actually controls, not inherited from an intent that never took effect.
+    //
+    // `true` keeps prod exactly as it has been running. Flipping to `false` here instead
+    // would have silently switched agent liveness probing off at the next deploy — including
+    // the prod verification of ENG-8302's PutMetricAlarm quota fix, which needs the cron
+    // alive to observe. The reliability concern behind ENG-8074 is addressed by ENG-8302;
+    // if it recurs, the kill switch is now a genuine admin-UI flip rather than a redeploy.
+    defaultValue: true,
     envVar: "AUGMENTED_SYNTHETIC_PROBE_ENABLED"
   },
   {

package/dist/{persistent-session-USTI74Q5.js → persistent-session-Q4YE53I5.js}

@@ -36,7 +36,7 @@ import {
   writeDirectChatSessionState,
   writeEgressAllowlist,
   writePersistentClaudeWrapper
-} from "./chunk-EOH75U22.js";
+} from "./chunk-4XLEJP7G.js";
 import "./chunk-XWVM4KPK.js";
 export {
   EGRESS_BASELINE_DOMAINS,
@@ -77,4 +77,4 @@ export {
   writeEgressAllowlist,
   writePersistentClaudeWrapper
 };
-//# sourceMappingURL=persistent-session-USTI74Q5.js.map
+//# sourceMappingURL=persistent-session-Q4YE53I5.js.map

package/dist/{responsiveness-probe-3PRCIAML.js → responsiveness-probe-MOFFFCOY.js}

@@ -1,6 +1,6 @@
 import {
   paneLogPath
-} from "./chunk-EOH75U22.js";
+} from "./chunk-4XLEJP7G.js";
 import "./chunk-XWVM4KPK.js";
 
 // src/lib/responsiveness-probe.ts
@@ -596,4 +596,4 @@ export {
   readAndResetSlackReplyBindingClassifications,
   readAndResetSlackReplyTargetClassifications
 };
-//# sourceMappingURL=responsiveness-probe-3PRCIAML.js.map
+//# sourceMappingURL=responsiveness-probe-MOFFFCOY.js.map

package/package.json

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