@canonry/canonry 7.32.0 → 7.44.0

package/dist/{chunk-QFXD7GR5.js → chunk-5LY7EG4U.js}

@@ -1,11 +1,14 @@
+import {
+  PACKAGE_VERSION,
+  canonryMcpTools,
+  toolOperationAccess
+} from "./chunk-MPWBFKGK.js";
 import {
   CliError,
   EXIT_SYSTEM_ERROR,
   EXIT_USER_ERROR,
-  PACKAGE_VERSION,
-  canonryMcpTools,
   isMachineFormat
-} from "./chunk-ZIETXJYU.js";
+} from "./chunk-HGMYEDAQ.js";
 import {
   AGENT_PROVIDER_IDS,
   CANONRY_NPM_PACKAGE_URL,
@@ -13,8 +16,11 @@ import {
   DEFAULT_VIEWER_RESEARCH_DAILY_RUN_LIMIT,
   OPERATIONAL_LOG_FIELDS_HEADER,
   OPERATIONAL_LOG_OPT_IN_CONTEXT_FIELDS,
+  OPERATION_ACCESS_HEADER,
+  OperationAccesses,
   RESEARCH_RUN_SCOPE,
   SKILL_MANIFEST_FILENAME,
+  STORED_ONLY_HEADER,
   SkillsClients,
   USAGE_TELEMETRY_HEADERS,
   agentPluginClientLabel,
@@ -31,8 +37,10 @@ import {
   isRetiredAgentProviderId,
   isSensitiveDiagnosticQueryKey,
   isStrictSemver,
+  matchOperationTemplate,
   normalizeAgentSlug,
   normalizeTelemetryStatus,
+  operationAccess,
   operationalLogListReadSchema,
   providerBatchConfigSchema,
   providerPricingSchema,
@@ -49,7 +57,7 @@ import {
   skillsClientSchema,
   upgradeCaveatFor,
   upgradeCommandFor
-} from "./chunk-42XUY243.js";
+} from "./chunk-GZ2KIONF.js";
 
 // src/config.ts
 import fs from "fs";
@@ -1505,6 +1513,22 @@ var getApiV1ProjectsByName = (options) => {
     ...options
   });
 };
+var patchApiV1ProjectsByName = (options) => {
+  return (options.client ?? client).patch({
+    security: [
+      {
+        scheme: "bearer",
+        type: "http"
+      }
+    ],
+    url: "/api/v1/projects/{name}",
+    ...options,
+    headers: {
+      "Content-Type": "application/json",
+      ...options.headers
+    }
+  });
+};
 var putApiV1ProjectsByName = (options) => {
   return (options.client ?? client).put({
     security: [
@@ -2949,6 +2973,34 @@ var getApiV1ProjectsByNameAnalyticsCompetitors = (options) => {
     ...options
   });
 };
+var getApiV1ProjectsByNameCompetitorSuggestions = (options) => {
+  return (options.client ?? client).get({
+    security: [
+      {
+        scheme: "bearer",
+        type: "http"
+      }
+    ],
+    url: "/api/v1/projects/{name}/competitor-suggestions",
+    ...options
+  });
+};
+var postApiV1ProjectsByNameCompetitorChangesPreview = (options) => {
+  return (options.client ?? client).post({
+    security: [
+      {
+        scheme: "bearer",
+        type: "http"
+      }
+    ],
+    url: "/api/v1/projects/{name}/competitor-changes/preview",
+    ...options,
+    headers: {
+      "Content-Type": "application/json",
+      ...options.headers
+    }
+  });
+};
 var getApiV1ProjectsByNameRuns = (options) => {
   return (options.client ?? client).get({
     security: [
@@ -3057,6 +3109,22 @@ var postApiV1Apply = (options) => {
     }
   });
 };
+var postApiV1ApplyPreview = (options) => {
+  return (options.client ?? client).post({
+    security: [
+      {
+        scheme: "bearer",
+        type: "http"
+      }
+    ],
+    url: "/api/v1/apply/preview",
+    ...options,
+    headers: {
+      "Content-Type": "application/json",
+      ...options.headers
+    }
+  });
+};
 var getApiV1ProjectsByNameHistory = (options) => {
   return (options.client ?? client).get({
     security: [
@@ -5245,6 +5313,18 @@ var getApiV1ProjectsByNameGaProperties = (options) => {
     ...options
   });
 };
+var getApiV1ProjectsByNameGaAcquisition = (options) => {
+  return (options.client ?? client).get({
+    security: [
+      {
+        scheme: "bearer",
+        type: "http"
+      }
+    ],
+    url: "/api/v1/projects/{name}/ga/acquisition",
+    ...options
+  });
+};
 var getApiV1ProjectsByNameGaMeasurementAnalysis = (options) => {
   return (options.client ?? client).get({
     security: [
@@ -5629,6 +5709,18 @@ var getApiV1Doctor = (options) => {
     ...options
   });
 };
+var getApiV1Status = (options) => {
+  return (options?.client ?? client).get({
+    security: [
+      {
+        scheme: "bearer",
+        type: "http"
+      }
+    ],
+    url: "/api/v1/status",
+    ...options
+  });
+};
 var getApiV1ProjectsByNameDoctor = (options) => {
   return (options.client ?? client).get({
     security: [
@@ -5977,6 +6069,18 @@ var getApiV1ProjectsByNameTrafficReferralAssessment = (options) => {
     ...options
   });
 };
+var getApiV1ProjectsByNameTrafficSamples = (options) => {
+  return (options.client ?? client).get({
+    security: [
+      {
+        scheme: "bearer",
+        type: "http"
+      }
+    ],
+    url: "/api/v1/projects/{name}/traffic/samples",
+    ...options
+  });
+};
 var getApiV1ProjectsByNameTrafficEvents = (options) => {
   return (options.client ?? client).get({
     security: [
@@ -6153,6 +6257,30 @@ var getApiV1ProjectsByNameTechnicalAeoChanges = (options) => {
     ...options
   });
 };
+var getApiV1ProjectsByNameTechnicalAeoIssues = (options) => {
+  return (options.client ?? client).get({
+    security: [
+      {
+        scheme: "bearer",
+        type: "http"
+      }
+    ],
+    url: "/api/v1/projects/{name}/technical-aeo/issues",
+    ...options
+  });
+};
+var getApiV1ProjectsByNameTechnicalAeoIssuesByIssueIdPages = (options) => {
+  return (options.client ?? client).get({
+    security: [
+      {
+        scheme: "bearer",
+        type: "http"
+      }
+    ],
+    url: "/api/v1/projects/{name}/technical-aeo/issues/{issueId}/pages",
+    ...options
+  });
+};
 var getApiV1ProjectsByNameTechnicalAeoCrawlPagesAudit = (options) => {
   return (options.client ?? client).get({
     security: [
@@ -6477,6 +6605,30 @@ function runWithUsageTags(client2, tags, fn) {
   if (!(client2 instanceof ApiClient)) return fn();
   return usageTagStore.run(tags, fn);
 }
+function classifyStoredOnlyRequest(method, url) {
+  const operation = matchOperationTemplate(method, url);
+  const separator = operation.indexOf(" ");
+  return {
+    operation,
+    access: operationAccess(operation.slice(0, separator), operation.slice(separator + 1), OperationAccesses.live)
+  };
+}
+function storedOnlyRequestHeaders(method, url) {
+  if (!["1", "true"].includes((process.env.CANONRY_STORED_ONLY ?? "").toLowerCase())) return {};
+  const { operation, access } = classifyStoredOnlyRequest(method, url);
+  if (access !== OperationAccesses.stored) {
+    throw new CliError({
+      code: "STORED_ONLY_REFUSED",
+      message: `Stored-only mode refuses ${access} operation ${operation}`,
+      details: { operation, access },
+      exitCode: EXIT_USER_ERROR
+    });
+  }
+  return { [STORED_ONLY_HEADER]: "1" };
+}
+function storedOnlyProbeHeaders() {
+  return ["1", "true"].includes((process.env.CANONRY_STORED_ONLY ?? "").toLowerCase()) ? { [STORED_ONLY_HEADER]: "1" } : {};
+}
 var SAFE_CLIENT_NAME = /^\w[\w./-]{0,127}$/;
 var SAFE_ACTOR_SESSION = /^\w[\w.:-]{0,127}$/;
 function safeClientName(value) {
@@ -6548,6 +6700,7 @@ var ApiClient = class {
     };
     this.heyClient = createClient2({ baseUrl: this.originUrl, apiKey: this.apiKey, headers: this.requestHeaders });
     this.heyClient.interceptors.request.use((request) => {
+      for (const [key, value] of Object.entries(storedOnlyRequestHeaders(request.method, request.url.toString()))) request.headers.set(key, value);
       const tags = usageTagStore.getStore();
       if (tags?.mcpTool) request.headers.set(USAGE_TELEMETRY_HEADERS.mcpTool, tags.mcpTool);
       if (tags?.mcpCall) request.headers.set(USAGE_TELEMETRY_HEADERS.mcpCall, tags.mcpCall);
@@ -6569,6 +6722,7 @@ var ApiClient = class {
         try {
           const origin = new URL(this.originUrl).origin;
           const res = await fetch(`${origin}/health`, {
+            headers: storedOnlyProbeHeaders(),
             signal: AbortSignal.timeout(2e3)
           });
           if (res.ok) {
@@ -6626,7 +6780,7 @@ var ApiClient = class {
     if (traceEnabled) {
       const durMs = Date.now() - traceStart;
       process.stderr.write(
-        `[trace] ${result.request.method} ${redactRequestTarget(result.request.url)} \u2192 ${result.response.status} (${durMs}ms)
+        `[trace] ${result.request.method} ${redactRequestTarget(result.request.url)} \u2192 ${result.response.status} (${durMs}ms) access=${result.response.headers.get(OPERATION_ACCESS_HEADER) ?? "unknown"}
 `
       );
     }
@@ -6729,10 +6883,13 @@ var ApiClient = class {
    * and releases the response when done.
    */
   async streamPost(path3, body, signal) {
+    const candidateUrl = `${this.originUrl}/api/v1${path3}`;
+    const storedOnlyHeaders = storedOnlyRequestHeaders("POST", candidateUrl);
     await this.probeBasePath();
     const url = `${this.originUrl}/api/v1${path3}`;
     const headers = {
       ...this.requestHeaders,
+      ...storedOnlyHeaders,
       "Content-Type": "application/json",
       Accept: "text/event-stream"
     };
@@ -6772,6 +6929,11 @@ var ApiClient = class {
       () => putApiV1ProjectsByName({ client: this.heyClient, path: { name }, body })
     );
   }
+  async patchProject(name, body) {
+    return this.invoke(
+      () => patchApiV1ProjectsByName({ client: this.heyClient, path: { name }, body })
+    );
+  }
   async listProjects() {
     return this.invoke(() => getApiV1Projects({ client: this.heyClient }));
   }
@@ -6786,19 +6948,26 @@ var ApiClient = class {
       () => getApiV1ProjectsByNameDeletePreview({ client: this.heyClient, path: { name } })
     );
   }
-  async getStatus(project) {
+  async getStatus(opts) {
     return this.invoke(
-      () => getApiV1ProjectsByName({ client: this.heyClient, path: { name: project } })
+      () => getApiV1Status({ client: this.heyClient, query: { project: opts?.project, problems: opts?.problems } })
     );
   }
-  async getExport(project) {
+  async getExport(project, opts) {
     return this.invoke(
-      () => getApiV1ProjectsByNameExport({ client: this.heyClient, path: { name: project } })
+      () => getApiV1ProjectsByNameExport({
+        client: this.heyClient,
+        path: { name: project },
+        query: { includeSecrets: opts?.includeSecrets }
+      })
     );
   }
   async apply(config) {
     return this.invoke(() => postApiV1Apply({ client: this.heyClient, body: config }));
   }
+  async previewApply(config) {
+    return this.invoke(() => postApiV1ApplyPreview({ client: this.heyClient, body: config }));
+  }
   async getProjectOverview(project, opts) {
     return this.invoke(
       () => getApiV1ProjectsByNameOverview({
@@ -6834,10 +7003,11 @@ var ApiClient = class {
     if (opts.until) params.set("until", opts.until);
     if (opts.includeProbes) params.set("includeProbes", "true");
     const url = `${this.originUrl}/api/v1/projects/${encodeURIComponent(project)}/results/export?${params.toString()}`;
+    const storedOnlyHeaders = storedOnlyRequestHeaders("GET", url);
     let res;
     try {
       res = await fetch(url, {
-        headers: { ...this.requestHeaders }
+        headers: { ...this.requestHeaders, ...storedOnlyHeaders }
       });
     } catch (err) {
       const message = describeError(err);
@@ -6941,13 +7111,27 @@ var ApiClient = class {
       () => getApiV1ProjectsByNameCompetitors({ client: this.heyClient, path: { name: project } })
     );
   }
+  async suggestCompetitors(project, query = {}) {
+    return this.invoke(
+      () => getApiV1ProjectsByNameCompetitorSuggestions({
+        client: this.heyClient,
+        path: { name: project },
+        query
+      })
+    );
+  }
+  async previewCompetitorChange(project, request) {
+    return this.invoke(
+      () => postApiV1ProjectsByNameCompetitorChangesPreview({ client: this.heyClient, path: { name: project }, body: request })
+    );
+  }
   /** Each entry is a domain or `{ domain, aliases }`; stated aliases are added to that competitor's list. */
-  async appendCompetitors(project, competitors) {
+  async appendCompetitors(project, competitors, options) {
     return this.invoke(
       () => postApiV1ProjectsByNameCompetitors({
         client: this.heyClient,
         path: { name: project },
-        body: { competitors }
+        body: { competitors, ...options?.acknowledgeBulkAdd !== void 0 ? { acknowledgeBulkAdd: options.acknowledgeBulkAdd } : {} }
       })
     );
   }
@@ -7519,13 +7703,13 @@ var ApiClient = class {
       })
     );
   }
-  async listRuns(project, limit, kind, status, excludeKind, excludeKinds) {
+  async listRuns(project, limit, kind, status, excludeKind, excludeKinds, since) {
     return this.invoke(
       () => getApiV1ProjectsByNameRuns({
         client: this.heyClient,
         path: { name: project },
         // Filters arrive as free CLI strings; the server validates them against the enums.
-        query: { limit, kind, status, excludeKind, excludeKinds }
+        query: { limit, kind, status, excludeKind, excludeKinds, since }
       })
     );
   }
@@ -7641,6 +7825,7 @@ var ApiClient = class {
    * never run the CLI about a newer release.
    */
   async getServerUpdateAvailable() {
+    if (storedOnlyProbeHeaders()[STORED_ONLY_HEADER]) return null;
     try {
       await this.probeBasePath();
       const res = await fetch(`${this.originUrl}/health`, { signal: AbortSignal.timeout(2e3) });
@@ -8653,6 +8838,9 @@ var ApiClient = class {
       () => getApiV1ProjectsByNameGaProperties({ client: this.heyClient, path: { name: project } })
     );
   }
+  async gaAcquisition(project, query) {
+    return this.invoke(() => getApiV1ProjectsByNameGaAcquisition({ client: this.heyClient, path: { name: project }, query }));
+  }
   async gaMeasurementAnalysis(project, params) {
     return this.invoke(
       () => getApiV1ProjectsByNameGaMeasurementAnalysis({
@@ -8852,6 +9040,9 @@ var ApiClient = class {
       query
     }));
   }
+  async trafficListSamples(project, query) {
+    return this.invoke(() => getApiV1ProjectsByNameTrafficSamples({ client: this.heyClient, path: { name: project }, query }));
+  }
   async trafficListEvents(project, params) {
     return this.invoke(
       () => getApiV1ProjectsByNameTrafficEvents({
@@ -9048,6 +9239,26 @@ var ApiClient = class {
       })
     );
   }
+  /** Stored findings across audited pages, including score-independent duplicate groups. */
+  async getSiteAuditIssues(project, opts) {
+    return this.invoke(
+      () => getApiV1ProjectsByNameTechnicalAeoIssues({
+        client: this.heyClient,
+        path: { name: project },
+        query: { runId: opts?.runId, cursor: opts?.cursor, limit: opts?.limit }
+      })
+    );
+  }
+  /** Page evidence for one stored audit issue; continuation stays pinned to its crawl. */
+  async getSiteAuditIssuePages(project, issueId, opts) {
+    return this.invoke(
+      () => getApiV1ProjectsByNameTechnicalAeoIssuesByIssueIdPages({
+        client: this.heyClient,
+        path: { name: project, issueId },
+        query: { runId: opts?.runId, cursor: opts?.cursor, limit: opts?.limit }
+      })
+    );
+  }
   /** Bounded semantic Site Health neighborhood; this never returns visualization layout. */
   async getSiteHealthSubgraph(project, opts) {
     return this.invoke(
@@ -9884,6 +10095,7 @@ var DynamicToolCatalog = class {
       eager: this.eager,
       loadedToolkits: [...this.loaded].sort(),
       coreTools: this.entries.filter((entry) => entry.tool.tier === "core").map((entry) => entry.tool.name),
+      liveTools: this.entries.filter((entry) => entry.tool.tier === "core" && toolOperationAccess(entry.tool) === OperationAccesses.live).map((entry) => entry.tool.name),
       toolkits: CANONRY_MCP_TOOLKITS.map((toolkit) => this.toolkitEntry(toolkit)).filter((entry) => entry.toolCount > 0),
       usage: this.eager ? "All tools available on this connection are already loaded. Use their listed schemas; tool visibility does not grant server permissions." : "Call canonry_load_toolkit with one of the toolkit names listed in `toolkits[].name` to register its tools for the rest of this session. Wait for its response before calling any newly enabled tool."
     };
@@ -9897,6 +10109,7 @@ var DynamicToolCatalog = class {
       whenToLoad: toolkit.whenToLoad,
       toolCount: tools.length,
       tools,
+      liveTools: this.entries.filter((entry) => entry.tool.tier === toolkit.name && toolOperationAccess(entry.tool) === OperationAccesses.live).map((entry) => entry.tool.name),
       loaded: this.loaded.has(toolkit.name)
     };
   }
@@ -9929,7 +10142,7 @@ var OPERATIONS_GUIDE = {
   "guideVersion": "v1",
   "operationsGuideUrl": "https://github.com/Canonry/canonry/blob/main/docs/agent-operations/v1.md",
   "resourceUri": "canonry://agent-operations/v1",
-  "initialize": 'Canonry tracks how AI answer engines mention brands and cite domains.\nStart with canonry_help({intent:"status"}), or name your intended workflow. It returns a small route of currently available tools and approval boundaries. Follow its stored-evidence reads before proposing action. No skill, resource reader, plugin installation, or local CLI is required for connected MCP clients. A host-native Canonry skill, if installed, is optional additional guidance.\nmentioned = brand in answer TEXT; cited = domain in SOURCE links. Never compute one from the other. A null answerMentioned means not checked, not false. No recorded sweep means no measured figure.\nGet explicit approval for live provider reads, sweeps, probes, research, syncs, and writes, bounded to the target and requested work. A readOnlyHint or GET is not proof of a free operation. Live ads reads include canonry_ads_account, canonry_ads_geo_search, canonry_ads_live_delivery, canonry_ads_conversion_pixels, canonry_ads_conversion_event_settings. Google live reads/syncs include canonry_google_ads_customers, canonry_gtm_accounts, canonry_gtm_containers, canonry_gtm_workspaces, canonry_google_ads_sync, canonry_gtm_sync.\nHelp and skills grant no permissions. The server enforces authority. On missing tools or 403, report the boundary; do not switch credentials or endpoints to bypass it. Hosted catalogs are fixed; only use canonry_load_toolkit when help explicitly offers it.\nIf you uncover a Canonry struggle (failure, confusing output, workaround) or a concrete improvement, tell the user and send it once with canonry_feedback. No secrets or customer data.\n',
+  "initialize": 'Canonry tracks how AI answer engines mention brands and cite domains. Start with canonry_help({intent:"status"}) or a workflow; follow its stored reads and approval boundaries. Connected MCP clients need no skill, resource, plugin, or local CLI. The Canonry skill offers optional additional guidance.\nmentioned = brand in answer TEXT; cited = domain in SOURCE links. Never compute one from the other. A null answerMentioned means not checked, not false. No recorded sweep means no measured figure.\nGet approval for live provider reads, sweeps, probes, research, syncs and writes, scoped to the exact target, action and work. A GET or readOnlyHint does not mean free. canonry_help returns all liveTools for this connection; each needs approval, including read-only tools.\nREST exposes x-canonry-access; CLI help/catalog expose access; MCP help lists liveTools.\nStored-only: CLI --stored-only or CANONRY_STORED_ONLY=1; MCP --stored-only, --scope=stored-only or CANONRY_MCP_SCOPE=stored-only. It refuses live/write work (including doctor) before execution and suppresses housekeeping. CLI refusal is STORED_ONLY_REFUSED. Explicit exports may write files; server accounting remains separate from business mutations.\nHelp and skills grant no permissions; the server enforces authority. Report missing tools or 403; never bypass them with other credentials or endpoints. Hosted catalogs are fixed; use canonry_load_toolkit only when help offers it.\nReport concrete Canonry failures, confusing output, workarounds or improvements to the user and once via canonry_feedback. Exclude secrets and customer data.\n',
   "approvalBoundary": [
     "provider reads",
     "sweeps",
@@ -9962,10 +10175,11 @@ var OPERATIONS_GUIDE = {
         "health"
       ],
       "next": [
+        "canonry_status",
         "canonry_projects_list",
         "canonry_project_overview"
       ],
-      "guidance": "Select an accessible project, then read its stored overview. Report freshness and missing evidence; do not start a sweep to fill a gap."
+      "guidance": "Read canonry_status first for stored integration health, freshness, and repeated failures across accessible projects, then inspect a project overview for detail. Report missing evidence; do not start a sweep or sync to fill a gap."
     },
     "diagnose": {
       "keywords": [
@@ -10030,12 +10244,13 @@ var OPERATIONS_GUIDE = {
         "gtm"
       ],
       "next": [
+        "canonry_status",
         "canonry_projects_list",
         "canonry_project_get",
         "canonry_ga_status",
         "canonry_google_ads_status"
       ],
-      "guidance": "Inspect stored connection status and snapshot freshness. Use the currently listed specialist tools for stored evidence. Connecting, selecting resources, syncing, and live provider reads require scoped approval; never request credentials in chat."
+      "guidance": "Read canonry_status first for the stored instance or project health view, then use specialist tools for detail. Connecting, selecting resources, syncing, and live provider reads require scoped approval; never request credentials in chat."
     },
     "reports": {
       "keywords": [
@@ -10052,7 +10267,7 @@ var OPERATIONS_GUIDE = {
       "guidance": "Build the requested summary from stored project overview, organic evidence, and the relevant visibility, measurement, integration, or traffic reads. Retain evidence dates, scope, sample sizes, missing data, and separate mention/citation signals; do not generate fresh runs implicitly."
     }
   },
-  "markdown": "# Canonry Operations Guide v1\n\nCanonry is an agent-first AI visibility platform. MCP is the universal entry\npoint for connected agents. Host-native skills are optional upgrades, not a\nprerequisite or a permission mechanism.\n\n## Connect and choose a route\n\nRead the initialization guidance, then call `canonry_help` with an `intent`:\n`status`, `diagnose`, `operations`, `prospecting`, `measurement`, `integrations`,\n`reports`, or a short task\ndescription. Select an accessible project with `canonry_projects_list` before\nusing its exact name in project tools. Inspect each listed tool's input schema;\nhelp suggests tool names, not invented arguments or authorization.\n\nHelp returns a versioned, compact route: connection `mode`, available `next`\ntools, workflow guidance, approval boundaries, and this guide's URL. It performs\nno provider calls, reads no project data, and changes no permissions.\n`next` lists stored reads. Optional `actions` lists loaded tools for work that\nrequires approval; listing an action does not authorize or execute it.\n`includeCatalog: true` additionally returns toolkit details when needed.\n\nHosted connections use a fixed catalog. Help only suggests tools offered by that\nconnection; it never tells a hosted agent to dynamically load a toolkit. A\nprogressive local stdio connection may return `loadToolkits`: call\n`canonry_load_toolkit` with one returned name, await it, then call help again.\nLoading only changes local tool discovery, never server authority.\n\nThe optional `canonry://agent-operations/v1` MCP resource contains this same\nguide. If the host cannot read resources or open links, continue through help.\nDo not install a plugin, local runtime, or skill merely to use connected MCP.\nAn installed Codex or Claude Canonry skill contains a generated copy of this\nguide plus links to host-native references. It does not replace runtime help.\n\n## Vocabulary and evidence\n\n- **Mentioned** means the brand appears in answer text. **Cited** means its\n  domain appears in source links. Either, both, or neither can occur; never\n  compute one signal from the other.\n- `answerMentioned: null` means not checked, not false. Missing runs and empty\n  populations mean no measurement, not zero visibility.\n- Preserve project, time window, provider, requested/served model, location,\n  sample size, and query class when comparing evidence. Use server-returned\n  metrics; do not invent a score from incompatible populations.\n- Simple projects and Advanced portfolios share the workflow. For Advanced\n  results, preserve Property, Target, market, plan revision, and class scope.\n  Groups organize navigation; do not infer an unrequested fan-out.\n- Research is isolated evidence, not tracked measurement. A probe still spends\n  quota and persists evidence but is excluded from normal tracking metrics.\n\n## Workflows\n\n**Status:** read the stored overview and freshness first. Say when evidence is\nmissing instead of silently creating it.\n\n**Setup:** Page Health needs no answer-engine provider; AI Visibility does.\nAfter a Page Health result on an install with no provider (a `NO_PROVIDER`\nnotice, or doctor's `providers.none-configured`), propose AI Visibility setup\nas the next step. The operator adds the provider key in the dashboard or in\ntheir own terminal; never ask for it in chat.\nRerunning `canonry bootstrap` after a provider change reloads saved provider\nsettings on a matching running local server and reports whether they became\nactive. If the server is offline, start it to apply the saved settings. For an\nexplicit reload of the connected server's own config, use\n`canonry settings reload-providers` or `canonry_providers_reload` with install\nadministrator authority. Remote servers are never reloaded automatically by\nbootstrap, and a local server that belongs to another install is left alone.\nPorts and database settings still need a restart.\n\n**Diagnose:** inspect stored history and comparable evidence. Explain what\nchanged separately from why it might have changed. A hypothesis is not a\nmeasured cause. Propose bounded verification if stored evidence is insufficient.\n\n**Prospecting:** generate a one-shot company snapshot without creating a project.\nInspect stored provider settings first. Agree on the company, domain, selected\nproviders, and queries before starting the quota-spending snapshot action.\nBrowser-only selection requires manual queries. Progressive stdio help offers\nthe discovery toolkit when this connection permits snapshots; load it, then\ncall help again. Fixed catalogs offer only already available actions. Read-only\nand restricted connections must not bypass missing snapshot access.\n\n**Measurement:** inspect the existing setup and results before proposing edits.\nKeep research, query tracking, plan publication, and sweep execution separate.\nFor direct research, submit the final editable query text in one context. For a\nreviewed batch, submit each explicit destination with its final text and one\nidempotency key. Pattern substitution happens in the client before either\nrequest; choosing a market or Property records a destination only and never\nrewrites a query or creates an automatic fan-out. `research.run` does not\nauthorize saving patterns, changing tracking, publishing plans, or settings.\nUse a supported preview where available, inspect its exact destination and\nrevision, then seek approval for the actual change. A preview may itself require\nwrite permission; never treat a dry-run flag as a universal safety guarantee.\n\n**Integrations:** inspect stored connection state and snapshot freshness first.\nProvider configuration evidence does not prove a browser event fired or a\nconversion was recorded. Connection, resource selection, refresh/sync, and live\nreads are separate actions. Credentials belong in the operator's secure setup\nflow, never in chat, tool arguments, reports, or public guidance.\n\n**Reports:** use saved evidence for the requested period and scope. Keep mention\nand citation signals separate, include dates and sample sizes, and state missing\nor stale inputs. For Advanced Property mention rankings, use\n`canonry_measurement_portfolio_summary` and its `mentionRanking.strongest`,\n`.weakest`, and `.excluded` lists. It defaults to non-brand questions; state the\nreturned class and report branded results separately. An unavailable portfolio\naggregate does not invalidate available Property mention rates. Flag excluded\nProperties individually; do not silently replace mention ranking with citation\nranking. Compact `nextCursor` completes only `pageList`; use `list` to enumerate\none ranking, markets, observed names or cited domains, preserving filters.\nFirst-page sibling lists are bounded summaries. Keep sample sizes and ties\nvisible. Preparing a report does not\nauthorize new measurement.\n\n## Authority and approval\n\n### Agent operations\n\nUse `canonry_key_self` (CLI `canonry key whoami --format json`) to inspect the\ncurrent credential's scopes, project boundary, and host-derived `operator`\nauthority without exposing its token. Missing `operator` means unapproved.\n`canonry_settings_get` and\n`canonry_telemetry_get` describe the connected server, not the agent's local\nmachine. Telemetry reports configured preference, effective state, and any\nenvironment override; inspecting status never creates an anonymous identifier.\nAfter approval, `canonry_telemetry_update` changes that preference and\n`canonry_provider_settings_update` changes an already-configured provider's\nmodel/quota. Both require `settings.write`; neither accepts credentials.\nServer telemetry reads and updates additionally require operator authority.\nOrdinary audit-history reads omit internal telemetry events and their state.\n\nOperator authority is deny-by-default and separate from customer admin roles.\nThe deployment owner must approve a dedicated, instance-wide API key's ID in\nthe server environment variable `CANONRY_OPERATOR_KEY_IDS` (comma-separated IDs),\nthen restart the server. Empty/unset approves nobody; wildcards are invalid.\nKeep the bearer private to internal operators; never approve a customer-held or\nshared proxy/bootstrap key. Use `logs.read` for read-only diagnostics, adding\n`settings.write` only when telemetry control is required. Ordinary key creation,\naccount roles, OAuth consent, and caller headers cannot grant operator status.\nRevoking an approved key invalidates it immediately. Host enrollment is a trust\nbootstrap step, intentionally unavailable through customer-facing APIs.\nAPI, CLI, and MCP enforce the same boundary; MCP hides internal tools unless\nthe server confirms operator authority, including in explicit read-only mode.\nProject analytics, research, and normal project permissions are unchanged.\n\n`canonry_logs_list` reads bounded, redacted runtime events from both the\napplication logger and Fastify request/error logging. It requires an\ninstance-wide `logs.read` grant (or wildcard) and a host-approved direct bearer.\nBrowser sessions, OAuth/delegated credentials, customer admins, and project-scoped\nkeys cannot use it, even with a project filter or a matching allowlist ID.\nA `logs.read`-only key is read-only automatically, without a\nsecond `read` marker. Named `*.read` scopes cannot grant mutations; an explicit\nwrite grant is needed and remains subject to its route gates. Returned messages\nare sanitized and bounded; raw request or response bodies, headers, cookies,\nprovider payloads, and stacks are not\npart of the queryable surface. The same secret-redaction policy runs before\nconsole output and storage. Do not deliberately log secrets: redaction is a\ndefense in depth, not permission to put credentials into diagnostic strings.\nOpaque escaped payloads containing secret assignments are omitted when safe\npartial masking cannot be guaranteed; correlate their retained error codes and IDs.\n\nFile-backed hosts retain runtime logs in SQLite across restarts, bounded to\n10,000 events and seven days. In-memory hosts report `retention: \"process\"`.\nFilter by `actor`, `requestId`, `runId`, `projectId`, `module`, `level`, or an\ninclusive `since`/`until` interval. Keep filters unchanged when resuming an\nopaque cursor; retention eviction can invalidate it. Inspect `retentionPolicy`,\n`captureErrors`, `dropped`, `truncated`, and `retention` before drawing\nconclusions. Missing logs are not proof that an action did not happen. Use\n`canonry_project_history` or `canonry_history_global` for persistent audit events;\noffset pages have deterministic ordering but are not snapshots of concurrent writes.\n\nAudit `actor` comes from authenticated identity (`user:<id>` or `api-key:<id>`),\nnot a caller-supplied header. A delegated MCP credential records its originating\nuser as actor and the actual credential in `credentialId`. `requestId` correlates\nHTTP events; `userAgent` and `actorSession` are bounded, untrusted client hints,\nnever identity or permission grants. Older audit rows are not backfilled with\nidentities the server cannot prove.\n\nBoth shipped HTTP hosts issue restart-safe UUID request IDs and return them in\n`x-request-id`. Use that value to correlate a CLI/API failure with log entries;\nHTTP diagnostics retain the method and route template, not raw URL parameters.\nRequest-bound loggers retain completion attribution, while generic background\ncontinuations stop inheriting caller identity after the response completes.\nCapture covers the owning server process after initialization, not arbitrary\nconsole output, other worker processes, or host/container logs. Run one server\ninstance per process and database, as required by the single-tenant deployment\nmodel; this is not a cross-tenant or distributed log collector.\n\nFor CLI use, settings reads are remote. Google setup and telemetry retain their\nlocal defaults: pass `--target server` explicitly to configure the connected\nserver. `schedule list <project>` lists all schedule kinds, and\n`notify events --target server` discovers the server's event catalog.\n\nMCP returns legacy text JSON plus structured results. Objects keep their shape;\narrays use `{items: [...]}` in `structuredContent`, and scalars use `{value: ...}`.\nErrors preserve the existing envelope and CLI exit codes: HTTP 4xx (including\n429 policy limits) use exit 1; HTTP 5xx use exit 2. Server-provided `Retry-After`\nand request IDs are exposed as `retryAfterMs` and `requestId` when available;\nclients do not infer retryability from HTTP 429 or retry automatically.\nFor a write with an ambiguous outcome, inspect saved state or its receipt before\nretrying; a retry hint is not proof that repeating a write is safe.\n\n### Action boundaries\n\nStart with stored evidence. Before a live provider read, sweep, probe, research\nrun, sync, write, or externally visible action, obtain approval covering its\nexact target, action, and bounded work. Approval already given for that exact\noperation need not be asked for again, but does not extend to more projects,\nlarger batches, retries with new identities, or recurring work.\n\nHTTP GET and MCP `readOnlyHint` describe aspects of an operation, not its cost\nor permission. Provider discovery, account reads, and live diagnostics may\nconsume quota even when labeled read-only. If the tool's effect is unclear,\ninspect its description and request direction before calling it.\n\nAuthentication, role/scope checks, project restrictions, quotas, and guarded\napproval receipts are enforced by the server. Help, skills, resources, and tool\nvisibility cannot grant authority. Never change credentials, endpoints, or\nproject identifiers to work around a missing tool or a `403` response.\n\nFor guarded ads writes, inspect unresolved operation receipts before retrying.\nUse the receipt's supported recovery action; do not replay a mutation under a\nnew identity. An executor cannot create or widen its own human approval grant.\nOn ambiguous results, exhausted bounds, or refusal, stop and report what is\nknown and what permission or operator action is needed.\n\n## Version and source\n\nThis public, versioned document is the source for initialization guidance,\nintent routes, the optional resource, and generated Canonry `SKILL.md` files.\nGuide v1 may receive compatible clarifications; incompatible routing contracts\nrequire a new guide version. The running server's help describes its actual\ncatalog and remains usable without fetching this document.\n"
+  "markdown": "# Canonry Operations Guide v1\n\nCanonry is an agent-first AI visibility platform. MCP is the universal entry\npoint for connected agents. Host-native skills are optional upgrades, not a\nprerequisite or a permission mechanism.\n\n## Connect and choose a route\n\nRead the initialization guidance, then call `canonry_help` with an `intent`:\n`status`, `diagnose`, `operations`, `prospecting`, `measurement`, `integrations`,\n`reports`, or a short task\ndescription. Select an accessible project with `canonry_projects_list` before\nusing its exact name in project tools. Inspect each listed tool's input schema;\nhelp suggests tool names, not invented arguments or authorization.\n\nHelp returns a versioned, compact route: connection `mode`, available `next`\ntools, workflow guidance, approval boundaries, and this guide's URL. It performs\nno provider calls, reads no project data, and changes no permissions.\n`next` lists stored reads. Optional `actions` lists loaded tools for work that\nrequires approval; listing an action does not authorize or execute it.\n`includeCatalog: true` additionally returns toolkit details when needed.\n\nHosted connections use a fixed catalog. Help only suggests tools offered by that\nconnection; it never tells a hosted agent to dynamically load a toolkit. A\nprogressive local stdio connection may return `loadToolkits`: call\n`canonry_load_toolkit` with one returned name, await it, then call help again.\nLoading only changes local tool discovery, never server authority.\n\nThe optional `canonry://agent-operations/v1` MCP resource contains this same\nguide. If the host cannot read resources or open links, continue through help.\nDo not install a plugin, local runtime, or skill merely to use connected MCP.\nAn installed Codex or Claude Canonry skill contains a generated copy of this\nguide plus links to host-native references. It does not replace runtime help.\n\n## Vocabulary and evidence\n\n- **Mentioned** means the brand appears in answer text. **Cited** means its\n  domain appears in source links. Either, both, or neither can occur; never\n  compute one signal from the other.\n- `answerMentioned: null` means not checked, not false. Missing runs and empty\n  populations mean no measurement, not zero visibility.\n- Preserve project, time window, provider, requested/served model, location,\n  sample size, and query class when comparing evidence. Use server-returned\n  metrics; do not invent a score from incompatible populations.\n- Simple projects and Advanced portfolios share the workflow. For Advanced\n  results, preserve Property, Target, market, plan revision, and class scope.\n  Groups organize navigation; do not infer an unrequested fan-out.\n- Research is isolated evidence, not tracked measurement. A probe still spends\n  quota and persists evidence but is excluded from normal tracking metrics.\n\n## Workflows\n\n**Status:** read the stored overview and freshness first. Say when evidence is\nmissing instead of silently creating it.\n\n**Setup:** Page Health needs no answer-engine provider; AI Visibility does.\nAfter a Page Health result on an install with no provider (a `NO_PROVIDER`\nnotice, or doctor's `providers.none-configured`), propose AI Visibility setup\nas the next step. The operator adds the provider key in the dashboard or in\ntheir own terminal; never ask for it in chat.\nRerunning `canonry bootstrap` after a provider change reloads saved provider\nsettings on a matching running local server and reports whether they became\nactive. If the server is offline, start it to apply the saved settings. For an\nexplicit reload of the connected server's own config, use\n`canonry settings reload-providers` or `canonry_providers_reload` with install\nadministrator authority. Remote servers are never reloaded automatically by\nbootstrap, and a local server that belongs to another install is left alone.\nPorts and database settings still need a restart.\n\n**Diagnose:** inspect stored history and comparable evidence. Explain what\nchanged separately from why it might have changed. A hypothesis is not a\nmeasured cause. Propose bounded verification if stored evidence is insufficient.\n\n**Site Health:** read `canonry_site_health_issues` for stored technical findings,\naffected-page counts and example URLs, then `canonry_site_health_issue_pages`\nfor a selected issue's remaining pages. Pin subsequent reads to the returned\nrun. Inspect coverage and omissions: a passing score can still have findings,\nan older scan may lack cross-page evidence, and a partial scan cannot establish\nsite-wide absence. Advisory findings require judgment before proposing a repair.\nAudit evidence informs technical repairs and existing-page recommendations;\nit does not itself establish a new-blog opportunity or authorize any edit.\n\n**Prospecting:** generate a one-shot company snapshot without creating a project.\nInspect stored provider settings first. Agree on the company, domain, selected\nproviders, and queries before starting the quota-spending snapshot action.\nBrowser-only selection requires manual queries. Progressive stdio help offers\nthe discovery toolkit when this connection permits snapshots; load it, then\ncall help again. Fixed catalogs offer only already available actions. Read-only\nand restricted connections must not bypass missing snapshot access.\n\n**Measurement:** inspect the existing setup and results before proposing edits.\nKeep research, query tracking, plan publication, and sweep execution separate.\nFor direct research, submit the final editable query text in one context. For a\nreviewed batch, submit each explicit destination with its final text and one\nidempotency key. Pattern substitution happens in the client before either\nrequest; choosing a market or Property records a destination only and never\nrewrites a query or creates an automatic fan-out. `research.run` does not\nauthorize saving patterns, changing tracking, publishing plans, or settings.\nUse a supported preview where available, inspect its exact destination and\nrevision, then seek approval for the actual change. A preview may itself require\nwrite permission; never treat a dry-run flag as a universal safety guarantee.\n\n**Integrations:** inspect stored connection state and snapshot freshness first.\nProvider configuration evidence does not prove a browser event fired or a\nconversion was recorded. Connection, resource selection, refresh/sync, and live\nreads are separate actions. Credentials belong in the operator's secure setup\nflow, never in chat, tool arguments, reports, or public guidance.\n\n**Reports:** use saved evidence for the requested period and scope. Keep mention\nand citation signals separate, include dates and sample sizes, and state missing\nor stale inputs. For Advanced Property mention rankings, use\n`canonry_measurement_portfolio_summary` and its `mentionRanking.strongest`,\n`.weakest`, and `.excluded` lists. It defaults to non-brand questions; state the\nreturned class and report branded results separately. An unavailable portfolio\naggregate does not invalidate available Property mention rates. Flag excluded\nProperties individually; do not silently replace mention ranking with citation\nranking. Compact `nextCursor` completes only `pageList`; use `list` to enumerate\none ranking, markets, observed names or cited domains, preserving filters.\nFirst-page sibling lists are bounded summaries. Keep sample sizes and ties\nvisible. Preparing a report does not\nauthorize new measurement.\n\n## Authority and approval\n\n### Agent operations\n\nUse `canonry_key_self` (CLI `canonry key whoami --format json`) to inspect the\ncurrent credential's scopes, project boundary, and host-derived `operator`\nauthority without exposing its token. Missing `operator` means unapproved.\n`canonry_settings_get` and\n`canonry_telemetry_get` describe the connected server, not the agent's local\nmachine. Telemetry reports configured preference, effective state, and any\nenvironment override; inspecting status never creates an anonymous identifier.\nAfter approval, `canonry_telemetry_update` changes that preference and\n`canonry_provider_settings_update` changes an already-configured provider's\nmodel/quota. Both require `settings.write`; neither accepts credentials.\nServer telemetry reads and updates additionally require operator authority.\nOrdinary audit-history reads omit internal telemetry events and their state.\n\nOperator authority is deny-by-default and separate from customer admin roles.\nThe deployment owner must approve a dedicated, instance-wide API key's ID in\nthe server environment variable `CANONRY_OPERATOR_KEY_IDS` (comma-separated IDs),\nthen restart the server. Empty/unset approves nobody; wildcards are invalid.\nKeep the bearer private to internal operators; never approve a customer-held or\nshared proxy/bootstrap key. Use `logs.read` for read-only diagnostics, adding\n`settings.write` only when telemetry control is required. Ordinary key creation,\naccount roles, OAuth consent, and caller headers cannot grant operator status.\nRevoking an approved key invalidates it immediately. Host enrollment is a trust\nbootstrap step, intentionally unavailable through customer-facing APIs.\nAPI, CLI, and MCP enforce the same boundary; MCP hides internal tools unless\nthe server confirms operator authority, including in explicit read-only mode.\nProject analytics, research, and normal project permissions are unchanged.\n\n`canonry_logs_list` reads bounded, redacted runtime events from both the\napplication logger and Fastify request/error logging. It requires an\ninstance-wide `logs.read` grant (or wildcard) and a host-approved direct bearer.\nBrowser sessions, OAuth/delegated credentials, customer admins, and project-scoped\nkeys cannot use it, even with a project filter or a matching allowlist ID.\nA `logs.read`-only key is read-only automatically, without a\nsecond `read` marker. Named `*.read` scopes cannot grant mutations; an explicit\nwrite grant is needed and remains subject to its route gates. Returned messages\nare sanitized and bounded; raw request or response bodies, headers, cookies,\nprovider payloads, and stacks are not\npart of the queryable surface. The same secret-redaction policy runs before\nconsole output and storage. Do not deliberately log secrets: redaction is a\ndefense in depth, not permission to put credentials into diagnostic strings.\nOpaque escaped payloads containing secret assignments are omitted when safe\npartial masking cannot be guaranteed; correlate their retained error codes and IDs.\n\nFile-backed hosts retain runtime logs in SQLite across restarts, bounded to\n10,000 events and seven days. In-memory hosts report `retention: \"process\"`.\nFilter by `actor`, `requestId`, `runId`, `projectId`, `module`, `level`, or an\ninclusive `since`/`until` interval. Keep filters unchanged when resuming an\nopaque cursor; retention eviction can invalidate it. Inspect `retentionPolicy`,\n`captureErrors`, `dropped`, `truncated`, and `retention` before drawing\nconclusions. Missing logs are not proof that an action did not happen. Use\n`canonry_project_history` or `canonry_history_global` for persistent audit events;\noffset pages have deterministic ordering but are not snapshots of concurrent writes.\n\nAudit `actor` comes from authenticated identity (`user:<id>` or `api-key:<id>`),\nnot a caller-supplied header. A delegated MCP credential records its originating\nuser as actor and the actual credential in `credentialId`. `requestId` correlates\nHTTP events; `userAgent` and `actorSession` are bounded, untrusted client hints,\nnever identity or permission grants. Older audit rows are not backfilled with\nidentities the server cannot prove.\n\nBoth shipped HTTP hosts issue restart-safe UUID request IDs and return them in\n`x-request-id`. Use that value to correlate a CLI/API failure with log entries;\nHTTP diagnostics retain the method and route template, not raw URL parameters.\nRequest-bound loggers retain completion attribution, while generic background\ncontinuations stop inheriting caller identity after the response completes.\nCapture covers the owning server process after initialization, not arbitrary\nconsole output, other worker processes, or host/container logs. Run one server\ninstance per process and database, as required by the single-tenant deployment\nmodel; this is not a cross-tenant or distributed log collector.\n\nFor CLI use, settings reads are remote. Google setup and telemetry retain their\nlocal defaults: pass `--target server` explicitly to configure the connected\nserver. `schedule list <project>` lists all schedule kinds, and\n`notify events --target server` discovers the server's event catalog.\n\nMCP returns legacy text JSON plus structured results. Objects keep their shape;\narrays use `{items: [...]}` in `structuredContent`, and scalars use `{value: ...}`.\nErrors preserve the existing envelope and CLI exit codes: HTTP 4xx (including\n429 policy limits) use exit 1; HTTP 5xx use exit 2. Server-provided `Retry-After`\nand request IDs are exposed as `retryAfterMs` and `requestId` when available;\nclients do not infer retryability from HTTP 429 or retry automatically.\nFor a write with an ambiguous outcome, inspect saved state or its receipt before\nretrying; a retry hint is not proof that repeating a write is safe.\n\n### Action boundaries\n\nStart with stored evidence. Before a live provider read, sweep, probe, research\nrun, sync, write, or externally visible action, obtain approval covering its\nexact target, action, and bounded work. Approval already given for that exact\noperation need not be asked for again, but does not extend to more projects,\nlarger batches, retries with new identities, or recurring work.\n\nHTTP GET and MCP `readOnlyHint` describe aspects of an operation, not its cost\nor permission. Provider discovery, account reads, and live diagnostics may\nconsume quota even when labeled read-only. If the tool's effect is unclear,\ninspect its description and request direction before calling it.\n\nAuthentication, role/scope checks, project restrictions, quotas, and guarded\napproval receipts are enforced by the server. Help, skills, resources, and tool\nvisibility cannot grant authority. Never change credentials, endpoints, or\nproject identifiers to work around a missing tool or a `403` response.\n\nFor guarded ads writes, inspect unresolved operation receipts before retrying.\nUse the receipt's supported recovery action; do not replay a mutation under a\nnew identity. An executor cannot create or widen its own human approval grant.\nOn ambiguous results, exhausted bounds, or refusal, stop and report what is\nknown and what permission or operator action is needed.\n\n## Version and source\n\nThis public, versioned document is the source for initialization guidance,\nintent routes, the optional resource, and generated Canonry `SKILL.md` files.\nGuide v1 may receive compatible clarifications; incompatible routing contracts\nrequire a new guide version. The running server's help describes its actual\ncatalog and remains usable without fetching this document.\n"
 };
 
 // src/mcp/operations-guide.ts
@@ -10071,6 +10286,8 @@ function operationsHelp(catalog, mode, intent = "", includeCatalog = false) {
   }
   const wanted = [...reads, ...requestedActions];
   const loadToolkits = mode === "stdio-progressive" ? catalog.toolkits.filter((t) => !t.loaded && t.tools.some((name) => wanted.includes(name))).map((t) => t.name) : [];
+  const liveTools = [...catalog.liveTools];
+  for (const toolkit of catalog.toolkits) liveTools.push(...toolkit.liveTools);
   return {
     guideVersion: OPERATIONS_GUIDE.guideVersion,
     mode,
@@ -10085,7 +10302,8 @@ function operationsHelp(catalog, mode, intent = "", includeCatalog = false) {
     authority: OPERATIONS_GUIDE.authority,
     operationsGuideUrl: OPERATIONS_GUIDE.operationsGuideUrl,
     ...loadToolkits.length ? { loadToolkits } : {},
-    ...includeCatalog ? catalog : {}
+    ...includeCatalog ? catalog : {},
+    liveTools: [...new Set(liveTools)].sort()
   };
 }
 
@@ -10209,7 +10427,7 @@ function getCanonryMcpTools(scope = "all", tiers, credentialScopes, operator = f
   const readOnly = scope === "read-only" || credentialScopes !== void 0 && isReadOnlyKey(credentialScopes);
   const restricted = credentialScopes && restrictedWriteScopes(credentialScopes);
   const authorized = canonryMcpTools.filter((tool) => !tool.requiresOperator || operator);
-  const byScope = readOnly ? authorized.filter((tool) => tool.access === "read") : authorized.filter((tool) => {
+  const byScope = scope === "stored-only" ? authorized.filter((tool) => toolOperationAccess(tool) === OperationAccesses.stored) : readOnly ? authorized.filter((tool) => tool.access === "read") : authorized.filter((tool) => {
     if (!restricted || tool.access === "read") return true;
     if (tool.requiredScope && restricted.includes(tool.requiredScope)) return true;
     return restricted.some((grant) => grant !== RESEARCH_RUN_SCOPE) && tool.tier === "ads";