/**
 * Graph-owned session payload (audit 2026-05-29, session split; extended
 * 2026-05-29 to carry per-rule detail for the Code Paths session view;
 * rebuilt from `Signal[]` directly in ADR-0011 Phase 5 — no `CliOutput`).
 *
 * `contracts` stores per-session detail as an opaque JSON blob and holds
 * zero tool vocabulary. Graph owns its own payload shape here, derived
 * straight from the run's `Signal[]`. The Code Paths → Sessions subtab
 * renders a per-rule detail panel, so the payload carries rule-grouped
 * detail (`summary` + `checks[]` of rule-grouped findings).
 *
 * The detail shape (`summary` + `checks[]` of rule-grouped findings) is the
 * dashboard's structural session-detail contract, consumed by the shared
 * `renderDetail` in @opensip-cli/dashboard. These types are graph-local
 * structural mirrors (not the retired `contracts` `CheckOutput`/
 * `FindingOutput`): the dashboard reads `checkSlug`/`passed`/`durationMs` and
 * each finding's `severity`/`message`/`filePath`/`line`/`suggestion`/`metadata`
 * structurally.
 *
 * Rule-ID vocabulary: `checkSlug` is the ENGINE slug (`graph:<rule>`), NOT the
 * OpenSIP-mapped rule ID the envelope/SARIF surfaces use. The dashboard's
 * per-rule metric columns (`RULE_METRIC_COLUMNS`) are keyed on engine slugs,
 * so the session detail stays in engine vocabulary (built upstream of the
 * envelope's Option-A remap).
 */
import type { GraphImpactReportProjection } from './impact-report-projection.js';
import type { JsonScalar, Signal, SignalRepair } from '@opensip-cli/core';
/** Two-level severity the dashboard buckets on (`critical|high → error`). */
export type GraphFindingSeverity = 'error' | 'warning';
/** A persisted finding row — the structural subset the dashboard renders. */
export interface GraphSessionFinding {
    readonly ruleId: string;
    readonly message: string;
    readonly severity: GraphFindingSeverity;
    readonly filePath: string;
    readonly line?: number;
    readonly column?: number;
    readonly suggestion?: string;
    readonly metadata?: Readonly<Record<string, JsonScalar>>;
    /** Structured repair guidance (ADR-0086) — round-trips through replay. */
    readonly repair?: SignalRepair;
}
/** A persisted per-rule detail row — the structural subset the dashboard renders. */
export interface GraphSessionCheck {
    readonly checkSlug: string;
    readonly passed: boolean;
    readonly violationCount: number;
    readonly findings: readonly GraphSessionFinding[];
    readonly durationMs: number;
}
/**
 * Opaque-to-contracts detail blob written for every `graph` session.
 *
 * `checks` is graph's rule-grouped detail: one entry per EVALUATED rule (a rule
 * that emitted no signal is a PASS with zero findings), each carrying its
 * findings. The dashboard's shared session-detail renderer reads `summary` and
 * `checks` structurally.
 */
export interface GraphSessionPayload {
    /** Inner version per the payload schema evolution convention (v1 shape). */
    readonly __version: 1;
    readonly summary: {
        /** Total rules evaluated (one `checks[]` row each; clean rules included). */
        readonly total: number;
        /** Rules with no error-severity signal (a clean run = all rules passed). */
        readonly passed: number;
        /** Rules with ≥1 error-severity signal. */
        readonly failed: number;
        /** Error-severity (critical|high) signal count. */
        readonly errors: number;
        /** Warning-severity (medium|low) signal count. */
        readonly warnings: number;
    };
    readonly checks: readonly GraphSessionCheck[];
    /** Bounded durable evidence for current `graph impact` sessions. */
    readonly impact?: GraphImpactReportProjection;
    /** Absent for legacy and ordinary graph sessions. */
    readonly impactStatus?: 'available' | 'omitted-overflow';
}
/**
 * Build the graph session payload directly from the run's `Signal[]`.
 *
 * Groups by ENGINE `ruleId` into the dashboard's rule-grouped detail
 * (`checks[]`), collapsing the 4-level signal severity to the dashboard's
 * two-level `error`/`warning` bucket. Per-rule `passed` follows fit's
 * semantics (warnings alone do not fail a rule). Persists the full detail
 * (no cap) — the datastore is a rebuildable local cache.
 *
 * `evaluatedRuleSlugs` is the full set of rules the run evaluated (engine
 * slugs). Every evaluated rule gets a `checks[]` row — a rule that emitted NO
 * signal is a PASS with zero findings — so a CLEAN run still shows its complete
 * rule list, exactly the way fitness shows every check (not just the failing
 * ones). When omitted (e.g. unit tests), only rules that fired are listed,
 * preserving the prior behaviour.
 *
 * @param signals - the run's raw engine signals.
 * @param evaluatedRuleSlugs - engine slugs of every rule the run evaluated.
 * @returns the opaque detail blob persisted for this graph session.
 */
export declare function buildGraphSessionPayload(signals: readonly Signal[], evaluatedRuleSlugs?: readonly string[]): GraphSessionPayload;
//# sourceMappingURL=session-payload.d.ts.map