/**
 * verify Command - Run the repository verification gates for a worktree
 * Issue #1544
 *
 * Exit codes:
 * - 0:   SUCCESS (every gate passed)
 * - 20:  VERIFY_FAILED (a gate failed, timed out, or errored)
 * - 21:  NOT_STARTED (work-evidence found nothing to verify)
 * - 124: TIMEOUT (--timeout elapsed before the run reached a verdict)
 * Infrastructure errors and verdict-less runs use ExitCode (1, 2, 99).
 *
 * Issue #1593 adds two read-only subcommands, `history` and `show`. They never
 * return 20/21: those codes mean "this working tree failed verification", and a
 * query about past runs is not a verdict on the current one. A read that
 * succeeds exits 0 even when it finds nothing.
 */
import { Command } from 'commander';
import type { VerificationScopeDetail } from '../types/api-responses';
/**
 * Read the scope gate's report back into structured evidence.
 *
 * Parsing the gate's own prose is not the shape anyone would choose, but it is
 * the only one available: `verification_gate_results` has no column for
 * structured detail, and the CLI's `formatDetail` already reads work-evidence's
 * counts out of `logTail` the same way (src/cli/utils/verify-runner.ts).
 *
 * Returns null when the tail is not a report — a skip, an error, or a gate that
 * was never entered all write a sentence — because an empty `admitted` on those
 * would claim the gate looked and found nothing.
 */
export declare function parseScopeEvidence(logTail: string | null | undefined): VerificationScopeDetail | null;
export declare function createVerifyCommand(): Command;
//# sourceMappingURL=verify.d.ts.map