export interface LocalProbeEnvironment {
    /**
     * The trusted absolute path to the resolved `claude` executable, or `null`
     * when the trusted server PATH holds no `claude`. The caller must not run a
     * local probe when this is `null`; it reports a probe-unavailable check
     * instead.
     */
    command: string | null;
    /**
     * The child environment for the local probe. It holds only allowlisted
     * caller values plus proxy values from the trusted input. It never holds a
     * caller-supplied proxy key, a loader variable, a PATH override, or a Windows
     * interpreter variable.
     */
    env: Record<string, string>;
}
/**
 * Build the child environment and executable for a local Claude adapter-test
 * hello probe. Both the ACP Test lane and the Claude CLI Test lane use this
 * builder, so the two lanes probe the host the same safe way.
 *
 * The builder denies by default. It never merges the arbitrary caller env into
 * a host base. It reads two separate inputs:
 *   - `callerEnv`: the untrusted adapter-config env from the Test request. The
 *     builder takes only allowlisted Claude, auth, and Bedrock keys from it. It
 *     discards every proxy key and every Windows interpreter key, in any case.
 *   - `trustedEnv`: the trusted server-resolved env (the server launch config
 *     and the authorized environment's server-resolved env). The builder takes
 *     proxy keys only from this input.
 *
 * The builder resolves `claude` to a trusted absolute executable with the
 * trusted server PATH, before it reads any caller value. It ignores a caller
 * `command` path.
 *
 * The builder never logs, returns, or reflects a proxy value in a check.
 */
export declare function buildLocalAdapterTestProbeEnv(input: {
    callerEnv: Record<string, string>;
    trustedEnv?: NodeJS.ProcessEnv;
    commandName?: string;
}): Promise<LocalProbeEnvironment>;
//# sourceMappingURL=probe-env.d.ts.map