@integrity-labs/agt-cli 0.28.474 → 0.28.476

package/dist/{chunk-YR6ESOCM.js → chunk-Q6RVMDAC.js}

@@ -6552,6 +6552,34 @@ var INTEGRATION_REGISTRY = [
     docs_url: "https://higgsfield.ai/mcp",
     beta: true
   },
+  {
+    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"],
+    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" }
+    ],
+    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"
+    }
+  },
   {
     id: "qmd",
     name: "QMD Memory Search",
@@ -8278,6 +8306,7 @@ function formatRunMarker(runId) {
   return `<!-- agt-run:${runId} -->`;
 }
 var RUN_MARKER_RE = /<!--\s*agt-run:([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12})\s*-->/;
+var RUN_MARKER_RE_GLOBAL = new RegExp(RUN_MARKER_RE.source, "g");
 
 // ../../packages/core/dist/claude-code-usage/transcript-parser.js
 function nonNegInt(value) {
@@ -8504,38 +8533,6 @@ function attributeTranscriptUsageByRun(jsonl) {
   return { perRunModel: [...agg.values()], runIds: [...runIds] };
 }
 
-// ../../packages/core/dist/claude-code-usage/usage-limit-marker.js
-var USAGE_LIMIT_MARKER_FILENAME = "claude-usage-limit.json";
-var USAGE_LIMIT_MARKER_VERSION = 1;
-function serializeUsageLimitMarker(limitedUntil) {
-  const marker = {
-    version: USAGE_LIMIT_MARKER_VERSION,
-    limited_until: limitedUntil.toISOString()
-  };
-  return JSON.stringify(marker);
-}
-function parseUsageLimitMarker(raw) {
-  let parsed;
-  try {
-    parsed = JSON.parse(raw);
-  } catch {
-    return null;
-  }
-  if (typeof parsed !== "object" || parsed === null || parsed.version !== USAGE_LIMIT_MARKER_VERSION) {
-    return null;
-  }
-  const until = parsed.limited_until;
-  if (typeof until !== "string" || !Number.isFinite(Date.parse(until)))
-    return null;
-  return { version: USAGE_LIMIT_MARKER_VERSION, limited_until: until };
-}
-function resolveUsageLimitUntil(marker, now) {
-  if (!marker)
-    return null;
-  const until = new Date(marker.limited_until);
-  return until.getTime() > now.getTime() ? until : null;
-}
-
 // ../../packages/core/dist/claude-code-usage/rate-limit-classifier.js
 var UNKNOWN_RATE_LIMIT = Object.freeze({
   verdict: "unknown",
@@ -9373,42 +9370,6 @@ var FLAG_REGISTRY = [
     // projectDefinition, so setting it does not roll FLAGS_SCHEMA_VERSION.
     since: "0.28.421"
   },
-  {
-    key: "usage-limit-reactive-notice",
-    description: "Report a Claude Code usage cap REACTIVELY instead of predicting it (ENG-8201). Today the manager guesses from the agent transcript that the next turn will be refused, writes a marker, and every channel MCP refuses to dispatch on the strength of that guess - so a wrong guess is a swallowed message, and because the notice is throttled per (channel, sender) while the DROP is not, the usual symptom is total silence rather than a wrong reply. A refused turn actually costs nothing (rejected in under a second, zero tokens) and Claude Code records it with the reset time in it, so there is no need to guess: dispatch, and report the refusal if one comes back. off = today behaviour (pre-dispatch marker gate, no watcher). shadow = still gate on the marker, but ALSO watch dispatched messages and log the refusal that would have been reported - measures the true-positive rate with no user-visible change. enforce = stop reading the marker before dispatch; every admitted human message reaches the agent and a refusal is answered in-thread with the reset time from the error itself. Read live from the heartbeat flags-cache (or the env override).",
-    flagType: "enum",
-    allowedValues: ["off", "shadow", "enforce"],
-    // Ships dark: off preserves today's gate byte-for-byte. shadow is a free
-    // local log line (the watch is a transcript read, no model spend), so it is a
-    // cheap soak; enforce changes what reaches the agent, so it is the audited
-    // per-org flip.
-    defaultValue: "off",
-    // Enum override AGT_USAGE_LIMIT_REACTIVE_MODE (off|shadow|enforce), resolved
-    // by resolveUsageLimitReactiveMode in the channel-server bundle.
-    envVar: "AGT_USAGE_LIMIT_REACTIVE_MODE",
-    // enforce sends a message to an agent the host currently believes is capped -
-    // a deliberate availability trade (the refusal is free, but it is still a
-    // dispatch the operator previously suppressed), so flipping toward it is an
-    // audited change (ADR-0022 sensitive-flag confirm).
-    sensitive: true,
-    // ENG-8149 / ENG-8229: the agt-cli that first carries
-    // resolveUsageLimitReactiveMode in ALL THREE channel servers - published from
-    // the ENG-8207 merge 0294fa1a8. Without this the flip-reach modal reports FULL
-    // reach, because an undefined `since` means "every host can honour it" - true
-    // for flags that predate the reach work, wrong for a NEW host-read flag whose
-    // reader older hosts simply do not have. Excluded from projectDefinition, so
-    // setting it does not roll FLAGS_SCHEMA_VERSION.
-    //
-    // Deliberately the LATER of the two versions this flag's reader shipped in.
-    // Unlike its siblings, this reader landed in two stages: direct-chat at the
-    // ENG-8201 Slice 2 publish, slack + telegram only at 0.28.450 (ENG-8207) - and
-    // `since` is one version per flag, so it cannot express "partially honoured".
-    // A host in between genuinely honours the flag for direct-chat and is still
-    // classified `stale`. That understates reach rather than overstating it, which
-    // is the safe direction, and it is the useful one while the flag sits at
-    // enforce and slack/telegram adoption is what an operator needs to track.
-    since: "0.28.450"
-  },
   {
     key: "slack-hot-thread-guard",
     description: "Server-side hot-thread guard on the slack.reply surface (ENG-7462). Prevents an agent posting a NEW top-level Slack message when it meant to reply inside the thread it is already working in - a prompt/memory rule proved insufficient (the agent had the rule and still slipped). When a reply would otherwise post to channel ROOT (no thread_ts / message_ts / inbound_id, no active kanban card) and the agent has a recent active thread in that channel (its last bot-posted thread, from the persisted trackedThreads cache, within a freshness window), the reply is redirected into that thread. proactive:true no longer implies channel root; posting at root becomes a deliberate action (the to_channel_root flag, or the thread_ts:null sentinel). off = guard never runs, replies with no coords root exactly as today (ships dark). shadow = compute + log the would-redirect but STILL post to root (measure the fire rate before acting). enforce = apply the redirect (a soft-block: redirect + inform, never a hard rejection). Read live from the heartbeat flags-cache (or the env override); enforce is a deliberate per-org flip after a shadow soak.",
@@ -13274,7 +13235,7 @@ function restartEgressSidecar(codeName) {
   }
 }
 function buildDockerRunCommand(args) {
-  const { codeName, agentId, wrapperPath, projectDir, homeDir, runId, passApiKey, passOpenRouter, egress, forwardSlackReplyBinding, forwardBlockTurnEndAllMarkers, forwardKanbanWaiting, forwardNotifyDispatch, forwardUsageLimitReactive, forwardTurnFailureNotice } = args;
+  const { codeName, agentId, wrapperPath, projectDir, homeDir, runId, passApiKey, passOpenRouter, egress, forwardSlackReplyBinding, forwardBlockTurnEndAllMarkers, forwardKanbanWaiting, forwardNotifyDispatch, forwardTurnFailureNotice } = args;
   const q = (s) => `'${s.replace(/'/g, `'\\''`)}'`;
   const agentDir2 = join5(homeDir, ".augmented", codeName);
   const agentIdDir = join5(homeDir, ".augmented", agentId);
@@ -13311,7 +13272,6 @@ function buildDockerRunCommand(args) {
   if (forwardBlockTurnEndAllMarkers) envArgs.push("-e AGT_BLOCK_TURN_END_ALL_MARKERS_ENABLED");
   if (forwardKanbanWaiting) envArgs.push("-e AGT_KANBAN_WAITING_ENABLED");
   if (forwardNotifyDispatch) envArgs.push("-e AGT_NOTIFY_DISPATCH");
-  if (forwardUsageLimitReactive) envArgs.push("-e AGT_USAGE_LIMIT_REACTIVE_MODE");
   if (forwardTurnFailureNotice) envArgs.push("-e AGT_WEDGE_TRANSIENT_NOTICE_ENABLED");
   const egressImage = process.env.AGT_EGRESS_IMAGE || "agt-squid:latest";
   const internalNet = `agt-net-${codeName}`;
@@ -13666,12 +13626,6 @@ function spawnSession(config, session) {
     if (config.notifyDispatchMode && config.notifyDispatchMode !== "off" && !process.env["AGT_NOTIFY_DISPATCH"]) {
       tmuxSessionEnvArgs.push("-e", `AGT_NOTIFY_DISPATCH=${config.notifyDispatchMode}`);
     }
-    if (config.usageLimitReactiveMode && config.usageLimitReactiveMode !== "off" && !process.env["AGT_USAGE_LIMIT_REACTIVE_MODE"]) {
-      tmuxSessionEnvArgs.push(
-        "-e",
-        `AGT_USAGE_LIMIT_REACTIVE_MODE=${config.usageLimitReactiveMode}`
-      );
-    }
     if (config.turnFailureNoticeEnabled && !process.env["AGT_WEDGE_TRANSIENT_NOTICE_ENABLED"]) {
       tmuxSessionEnvArgs.push("-e", "AGT_WEDGE_TRANSIENT_NOTICE_ENABLED=true");
     }
@@ -13708,12 +13662,6 @@ function spawnSession(config, session) {
       // the session env (operator-set OR materialized from the flag above).
       forwardNotifyDispatch: !!process.env["AGT_NOTIFY_DISPATCH"] || // feature-gate-allow: registry-flag envVar operator-override precedence, not a new gate
       !!config.notifyDispatchMode && config.notifyDispatchMode !== "off",
-      // ENG-8201: forward AGT_USAGE_LIMIT_REACTIVE_MODE if it will be in the
-      // session env (operator-set OR materialized from the flag above). This
-      // is the ONLY way the flag reaches an isolated agent — the flags-cache
-      // is not in the container's mount set.
-      forwardUsageLimitReactive: !!process.env["AGT_USAGE_LIMIT_REACTIVE_MODE"] || // feature-gate-allow: registry-flag envVar operator-override precedence, not a new gate
-      !!config.usageLimitReactiveMode && config.usageLimitReactiveMode !== "off",
       // ENG-8269: forward AGT_WEDGE_TRANSIENT_NOTICE_ENABLED if it will be in
       // the session env (operator-set OR materialized from the flag above).
       // Without this the tmux-level materialization above stops at the
@@ -14409,10 +14357,6 @@ export {
   sumTranscriptUsageInWindow,
   isEmptyTotals,
   attributeTranscriptUsageByRun,
-  USAGE_LIMIT_MARKER_FILENAME,
-  serializeUsageLimitMarker,
-  parseUsageLimitMarker,
-  resolveUsageLimitUntil,
   UNKNOWN_RATE_LIMIT,
   pickNewerClassification,
   classifyTranscriptRateLimit,
@@ -14500,4 +14444,4 @@ export {
   stopAllSessionsAndWait,
   getProjectDir
 };
-//# sourceMappingURL=chunk-YR6ESOCM.js.map
+//# sourceMappingURL=chunk-Q6RVMDAC.js.map