/**
 * Remote Execution — remote verification (2.14.0).
 *
 * The central verifier remains authoritative, but its deterministic commands
 * run against the remote workspace so `node test.js` actually tests the file
 * the remote child edited on the target. This adapts the existing
 * `VerificationExecutor` contract to a remote command runner; `verify()` itself
 * is unchanged.
 */
import type { MissionRequest } from "../mission-domain/mission-request.js";
import type { ProcessMissionVerifier } from "../mission-domain/process-mission-executor.js";
import type { VerificationExecutor } from "../reliability/verifier.js";
import type { RemoteExecutionTarget } from "./remote-target-types.js";
import type { RemoteCommandRunner } from "./remote-transport.js";
export interface RemoteVerificationOptions {
    runner: RemoteCommandRunner;
    target: RemoteExecutionTarget;
    /** Remote absolute working directory for relative verification paths. */
    cwd: string;
    commandTimeoutMs?: number;
    signal?: AbortSignal;
}
/**
 * Build a VerificationExecutor whose filesystem/process operations execute on
 * the remote target. `runCommand` uses the remote command runner; file/state
 * operations round-trip through the same runner via platform-neutral helpers.
 */
export declare function createRemoteVerificationExecutor(options: RemoteVerificationOptions): VerificationExecutor;
/**
 * Build the remote acceptance-criteria verifier. Returns `undefined` when the
 * mission declares no verifiable criteria (so a clean exit-0 stays PARTIAL,
 * never SUCCEEDED). Identical semantics to the local worker verifier, but the
 * verification operations execute remotely.
 */
export declare function buildRemoteAcceptanceCriteriaVerifier(request: MissionRequest, options: RemoteVerificationOptions): ProcessMissionVerifier | undefined;
//# sourceMappingURL=remote-verification.d.ts.map