/**
 * Grounding for design-review findings (S8 = S7 applied to the reviewer).
 *
 * Conceptual/contract findings are architectural — they rarely cite a single
 * quotable line, so quote-and-verify (tier-1) does not fit. But they must still
 * point at something real: every finding has to cite at least one **component**
 * (an `affected_files` path that exists in the repository). A finding that cites
 * no component, or only paths not in the repo, is `ungrounded` — it points at
 * nothing checkable — and is surfaced/quarantined like any other ungrounded
 * finding (the same tier-3 machinery), never silently admitted as confirmed.
 *
 * Before this, design findings were ingested on `Array.isArray()` alone, with no
 * evidence requirement — unlike the schema-gated AuditResult path.
 *
 * Single source for both orchestrators (lives in shared next to the quote-and-
 * verify primitives) so neither orchestrator forks the design-grounding logic and
 * there is no remediate→audit cross-area import.
 */
import type { Finding, FindingGrounding } from "../types/finding.js";
/**
 * Ground a single design finding against the set of real repository paths. The
 * verdict is the tool's check, never the model's word: a finding survives as
 * `grounded` only if at least one cited `affected_files` path exists in the repo.
 */
export declare function groundDesignFinding(finding: Finding, knownPaths: ReadonlySet<string>): FindingGrounding;
/**
 * Annotate each design finding with its grounding verdict. When no repo manifest
 * is available the findings cannot be grounded against a known file set, so they
 * are returned unchanged — better than false-quarantining everything on a missing
 * input.
 */
export declare function groundDesignFindings(findings: Finding[], repoManifest: {
    files?: Array<{
        path: string;
    }>;
} | undefined): Finding[];
//# sourceMappingURL=designFindingGrounding.d.ts.map