@integrity-labs/agt-cli 0.28.508 → 0.28.509

package/dist/{claude-pair-runtime-YQ7V5TS6.js → claude-pair-runtime-5CDR4XPI.js}

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

package/dist/lib/manager-worker.js

@@ -53,7 +53,7 @@ import {
   safeWriteJsonAtomic,
   setConfigHash,
   tripClass
-} from "../chunk-GK3TSZ4S.js";
+} from "../chunk-S5X4XFAC.js";
 import {
   getProjectDir as getProjectDir2,
   getReadyTasks,
@@ -173,7 +173,7 @@ import {
   toOpencodeModel,
   transcriptActivityAgeSeconds,
   writeEgressAllowlist
-} from "../chunk-LNPJI2AE.js";
+} from "../chunk-7U63M5R6.js";
 import {
   reapOrphanChannelMcps
 } from "../chunk-XWVM4KPK.js";
@@ -10038,7 +10038,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.508" : "dev";
+var agtCliVersion = true ? "0.28.509" : "dev";
 function resolveBrewPath(execFileSync2) {
   try {
     const out = execFileSync2("which", ["brew"], { timeout: 5e3 }).toString().trim();
@@ -11245,7 +11245,7 @@ function flushRestartedAgentDiagnostics(hostId, codeNames) {
   if (codeNames.length === 0) return;
   void (async () => {
     try {
-      const { collectDiagnostics } = await import("../persistent-session-VX37ESOS.js");
+      const { collectDiagnostics } = await import("../persistent-session-BDNW4K6M.js");
       await api.post("/host/heartbeat", {
         host_id: hostId,
         agent_diagnostics: collectDiagnostics(codeNames, quarantineEntriesFor, claudeMdSizeFor)
@@ -11352,7 +11352,7 @@ async function pollCycle() {
     }
     try {
       const { detectHostSecurity } = await import("../host-security-6PDFG7F5.js");
-      const { collectDiagnostics } = await import("../persistent-session-VX37ESOS.js");
+      const { collectDiagnostics } = await import("../persistent-session-BDNW4K6M.js");
       const diagCodeNames = [...agentState.persistentSessionAgents];
       const agentDiagnostics = diagCodeNames.length > 0 ? collectDiagnostics(diagCodeNames, quarantineEntriesFor, claudeMdSizeFor) : void 0;
       let tailscaleHostname;
@@ -11467,7 +11467,7 @@ async function pollCycle() {
         collectResponsivenessProbes,
         collectPanelessActivityProbes,
         getResponsivenessIntervalMs
-      } = await import("../responsiveness-probe-5MEW5XNI.js");
+      } = await import("../responsiveness-probe-KR73VA2S.js");
       const probeIntervalMs = getResponsivenessIntervalMs();
       if (now - lastResponsivenessProbeAt > probeIntervalMs) {
         const probeCodeNames = [...agentState.persistentSessionAgents];
@@ -11531,7 +11531,7 @@ async function pollCycle() {
           collectResponsivenessProbes,
           livePendingInboundOldestAgeSeconds,
           parkPendingInbound
-        } = await import("../responsiveness-probe-5MEW5XNI.js");
+        } = await import("../responsiveness-probe-KR73VA2S.js");
         const { getProjectDir: wedgeProjectDir } = await import("../scheduler-engine-NDP36U7O.js");
         const wedgeNow = /* @__PURE__ */ new Date();
         const liveAgents = agentState.persistentSessionAgents;
@@ -15023,7 +15023,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-VX37ESOS.js");
+        const { collectDiagnostics } = await import("../persistent-session-BDNW4K6M.js");
         await api.post("/host/heartbeat", {
           host_id: hostId,
           agent_diagnostics: collectDiagnostics([codeName], quarantineEntriesFor, claudeMdSizeFor)
@@ -15073,7 +15073,7 @@ async function respawnAgentAfterMcpStop(codeName, reason) {
     }
     try {
       const hostId = await getHostId();
-      const { collectDiagnostics } = await import("../persistent-session-VX37ESOS.js");
+      const { collectDiagnostics } = await import("../persistent-session-BDNW4K6M.js");
       await api.post("/host/heartbeat", {
         host_id: hostId,
         agent_diagnostics: collectDiagnostics([codeName], quarantineEntriesFor, claudeMdSizeFor)
@@ -15591,7 +15591,7 @@ async function processClaudePairSessions(agents) {
     killPairSession,
     pairTmuxSession,
     finalizeClaudePairOnboarding
-  } = await import("../claude-pair-runtime-YQ7V5TS6.js");
+  } = await import("../claude-pair-runtime-5CDR4XPI.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

@@ -32955,29 +32955,44 @@ var INTEGRATION_REGISTRY = [
     id: "vercel",
     name: "Vercel",
     category: "infrastructure",
-    description: "Check on Vercel app deployments \u2014 status, build/runtime logs \u2014 and search Vercel documentation. Remote streamable-HTTP MCP at https://mcp.vercel.com.",
-    // Same OAuth pattern as Granola/Higgsfield: Claude Code brokers the
-    // browser sign-in at runtime; nothing for the manager API to provision.
-    supported_auth_types: ["none"],
+    description: "Check on Vercel app deployments \u2014 what's live, deployment status, and build logs \u2014 through Vercel's REST API with your own API token.",
+    // ENG-8421: api_key, NOT the host-brokered MCP this used to be.
+    //
+    // Vercel MCP (`https://mcp.vercel.com`) is not completable from the
+    // console, and that is a vendor constraint rather than a gap in our
+    // plumbing. Established empirically 2026-08-03: Dynamic Client
+    // Registration REJECTS an https redirect (`invalid_redirect_uri` — "not
+    // approved for use by this authorization server") and ACCEPTS only
+    // localhost; the device-code grant, the one flow needing no redirect, is
+    // refused to DCR clients (`unauthorized_client`). So the only client
+    // Vercel permits is a local one redirecting to its own ephemeral port —
+    // i.e. Claude Code on the agent's host, driven by an operator running
+    // `/mcp` in tmux. No console work can remove that step.
+    //
+    // The REST API has none of those constraints: plain bearer auth
+    // (unauthenticated → `{"code":"forbidden","missingToken":true}`, bogus
+    // bearer → `{"invalidToken":true}`), so a token the customer creates in
+    // their own Vercel dashboard works directly. That makes this an ordinary
+    // paste-a-key integration, and it means WE hold the credential — so it can
+    // be stored, rotated, revoked and audited, none of which was true when the
+    // grant lived in Claude Code's `~/.claude.json` on the host.
+    //
+    // Tools are declared as data on `integration_definitions.metadata.tools`
+    // and dispatch through the existing Direct HTTP broker (the v0 pattern) —
+    // there is deliberately no bespoke Vercel client and no bespoke broker.
+    supported_auth_types: ["api_key"],
     capabilities: [
-      { id: "vercel:read-deployments", name: "Read Deployments", description: "List teams/projects, check deployment status, and read build/runtime logs.", access: "read" },
-      { id: "vercel:search-docs", name: "Search Documentation", description: "Search Vercel platform documentation.", access: "read" }
+      { id: "vercel:read-deployments", name: "Read Deployments", description: "List teams/projects, check deployment status, and read build logs.", access: "read" }
     ],
-    docs_url: "https://vercel.com/docs/agent-resources/vercel-mcp",
-    // Beta until the headless OAuth flow (and Vercel's OAuth-client allowlist,
-    // which is vendor-side and outside our control) is verified end-to-end.
-    beta: true,
-    // No `auth`/`headers` — host-brokered OAuth (Claude Code authenticates
-    // directly with Vercel; nothing for us to inject). Declaring this here
-    // (rather than a hardcoded buildMcpJson/writeIntegrations branch, the
-    // pre-ENG-8035 Higgsfield-era pattern) lets the generic remote-MCP loop
-    // render the `.mcp.json` entry AND enrolls 'vercel' in the
-    // `registryRemoteMcpKeys` prune universe automatically, so an uninstall
-    // actually removes the entry instead of leaving it stale.
-    remoteMcp: {
-      type: "http",
-      url: "https://mcp.vercel.com"
-    }
+    docs_url: "https://vercel.com/docs/rest-api",
+    // Beta until the REST tool surface has been exercised against a real
+    // customer token. (The previous reason — "until the headless OAuth flow is
+    // verified end-to-end" — is void: there is no OAuth flow any more.)
+    beta: true
+    // NO `remoteMcp`. See the tombstone in the claudecode adapter's prune
+    // universe: dropping this field also drops `vercel` from
+    // `registryRemoteMcpKeys`, which would strand the `.mcp.json` entry on
+    // every host that installed the MCP variant.
   },
   {
     id: "qmd",

package/dist/mcp/origami.js

@@ -39282,29 +39282,44 @@ var INTEGRATION_REGISTRY = [
     id: "vercel",
     name: "Vercel",
     category: "infrastructure",
-    description: "Check on Vercel app deployments \u2014 status, build/runtime logs \u2014 and search Vercel documentation. Remote streamable-HTTP MCP at https://mcp.vercel.com.",
-    // Same OAuth pattern as Granola/Higgsfield: Claude Code brokers the
-    // browser sign-in at runtime; nothing for the manager API to provision.
-    supported_auth_types: ["none"],
+    description: "Check on Vercel app deployments \u2014 what's live, deployment status, and build logs \u2014 through Vercel's REST API with your own API token.",
+    // ENG-8421: api_key, NOT the host-brokered MCP this used to be.
+    //
+    // Vercel MCP (`https://mcp.vercel.com`) is not completable from the
+    // console, and that is a vendor constraint rather than a gap in our
+    // plumbing. Established empirically 2026-08-03: Dynamic Client
+    // Registration REJECTS an https redirect (`invalid_redirect_uri` — "not
+    // approved for use by this authorization server") and ACCEPTS only
+    // localhost; the device-code grant, the one flow needing no redirect, is
+    // refused to DCR clients (`unauthorized_client`). So the only client
+    // Vercel permits is a local one redirecting to its own ephemeral port —
+    // i.e. Claude Code on the agent's host, driven by an operator running
+    // `/mcp` in tmux. No console work can remove that step.
+    //
+    // The REST API has none of those constraints: plain bearer auth
+    // (unauthenticated → `{"code":"forbidden","missingToken":true}`, bogus
+    // bearer → `{"invalidToken":true}`), so a token the customer creates in
+    // their own Vercel dashboard works directly. That makes this an ordinary
+    // paste-a-key integration, and it means WE hold the credential — so it can
+    // be stored, rotated, revoked and audited, none of which was true when the
+    // grant lived in Claude Code's `~/.claude.json` on the host.
+    //
+    // Tools are declared as data on `integration_definitions.metadata.tools`
+    // and dispatch through the existing Direct HTTP broker (the v0 pattern) —
+    // there is deliberately no bespoke Vercel client and no bespoke broker.
+    supported_auth_types: ["api_key"],
     capabilities: [
-      { id: "vercel:read-deployments", name: "Read Deployments", description: "List teams/projects, check deployment status, and read build/runtime logs.", access: "read" },
-      { id: "vercel:search-docs", name: "Search Documentation", description: "Search Vercel platform documentation.", access: "read" }
+      { id: "vercel:read-deployments", name: "Read Deployments", description: "List teams/projects, check deployment status, and read build logs.", access: "read" }
     ],
-    docs_url: "https://vercel.com/docs/agent-resources/vercel-mcp",
-    // Beta until the headless OAuth flow (and Vercel's OAuth-client allowlist,
-    // which is vendor-side and outside our control) is verified end-to-end.
-    beta: true,
-    // No `auth`/`headers` — host-brokered OAuth (Claude Code authenticates
-    // directly with Vercel; nothing for us to inject). Declaring this here
-    // (rather than a hardcoded buildMcpJson/writeIntegrations branch, the
-    // pre-ENG-8035 Higgsfield-era pattern) lets the generic remote-MCP loop
-    // render the `.mcp.json` entry AND enrolls 'vercel' in the
-    // `registryRemoteMcpKeys` prune universe automatically, so an uninstall
-    // actually removes the entry instead of leaving it stale.
-    remoteMcp: {
-      type: "http",
-      url: "https://mcp.vercel.com"
-    }
+    docs_url: "https://vercel.com/docs/rest-api",
+    // Beta until the REST tool surface has been exercised against a real
+    // customer token. (The previous reason — "until the headless OAuth flow is
+    // verified end-to-end" — is void: there is no OAuth flow any more.)
+    beta: true
+    // NO `remoteMcp`. See the tombstone in the claudecode adapter's prune
+    // universe: dropping this field also drops `vercel` from
+    // `registryRemoteMcpKeys`, which would strand the `.mcp.json` entry on
+    // every host that installed the MCP variant.
   },
   {
     id: "qmd",

package/dist/mcp/slack-channel.js

@@ -33177,29 +33177,44 @@ var INTEGRATION_REGISTRY = [
     id: "vercel",
     name: "Vercel",
     category: "infrastructure",
-    description: "Check on Vercel app deployments \u2014 status, build/runtime logs \u2014 and search Vercel documentation. Remote streamable-HTTP MCP at https://mcp.vercel.com.",
-    // Same OAuth pattern as Granola/Higgsfield: Claude Code brokers the
-    // browser sign-in at runtime; nothing for the manager API to provision.
-    supported_auth_types: ["none"],
+    description: "Check on Vercel app deployments \u2014 what's live, deployment status, and build logs \u2014 through Vercel's REST API with your own API token.",
+    // ENG-8421: api_key, NOT the host-brokered MCP this used to be.
+    //
+    // Vercel MCP (`https://mcp.vercel.com`) is not completable from the
+    // console, and that is a vendor constraint rather than a gap in our
+    // plumbing. Established empirically 2026-08-03: Dynamic Client
+    // Registration REJECTS an https redirect (`invalid_redirect_uri` — "not
+    // approved for use by this authorization server") and ACCEPTS only
+    // localhost; the device-code grant, the one flow needing no redirect, is
+    // refused to DCR clients (`unauthorized_client`). So the only client
+    // Vercel permits is a local one redirecting to its own ephemeral port —
+    // i.e. Claude Code on the agent's host, driven by an operator running
+    // `/mcp` in tmux. No console work can remove that step.
+    //
+    // The REST API has none of those constraints: plain bearer auth
+    // (unauthenticated → `{"code":"forbidden","missingToken":true}`, bogus
+    // bearer → `{"invalidToken":true}`), so a token the customer creates in
+    // their own Vercel dashboard works directly. That makes this an ordinary
+    // paste-a-key integration, and it means WE hold the credential — so it can
+    // be stored, rotated, revoked and audited, none of which was true when the
+    // grant lived in Claude Code's `~/.claude.json` on the host.
+    //
+    // Tools are declared as data on `integration_definitions.metadata.tools`
+    // and dispatch through the existing Direct HTTP broker (the v0 pattern) —
+    // there is deliberately no bespoke Vercel client and no bespoke broker.
+    supported_auth_types: ["api_key"],
     capabilities: [
-      { id: "vercel:read-deployments", name: "Read Deployments", description: "List teams/projects, check deployment status, and read build/runtime logs.", access: "read" },
-      { id: "vercel:search-docs", name: "Search Documentation", description: "Search Vercel platform documentation.", access: "read" }
+      { id: "vercel:read-deployments", name: "Read Deployments", description: "List teams/projects, check deployment status, and read build logs.", access: "read" }
     ],
-    docs_url: "https://vercel.com/docs/agent-resources/vercel-mcp",
-    // Beta until the headless OAuth flow (and Vercel's OAuth-client allowlist,
-    // which is vendor-side and outside our control) is verified end-to-end.
-    beta: true,
-    // No `auth`/`headers` — host-brokered OAuth (Claude Code authenticates
-    // directly with Vercel; nothing for us to inject). Declaring this here
-    // (rather than a hardcoded buildMcpJson/writeIntegrations branch, the
-    // pre-ENG-8035 Higgsfield-era pattern) lets the generic remote-MCP loop
-    // render the `.mcp.json` entry AND enrolls 'vercel' in the
-    // `registryRemoteMcpKeys` prune universe automatically, so an uninstall
-    // actually removes the entry instead of leaving it stale.
-    remoteMcp: {
-      type: "http",
-      url: "https://mcp.vercel.com"
-    }
+    docs_url: "https://vercel.com/docs/rest-api",
+    // Beta until the REST tool surface has been exercised against a real
+    // customer token. (The previous reason — "until the headless OAuth flow is
+    // verified end-to-end" — is void: there is no OAuth flow any more.)
+    beta: true
+    // NO `remoteMcp`. See the tombstone in the claudecode adapter's prune
+    // universe: dropping this field also drops `vercel` from
+    // `registryRemoteMcpKeys`, which would strand the `.mcp.json` entry on
+    // every host that installed the MCP variant.
   },
   {
     id: "qmd",

package/dist/mcp/telegram-channel.js

@@ -33503,29 +33503,44 @@ var INTEGRATION_REGISTRY = [
     id: "vercel",
     name: "Vercel",
     category: "infrastructure",
-    description: "Check on Vercel app deployments \u2014 status, build/runtime logs \u2014 and search Vercel documentation. Remote streamable-HTTP MCP at https://mcp.vercel.com.",
-    // Same OAuth pattern as Granola/Higgsfield: Claude Code brokers the
-    // browser sign-in at runtime; nothing for the manager API to provision.
-    supported_auth_types: ["none"],
+    description: "Check on Vercel app deployments \u2014 what's live, deployment status, and build logs \u2014 through Vercel's REST API with your own API token.",
+    // ENG-8421: api_key, NOT the host-brokered MCP this used to be.
+    //
+    // Vercel MCP (`https://mcp.vercel.com`) is not completable from the
+    // console, and that is a vendor constraint rather than a gap in our
+    // plumbing. Established empirically 2026-08-03: Dynamic Client
+    // Registration REJECTS an https redirect (`invalid_redirect_uri` — "not
+    // approved for use by this authorization server") and ACCEPTS only
+    // localhost; the device-code grant, the one flow needing no redirect, is
+    // refused to DCR clients (`unauthorized_client`). So the only client
+    // Vercel permits is a local one redirecting to its own ephemeral port —
+    // i.e. Claude Code on the agent's host, driven by an operator running
+    // `/mcp` in tmux. No console work can remove that step.
+    //
+    // The REST API has none of those constraints: plain bearer auth
+    // (unauthenticated → `{"code":"forbidden","missingToken":true}`, bogus
+    // bearer → `{"invalidToken":true}`), so a token the customer creates in
+    // their own Vercel dashboard works directly. That makes this an ordinary
+    // paste-a-key integration, and it means WE hold the credential — so it can
+    // be stored, rotated, revoked and audited, none of which was true when the
+    // grant lived in Claude Code's `~/.claude.json` on the host.
+    //
+    // Tools are declared as data on `integration_definitions.metadata.tools`
+    // and dispatch through the existing Direct HTTP broker (the v0 pattern) —
+    // there is deliberately no bespoke Vercel client and no bespoke broker.
+    supported_auth_types: ["api_key"],
     capabilities: [
-      { id: "vercel:read-deployments", name: "Read Deployments", description: "List teams/projects, check deployment status, and read build/runtime logs.", access: "read" },
-      { id: "vercel:search-docs", name: "Search Documentation", description: "Search Vercel platform documentation.", access: "read" }
+      { id: "vercel:read-deployments", name: "Read Deployments", description: "List teams/projects, check deployment status, and read build logs.", access: "read" }
     ],
-    docs_url: "https://vercel.com/docs/agent-resources/vercel-mcp",
-    // Beta until the headless OAuth flow (and Vercel's OAuth-client allowlist,
-    // which is vendor-side and outside our control) is verified end-to-end.
-    beta: true,
-    // No `auth`/`headers` — host-brokered OAuth (Claude Code authenticates
-    // directly with Vercel; nothing for us to inject). Declaring this here
-    // (rather than a hardcoded buildMcpJson/writeIntegrations branch, the
-    // pre-ENG-8035 Higgsfield-era pattern) lets the generic remote-MCP loop
-    // render the `.mcp.json` entry AND enrolls 'vercel' in the
-    // `registryRemoteMcpKeys` prune universe automatically, so an uninstall
-    // actually removes the entry instead of leaving it stale.
-    remoteMcp: {
-      type: "http",
-      url: "https://mcp.vercel.com"
-    }
+    docs_url: "https://vercel.com/docs/rest-api",
+    // Beta until the REST tool surface has been exercised against a real
+    // customer token. (The previous reason — "until the headless OAuth flow is
+    // verified end-to-end" — is void: there is no OAuth flow any more.)
+    beta: true
+    // NO `remoteMcp`. See the tombstone in the claudecode adapter's prune
+    // universe: dropping this field also drops `vercel` from
+    // `registryRemoteMcpKeys`, which would strand the `.mcp.json` entry on
+    // every host that installed the MCP variant.
   },
   {
     id: "qmd",

package/dist/{persistent-session-VX37ESOS.js → persistent-session-BDNW4K6M.js}

@@ -37,7 +37,7 @@ import {
   writeDirectChatSessionState,
   writeEgressAllowlist,
   writePersistentClaudeWrapper
-} from "./chunk-LNPJI2AE.js";
+} from "./chunk-7U63M5R6.js";
 import "./chunk-XWVM4KPK.js";
 export {
   EGRESS_BASELINE_DOMAINS,
@@ -79,4 +79,4 @@ export {
   writeEgressAllowlist,
   writePersistentClaudeWrapper
 };
-//# sourceMappingURL=persistent-session-VX37ESOS.js.map
+//# sourceMappingURL=persistent-session-BDNW4K6M.js.map

package/dist/{responsiveness-probe-5MEW5XNI.js → responsiveness-probe-KR73VA2S.js}

@@ -1,6 +1,6 @@
 import {
   paneLogPath
-} from "./chunk-LNPJI2AE.js";
+} from "./chunk-7U63M5R6.js";
 import "./chunk-XWVM4KPK.js";
 
 // src/lib/responsiveness-probe.ts
@@ -662,4 +662,4 @@ export {
   readAndResetSlackReplyBindingClassifications,
   readAndResetSlackReplyTargetClassifications
 };
-//# sourceMappingURL=responsiveness-probe-5MEW5XNI.js.map
+//# sourceMappingURL=responsiveness-probe-KR73VA2S.js.map

package/package.json

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