/**
 * `openclaw senpi validate` — the command surface.
 *
 * Thin by design: parse flags, call the runner, render, set the exit code. Everything worth testing
 * lives behind this in `src/validate/`, so the tests do not have to drive a command line.
 *
 * ## Why this one runs locally
 *
 * Every other `senpi` subcommand forwards to the gateway. This one does not, deliberately:
 *
 *   - continuous integration can run the offline depths with no gateway present at all
 *   - it keeps validation out of the process that hosts live runtimes, so a scanner being validated
 *     cannot interact with a strategy that is running
 *   - an external scanner's files must be on this machine anyway, since the recipe locates them by
 *     path, so there is nothing a remote gateway could do with the request
 *
 * The inconsistency with its neighbours is intentional. Please do not "fix" it by routing this
 * through the gateway without reading the above.
 */
interface CommanderCommand {
    command(name: string): CommanderCommand;
    description(text: string): CommanderCommand;
    option(flags: string, description: string, defaultValue?: unknown): CommanderCommand;
    argument(name: string, description: string): CommanderCommand;
    action(handler: (...args: never[]) => void | Promise<void>): CommanderCommand;
}
export declare function registerValidateCommand(senpi: CommanderCommand): void;
export {};
//# sourceMappingURL=validate-command.d.ts.map