/**
 * report-generator.ts
 *
 * Writes execution reports to disk and prints a human-readable summary
 * to stderr after a test run completes.
 *
 * Each time a test finishes (via the execute_test MCP tool), the Executor
 * hands an ExecutionReport to this class. The report captures overall test
 * status (passed / failed / healed), total duration, and per-step context
 * including any healing that occurred.
 *
 * Reports are saved in <artifactsDir>/execution/ as timestamped JSON files
 * so developers can review trends and diagnose failures over time.
 *
 * Role in the overall flow:
 *   Executor → ExecutionReport → ReportGenerator.write()
 *                              → ReportGenerator.summary()  (optional batch summary)
 */
import { ExecutionReport } from '../types';
/**
 * Handles persisting individual execution reports and printing a concise
 * pass/fail/healed summary for a batch of reports.
 */
export declare class ReportGenerator {
    private artifactsDir;
    /**
     * @param artifactsDir - Root directory where execution reports are stored.
     */
    constructor(artifactsDir: string);
    /**
     * Write a single ExecutionReport to disk as a timestamped JSON file.
     * The file is saved under <artifactsDir>/execution/<test-slug>-<timestamp>.json.
     *
     * @param report - The completed execution report to persist.
     */
    write(report: ExecutionReport): Promise<void>;
    /**
     * Print a one-line pass/healed/failed tally for a collection of reports to stderr.
     * Useful after running a batch of tests to see the overall outcome at a glance.
     *
     * @param reports - Array of ExecutionReports to summarise.
     */
    summary(reports: ExecutionReport[]): void;
}
//# sourceMappingURL=report-generator.d.ts.map