/**
 * Worker Verification Bridge (2.13.0).
 *
 * Maps a durable mission's declared acceptance criteria (each optionally
 * carrying a deterministic `VerificationSpec`) into a `ProcessMissionVerifier`
 * that the Worker can hand to the existing execution path. A clean exit-0 child
 * is only promoted from PARTIAL (unverified) to SUCCEEDED when every declared
 * verification spec passes deterministically; a model's self-reported success is
 * never the authority.
 *
 * This is deliberately a thin bridge: the Reliability Kernel's
 * `verify()` + `createWorkspaceVerificationExecutor()` remain the verification
 * authority; `ProcessMissionExecutor` remains the promotion authority. The
 * worker only composes them.
 */
import type { MissionRequest } from "../mission-domain/mission-request.js";
import type { ProcessMissionVerifier } from "../mission-domain/process-mission-executor.js";
/**
 * Build a verifier for a mission whose acceptance criteria carry deterministic
 * verification specs. Returns `undefined` when the mission declares no
 * verifiable criteria (so a bare exit-0 remains PARTIAL, never SUCCEEDED).
 */
export declare function buildAcceptanceCriteriaVerifier(request: MissionRequest, options?: {
    commandTimeoutMs?: number;
}): ProcessMissionVerifier | undefined;
//# sourceMappingURL=worker-verification.d.ts.map