@zackbart/connecta 0.18.2 → 0.19.0

package/dist/providers/revenuecat.d.ts

@@ -3,15 +3,7 @@ import type { Connector, ConnectorCallAdmissionPolicy } from "../types.js";
 /** RevenueCat publishes one hosted MCP endpoint, streamable HTTP. */
 export declare const REVENUECAT_MCP_ENDPOINT = "https://mcp.revenuecat.ai/mcp";
 export interface RevenueCatOptions {
-    /**
-     * Human-readable display name; defaults to "RevenueCat" for OAuth and
-     * "RevenueCat (single project)" for a static API v2 secret key. The scope
-     * shape rides the title because it is the one routing fact connecta can
-     * know at construction: an `sk_` key reaches exactly one project, an OAuth
-     * session reaches every project the account can. *Which* project a key
-     * reaches is not knowable here (P10 — no credential test), so the guide's
-     * first line carries the operator's stated purpose instead.
-     */
+    /** Display name; scope defaults are in `documentation/revenuecat.md`. */
     title?: string;
     /**
      * Which project this connector is for and what decisions it answers. With
@@ -19,61 +11,16 @@ export interface RevenueCatOptions {
      * so it goes in the guide's first line and its summary.
      */
     purpose: string;
-    /**
-     * OAuth by default; static headers support a RevenueCat API v2 secret key
-     * as `Authorization: Bearer sk_…`. `{ type: "credential" }` is the same
-     * single-project scope with the key pasted at `/credentials` instead — which
-     * is what two projects on two keys wants, since each is its own connector.
-     */
+    /** OAuth or a single-project API v2 key; see `documentation/revenuecat.md`. */
     auth?: RemoteMcpAuth;
     /** Project-specific conventions appended to the maintained provider guide. */
     instructions?: string;
     /** Connector-specific inline result limit; omit to inherit the deployment. */
     maxResultBytes?: number;
-    /**
-     * Optional per-runtime call-admission policy. Deliberately not defaulted,
-     * even though RevenueCat does publish numbers.
-     *
-     * API v2 meters per *domain*, and the domains disagree by a factor of
-     * nineteen: Customer Information 480/min, Virtual Currencies 480/min,
-     * Subscription Transactions Refunds 480/min, Audiences 60/min, Project
-     * Configuration 60/min, Charts & Metrics 25/min
-     * (https://www.revenuecat.com/docs/api-v2#tag/Rate-Limit, read 2026-08-18).
-     * A `ConnectorCallAdmissionPolicy` carries exactly one rule, so a
-     * connector-wide budget has to pick one of those six numbers for all ninety-
-     * five tools. Transcribing 25 would throttle a customer read loop to a
-     * nineteenth of its documented allowance; transcribing 480 would leave a
-     * chart sweep unprotected. Neither is the provider's limit, and both would
-     * look like RevenueCat being flaky.
-     *
-     * The metering scope says the same thing again: the limit applies per API
-     * key for app-level keys and per *developer* for developer-level keys, so
-     * an OAuth session shares one budget with everything else that developer
-     * does — which a per-runtime counter cannot approximate in either
-     * direction. So the number stays with the operator who knows the account,
-     * exactly as P12 prescribes; `documentation/revenuecat.md` shows how to
-     * supply one.
-     */
+    /** Optional per-runtime policy; see `documentation/revenuecat.md#rate-limits`. */
     callAdmission?: ConnectorCallAdmissionPolicy;
 }
-/**
- * The manifest this release reviewed: both lists in one place, which is what
- * makes the classification the connector applies and the drift check that runs
- * beside it the same fact (P13). Ninety-four of the ninety-five tools
- * RevenueCat's reference lists on 2026-08-18 are classified; the ninety-fifth,
- * `render-paywall-screenshot`, has no access column to classify from and fails
- * closed.
- *
- * No schema digests. No release has read RevenueCat's live schemas and written
- * them down — that needs a live project and a maintainer's own `sk_` key — and
- * an invented digest would report a change that never happened.
- * `npm run drift:check -- --record` reads them from a live catalog and prints
- * the block to paste in
- * ([#351](https://github.com/zackbart/connecta/issues/351)).
- *
- * Exported because the maintainer-run check compares against this manifest and
- * *names* what moved, which the runtime check deliberately cannot.
- */
+/** Release-reviewed manifest; see provider conventions P5 and P13. */
 export declare const REVENUECAT_VETTED_CATALOG: import("../catalog-drift.js").VettedCatalog;
 /** A maintained RevenueCat hosted-MCP connection. */
 export declare function revenuecat(id: string, options: RevenueCatOptions): Connector;

package/dist/providers/revenuecat.js

@@ -1,16 +1,9 @@
 import { remoteMcp, withCredentialDefaults, } from "../connectors/remote-mcp.js";
 import { vettedCatalog, withVettedCatalog } from "../catalog-drift.js";
+import { defined } from "../connectors/api.js";
 /** RevenueCat publishes one hosted MCP endpoint, streamable HTTP. */
 export const REVENUECAT_MCP_ENDPOINT = "https://mcp.revenuecat.ai/mcp";
-/**
- * Tools whose official contract is observational rather than mutating.
- *
- * Every name here carries `Read` in RevenueCat's own tool reference
- * (https://www.revenuecat.com/docs/tools/mcp/tools-reference, read
- * 2026-08-18). The list is a superset by design (P5): a name a project never
- * serves costs nothing, while an unclassified new one fails closed onto
- * `call_destructive_tool`.
- */
+/** Reviewed reads; see `documentation/revenuecat.md` and convention P5. */
 const READ_ONLY_TOOLS = new Set([
     // Projects and apps
     "get-account-billing",
@@ -76,65 +69,26 @@ const READ_ONLY_TOOLS = new Set([
     // *start* one are writes and sit below.
     "get-paywall-ai-task",
 ]);
-/**
- * The maintained write catalog. `"destructive"` tools modify or remove state
- * that already exists; `"additive"` ones only bring something new into being.
- * Both leave the read-only path — the distinction only decides whether the
- * connection asserts `destructiveHint`, which shapes the host's approval copy.
- *
- * Every name here carries `Write` in RevenueCat's tool reference. The mass
- * verdicts follow the verb: `archive-*` and `unarchive-*` flip an existing
- * object's active state, `update-*` and `delete-*` and `publish-*` and
- * `unpublish-*` and `detach-*` change or remove something that already exists,
- * and a plain `create-*` brings a new object into being beside the old ones.
- *
- * Nine verdicts are not decided by the verb, and each is argued where it sits:
- * `create-product-prices`, `equalize-subscription-prices`,
- * `validate-app-credentials`, `upload-product-store-state-screenshot`,
- * `attach-products-to-entitlement`, `attach-products-to-package`,
- * `duplicate-paywall`, `create-paywall-ai`, and `edit-paywall-ai`.
- *
- * `render-paywall-screenshot` is deliberately on neither list. RevenueCat's
- * reference gives it no access column at all, and a tool nobody has classified
- * fails closed (P5) rather than being guessed into the read path because its
- * name sounds harmless.
- */
+/** Reviewed writes and verb exceptions: `documentation/revenuecat.md`. */
 const WRITE_TOOLS = new Map([
     // Projects and apps
     ["create-app", "additive"],
     ["create-project", "additive"],
     ["update-app", "destructive"],
     ["update-project-ui-config", "destructive"],
-    // "Checks one saved App Store or Google Play credential set." RevenueCat
-    // files it Write, so it does not reach the read path — but it leaves the
-    // credentials themselves alone and only records the outcome of a check.
-    // Additive: a verdict comes into being, nothing existing is overwritten.
     ["validate-app-credentials", "additive"],
     // Products and prices
     ["archive-product", "destructive"],
     ["create-product", "additive"],
-    // Named `create-`, described "Configure prices for a product". A product's
-    // price set already exists, and configuring it replaces what is there
-    // rather than adding a second price beside the first. Money-facing and
-    // overwriting, so: destructive, whatever the verb says.
     ["create-product-prices", "destructive"],
-    // "Fills missing App Store subscription territory prices." By RevenueCat's
-    // own word it only writes where a price is absent, so nothing already set
-    // is changed. Additive.
     ["equalize-subscription-prices", "additive"],
     ["set-product-store-state", "destructive"],
     ["submit-products-to-store", "destructive"],
     ["unarchive-product", "destructive"],
     ["update-product", "destructive"],
-    // "Reserves an App Store Connect review screenshot slot." A new slot comes
-    // into being; no existing screenshot is replaced by the reservation.
     ["upload-product-store-state-screenshot", "additive"],
     // Entitlements
     ["archive-entitlement", "destructive"],
-    // Attach adds a product to a membership set and removes nothing;
-    // `detach-products-from-entitlement` is its destructive counterpart. Filing
-    // both destructive would make the pair read identically in the approval copy
-    // a human is shown, which is exactly the inflation P5 warns about.
     ["attach-products-to-entitlement", "additive"],
     ["create-entitlement", "additive"],
     ["detach-products-from-entitlement", "destructive"],
@@ -142,7 +96,6 @@ const WRITE_TOOLS = new Map([
     ["update-entitlement", "destructive"],
     // Offerings and packages
     ["archive-offering", "destructive"],
-    // The same attach/detach argument one level down.
     ["attach-products-to-package", "additive"],
     ["create-offering", "additive"],
     ["create-packages", "additive"],
@@ -154,19 +107,10 @@ const WRITE_TOOLS = new Map([
     ["create-audience", "additive"],
     ["update-audience", "destructive"],
     // Paywalls
-    // "Duplicates an existing paywall's current draft." The original is
-    // untouched and a new paywall appears beside it. Additive.
     ["duplicate-paywall", "additive"],
     ["publish-paywall", "destructive"],
     ["unpublish-paywall", "destructive"],
-    // Customers and subscriptions. Neither verb is in the mass rule and neither
-    // removes anything, so the file's own criterion would read them additive.
-    // They are destructive on consequence, the way `create_refund` is in
-    // `stripe.ts`: `assign-customer-offering` overrides which offering a live
-    // customer's app serves, and `grant-customer-entitlement` opens paid access
-    // to a real person without a store purchase (the promotional subscription it
-    // creates is the mechanism, not the point). Both change what a customer
-    // gets today, and both deserve the destructive approval copy.
+    // Customers and subscriptions
     ["assign-customer-offering", "destructive"],
     ["grant-customer-entitlement", "destructive"],
     // Virtual currencies
@@ -175,39 +119,14 @@ const WRITE_TOOLS = new Map([
     ["unarchive-virtual-currency", "destructive"],
     ["update-virtual-currency", "destructive"],
     // Integrations and webhooks
-    // A new integration is a new object, but one that "starts delivering
-    // RevenueCat events to the given url" — with filters omitted, every customer
-    // event in the project, to a URL the caller typed. That is customer data
-    // leaving the account on consequence, which is the `create_refund` argument
-    // again: the verb says additive, the effect says destructive, and the
-    // approval copy should say the latter.
     ["create-webhook-integration", "destructive"],
     ["delete-webhook-integration", "destructive"],
     ["update-webhook-integration", "destructive"],
-    // Paywall editing. Both start an async task; what the task does decides the
-    // verdict. Creating a paywall leaves every existing one alone (additive);
-    // editing one rewrites a draft that already exists (destructive).
+    // Paywall editing
     ["create-paywall-ai", "additive"],
     ["edit-paywall-ai", "destructive"],
 ]);
-/**
- * The manifest this release reviewed: both lists in one place, which is what
- * makes the classification the connector applies and the drift check that runs
- * beside it the same fact (P13). Ninety-four of the ninety-five tools
- * RevenueCat's reference lists on 2026-08-18 are classified; the ninety-fifth,
- * `render-paywall-screenshot`, has no access column to classify from and fails
- * closed.
- *
- * No schema digests. No release has read RevenueCat's live schemas and written
- * them down — that needs a live project and a maintainer's own `sk_` key — and
- * an invented digest would report a change that never happened.
- * `npm run drift:check -- --record` reads them from a live catalog and prints
- * the block to paste in
- * ([#351](https://github.com/zackbart/connecta/issues/351)).
- *
- * Exported because the maintainer-run check compares against this manifest and
- * *names* what moved, which the runtime check deliberately cannot.
- */
+/** Release-reviewed manifest; see provider conventions P5 and P13. */
 export const REVENUECAT_VETTED_CATALOG = vettedCatalog({
     reads: READ_ONLY_TOOLS,
     writes: WRITE_TOOLS,
@@ -312,12 +231,10 @@ export function revenuecat(id, options) {
             // carries the project-resolution sequence, which is worth reading before
             // a run rather than before every call.
         },
-        ...(options.callAdmission !== undefined
-            ? { callAdmission: options.callAdmission }
-            : {}),
-        ...(options.maxResultBytes !== undefined
-            ? { maxResultBytes: options.maxResultBytes }
-            : {}),
+        ...defined({
+            callAdmission: options.callAdmission,
+            maxResultBytes: options.maxResultBytes,
+        }),
     });
     return withVettedCatalog(connector, REVENUECAT_VETTED_CATALOG);
 }

package/dist/providers/stripe.d.ts

@@ -38,18 +38,7 @@ export interface StripeHeaderOptions extends StripeCommonOptions {
     connectedAccount?: string;
 }
 export type StripeOptions = StripeOAuthOptions | StripeHeaderOptions;
-/**
- * The manifest this release reviewed: both lists in one place, which is what
- * makes the classification the connector applies and the drift check that runs
- * beside it the same fact (P13). No schema digests yet — no release has read
- * Stripe's live schemas and written them down, and an invented digest would
- * report a change that never happened. `npm run drift:check -- --record` reads
- * them from a live account and prints the block to paste in
- * ([#351](https://github.com/zackbart/connecta/issues/351)).
- *
- * Exported because the maintainer-run check compares against this manifest and
- * *names* what moved, which the runtime check deliberately cannot.
- */
+/** Release-reviewed manifest; see provider conventions P5 and P13. */
 export declare const STRIPE_VETTED_CATALOG: import("../catalog-drift.js").VettedCatalog;
 /** A maintained Stripe hosted-MCP connection. */
 export declare function stripe(id: string, options: StripeOptions): Connector;

package/dist/providers/stripe.js

@@ -1,17 +1,9 @@
 import { remoteMcp, withCredentialDefaults, } from "../connectors/remote-mcp.js";
 import { vettedCatalog, withVettedCatalog } from "../catalog-drift.js";
+import { defined } from "../connectors/api.js";
 /** Stripe publishes one hosted MCP endpoint for every account and mode. */
 export const STRIPE_MCP_ENDPOINT = "https://mcp.stripe.com/";
-/**
- * Stripe documents no MCP-specific rate limit, so this transcribes the account
- * limit the MCP server spends: 100 requests per second in live mode, 25 in a
- * sandbox (https://docs.stripe.com/rate-limits). The concurrency bound is
- * connecta's own conservative choice — Stripe documents that per-account and
- * per-endpoint concurrency limits exist and surface as `429` with a
- * `Stripe-Rate-Limited-Reason` of `global-concurrency` or
- * `endpoint-concurrency`, but publishes no number. Declaring `maxConcurrency`
- * is also what earns the right to the queue settings beside it.
- */
+/** Account limits and local concurrency rationale: `documentation/stripe.md`. */
 const STRIPE_ADMISSION = {
     production: {
         rules: [
@@ -50,34 +42,14 @@ const READ_ONLY_TOOLS = new Set([
     "search_stripe_documentation",
     "stripe_implementation_planner",
 ]);
-/**
- * The maintained write catalog. `"destructive"` tools modify or remove state
- * that already exists; `"additive"` ones only bring something new into being.
- * Both leave the read-only path — the distinction only decides whether the
- * connection asserts `destructiveHint`, which shapes the host's approval copy.
- *
- * `create_refund` is filed destructive despite its name: it reverses a
- * settled charge and moves money back out, which is a mutation of something
- * that already exists, not a fresh object appearing beside it.
- */
+/** Reviewed writes, including refund rationale: `documentation/stripe.md`. */
 const WRITE_TOOLS = new Map([
     ["stripe_api_write", "destructive"],
     ["create_refund", "destructive"],
     ["stripe_report", "additive"],
     ["send_stripe_mcp_feedback", "additive"],
 ]);
-/**
- * The manifest this release reviewed: both lists in one place, which is what
- * makes the classification the connector applies and the drift check that runs
- * beside it the same fact (P13). No schema digests yet — no release has read
- * Stripe's live schemas and written them down, and an invented digest would
- * report a change that never happened. `npm run drift:check -- --record` reads
- * them from a live account and prints the block to paste in
- * ([#351](https://github.com/zackbart/connecta/issues/351)).
- *
- * Exported because the maintainer-run check compares against this manifest and
- * *names* what moved, which the runtime check deliberately cannot.
- */
+/** Release-reviewed manifest; see provider conventions P5 and P13. */
 export const STRIPE_VETTED_CATALOG = vettedCatalog({
     reads: READ_ONLY_TOOLS,
     writes: WRITE_TOOLS,
@@ -85,14 +57,7 @@ export const STRIPE_VETTED_CATALOG = vettedCatalog({
 /** Stripe key prefixes carry their own mode; only a clear reading counts. */
 const LIVE_KEY = /\b(?:sk|rk|pk)_live_/;
 const TEST_KEY = /\b(?:sk|rk|pk)_test_/;
-/**
- * Refuse a deployment whose declared mode and supplied key disagree.
- *
- * This is the one half of production/sandbox routing connecta can actually
- * enforce. Nothing here reads or reports key material: an unrecognizable key
- * shape is left alone rather than guessed at, and a mismatch names only the
- * two modes.
- */
+/** Refuse a recognizable key/mode mismatch; see `documentation/stripe.md`. */
 function assertModeMatchesKey(id, mode, auth) {
     if (auth.type !== "headers")
         return;
@@ -139,7 +104,6 @@ function resolveAuth(id, options) {
         headers: { ...auth.headers, "Stripe-Account": connectedAccount },
     };
 }
-const OAUTH_ADMISSION = STRIPE_ADMISSION.sandbox;
 function oauthUsageGuide(purpose, instructions) {
     const accountInstructions = instructions?.trim();
     return `# Stripe usage
@@ -233,7 +197,7 @@ export function stripe(id, options) {
             : `Stripe payments (${copy?.blurb}) — ${purpose}`,
         auth,
         requireHttps: true,
-        callAdmission: mode === undefined ? OAUTH_ADMISSION : STRIPE_ADMISSION[mode],
+        callAdmission: STRIPE_ADMISSION[mode ?? "sandbox"],
         usageGuide: {
             content: mode === undefined
                 ? oauthUsageGuide(purpose, options.instructions)
@@ -248,9 +212,7 @@ export function stripe(id, options) {
             // Not `required`. The four generic tools are the routing decision; a
             // guide forced into every call would pay for the same prose repeatedly.
         },
-        ...(options.maxResultBytes !== undefined
-            ? { maxResultBytes: options.maxResultBytes }
-            : {}),
+        ...defined({ maxResultBytes: options.maxResultBytes }),
     });
     return withVettedCatalog(connector, STRIPE_VETTED_CATALOG);
 }

package/dist/registry.d.ts

@@ -43,32 +43,25 @@ export declare function isValidMaxResultBytes(value: number): boolean;
  * a broken cap.
  */
 export declare function resolveMaxResultBytes(value: number | undefined, inherited: number): number;
-export interface HealthObservation {
-    lastSuccessAt?: string;
-    lastFailureAt?: string;
-    lastLatencyMs?: number;
-    consecutiveFailures: number;
-    lastError?: string;
-}
 export interface RegistryOptions {
     storage: KVStorage;
     logger: Logger;
-    credentialVault?: CredentialVault;
-    toolCacheTtlSeconds?: number;
-    persistToolCatalog?: boolean;
-    toolCatalogStaleSeconds?: number;
+    credentialVault?: CredentialVault | undefined;
+    toolCacheTtlSeconds?: number | undefined;
+    persistToolCatalog?: boolean | undefined;
+    toolCatalogStaleSeconds?: number | undefined;
     /**
      * Cap on inline result size before truncation + get_result paging. Must be a
      * whole number of bytes >= 1; anything else warns at startup and falls back
      * to the default 50_000.
      */
-    maxResultBytes?: number;
+    maxResultBytes?: number | undefined;
     /**
      * Where payload-free catalog-drift observations go. Present only when the
      * deployment configured an activity store; drift is reported through
      * connector status either way.
      */
-    catalogDriftActivity?: Omit<CatalogDriftActivityContext, "logger">;
+    catalogDriftActivity?: Omit<CatalogDriftActivityContext, "logger"> | undefined;
 }
 export type ConnectorOperationOptions = Pick<ConnectorContext, "signal" | "timeoutMs">;
 /** Agent-only catalog behavior. This never enters a ConnectorContext. */
@@ -96,8 +89,6 @@ export interface RegistryView {
         toolName: string;
     } | null;
     getTools(id: string, baseUrl: string, requestScope?: object, callOptions?: ConnectorOperationOptions, readOptions?: CatalogReadOptions): Promise<ToolDef[]>;
-    refreshTools(id: string, baseUrl: string, requestScope?: object, callOptions?: ConnectorOperationOptions): Promise<ToolDef[]>;
-    peekTools(id: string): ToolDef[] | undefined;
     contextFor(id: string, baseUrl: string, requestScope?: object, callOptions?: ConnectorOperationOptions): ConnectorContext;
     /** Acquire the connector's shared downstream-call permit. */
     admitCall(id: string, input: {
@@ -106,13 +97,12 @@ export interface RegistryView {
         signal?: AbortSignal;
     }): Promise<CallAdmissionPermit>;
     resultsStorage(): KVStorage;
-    recordSuccess(id: string, latencyMs: number): void;
-    recordFailure(id: string, latencyMs: number, error: unknown): void;
-    healthFor(id: string): HealthObservation | undefined;
-    hasObservedSuccess(id: string): boolean;
-    observedSuccessAt(id: string): string | undefined;
     /** Local declared-vs-stored credential mismatch, with no downstream I/O. */
     credentialDriftFor(id: string): Promise<string | undefined>;
+    /** Value-free shape learned from successful calls, never a provider declaration. */
+    observedOutputSchema(connectorId: string, definition: ToolDef): ToolDef["outputSchema"] | undefined;
+    /** Passively learn one successful unwrapped result; failures stay isolated. */
+    observeOutputShape(connectorId: string, definition: ToolDef, value: unknown): void;
     statusFor(id: string, baseUrl: string, requestScope?: object, callOptions?: ConnectorOperationOptions): Promise<ConnectorStatus>;
     invalidateStored(id: string): Promise<void>;
 }
@@ -131,16 +121,16 @@ export declare class Registry implements RegistryView {
     private readonly catalogGenerations;
     /** Serialize persisted catalog set/delete operations within this isolate. */
     private readonly catalogMutations;
-    /** Same-request cold loads share one promise without retaining the request. */
+    /** Same-request cold loads share one promise without retaining the request.
+     * See documentation/architecture.md#the-two-lifetimes. */
     private readonly requestCatalogLoads;
     /** One live refresh per connector across agent and operator requests. */
     private readonly catalogRefreshes;
     /** Last payload-free agent catalog access in this runtime. */
     private readonly catalogAccess;
-    /** Deployment-wide observations — every call, whatever view made it. */
-    private readonly health;
     /** Last drift counts reported to activity, per connector, in this runtime. */
     private readonly reportedDrift;
+    private readonly observedOutputSchemas;
     private readonly ttlMs;
     private readonly staleMs;
     private readonly persistToolCatalog;
@@ -203,6 +193,8 @@ export declare class Registry implements RegistryView {
      * separate from any connector's `conn:<id>:` namespace. Backs get_result.
      */
     resultsStorage(): KVStorage;
+    observedOutputSchema(connectorId: string, definition: ToolDef): ToolDef["outputSchema"] | undefined;
+    observeOutputShape(connectorId: string, definition: ToolDef, value: unknown): void;
     /** Resolve "<connectorId>.<toolName>" → connector + tool name. */
     resolveAddress(address: string): {
         connector: Connector;
@@ -210,7 +202,6 @@ export declare class Registry implements RegistryView {
     } | null;
     private catalogKey;
     private catalogChunkKey;
-    private validLegacyCatalog;
     private validCatalogTools;
     private validCatalogManifest;
     private parseCatalogManifest;
@@ -234,7 +225,7 @@ export declare class Registry implements RegistryView {
      */
     private startCatalogRefresh;
     /** Force a live listTools refresh and replace both catalog cache layers. */
-    refreshTools(id: string, baseUrl: string, requestScope?: object, callOptions?: ConnectorOperationOptions): Promise<ToolDef[]>;
+    private refreshTools;
     private observeCatalogAccess;
     /**
      * Start or join one shared refresh. A newly deferred task owns its scope,
@@ -253,15 +244,6 @@ export declare class Registry implements RegistryView {
      * later callers join only its result, never its request scope.
      */
     getTools(id: string, baseUrl: string, requestScope?: object, callOptions?: ConnectorOperationOptions, readOptions?: CatalogReadOptions): Promise<ToolDef[]>;
-    /** Return a cached catalog without performing storage or network I/O. */
-    peekTools(id: string): ToolDef[] | undefined;
-    recordSuccess(id: string, latencyMs: number): void;
-    recordFailure(id: string, latencyMs: number, error: unknown): void;
-    healthFor(id: string): HealthObservation | undefined;
-    /** Whether this deployment has seen a successful call to `id`. */
-    hasObservedSuccess(id: string): boolean;
-    /** The timestamp behind `hasObservedSuccess`. */
-    observedSuccessAt(id: string): string | undefined;
     credentialDriftFor(id: string): Promise<string | undefined>;
     /** Best-effort connector status for the operator UI. */
     statusFor(id: string, baseUrl: string, requestScope?: object, callOptions?: ConnectorOperationOptions): Promise<ConnectorStatus>;