/**
 * A validation report as text.
 *
 * Layer 7, and pure. Part of `edfcore/validate`.
 *
 * `validateRecording` returns a report a program can branch on; this turns it into the thing a
 * person reads at the end of a CI job or a conformance sweep.
 *
 * The one judgement it makes is what to lead with. A sweep over a damaged file can produce six
 * figures of diagnostics — `TIMEKEEPING_TAL_MISSING` is per record — and a wall of them buries
 * the answer. So the counts come first, then the distinct codes with how often each occurred,
 * and only then the individual entries, capped. What a reader needs first is *which kinds* of
 * thing are wrong and how much of the file is affected.
 */
import type { EdfHeader, FormatReportOptions, ValidationReport } from './types.js';
/**
 * A multi-line summary of a validation report.
 *
 * `header` is optional and only used to name signals: a report is perfectly readable without it,
 * and a caller who has one gets `EEG Fpz-Cz` instead of `signal 0`.
 */
export declare function formatValidationReport(report: ValidationReport, options?: FormatReportOptions): string;
/** The header type, re-exported so a consumer of the subpath can name the option. */
export type { EdfHeader };
//# sourceMappingURL=format-report.d.ts.map