/**
 * JIT layer-2 tools — assembly of the governed retrieval tool.  The machinery
 * lives in sibling modules (one responsibility each):
 *
 *   pipelines.ts     — the shared governance seam (threshold offload) + tm_fetch
 *   result.ts        — structured errors + ToolResult rendering contract
 *   client-unwrap.ts — host client result unwrapping + text extraction
 *   shell-bridge.ts  — the host `$` shell bridge + shell error hygiene
 *   args-schema.ts   — zod raw-shape arg schemas (descriptor fallback)
 *
 * (tm_read / tm_grep / tm_bash were the v1-only governed passthroughs; they are
 * gone with the v1 personality — on v2 the host's native read / grep / shell are
 * governed by src/host/v2-offload.ts over the SAME pipeline.)
 */
import type { ToolDefinition } from "../types.js";
import { type TmDeps, type TmPipelines } from "./pipelines.js";
/**
 * Build the tool definitions.  Async only because of the optional zod
 * load; every pipeline itself is runtime-defensive against raw args.  Every
 * execute() funnels through toToolResult so the return value ALWAYS satisfies
 * the host ToolResult contract ({output: string}) — handles, structured
 * errors, pages and degraded warnings included.
 * `pipelines` lets the caller inject a SHARED pipeline instance (tm/index
 * reuses one instance for the tools AND tm_webfetch so their step ids
 * never collide); when omitted, a fresh instance is built from deps.
 */
export declare function buildTmTools(deps: TmDeps, pipelines?: TmPipelines): Promise<Record<string, ToolDefinition>>;
//# sourceMappingURL=tools.d.ts.map