import { type CelFunctionInfo } from "@telorun/templating";
import type { Argv } from "yargs";
/** A CEL built-in, in the same shape as a catalog entry so one listing covers
 *  both halves of what a manifest may call. `receiver` is what the catalog
 *  cannot express: a built-in is usually a METHOD, and calling it as a global
 *  does not type-check. Leaving them out was the reason an author could read
 *  this command end to end and still write `startsWith(key, 'x')`. */
interface CelBuiltinInfo {
    name: string;
    signature: string;
    category: "builtin";
    receiver: string | null;
}
/** The `--json` document: Telo's catalog followed by CEL's built-ins. Exported
 *  for tests — the listing is what every new CEL diagnostic points a reader at,
 *  so "does it contain the functions those diagnostics are about" is worth
 *  asserting without spawning a CLI. */
export declare function functionListing(): (CelFunctionInfo | CelBuiltinInfo)[];
export declare function celCommand(yargs: Argv): Argv;
export {};
//# sourceMappingURL=cel.d.ts.map