import type { AnyOperation } from './operation.js';
/** A labeled set of operations for the capability table: its provenance + the ops. */
export type CapabilityGroup<Client> = {
    /** Provenance shown in the Source column. */
    kind: CapabilityKind;
    operations: Record<string, AnyOperation<Client>>;
};
/** The two provenance kinds a capability group can carry (Google's two reference trees). */
export type CapabilityKind = 'MCP Tool' | 'REST Method';
/**
 * Render the operations as a Markdown capability table (name, source, description,
 * and a destructive marker), derived from the same registries the server
 * dispatches. The Source column makes the provenance explicit: a service is an
 * MCP-toolset wrapper and a REST wrapper (or REST only, where Google publishes
 * no toolset), because MCP's toolset alone cannot fully drive a service. A
 * static mirror; agents that speak MCP discover the live, fully-schema'd
 * surface via `tools/list`. Pure; a service regenerates its CAPABILITIES.md
 * from this (and a test pins the file to it) so the doc cannot drift from the code.
 */
export declare function renderCapabilities<Client>(title: string, groups: CapabilityGroup<Client>[]): string;
/**
 * Write CAPABILITIES.md beside the calling bootstrap module: each service's
 * `capabilities.ts` passes its own `import.meta.url`, so the doc always lands
 * next to the registries it renders, and the wing's equality test can pin the
 * committed file to `renderCapabilities` of the live registries.
 */
export declare function writeCapabilities<Client>(moduleUrl: string, title: string, groups: CapabilityGroup<Client>[]): void;
//# sourceMappingURL=capabilities.d.ts.map