/**
 * log10x_validate — test-drive Log10x pipeline config changes locally.
 *
 * Workflow this tool enables:
 *
 *   1. Agent drafts a new JS module (e.g. a GeoRefCityObject-style
 *      constructor, a groupFilter helper, or a full stream.yaml override).
 *   2. Agent synthesizes 3-20 sample event lines that represent the shape
 *      the change needs to handle (from natural-language intent, or by
 *      copying observed production samples).
 *   3. Agent calls log10x_validate with the draft + samples.
 *   4. Tool runs the local `tenx @apps/mcp` CLI against the input, captures
 *      emitted templates + encoded events + stdout (including any
 *      TenXConsole.log the JS emitted for inspection) + stderr.
 *   5. Tool returns structured output. Agent decides whether to proceed to
 *      deploy, iterate, or discard.
 *
 * Runs fully local — no network, no cluster access, no persistence.
 * Requires a local `tenx` CLI install and the workspace config tree on
 * disk (see `LOG10X_TENX_CONFIG_ROOT` / `LOG10X_TENX_MODULES_ROOT`).
 *
 * Intended callers: agents preparing PRs to the config repo or proposing
 * engine-adjacent JS changes. NOT a general "run my log pipeline" tool —
 * use the existing log10x_resolve_batch for that.
 */
import { z } from 'zod';
export declare const validateSchema: {
    input_lines: z.ZodArray<z.ZodString, "many">;
    extra_files: z.ZodOptional<z.ZodRecord<z.ZodString, z.ZodString>>;
    pipeline_app: z.ZodDefault<z.ZodString>;
    extra_args: z.ZodOptional<z.ZodArray<z.ZodTuple<[z.ZodString, z.ZodString], null>, "many">>;
    timeout_ms: z.ZodDefault<z.ZodNumber>;
};
interface ValidateArgs {
    input_lines: string[];
    extra_files?: Record<string, string>;
    pipeline_app: string;
    extra_args?: Array<[string, string]>;
    timeout_ms: number;
}
export declare function executeValidate(args: ValidateArgs): Promise<string>;
export {};