@integrity-labs/agt-cli 0.28.927 → 0.28.929

package/dist/{chunk-Y7ERASS6.js → chunk-IIIMUCGD.js}

@@ -6581,6 +6581,23 @@ var FLAG_REGISTRY = [
     // env var is retired.
     envVar: "AUGMENTED_CONNECTIVITY_ESCALATION_ENABLED"
   },
+  {
+    key: "integration-connectivity-reconcile",
+    description: "Arm integration-connectivity STATUS reconciliation (ENG-6139, armable per-org by ENG-10473). When on, a hard-down connectivity observation (a `down` reading with consecutive_connectivity_failures at/over the hysteresis threshold) on an otherwise-healthy row downgrades it to status=error, status_message=connectivity_down, so the record stops asserting a live connection the probe has disproved; recovery restores status=active, but ONLY for rows this path downgraded. When off it stays shadow - logs what it WOULD downgrade and touches only the connectivity columns. \u26A0\uFE0F A downgraded row drops out of host-runtime's `.in('status',['active','configured'])` provisioning filter, so the agent LOSES that MCP server: correct for a dead credential, and a provisioning change either way, which is why arming is a deliberate operator act. Sibling of integration-connectivity-escalation: that flag arms the alert, this one arms the record.",
+    flagType: "boolean",
+    // Declared safe value is `false` (shadow / record untouched). It matches the
+    // route's compiled default since ENG-6139, so migrating the reader onto this
+    // flag (ADR-0022) preserves fleet behaviour exactly. `false` is also the
+    // fail-safe direction: a flag-DB read error must never de-provision an
+    // integration on its own.
+    defaultValue: false,
+    // Migration override (ADR-0022): the pre-flags env gate stays the
+    // highest-precedence operator override. ENG-10473 deliberately does NOT wire
+    // this var in sst.config.ts - ENG-8303 records what happens when a declared
+    // envVar is pinned there: it outranks the DB value and makes the flag inert
+    // everywhere it matters.
+    envVar: "AUGMENTED_CONNECTIVITY_RECONCILE_STATUS"
+  },
   {
     key: "slack-manifest-remediate",
     description: "Let the Slack manifest drift monitor PUSH, not just alert (ENG-9963). updateSlackManifest had exactly one caller \u2014 a console button \u2014 so nothing but a human click ever pushed a manifest; ENG-7762 changed the generator with no rollout mechanism and 26 agents went 53 days with no working per-agent slash commands. When on, the daily drift cron pushes the generated manifest for a drifted agent. When off it alerts exactly as before. NOTE what arming this authorises: a push REPLACES a customer-owned Slack app's entire manifest, so the cron only ever pushes drift whose diffs are purely additive (isSafelyRemediable) \u2014 an app with live-only entries a push would destroy is declined and left for a human. Boolean gate; ships dark.",
@@ -14618,4 +14635,4 @@ export {
   peekCurrentSession,
   readDailySessionPin
 };
-//# sourceMappingURL=chunk-Y7ERASS6.js.map
+//# sourceMappingURL=chunk-IIIMUCGD.js.map