/**
 * `qulib validate` — spec-grounded validation.
 *
 * Grades whether a deployed app's OBSERVED behavior conforms to a SUPPLIED spec
 * (PRD / requirements document). Not "does it crash" — "does it match intent."
 *
 * Usage:
 *   qulib validate --spec <spec.md> --url <url> [--enable-llm-judge] [--fail-on-violation] [--json]
 *   qulib validate --spec <spec.md> --report <analyze-report.json> [--enable-llm-judge] [--fail-on-violation] [--json]
 *
 * --spec <file>          Required. A text or markdown file; each non-empty, non-heading
 *                        line becomes a requirement (strips leading "- ", "* ", "N. ").
 * --url <url>            Run analyzeApp against this URL and use its output as the
 *                        observed summary.
 * --report <file>        Read a qulib analyze report.json and use a trimmed subset as
 *                        the observed summary. Mutually exclusive with --url.
 * --json                 Emit the full SpecConformanceResult as JSON on stdout.
 * --enable-llm-judge     Enable the LLM judge (requires ANTHROPIC_API_KEY). Without
 *                        this flag, all requirements return 'unknown'.
 * --fail-on-violation    Exit code 1 when verdict is 'violates' or 'partial'.
 *                        'insufficient-evidence' does NOT trigger this gate.
 */
import type { Command } from 'commander';
export declare function registerSpecValidateCommand(program: Command): void;
//# sourceMappingURL=spec-validate-run.d.ts.map