import { type ProveControlReport } from '../lib/prove-control';
/**
 * `enterprise-skills prove-control` -- does this test fail against the pre-fix
 * code? (docs/DEFECT_LEDGER_DESIGN.md section 3, acceptance 4 and 5.)
 *
 * Exit codes are distinct on purpose, exactly as `probe run`'s are: "your test
 * does not test the defect" and "I could not assess this" are different
 * problems and a CI job must be able to tell them apart without parsing prose.
 *   0 -- PROVED:         the test fails without the fix
 *   1 -- NOT PROVED:     the test passes without the fix (it tests something else)
 *   3 -- INCONCLUSIVE:   no verdict was reached
 *   4 -- NOT APPLICABLE: the fix is not in source; this tool cannot assess it
 *
 * There is deliberately no exit code that means "assume it is fine".
 */
export interface ProveControlCliOptions {
    test?: string;
    source?: string[];
    ref?: string;
    cmd?: string;
    json?: boolean;
    cwd?: string;
    timeout?: string;
    skipBaseline?: boolean;
}
export declare function proveControlCommand(options?: ProveControlCliOptions): Promise<ProveControlReport | null>;
//# sourceMappingURL=prove-control.d.ts.map