/**
 * specify verify <spec-dir> [--graph <graph.json>] [--code <dir>]
 *
 * Deterministic conformance pass: builds a coverage map between every behavioral
 * trigger declared in the spec and the code symbols of the project.
 *
 * Two modes, picked automatically:
 *   - `graphify` — a graphify graph.json is present (richest: deduped, parser-
 *     extracted, community-aware symbols). graphify is an ACCELERATOR.
 *   - `codescan` — no graph; we scan the code directory directly for declared
 *     symbol names (zero-setup fallback). Slightly coarser, no deps, no build.
 *
 * Either way the matching is identical lexical overlap. This pass does NOT decide
 * whether behavior is *correctly* implemented — that judgment is the AI skill's,
 * reading the matched code. It answers the cheap half: which behaviors have a
 * plausible implementation site, and which appear to have none (the drift signal).
 *
 * Output is a JSON dossier the skill consumes — the spec stays code-free; all
 * code references live here, in the verify output, not in the spec.
 */
import { type TriggerCoverage } from '../graph/graphify.js';
export interface VerifyResult {
    status: 'ok' | 'drift' | 'error';
    spec_dir: string;
    /** Which surface was matched against: graphify graph, or a direct code scan. */
    mode: 'graphify' | 'codescan';
    graph: string | null;
    /** Code dir scanned in codescan mode (null in graphify mode). */
    code_dir: string | null;
    threshold: number;
    total_triggers: number;
    covered: number;
    uncovered: number;
    coverage: TriggerCoverage[];
    hint?: string;
    message?: string;
}
export interface VerifyOptions {
    graphPath?: string;
    codeDir?: string;
    threshold?: number;
    topK?: number;
}
export declare function verifySpec(specDir: string, opts?: VerifyOptions): VerifyResult;
//# sourceMappingURL=verify.d.ts.map