@integrity-labs/agt-cli 0.28.658 → 0.28.660

package/dist/{chunk-LAYT5BNW.js → chunk-Y63W2XP5.js}

@@ -16,7 +16,7 @@ import {
   rotateDailySession,
   sessionFileExists,
   todayLocalIso
-} from "./chunk-RASKCVAA.js";
+} from "./chunk-VR3VB3FR.js";
 import {
   reapOrphanChannelMcps
 } from "./chunk-XWVM4KPK.js";
@@ -4322,4 +4322,4 @@ export {
   stopAllSessionsAndWait,
   getProjectDir
 };
-//# sourceMappingURL=chunk-LAYT5BNW.js.map
+//# sourceMappingURL=chunk-Y63W2XP5.js.map

package/dist/{claude-pair-runtime-TRRXWBEM.js → claude-pair-runtime-JMESZQPN.js}

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

package/dist/lib/manager-worker.js

@@ -55,7 +55,7 @@ import {
   safeWriteJsonAtomic,
   setConfigHash,
   tripClass
-} from "../chunk-QIOFZ6EP.js";
+} from "../chunk-ESEOTR5J.js";
 import {
   getProjectDir as getProjectDir2,
   getReadyTasks,
@@ -111,7 +111,7 @@ import {
   takeZombieDetection,
   toOpencodeModel,
   writeEgressAllowlist
-} from "../chunk-LAYT5BNW.js";
+} from "../chunk-Y63W2XP5.js";
 import {
   ACCOUNT_ENFORCEMENT_MARKER_FILENAME,
   AnchorSessionClient,
@@ -192,7 +192,7 @@ import {
   subagentActivityAgeSeconds,
   sumTranscriptUsageInWindow,
   transcriptActivityAgeSeconds
-} from "../chunk-RASKCVAA.js";
+} from "../chunk-VR3VB3FR.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-HP6SYFOJ.js");
+  const { newestPendingInboundActivityMtimeMs } = await import("../responsiveness-probe-EII7QAGR.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.658" : "dev";
+var agtCliVersion = true ? "0.28.660" : "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-PG7POJ3L.js");
+      const { collectDiagnostics } = await import("../persistent-session-ADS4LIGF.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-PG7POJ3L.js");
+      const { collectDiagnostics } = await import("../persistent-session-ADS4LIGF.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-HP6SYFOJ.js");
+      } = await import("../responsiveness-probe-EII7QAGR.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-HP6SYFOJ.js");
+        } = await import("../responsiveness-probe-EII7QAGR.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-RIAIWHHV.js");
+      const { probeSessionAuth } = await import("../session-auth-dead-TY2WU55Z.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-PG7POJ3L.js");
+        const { collectDiagnostics } = await import("../persistent-session-ADS4LIGF.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-PG7POJ3L.js");
+      const { collectDiagnostics } = await import("../persistent-session-ADS4LIGF.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-TRRXWBEM.js");
+  } = await import("../claude-pair-runtime-JMESZQPN.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

@@ -40801,6 +40801,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",
@@ -44429,6 +44492,48 @@ server.tool(
     }
   }
 );
+server.tool(
+  "kanban_reopen",
+  "Send a card you assigned back to the agent that did the work, WITH your review feedback. Use this when you delegated a task with kanban_assign, the agent completed it, and you reviewed the delivery and found something wrong. The card reopens on THEIR board in todo carrying your feedback, and they are notified on the card itself. This is the only way your review reaches them: their card is not on your board, so notes you write on your own card are invisible to them, and opening a NEW card reframes a correction as fresh work and loses the link to what it corrected. You may only reopen a card YOU assigned, to somebody else, on your own team, that is finished (done or failed). You cannot reopen your own card this way - that would be a way around the rule that closed work stays closed; open a new card instead. BOUNDED: two reopens per card. A third means the two of you have not converged, and the answer to that is a human, not another round - raise it with yours.",
+  {
+    item_id: external_exports.string().describe("The card id, as returned by kanban_assign or shown on the completion notice."),
+    feedback: external_exports.string().trim().min(1, "feedback is required - a reopen with nothing attached just deletes a result nobody replaced").max(2e3, "feedback is too long - send the correction (the criterion, the file, the behaviour), not the whole review").describe(
+      'What is wrong and what you want changed. REQUIRED and it must say something - a reopen with nothing attached just deletes a result nobody replaced. Be specific enough to act on: name the acceptance criterion, the file, or the behaviour, not "needs work".'
+    )
+  },
+  async (params) => {
+    try {
+      const data = await apiPost("/host/kanban/reopen", {
+        agent_id: AGT_AGENT_ID,
+        item_id: params.item_id,
+        feedback: params.feedback
+      });
+      if (!data?.ok) {
+        const detail = data?.error ?? `Could not reopen that card (${data?.reason ?? "unknown"}).`;
+        return { content: [{ type: "text", text: detail }] };
+      }
+      const turns = data.is_last_turn ? " That was the last reopen this card allows - if it comes back wrong again, raise it with a human rather than sending it back." : "";
+      const delivery = data.notified ? " They have been notified on the card." : ` NOTE: the card reopened but the notification did NOT go out${data.notify_error ? ` (${data.notify_error})` : ""}, so they may not know yet - tell them directly.`;
+      return {
+        content: [
+          {
+            type: "text",
+            text: `Reopened "${data.title ?? params.item_id}" on the assignee's board with your feedback (reopen ${data.reopen_count ?? 1} of 2).${delivery}${turns}`
+          }
+        ]
+      };
+    } catch (err) {
+      return {
+        content: [
+          {
+            type: "text",
+            text: `Could not reopen that card: ${err instanceof Error ? err.message : String(err)}`
+          }
+        ]
+      };
+    }
+  }
+);
 server.tool(
   "kanban_recall",
   'Pull a card you assigned to a HUMAN teammate back onto your own board. Use this when a card shows under "Assigned to a person" in kanban_list and you need to act on it - typically because the person finished the work (or it is no longer needed) and the card has to be closed. While a card is assigned to a person, every kanban write to it is refused; recall makes it yours again so kanban_move / kanban_done / kanban_log work. Recall does NOT complete the card - after recalling, close it yourself with kanban_done and a result. You can only recall a card you assigned.',
@@ -46084,6 +46189,8 @@ var LOCAL_TOOL_NAMES = /* @__PURE__ */ new Set([
   // ENG-8281: the inverse of assign_kanban_to_human — take a human-assigned
   // card back so the agent can finally close it.
   "kanban_recall",
+  // ENG-9050: the return path for delegated work.
+  "kanban_reopen",
   // ENG-6953: agent + people directory lookup (always registered locally).
   "directory_lookup",
   "status_standup",

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-PG7POJ3L.js → persistent-session-ADS4LIGF.js}

@@ -43,8 +43,8 @@ import {
   writeDirectChatSessionState,
   writeEgressAllowlist,
   writePersistentClaudeWrapper
-} from "./chunk-LAYT5BNW.js";
-import "./chunk-RASKCVAA.js";
+} from "./chunk-Y63W2XP5.js";
+import "./chunk-VR3VB3FR.js";
 import "./chunk-XWVM4KPK.js";
 export {
   EGRESS_BASELINE_DOMAINS,
@@ -92,4 +92,4 @@ export {
   writeEgressAllowlist,
   writePersistentClaudeWrapper
 };
-//# sourceMappingURL=persistent-session-PG7POJ3L.js.map
+//# sourceMappingURL=persistent-session-ADS4LIGF.js.map

package/dist/{responsiveness-probe-HP6SYFOJ.js → responsiveness-probe-EII7QAGR.js}

@@ -1,7 +1,7 @@
 import {
   paneLogPath
-} from "./chunk-LAYT5BNW.js";
-import "./chunk-RASKCVAA.js";
+} from "./chunk-Y63W2XP5.js";
+import "./chunk-VR3VB3FR.js";
 import "./chunk-XWVM4KPK.js";
 
 // src/lib/responsiveness-probe.ts
@@ -727,4 +727,4 @@ export {
   readAndResetSlackReplyBindingClassifications,
   readAndResetSlackReplyTargetClassifications
 };
-//# sourceMappingURL=responsiveness-probe-HP6SYFOJ.js.map
+//# sourceMappingURL=responsiveness-probe-EII7QAGR.js.map

package/dist/{session-auth-dead-RIAIWHHV.js → session-auth-dead-TY2WU55Z.js}

@@ -1,6 +1,6 @@
 import {
   sessionTranscriptDir
-} from "./chunk-RASKCVAA.js";
+} from "./chunk-VR3VB3FR.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-RIAIWHHV.js.map
+//# sourceMappingURL=session-auth-dead-TY2WU55Z.js.map

package/package.json

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