@integrity-labs/agt-cli 0.28.659 → 0.28.661

package/dist/{claude-pair-runtime-ODPRSH45.js → claude-pair-runtime-AAHU6VUL.js}

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

package/dist/lib/manager-worker.js

@@ -55,7 +55,7 @@ import {
   safeWriteJsonAtomic,
   setConfigHash,
   tripClass
-} from "../chunk-ACQZZIK6.js";
+} from "../chunk-WDCI3FYP.js";
 import {
   getProjectDir as getProjectDir2,
   getReadyTasks,
@@ -111,7 +111,7 @@ import {
   takeZombieDetection,
   toOpencodeModel,
   writeEgressAllowlist
-} from "../chunk-LUIGOCT4.js";
+} from "../chunk-5JAUM7J2.js";
 import {
   ACCOUNT_ENFORCEMENT_MARKER_FILENAME,
   AnchorSessionClient,
@@ -192,7 +192,7 @@ import {
   subagentActivityAgeSeconds,
   sumTranscriptUsageInWindow,
   transcriptActivityAgeSeconds
-} from "../chunk-NLCHGFD5.js";
+} from "../chunk-SU2J2QRH.js";
 import {
   reapOrphanChannelMcps
 } from "../chunk-XWVM4KPK.js";
@@ -11609,7 +11609,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-NN4BNX2V.js");
+  const { newestPendingInboundActivityMtimeMs } = await import("../responsiveness-probe-APGLAESO.js");
   const newest = newestPendingInboundActivityMtimeMs(dirname10(paneLogPath(codeName)));
   if (newest === null) return null;
   return Math.max(0, Math.floor((Date.now() - newest) / 1e3));
@@ -12252,7 +12252,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.659" : "dev";
+var agtCliVersion = true ? "0.28.661" : "dev";
 function resolveBrewPath(execFileSync3) {
   try {
     const out = execFileSync3("which", ["brew"], { timeout: 5e3 }).toString().trim();
@@ -13562,7 +13562,7 @@ function flushRestartedAgentDiagnostics(hostId, codeNames) {
   if (codeNames.length === 0) return;
   void (async () => {
     try {
-      const { collectDiagnostics } = await import("../persistent-session-QVLWWFK3.js");
+      const { collectDiagnostics } = await import("../persistent-session-WOZN2ORO.js");
       await api.post("/host/heartbeat", {
         host_id: hostId,
         agent_diagnostics: collectDiagnostics(codeNames, quarantineEntriesFor, claudeMdSizeFor, spawnOutcomeForDiagnostics, pidPressureFor)
@@ -13678,7 +13678,7 @@ async function pollCycleInner() {
     }
     try {
       const { detectHostSecurity } = await import("../host-security-6PDFG7F5.js");
-      const { collectDiagnostics } = await import("../persistent-session-QVLWWFK3.js");
+      const { collectDiagnostics } = await import("../persistent-session-WOZN2ORO.js");
       const diagCodeNames = [...agentState.persistentSessionAgents];
       const agentDiagnostics = diagCodeNames.length > 0 ? collectDiagnostics(diagCodeNames, quarantineEntriesFor, claudeMdSizeFor, spawnOutcomeForDiagnostics, pidPressureFor) : void 0;
       let tailscaleHostname;
@@ -13801,7 +13801,7 @@ async function pollCycleInner() {
         collectPanelessActivityProbes,
         getResponsivenessIntervalMs,
         occupancyQualificationClassifications
-      } = await import("../responsiveness-probe-NN4BNX2V.js");
+      } = await import("../responsiveness-probe-APGLAESO.js");
       const probeIntervalMs = getResponsivenessIntervalMs();
       if (now - lastResponsivenessProbeAt > probeIntervalMs) {
         const probeCodeNames = [...agentState.persistentSessionAgents];
@@ -13911,7 +13911,7 @@ async function pollCycleInner() {
           collectResponsivenessProbes,
           livePendingInboundOldestAgeSeconds,
           parkPendingInbound
-        } = await import("../responsiveness-probe-NN4BNX2V.js");
+        } = await import("../responsiveness-probe-APGLAESO.js");
         const { getProjectDir: wedgeProjectDir } = await import("../scheduler-engine-NDP36U7O.js");
         const wedgeNow = /* @__PURE__ */ new Date();
         const liveAgents = agentState.persistentSessionAgents;
@@ -14067,7 +14067,7 @@ async function pollCycleInner() {
     }
     try {
       const { scrapeMcpFailedBannerCount } = await import("../pane-mcp-banner-scraper-JA437JIB.js");
-      const { probeSessionAuth } = await import("../session-auth-dead-KD66YN7O.js");
+      const { probeSessionAuth } = await import("../session-auth-dead-SMMFC3UF.js");
       const observations = [];
       const pendingCacheCommits = [];
       const modelApiErrorReportingOn = hostFlagStore().getBoolean("model-api-error-reporting");
@@ -17700,7 +17700,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-QVLWWFK3.js");
+        const { collectDiagnostics } = await import("../persistent-session-WOZN2ORO.js");
         await api.post("/host/heartbeat", {
           host_id: hostId,
           agent_diagnostics: collectDiagnostics([codeName], quarantineEntriesFor, claudeMdSizeFor, spawnOutcomeForDiagnostics, pidPressureFor)
@@ -17751,7 +17751,7 @@ async function respawnAgentAfterMcpStop(codeName, reason) {
     }
     try {
       const hostId = await getHostId();
-      const { collectDiagnostics } = await import("../persistent-session-QVLWWFK3.js");
+      const { collectDiagnostics } = await import("../persistent-session-WOZN2ORO.js");
       await api.post("/host/heartbeat", {
         host_id: hostId,
         agent_diagnostics: collectDiagnostics([codeName], quarantineEntriesFor, claudeMdSizeFor, spawnOutcomeForDiagnostics, pidPressureFor)
@@ -18348,7 +18348,7 @@ async function processClaudePairSessions(agents) {
     killPairSession,
     pairTmuxSession,
     finalizeClaudePairOnboarding
-  } = await import("../claude-pair-runtime-ODPRSH45.js");
+  } = await import("../claude-pair-runtime-AAHU6VUL.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

@@ -33419,6 +33419,69 @@ var INTEGRATION_REGISTRY = [
       args: ["mcp"]
     }
   },
+  {
+    // ENG-9244 / CS-1593. Framer is the first `cli_tool` integration whose CLI
+    // does NOT authenticate from `env_key`, so read
+    // `integrations/framer-credentials.ts` before changing anything here — the
+    // env var below serves the SDK, and the CLI is served by a separate
+    // `projects.json` the provisioner materialises.
+    id: "framer",
+    name: "Framer",
+    category: "ui-generation",
+    description: "Design, edit and publish a Framer website \u2014 update page copy and images, manage CMS collections, and publish deployments",
+    supported_auth_types: ["api_key"],
+    // Pre-1.0 on both halves (@framer/agent 0.0.44, framer-api 0.1.29) and
+    // Framer bills the Server API itself as a preview. Expect churn.
+    beta: true,
+    installable: { category: "Website", authTypes: ["api_key"] },
+    capabilities: [
+      {
+        id: "framer:read-site",
+        name: "Read Site",
+        description: "Read page text, structure, styles, fonts and CMS content",
+        access: "read"
+      },
+      {
+        id: "framer:edit-site",
+        name: "Edit Site",
+        description: "Update page text and images, create pages, manage CMS collections, redirects and localisation",
+        access: "write"
+      },
+      {
+        id: "framer:publish",
+        name: "Publish",
+        description: "Publish the site and promote a deployment to production",
+        access: "write"
+      }
+    ],
+    cli_tool: {
+      package: "@framer/agent",
+      // UPSTREAM HAZARD: the package's own bin name is `agent`. On a fleet whose
+      // whole job is running agents, putting a global `agent` on PATH is asking
+      // for a collision, so the binary we look for and invoke is the shimmed
+      // `framer-agent`. `installer: 'script'` (rather than plain npm) is what
+      // creates that shim — a bare `npm install -g @framer/agent` would publish
+      // `agent` and we would have shipped the collision.
+      binary: "framer-agent",
+      // Serves the `framer-api` SDK, which DOES read this. The CLI does not —
+      // see framer-credentials.ts for why that distinction matters.
+      env_key: "FRAMER_API_KEY",
+      skill_id: "framer",
+      installer: "script",
+      // The catalog is the trust boundary for this string (same contract as the
+      // `gh` entry above). Installs into a private prefix and links ONLY the
+      // renamed binary, so `agent` never lands on PATH.
+      // VERSION IS PINNED ON PURPOSE. `framer-credentials.ts` mirrors this
+      // CLI's pre-1.0 `projects.json` schema (already at version 2, with a
+      // legacy credentials.json path still in its source — this format HAS
+      // churned). An unpinned global install would let a future release land a
+      // schema we do not write, leaving the CLI unauthenticated on a headless
+      // host. Bump this only alongside a compatibility check of the config
+      // format against the new release.
+      script: "npm install -g --prefix /usr/local/framer-agent @framer/agent@0.0.44 && ln -sf /usr/local/framer-agent/bin/agent /usr/local/bin/framer-agent"
+    },
+    docs_url: "https://www.framer.com/developers/server-api-quick-start"
+  },
   {
     id: "v0",
     name: "v0 by Vercel",

package/dist/mcp/index.js

@@ -37309,6 +37309,12 @@ function describeFeatureRequestResult(resp) {
       isError: false
     };
   }
+  if (resp.status === "catalogue_match") {
+    return {
+      text: `Not filed \u2014 we already sell this. ${resp.message ?? ""}`.trim(),
+      isError: false
+    };
+  }
   return {
     text: `Could not submit the feature request${resp.message ? `: ${resp.message}` : ""}. Tell your operator what you need and don't keep retrying.`,
     isError: true
@@ -40801,6 +40807,69 @@ var INTEGRATION_REGISTRY = [
       args: ["mcp"]
     }
   },
+  {
+    // ENG-9244 / CS-1593. Framer is the first `cli_tool` integration whose CLI
+    // does NOT authenticate from `env_key`, so read
+    // `integrations/framer-credentials.ts` before changing anything here — the
+    // env var below serves the SDK, and the CLI is served by a separate
+    // `projects.json` the provisioner materialises.
+    id: "framer",
+    name: "Framer",
+    category: "ui-generation",
+    description: "Design, edit and publish a Framer website \u2014 update page copy and images, manage CMS collections, and publish deployments",
+    supported_auth_types: ["api_key"],
+    // Pre-1.0 on both halves (@framer/agent 0.0.44, framer-api 0.1.29) and
+    // Framer bills the Server API itself as a preview. Expect churn.
+    beta: true,
+    installable: { category: "Website", authTypes: ["api_key"] },
+    capabilities: [
+      {
+        id: "framer:read-site",
+        name: "Read Site",
+        description: "Read page text, structure, styles, fonts and CMS content",
+        access: "read"
+      },
+      {
+        id: "framer:edit-site",
+        name: "Edit Site",
+        description: "Update page text and images, create pages, manage CMS collections, redirects and localisation",
+        access: "write"
+      },
+      {
+        id: "framer:publish",
+        name: "Publish",
+        description: "Publish the site and promote a deployment to production",
+        access: "write"
+      }
+    ],
+    cli_tool: {
+      package: "@framer/agent",
+      // UPSTREAM HAZARD: the package's own bin name is `agent`. On a fleet whose
+      // whole job is running agents, putting a global `agent` on PATH is asking
+      // for a collision, so the binary we look for and invoke is the shimmed
+      // `framer-agent`. `installer: 'script'` (rather than plain npm) is what
+      // creates that shim — a bare `npm install -g @framer/agent` would publish
+      // `agent` and we would have shipped the collision.
+      binary: "framer-agent",
+      // Serves the `framer-api` SDK, which DOES read this. The CLI does not —
+      // see framer-credentials.ts for why that distinction matters.
+      env_key: "FRAMER_API_KEY",
+      skill_id: "framer",
+      installer: "script",
+      // The catalog is the trust boundary for this string (same contract as the
+      // `gh` entry above). Installs into a private prefix and links ONLY the
+      // renamed binary, so `agent` never lands on PATH.
+      // VERSION IS PINNED ON PURPOSE. `framer-credentials.ts` mirrors this
+      // CLI's pre-1.0 `projects.json` schema (already at version 2, with a
+      // legacy credentials.json path still in its source — this format HAS
+      // churned). An unpinned global install would let a future release land a
+      // schema we do not write, leaving the CLI unauthenticated on a headless
+      // host. Bump this only alongside a compatibility check of the config
+      // format against the new release.
+      script: "npm install -g --prefix /usr/local/framer-agent @framer/agent@0.0.44 && ln -sf /usr/local/framer-agent/bin/agent /usr/local/bin/framer-agent"
+    },
+    docs_url: "https://www.framer.com/developers/server-api-quick-start"
+  },
   {
     id: "v0",
     name: "v0 by Vercel",
@@ -44572,6 +44641,9 @@ server.tool(
     provider: external_exports.string().max(120).optional().describe(
       'For feature_type="integration": the name of the service/provider requested (e.g. "Notion", "QuickBooks"). Omit for other types.'
     ),
+    acknowledged_catalogue_alternative: external_exports.boolean().optional().describe(
+      "ENG-9246. Leave this unset on a first attempt. If your request is declined because Augmented already sells the capability, the reply names the integration and the request_integration_access call to make instead \u2014 do that. Only set this to true, and say why in the description, when the customer genuinely needs a DIFFERENT vendor rather than the capability itself. It does not make a stronger case; it just records that you checked."
+    ),
     requester_email: external_exports.string().email().max(320).optional().describe(
       "The email address of the end user who asked for this, so Augmented Team can email them when it is resolved. Only include an email the user has given you and agreed to be contacted at - do NOT guess or invent one. Omit if you don't have their consent or an address."
     ),
@@ -44595,7 +44667,8 @@ server.tool(
         description: params.description,
         ...params.provider ? { provider: params.provider } : {},
         ...params.requester_email ? { requester_email: params.requester_email } : {},
-        ...params.requester_user_id ? { requester_user_id: params.requester_user_id } : {}
+        ...params.requester_user_id ? { requester_user_id: params.requester_user_id } : {},
+        ...params.acknowledged_catalogue_alternative ? { acknowledged_catalogue_alternative: true } : {}
       });
     } catch (err) {
       return {

package/dist/mcp/origami.js

@@ -39639,6 +39639,69 @@ var INTEGRATION_REGISTRY = [
       args: ["mcp"]
     }
   },
+  {
+    // ENG-9244 / CS-1593. Framer is the first `cli_tool` integration whose CLI
+    // does NOT authenticate from `env_key`, so read
+    // `integrations/framer-credentials.ts` before changing anything here — the
+    // env var below serves the SDK, and the CLI is served by a separate
+    // `projects.json` the provisioner materialises.
+    id: "framer",
+    name: "Framer",
+    category: "ui-generation",
+    description: "Design, edit and publish a Framer website \u2014 update page copy and images, manage CMS collections, and publish deployments",
+    supported_auth_types: ["api_key"],
+    // Pre-1.0 on both halves (@framer/agent 0.0.44, framer-api 0.1.29) and
+    // Framer bills the Server API itself as a preview. Expect churn.
+    beta: true,
+    installable: { category: "Website", authTypes: ["api_key"] },
+    capabilities: [
+      {
+        id: "framer:read-site",
+        name: "Read Site",
+        description: "Read page text, structure, styles, fonts and CMS content",
+        access: "read"
+      },
+      {
+        id: "framer:edit-site",
+        name: "Edit Site",
+        description: "Update page text and images, create pages, manage CMS collections, redirects and localisation",
+        access: "write"
+      },
+      {
+        id: "framer:publish",
+        name: "Publish",
+        description: "Publish the site and promote a deployment to production",
+        access: "write"
+      }
+    ],
+    cli_tool: {
+      package: "@framer/agent",
+      // UPSTREAM HAZARD: the package's own bin name is `agent`. On a fleet whose
+      // whole job is running agents, putting a global `agent` on PATH is asking
+      // for a collision, so the binary we look for and invoke is the shimmed
+      // `framer-agent`. `installer: 'script'` (rather than plain npm) is what
+      // creates that shim — a bare `npm install -g @framer/agent` would publish
+      // `agent` and we would have shipped the collision.
+      binary: "framer-agent",
+      // Serves the `framer-api` SDK, which DOES read this. The CLI does not —
+      // see framer-credentials.ts for why that distinction matters.
+      env_key: "FRAMER_API_KEY",
+      skill_id: "framer",
+      installer: "script",
+      // The catalog is the trust boundary for this string (same contract as the
+      // `gh` entry above). Installs into a private prefix and links ONLY the
+      // renamed binary, so `agent` never lands on PATH.
+      // VERSION IS PINNED ON PURPOSE. `framer-credentials.ts` mirrors this
+      // CLI's pre-1.0 `projects.json` schema (already at version 2, with a
+      // legacy credentials.json path still in its source — this format HAS
+      // churned). An unpinned global install would let a future release land a
+      // schema we do not write, leaving the CLI unauthenticated on a headless
+      // host. Bump this only alongside a compatibility check of the config
+      // format against the new release.
+      script: "npm install -g --prefix /usr/local/framer-agent @framer/agent@0.0.44 && ln -sf /usr/local/framer-agent/bin/agent /usr/local/bin/framer-agent"
+    },
+    docs_url: "https://www.framer.com/developers/server-api-quick-start"
+  },
   {
     id: "v0",
     name: "v0 by Vercel",

package/dist/mcp/slack-channel.js

@@ -33705,6 +33705,69 @@ var INTEGRATION_REGISTRY = [
       args: ["mcp"]
     }
   },
+  {
+    // ENG-9244 / CS-1593. Framer is the first `cli_tool` integration whose CLI
+    // does NOT authenticate from `env_key`, so read
+    // `integrations/framer-credentials.ts` before changing anything here — the
+    // env var below serves the SDK, and the CLI is served by a separate
+    // `projects.json` the provisioner materialises.
+    id: "framer",
+    name: "Framer",
+    category: "ui-generation",
+    description: "Design, edit and publish a Framer website \u2014 update page copy and images, manage CMS collections, and publish deployments",
+    supported_auth_types: ["api_key"],
+    // Pre-1.0 on both halves (@framer/agent 0.0.44, framer-api 0.1.29) and
+    // Framer bills the Server API itself as a preview. Expect churn.
+    beta: true,
+    installable: { category: "Website", authTypes: ["api_key"] },
+    capabilities: [
+      {
+        id: "framer:read-site",
+        name: "Read Site",
+        description: "Read page text, structure, styles, fonts and CMS content",
+        access: "read"
+      },
+      {
+        id: "framer:edit-site",
+        name: "Edit Site",
+        description: "Update page text and images, create pages, manage CMS collections, redirects and localisation",
+        access: "write"
+      },
+      {
+        id: "framer:publish",
+        name: "Publish",
+        description: "Publish the site and promote a deployment to production",
+        access: "write"
+      }
+    ],
+    cli_tool: {
+      package: "@framer/agent",
+      // UPSTREAM HAZARD: the package's own bin name is `agent`. On a fleet whose
+      // whole job is running agents, putting a global `agent` on PATH is asking
+      // for a collision, so the binary we look for and invoke is the shimmed
+      // `framer-agent`. `installer: 'script'` (rather than plain npm) is what
+      // creates that shim — a bare `npm install -g @framer/agent` would publish
+      // `agent` and we would have shipped the collision.
+      binary: "framer-agent",
+      // Serves the `framer-api` SDK, which DOES read this. The CLI does not —
+      // see framer-credentials.ts for why that distinction matters.
+      env_key: "FRAMER_API_KEY",
+      skill_id: "framer",
+      installer: "script",
+      // The catalog is the trust boundary for this string (same contract as the
+      // `gh` entry above). Installs into a private prefix and links ONLY the
+      // renamed binary, so `agent` never lands on PATH.
+      // VERSION IS PINNED ON PURPOSE. `framer-credentials.ts` mirrors this
+      // CLI's pre-1.0 `projects.json` schema (already at version 2, with a
+      // legacy credentials.json path still in its source — this format HAS
+      // churned). An unpinned global install would let a future release land a
+      // schema we do not write, leaving the CLI unauthenticated on a headless
+      // host. Bump this only alongside a compatibility check of the config
+      // format against the new release.
+      script: "npm install -g --prefix /usr/local/framer-agent @framer/agent@0.0.44 && ln -sf /usr/local/framer-agent/bin/agent /usr/local/bin/framer-agent"
+    },
+    docs_url: "https://www.framer.com/developers/server-api-quick-start"
+  },
   {
     id: "v0",
     name: "v0 by Vercel",

package/dist/mcp/telegram-channel.js

@@ -33849,6 +33849,69 @@ var INTEGRATION_REGISTRY = [
       args: ["mcp"]
     }
   },
+  {
+    // ENG-9244 / CS-1593. Framer is the first `cli_tool` integration whose CLI
+    // does NOT authenticate from `env_key`, so read
+    // `integrations/framer-credentials.ts` before changing anything here — the
+    // env var below serves the SDK, and the CLI is served by a separate
+    // `projects.json` the provisioner materialises.
+    id: "framer",
+    name: "Framer",
+    category: "ui-generation",
+    description: "Design, edit and publish a Framer website \u2014 update page copy and images, manage CMS collections, and publish deployments",
+    supported_auth_types: ["api_key"],
+    // Pre-1.0 on both halves (@framer/agent 0.0.44, framer-api 0.1.29) and
+    // Framer bills the Server API itself as a preview. Expect churn.
+    beta: true,
+    installable: { category: "Website", authTypes: ["api_key"] },
+    capabilities: [
+      {
+        id: "framer:read-site",
+        name: "Read Site",
+        description: "Read page text, structure, styles, fonts and CMS content",
+        access: "read"
+      },
+      {
+        id: "framer:edit-site",
+        name: "Edit Site",
+        description: "Update page text and images, create pages, manage CMS collections, redirects and localisation",
+        access: "write"
+      },
+      {
+        id: "framer:publish",
+        name: "Publish",
+        description: "Publish the site and promote a deployment to production",
+        access: "write"
+      }
+    ],
+    cli_tool: {
+      package: "@framer/agent",
+      // UPSTREAM HAZARD: the package's own bin name is `agent`. On a fleet whose
+      // whole job is running agents, putting a global `agent` on PATH is asking
+      // for a collision, so the binary we look for and invoke is the shimmed
+      // `framer-agent`. `installer: 'script'` (rather than plain npm) is what
+      // creates that shim — a bare `npm install -g @framer/agent` would publish
+      // `agent` and we would have shipped the collision.
+      binary: "framer-agent",
+      // Serves the `framer-api` SDK, which DOES read this. The CLI does not —
+      // see framer-credentials.ts for why that distinction matters.
+      env_key: "FRAMER_API_KEY",
+      skill_id: "framer",
+      installer: "script",
+      // The catalog is the trust boundary for this string (same contract as the
+      // `gh` entry above). Installs into a private prefix and links ONLY the
+      // renamed binary, so `agent` never lands on PATH.
+      // VERSION IS PINNED ON PURPOSE. `framer-credentials.ts` mirrors this
+      // CLI's pre-1.0 `projects.json` schema (already at version 2, with a
+      // legacy credentials.json path still in its source — this format HAS
+      // churned). An unpinned global install would let a future release land a
+      // schema we do not write, leaving the CLI unauthenticated on a headless
+      // host. Bump this only alongside a compatibility check of the config
+      // format against the new release.
+      script: "npm install -g --prefix /usr/local/framer-agent @framer/agent@0.0.44 && ln -sf /usr/local/framer-agent/bin/agent /usr/local/bin/framer-agent"
+    },
+    docs_url: "https://www.framer.com/developers/server-api-quick-start"
+  },
   {
     id: "v0",
     name: "v0 by Vercel",

package/dist/{persistent-session-QVLWWFK3.js → persistent-session-WOZN2ORO.js}

@@ -43,8 +43,8 @@ import {
   writeDirectChatSessionState,
   writeEgressAllowlist,
   writePersistentClaudeWrapper
-} from "./chunk-LUIGOCT4.js";
-import "./chunk-NLCHGFD5.js";
+} from "./chunk-5JAUM7J2.js";
+import "./chunk-SU2J2QRH.js";
 import "./chunk-XWVM4KPK.js";
 export {
   EGRESS_BASELINE_DOMAINS,
@@ -92,4 +92,4 @@ export {
   writeEgressAllowlist,
   writePersistentClaudeWrapper
 };
-//# sourceMappingURL=persistent-session-QVLWWFK3.js.map
+//# sourceMappingURL=persistent-session-WOZN2ORO.js.map

package/dist/{responsiveness-probe-NN4BNX2V.js → responsiveness-probe-APGLAESO.js}

@@ -1,7 +1,7 @@
 import {
   paneLogPath
-} from "./chunk-LUIGOCT4.js";
-import "./chunk-NLCHGFD5.js";
+} from "./chunk-5JAUM7J2.js";
+import "./chunk-SU2J2QRH.js";
 import "./chunk-XWVM4KPK.js";
 
 // src/lib/responsiveness-probe.ts
@@ -727,4 +727,4 @@ export {
   readAndResetSlackReplyBindingClassifications,
   readAndResetSlackReplyTargetClassifications
 };
-//# sourceMappingURL=responsiveness-probe-NN4BNX2V.js.map
+//# sourceMappingURL=responsiveness-probe-APGLAESO.js.map

package/dist/{session-auth-dead-KD66YN7O.js → session-auth-dead-SMMFC3UF.js}

@@ -1,6 +1,6 @@
 import {
   sessionTranscriptDir
-} from "./chunk-NLCHGFD5.js";
+} from "./chunk-SU2J2QRH.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-KD66YN7O.js.map
+//# sourceMappingURL=session-auth-dead-SMMFC3UF.js.map

package/package.json

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