/**
 * Parse-health boundary surfacing (change: add-parse-health-boundary-disclosure).
 *
 * The analyzer records per-file parse health into `parse-health.json`. This module is the read side
 * shared by every MCP surface that discloses it: it loads the report and, given the files a
 * conclusion's result set touches, produces a single disclosed boundary string when any of them
 * parsed with errors — so a conclusion built on a degraded file says *"symbols/edges there are a
 * lower bound"* instead of implying the missing symbols are genuinely absent (the `NoFalseCompleteness`
 * failure mode). A clean repo has no artifact, so every helper here fails open to "no boundary".
 */
import { type ParseHealthReport } from '../../analyzer/parse-health.js';
/** Load the persisted parse-health report, or `null` when absent/unreadable (a clean repo). */
export declare function loadParseHealthReport(absDir: string): Promise<ParseHealthReport | null>;
/**
 * Given the files a conclusion's result set touches, return a disclosed boundary string, else
 * `undefined`. Two disclosures ride the same string:
 *
 *  1. the per-file boundary — files IN THIS result that parsed with errors;
 *  2. language grammars that were unavailable for the whole analysis;
 *  3. a whole-analysis memory-pressure reduction (change: make-analyze-scale-to-any-repo). When the
 *     degradation ladder shed the CFG overlay and/or deep-analysis breadth, that reduction has NO
 *     per-file record — it affects every result over this index — so it is surfaced REGARDLESS of
 *     which files the result touched. Without this the shed coverage would read as genuine absence,
 *     the exact `NoFalseCompleteness` failure the disclosure exists to prevent.
 */
export declare function parseHealthBoundary(report: ParseHealthReport | null, touchedFiles: Iterable<string>): string | undefined;
//# sourceMappingURL=parse-health-boundary.d.ts.map