@integrity-labs/agt-cli 0.28.497 → 0.28.498

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

@@ -35243,6 +35243,18 @@ var FLAG_REGISTRY = [
     // env var is retired.
     envVar: "AUGMENTED_CONNECTIVITY_ESCALATION_ENABLED"
   },
+  {
+    key: "integration-reauth-reminders",
+    description: "Re-notify an integration that stays in needs_reauth (ENG-8370). Failure notification is at-most-once PER TRANSITION, so an integration nobody repairs is announced once and then silent forever - prod carried a row failing every 30-minute tick for ~21 days on a single day-one notification. When on, the IntegrationReauthReminder cron re-fires the existing reconnect notification on a backoff measured from failure ONSET (+1d, +3d, +7d, then weekly), skipping rows an operator has muted. When off the cron still scans and logs what it WOULD have sent, so the volume can be sized before anyone is messaged. Boolean gate; ships dark.",
+    flagType: "boolean",
+    // `false` is both the pre-ENG-8370 fleet behaviour AND the fail-safe
+    // direction: this flag governs how often real humans get messaged, so a
+    // flag-DB read error must never start sending on its own. Turning it on is
+    // a deliberate per-org act from the admin Feature Flags page, never a
+    // side-effect of a deploy. No env override - net-new gate, registry-only
+    // (ADR-0022).
+    defaultValue: false
+  },
   {
     key: "managed-health-connectivity-flip",
     description: "Arm the managed-connection-health status flip on data-plane hard-down (ENG-7539). When on, the managed-connection-health cron flips a managed integration to needs_reauth when the host-side connectivity probe reports a sustained hard-down (consecutive_connectivity_failures at/over the hysteresis threshold with a down observation), even if Composio account-status still reads ACTIVE. When off it keeps the pre-ENG-7539 behaviour: status is driven only by the account-status probe, so a live 401 behind an ACTIVE account never flips status. Boolean gate; ships dark. Sibling of integration-connectivity-escalation: that flag arms the alert; this flag arms the status flip plus the reconnect notification.",

package/dist/mcp/origami.js

@@ -41145,6 +41145,18 @@ var FLAG_REGISTRY = [
     // env var is retired.
     envVar: "AUGMENTED_CONNECTIVITY_ESCALATION_ENABLED"
   },
+  {
+    key: "integration-reauth-reminders",
+    description: "Re-notify an integration that stays in needs_reauth (ENG-8370). Failure notification is at-most-once PER TRANSITION, so an integration nobody repairs is announced once and then silent forever - prod carried a row failing every 30-minute tick for ~21 days on a single day-one notification. When on, the IntegrationReauthReminder cron re-fires the existing reconnect notification on a backoff measured from failure ONSET (+1d, +3d, +7d, then weekly), skipping rows an operator has muted. When off the cron still scans and logs what it WOULD have sent, so the volume can be sized before anyone is messaged. Boolean gate; ships dark.",
+    flagType: "boolean",
+    // `false` is both the pre-ENG-8370 fleet behaviour AND the fail-safe
+    // direction: this flag governs how often real humans get messaged, so a
+    // flag-DB read error must never start sending on its own. Turning it on is
+    // a deliberate per-org act from the admin Feature Flags page, never a
+    // side-effect of a deploy. No env override - net-new gate, registry-only
+    // (ADR-0022).
+    defaultValue: false
+  },
   {
     key: "managed-health-connectivity-flip",
     description: "Arm the managed-connection-health status flip on data-plane hard-down (ENG-7539). When on, the managed-connection-health cron flips a managed integration to needs_reauth when the host-side connectivity probe reports a sustained hard-down (consecutive_connectivity_failures at/over the hysteresis threshold with a down observation), even if Composio account-status still reads ACTIVE. When off it keeps the pre-ENG-7539 behaviour: status is driven only by the account-status probe, so a live 401 behind an ACTIVE account never flips status. Boolean gate; ships dark. Sibling of integration-connectivity-escalation: that flag arms the alert; this flag arms the status flip plus the reconnect notification.",

package/dist/mcp/slack-channel.js

@@ -35423,6 +35423,18 @@ var FLAG_REGISTRY = [
     // env var is retired.
     envVar: "AUGMENTED_CONNECTIVITY_ESCALATION_ENABLED"
   },
+  {
+    key: "integration-reauth-reminders",
+    description: "Re-notify an integration that stays in needs_reauth (ENG-8370). Failure notification is at-most-once PER TRANSITION, so an integration nobody repairs is announced once and then silent forever - prod carried a row failing every 30-minute tick for ~21 days on a single day-one notification. When on, the IntegrationReauthReminder cron re-fires the existing reconnect notification on a backoff measured from failure ONSET (+1d, +3d, +7d, then weekly), skipping rows an operator has muted. When off the cron still scans and logs what it WOULD have sent, so the volume can be sized before anyone is messaged. Boolean gate; ships dark.",
+    flagType: "boolean",
+    // `false` is both the pre-ENG-8370 fleet behaviour AND the fail-safe
+    // direction: this flag governs how often real humans get messaged, so a
+    // flag-DB read error must never start sending on its own. Turning it on is
+    // a deliberate per-org act from the admin Feature Flags page, never a
+    // side-effect of a deploy. No env override - net-new gate, registry-only
+    // (ADR-0022).
+    defaultValue: false
+  },
   {
     key: "managed-health-connectivity-flip",
     description: "Arm the managed-connection-health status flip on data-plane hard-down (ENG-7539). When on, the managed-connection-health cron flips a managed integration to needs_reauth when the host-side connectivity probe reports a sustained hard-down (consecutive_connectivity_failures at/over the hysteresis threshold with a down observation), even if Composio account-status still reads ACTIVE. When off it keeps the pre-ENG-7539 behaviour: status is driven only by the account-status probe, so a live 401 behind an ACTIVE account never flips status. Boolean gate; ships dark. Sibling of integration-connectivity-escalation: that flag arms the alert; this flag arms the status flip plus the reconnect notification.",

package/dist/mcp/telegram-channel.js

@@ -35749,6 +35749,18 @@ var FLAG_REGISTRY = [
     // env var is retired.
     envVar: "AUGMENTED_CONNECTIVITY_ESCALATION_ENABLED"
   },
+  {
+    key: "integration-reauth-reminders",
+    description: "Re-notify an integration that stays in needs_reauth (ENG-8370). Failure notification is at-most-once PER TRANSITION, so an integration nobody repairs is announced once and then silent forever - prod carried a row failing every 30-minute tick for ~21 days on a single day-one notification. When on, the IntegrationReauthReminder cron re-fires the existing reconnect notification on a backoff measured from failure ONSET (+1d, +3d, +7d, then weekly), skipping rows an operator has muted. When off the cron still scans and logs what it WOULD have sent, so the volume can be sized before anyone is messaged. Boolean gate; ships dark.",
+    flagType: "boolean",
+    // `false` is both the pre-ENG-8370 fleet behaviour AND the fail-safe
+    // direction: this flag governs how often real humans get messaged, so a
+    // flag-DB read error must never start sending on its own. Turning it on is
+    // a deliberate per-org act from the admin Feature Flags page, never a
+    // side-effect of a deploy. No env override - net-new gate, registry-only
+    // (ADR-0022).
+    defaultValue: false
+  },
   {
     key: "managed-health-connectivity-flip",
     description: "Arm the managed-connection-health status flip on data-plane hard-down (ENG-7539). When on, the managed-connection-health cron flips a managed integration to needs_reauth when the host-side connectivity probe reports a sustained hard-down (consecutive_connectivity_failures at/over the hysteresis threshold with a down observation), even if Composio account-status still reads ACTIVE. When off it keeps the pre-ENG-7539 behaviour: status is driven only by the account-status probe, so a live 401 behind an ACTIVE account never flips status. Boolean gate; ships dark. Sibling of integration-connectivity-escalation: that flag arms the alert; this flag arms the status flip plus the reconnect notification.",

package/dist/{persistent-session-NRNYTSZA.js → persistent-session-E3P3H777.js}

@@ -36,7 +36,7 @@ import {
   writeDirectChatSessionState,
   writeEgressAllowlist,
   writePersistentClaudeWrapper
-} from "./chunk-UNAP4CMY.js";
+} from "./chunk-WRII2Q5W.js";
 import "./chunk-XWVM4KPK.js";
 export {
   EGRESS_BASELINE_DOMAINS,
@@ -77,4 +77,4 @@ export {
   writeEgressAllowlist,
   writePersistentClaudeWrapper
 };
-//# sourceMappingURL=persistent-session-NRNYTSZA.js.map
+//# sourceMappingURL=persistent-session-E3P3H777.js.map

package/dist/{responsiveness-probe-LIXS2WDP.js → responsiveness-probe-LIDRKFGT.js}

@@ -1,6 +1,6 @@
 import {
   paneLogPath
-} from "./chunk-UNAP4CMY.js";
+} from "./chunk-WRII2Q5W.js";
 import "./chunk-XWVM4KPK.js";
 
 // src/lib/responsiveness-probe.ts
@@ -658,4 +658,4 @@ export {
   readAndResetSlackReplyBindingClassifications,
   readAndResetSlackReplyTargetClassifications
 };
-//# sourceMappingURL=responsiveness-probe-LIXS2WDP.js.map
+//# sourceMappingURL=responsiveness-probe-LIDRKFGT.js.map

package/package.json

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