/**
 * Talking to herdr: one command, one JSON envelope, plus the two questions ADR-0031 needs answered.
 *
 * Lifted out of `src/executors/run-herdr.ts`, which was at 357 of the 400-line ceiling and gains output polling under
 * ADR-0032. But the split is not only about lines: **the probe is not an executor concern**. It runs at session
 * start, before any delegation exists, to decide *which* executor a session will use — so leaving it inside the
 * herdr executor would mean the session imported the thing it was deciding whether to use.
 *
 * Every rule here is tested against an injected `exec`, so the suite stays fast, pi-free and herdr-free. The
 * facts the fakes reproduce were measured against real herdr 0.7.5 (probe `g16-herdr`).
 */
export { ENV_HERDR_WORKSPACE } from "../kernel/env-names.ts";
/** One herdr CLI invocation. Injectable so every rule below is testable without herdr installed. */
export type HerdrExec = (args: string[]) => Promise<{
    code: number | null;
    stdout: string;
    stderr: string;
}>;
export declare const defaultExec: HerdrExec;
/**
 * Parse herdr's JSON envelope. Every command replies `{id, result}` or `{id, error:{code,message}}`.
 *
 * `stderr` is folded into the message because the first end-to-end run failed with an EMPTY stdout and the
 * real reason on stderr, producing the useless diagnostic "unparseable herdr reply: ". A wrapper that
 * hides the substrate's own error message costs more time than it saves.
 */
export declare function parseReply(reply: {
    stdout: string;
    stderr: string;
}): {
    result?: Record<string, unknown>;
    error?: string;
};
/** Bound on the session-start probe. Short: it sits in front of the operator's first prompt. */
export declare const PROBE_TIMEOUT_MS = 2000;
export interface HerdrProbe {
    ok: boolean;
    /** herdr's own words when it is not reachable. Carried so the disclosure line can name the reason. */
    error?: string;
}
/**
 * Is there a herdr server that will answer right now? — ADR-0031's selection input.
 *
 * **`tab list`, not `which herdr`.** ADR-0031 rejects `PATH` detection as option C by name: a binary on `PATH`
 * with no server behind it would make every delegation fail at `tab create`, on a path the operator never
 * chose, and the diagnostic would arrive at the first delegation rather than at startup. Only a parsed
 * `result` envelope counts as reachable; an `error` envelope, a non-JSON reply, a timeout and a throwing
 * `exec` are all "not reachable" with the reason preserved.
 *
 * **Zero tabs is a successful answer**, deliberately: a fresh herdr with nothing open is reachable.
 *
 * Never throws. A probe that threw out of `session_start` would cancel every control after it, which is
 * R-60's shape exactly — and this one runs *before* the line that discloses what it decided.
 */
export declare function probeHerdr(options?: {
    exec?: HerdrExec;
    timeoutMs?: number;
}): Promise<HerdrProbe>;
/** herdr's own variable, set in every pane it creates. Measured 2026-08-17; documented nowhere. */
export declare const ENV_PARENT_WORKSPACE = "HERDR_WORKSPACE_ID";
/** The operator's explicit override. Defined here because this is the only module that reads it. */
/**
 * Which herdr workspace a governed child's pane belongs in.
 *
 * **Defaults to the parent's own workspace.** herdr tells a pane which workspace it is in
 * (`HERDR_WORKSPACE_ID`, alongside `HERDR_TAB_ID` and `HERDR_PANE_ID`), and a child placed in a *different*
 * workspace from the pi session that spawned it turns "switch between them" into a workspace hop — which is
 * the entire feature ADR-0032 exists to deliver. The previous behaviour was "omitted lets herdr choose",
 * which is that failure by default on any machine with more than one workspace.
 *
 * `PI_DADDY_HERDR_WORKSPACE` still wins: it is the operator saying so explicitly, and an explicit answer
 * beating an inference is this package's standing rule (ADR-0030 says it about the grant itself).
 *
 * Blank is treated as absent rather than passed through — `--workspace ""` is not a workspace, and it would
 * fail `tab create` on a path nobody chose.
 */
export declare function resolveWorkspace(env: NodeJS.ProcessEnv): string | undefined;
//# sourceMappingURL=herdr-cli.d.ts.map