/**
 * report-data contribution — fitness's inputs to the cross-tool HTML
 * report.
 *
 * Audit 2026-05-29 (L2): the CLI is now the report composition root.
 * Fitness no longer loads sessions, the graph catalog, writes the file,
 * or opens the browser. It just returns ITS OWN dashboard inputs (the
 * check + recipe catalogs and the editor protocol) keyed by the field
 * names `generateDashboardHtml` consumes. The CLI walks every tool's
 * `collectReportData` and merges the contributions into one
 * `DashboardInput`. This decouples fitness from graph entirely.
 */
import type { ToolScope } from '@opensip-cli/core';
/** Check catalog entry for dashboard display. */
export interface CheckCatalogEntry {
    readonly slug: string;
    readonly name: string;
    readonly icon: string;
    readonly description: string;
    readonly longDescription?: string;
    readonly tags: readonly string[];
    readonly confidence: 'high' | 'medium' | 'low';
    readonly source: 'built-in' | 'community';
}
/** Recipe catalog entry for dashboard display. */
export interface RecipeCatalogEntry {
    readonly name: string;
    readonly displayName: string;
    readonly description: string;
    readonly tags: readonly string[];
    readonly selectorType: string;
    readonly mode: string;
    readonly timeout: number;
}
/**
 * Fitness's report-data contribution (audit 2026-05-29, L2). Returns
 * the check catalog, recipe catalog, and editor protocol under the keys
 * `generateDashboardHtml` consumes. Best-effort: a missing signalers
 * config degrades the editor protocol to null; catalog building always
 * succeeds once checks are loaded. The CLI merges this onto the shared
 * `DashboardInput` alongside other tools' contributions.
 */
export declare function collectFitnessReportData(scope: ToolScope): Promise<Record<string, unknown>>;
//# sourceMappingURL=report-data.d.ts.map