@integrity-labs/agt-cli 0.28.928 → 0.28.929

package/dist/{chunk-NIUBYSLW.js → chunk-ZNVYUZSM.js}

@@ -19,7 +19,7 @@ import {
   rotateDailySession,
   sessionFileExists,
   todayLocalIso
-} from "./chunk-Y7ERASS6.js";
+} from "./chunk-IIIMUCGD.js";
 import {
   reapOrphanChannelMcps
 } from "./chunk-XWVM4KPK.js";
@@ -5730,4 +5730,4 @@ export {
   stopAllSessionsAndWait,
   getProjectDir
 };
-//# sourceMappingURL=chunk-NIUBYSLW.js.map
+//# sourceMappingURL=chunk-ZNVYUZSM.js.map

package/dist/{claude-pair-runtime-RFY57WC3.js → claude-pair-runtime-MA4CLC6B.js}

@@ -100,7 +100,7 @@ async function spawnPairSession(session) {
     return { ok: true };
   } catch {
   }
-  const { resolveClaudeBinary } = await import("./persistent-session-O3AKW6IW.js");
+  const { resolveClaudeBinary } = await import("./persistent-session-PYQ5U6FU.js");
   const claudeBin = resolveClaudeBinary();
   const pairEnv = {
     ...process.env,
@@ -373,4 +373,4 @@ export {
   startClaudePair,
   submitClaudePairCode
 };
-//# sourceMappingURL=claude-pair-runtime-RFY57WC3.js.map
+//# sourceMappingURL=claude-pair-runtime-MA4CLC6B.js.map

package/dist/lib/manager-worker.js

@@ -63,7 +63,7 @@ import {
   safeWriteJsonAtomic,
   setConfigHash,
   tripClass
-} from "../chunk-OXWLTPU2.js";
+} from "../chunk-VZVCPJC7.js";
 import {
   getProjectDir as getProjectDir2,
   getReadyTasks,
@@ -136,7 +136,7 @@ import {
   takeZombieDetection,
   toOpencodeModel,
   writeEgressAllowlist
-} from "../chunk-NIUBYSLW.js";
+} from "../chunk-ZNVYUZSM.js";
 import {
   ACCOUNT_ENFORCEMENT_MARKER_FILENAME,
   AnchorSessionClient,
@@ -231,7 +231,7 @@ import {
   subagentActivityAgeSeconds,
   sumTranscriptUsageInWindow,
   transcriptActivityAgeSeconds
-} from "../chunk-Y7ERASS6.js";
+} from "../chunk-IIIMUCGD.js";
 import {
   reapOrphanChannelMcps
 } from "../chunk-XWVM4KPK.js";
@@ -13221,7 +13221,7 @@ var pendingDayRolloverReset = /* @__PURE__ */ new Set();
 var dayRolloverInboundHold = /* @__PURE__ */ new Map();
 var INBOUND_HOLD_EPISODE_GAP_MS = 12e4;
 async function channelInboundActivityAgeSecondsFor(codeName) {
-  const { newestPendingInboundActivityMtimeMs } = await import("../responsiveness-probe-MIPUX3BG.js");
+  const { newestPendingInboundActivityMtimeMs } = await import("../responsiveness-probe-T4LKSNFO.js");
   const newest = newestPendingInboundActivityMtimeMs(dirname11(paneLogPath(codeName)));
   if (newest === null) return null;
   return Math.max(0, Math.floor((Date.now() - newest) / 1e3));
@@ -13906,7 +13906,7 @@ var agentRestartTimezoneInputs = /* @__PURE__ */ new Map();
 var lastVersionCheckAt = 0;
 var VERSION_CHECK_INTERVAL_MS = 5 * 60 * 1e3;
 var lastResponsivenessProbeAt = 0;
-var agtCliVersion = true ? "0.28.928" : "dev";
+var agtCliVersion = true ? "0.28.929" : "dev";
 function resolveBrewPath(execFileSync2) {
   try {
     const out = execFileSync2("which", ["brew"], { timeout: 5e3 }).toString().trim();
@@ -15496,7 +15496,7 @@ function flushRestartedAgentDiagnostics(hostId, codeNames) {
   if (codeNames.length === 0) return;
   void (async () => {
     try {
-      const { collectDiagnostics } = await import("../persistent-session-O3AKW6IW.js");
+      const { collectDiagnostics } = await import("../persistent-session-PYQ5U6FU.js");
       await api.post("/host/heartbeat", {
         host_id: hostId,
         agent_diagnostics: collectDiagnostics(codeNames, quarantineEntriesFor, claudeMdSizeFor, spawnOutcomeForDiagnostics, pidPressureFor, forwardedToolsFor)
@@ -15638,7 +15638,7 @@ async function pollCycleInner() {
     }
     try {
       const { detectHostSecurity } = await import("../host-security-6PDFG7F5.js");
-      const { collectDiagnostics } = await import("../persistent-session-O3AKW6IW.js");
+      const { collectDiagnostics } = await import("../persistent-session-PYQ5U6FU.js");
       const diagCodeNames = [...agentState.persistentSessionAgents];
       const agentDiagnostics = diagCodeNames.length > 0 ? collectDiagnostics(diagCodeNames, quarantineEntriesFor, claudeMdSizeFor, spawnOutcomeForDiagnostics, pidPressureFor, forwardedToolsFor) : void 0;
       let tailscaleHostname;
@@ -15813,7 +15813,7 @@ async function pollCycleInner() {
         collectPanelessActivityProbes,
         getResponsivenessIntervalMs,
         occupancyQualificationClassifications
-      } = await import("../responsiveness-probe-MIPUX3BG.js");
+      } = await import("../responsiveness-probe-T4LKSNFO.js");
       const probeIntervalMs = getResponsivenessIntervalMs();
       if (now - lastResponsivenessProbeAt > probeIntervalMs) {
         const probeCodeNames = [...agentState.persistentSessionAgents];
@@ -15930,7 +15930,7 @@ async function pollCycleInner() {
           collectResponsivenessProbes,
           livePendingInboundOldestAgeSeconds,
           parkPendingInbound
-        } = await import("../responsiveness-probe-MIPUX3BG.js");
+        } = await import("../responsiveness-probe-T4LKSNFO.js");
         const { getProjectDir: wedgeProjectDir } = await import("../scheduler-engine-NDP36U7O.js");
         const wedgeNow = /* @__PURE__ */ new Date();
         const liveAgents = agentState.persistentSessionAgents;
@@ -16086,7 +16086,7 @@ async function pollCycleInner() {
     }
     try {
       const { scrapeMcpFailedBannerCount } = await import("../pane-mcp-banner-scraper-JA437JIB.js");
-      const { probeSessionAuth } = await import("../session-auth-dead-ZGZZLE4X.js");
+      const { probeSessionAuth } = await import("../session-auth-dead-M5SFWTQH.js");
       const observations = [];
       const pendingCacheCommits = [];
       const modelApiErrorReportingOn = hostFlagStore().getBoolean("model-api-error-reporting");
@@ -20350,7 +20350,7 @@ async function handleRestartDoorbell(agentId, requestedAt, restartReason) {
       try {
         const freshId = rotateSessionForWedge(codeName);
         consecutiveWedgeCycles.delete(codeName);
-        const { parkPendingInbound: parkForRestart } = await import("../responsiveness-probe-MIPUX3BG.js");
+        const { parkPendingInbound: parkForRestart } = await import("../responsiveness-probe-T4LKSNFO.js");
         const { parked, deadLettered } = parkForRestart(codeName, /* @__PURE__ */ new Date());
         const parkNote = parked > 0 ? `, ${parked} inbound parked` : "";
         const deadNote = deadLettered > 0 ? `, ${deadLettered} undeliverable dead-lettered` : "";
@@ -20393,7 +20393,7 @@ async function handleRestartDoorbell(agentId, requestedAt, restartReason) {
     void api.post("/host/restart-ack", { host_id: hostId, agent_id: agentId, restart_requested_at: requestedAt }).catch((err) => log(`[restart-lane] ack failed for '${codeName}': ${err.message}`));
     void (async () => {
       try {
-        const { collectDiagnostics } = await import("../persistent-session-O3AKW6IW.js");
+        const { collectDiagnostics } = await import("../persistent-session-PYQ5U6FU.js");
         await api.post("/host/heartbeat", {
           host_id: hostId,
           agent_diagnostics: collectDiagnostics([codeName], quarantineEntriesFor, claudeMdSizeFor, spawnOutcomeForDiagnostics, pidPressureFor, forwardedToolsFor)
@@ -20444,7 +20444,7 @@ async function respawnAgentAfterMcpStop(codeName, reason) {
     }
     try {
       const hostId = await getHostId();
-      const { collectDiagnostics } = await import("../persistent-session-O3AKW6IW.js");
+      const { collectDiagnostics } = await import("../persistent-session-PYQ5U6FU.js");
       await api.post("/host/heartbeat", {
         host_id: hostId,
         agent_diagnostics: collectDiagnostics([codeName], quarantineEntriesFor, claudeMdSizeFor, spawnOutcomeForDiagnostics, pidPressureFor, forwardedToolsFor)
@@ -21086,7 +21086,7 @@ async function processClaudePairSessions(agents) {
     killPairSession,
     pairTmuxSession,
     finalizeClaudePairOnboarding
-  } = await import("../claude-pair-runtime-RFY57WC3.js");
+  } = await import("../claude-pair-runtime-MA4CLC6B.js");
   for (const pairId of pendingResp.cancelled_pair_ids ?? []) {
     log(`[claude-pair] sweeping orphan tmux session for pair ${pairId.slice(0, 8)}`);
     const killed = await killPairSession(pairTmuxSession(pairId));

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

@@ -37410,6 +37410,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.",

package/dist/mcp/index.js

@@ -29726,6 +29726,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.",

package/dist/mcp/origami.js

@@ -43627,6 +43627,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.",

package/dist/mcp/slack-channel.js

@@ -38286,6 +38286,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.",

package/dist/mcp/telegram-channel.js

@@ -38322,6 +38322,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.",

package/dist/{persistent-session-O3AKW6IW.js → persistent-session-PYQ5U6FU.js}

@@ -62,8 +62,8 @@ import {
   writeDirectChatSessionState,
   writeEgressAllowlist,
   writePersistentClaudeWrapper
-} from "./chunk-NIUBYSLW.js";
-import "./chunk-Y7ERASS6.js";
+} from "./chunk-ZNVYUZSM.js";
+import "./chunk-IIIMUCGD.js";
 import "./chunk-XWVM4KPK.js";
 export {
   CLAUDE_HOST_WIDE,
@@ -130,4 +130,4 @@ export {
   writeEgressAllowlist,
   writePersistentClaudeWrapper
 };
-//# sourceMappingURL=persistent-session-O3AKW6IW.js.map
+//# sourceMappingURL=persistent-session-PYQ5U6FU.js.map

package/dist/{responsiveness-probe-MIPUX3BG.js → responsiveness-probe-T4LKSNFO.js}

@@ -1,7 +1,7 @@
 import {
   paneLogPath
-} from "./chunk-NIUBYSLW.js";
-import "./chunk-Y7ERASS6.js";
+} from "./chunk-ZNVYUZSM.js";
+import "./chunk-IIIMUCGD.js";
 import "./chunk-XWVM4KPK.js";
 
 // src/lib/responsiveness-probe.ts
@@ -799,4 +799,4 @@ export {
   readAndResetSlackReplyBindingClassifications,
   readAndResetSlackReplyTargetClassifications
 };
-//# sourceMappingURL=responsiveness-probe-MIPUX3BG.js.map
+//# sourceMappingURL=responsiveness-probe-T4LKSNFO.js.map

package/dist/{session-auth-dead-ZGZZLE4X.js → session-auth-dead-M5SFWTQH.js}

@@ -1,6 +1,6 @@
 import {
   sessionTranscriptDir
-} from "./chunk-Y7ERASS6.js";
+} from "./chunk-IIIMUCGD.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-ZGZZLE4X.js.map
+//# sourceMappingURL=session-auth-dead-M5SFWTQH.js.map

package/package.json

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