/**
 * Where default-eval runs are kept: beside the steering evals, under the daemon state home.
 *
 *   <home>/evals/default/runs.jsonl        one {@link DefaultEvalSummary} per line (the list)
 *   <home>/evals/default/results/<id>.json the full report and its cases (the drilldown)
 *
 * Same posture as `api/eval-store.ts`: the detail is written first (tmp + rename), then the index line, so every
 * listed row has a readable detail; a torn line is skipped on read, never the store.
 */
import type { DefaultEvalDetail, DefaultEvalSummary } from './types.js';
import { type PreviousScores } from './runner.js';
/** `<eval store root>/default`: the steering eval store's root (its env override, else the state home's `evals`). */
export declare function defaultEvalsRoot(env?: NodeJS.ProcessEnv): string;
export type { DefaultEvalDetail };
export declare class DefaultEvalStore {
    private readonly root;
    constructor(root?: string);
    record(detail: DefaultEvalDetail): Promise<DefaultEvalSummary>;
    /** Newest first. */
    list(): Promise<DefaultEvalSummary[]>;
    get(id: string): Promise<DefaultEvalDetail | null>;
    /** Per suite, the most recent stored score of the same scope (`null` project = every project). A run that
     *  skipped a suite is passed over for that suite, so a narrower run never erases a trend baseline. */
    previous(project: string | null): Promise<PreviousScores>;
}
//# sourceMappingURL=store.d.ts.map