import type { CanvasGraph } from '../graph-projection.js';
import type { VisualDiagnostic } from '../adapters/visual/protocol-contract.js';
/**
 * What failed, and where to look for it.
 *
 * The rule this exists to keep: the summary never reads clean while anything
 * is open. A diagnostic whose subject is on the canvas can be marked there; one
 * that belongs to no subject - a parse failure, a manifest, a projection's own
 * definition - has nothing to mark, and reporting a failure with nothing on
 * screen changed is how a reviewer stops believing the tool. So the two are
 * counted separately and both are named.
 *
 * Absence of `subjects` is meaningful rather than missing: Core populates it
 * wherever a diagnostic's pointer identifies a subject, so an empty list means
 * this one belongs somewhere other than the canvas.
 */
export interface FaultSummary {
    readonly total: number;
    /** Marked on the diagram, because their subject is drawn there. */
    readonly onCanvas: number;
    /** Real, and not markable: they belong to no drawn subject. */
    readonly elsewhere: number;
}
export declare const summarise: (diagnostics: readonly VisualDiagnostic[], graph: CanvasGraph) => FaultSummary;
/** The subject ids any diagnostic names, for the canvas to mark. */
export declare const faultedSubjects: (diagnostics: readonly VisualDiagnostic[]) => ReadonlySet<string>;