import type { McpInstallCommand, McpInstallOutcome, McpInstallRunner } from './mcp-install.js';
/**
 * Ceiling on ONE harness command. `spawnSync` without `timeout` has no ceiling
 * at all, and the failure it lets through is measured, not hypothetical: a
 * real harness binary on this host starts and then does not return within 25 s.
 * Unbounded, that blocks `peaks mcp install` in the foreground forever. Same
 * class the MCP CLI executor bounds (`cli-executor.ts`), set to twice its 15 s
 * because the child is the harness's binary and its startup is its own to
 * spend. A plan is at most three commands, so the install is bounded at 3x.
 */
export declare const MCP_INSTALL_TIMEOUT_MS = 30000;
/**
 * One harness command, with the deadline applied. `windowsHide` is the tree's
 * spawn contract: a CLI that briefly runs a harness must not flash a console
 * window on a desktop OS. `timeoutMs` is a parameter only so a test can watch
 * the deadline fire without waiting out the production value — callers want
 * `spawnMcpInstallRunner`, which fixes it.
 */
export declare function spawnMcpInstallCommand(command: McpInstallCommand, timeoutMs?: number): McpInstallOutcome;
/** The production runner: the deadline above, and nothing else left to decide. */
export declare const spawnMcpInstallRunner: McpInstallRunner;