/**
 * Recipe domain — compile, plan, diff, push.
 *
 * `recipe_compile` is pure-logic and explicitly does NOT touch disk
 * (unlike the CLI counterpart, which writes the IR alongside the input).
 * The other three (plan, diff, push) talk to the bound tenant via
 * `runRecipePlan` / `runRecipeDiff` / `runRecipePush`; their CLI-shaped
 * task runners stay the contract surface so the MCP layer benefits from
 * cache reuse, retry behaviour, and execution-event collation without
 * re-implementing them.
 *
 * Inline-TS recipe sources are intentionally not supported in v1 —
 * agents should reference a recipe by file path. (A TS-source escape
 * hatch would require an in-process compile to JS and is a code-injection
 * risk that's out-of-scope for this milestone.)
 */
import type { McpRegistry } from "../registry.js";
export declare const registerRecipeTools: (registry: McpRegistry) => void;