/**
 * Top-level convenience that runs a crawl and returns a pre-decided
 * pass/fail + exit code. Most programmatic consumers end up re-deriving
 * these from CrawlReport; this just makes the common case one call.
 */
import { type Page } from "playwright";
import { diffReports, hasRegressions, loadBaseline } from "./diff.js";
import type { CrawlerEvents, CrawlerOptions, CrawlReport, ChaosRemoteServer } from "./types.js";
export interface ChaosResult {
    report: CrawlReport;
    passed: boolean;
    exitCode: number;
}
/**
 * Context handed to the `setup` hook. `page` is a one-shot Playwright page
 * that lives only for the duration of the hook; it is closed before the
 * crawler starts. Use `page.request` for REST seeding, or drive UI flows
 * (e.g. login, then save the resulting `storageState` to disk and feed the
 * path to `options.storageState`) when you need browser context to carry
 * into the crawl.
 */
export interface ChaosSetupContext {
    page: Page;
    baseUrl: string;
}
export type ChaosSetupHook = (ctx: ChaosSetupContext) => Promise<void>;
export interface ChaosRunOptions extends CrawlerOptions {
    /** Treat console errors / JS exceptions as failures when computing exitCode. */
    strict?: boolean;
    /**
     * Path to a previous report to diff against. A missing file is treated as
     * "first run" (no diff is produced, no warning raised in the library —
     * the CLI handles the warning). When supplied and readable, `report.diff`
     * is populated.
     */
    baseline?: string;
    /** When true, new regressions vs the baseline force exitCode=1. */
    baselineStrict?: boolean;
    /**
     * Pre-run hook that fires before any chaos action or fault rolls. Receives
     * a Playwright page in a disposable browser context. Typical use is REST
     * seeding via `page.request.post(...)` so the crawler has navigable state
     * to discover. The disposable context does NOT carry into the crawl —
     * propagate shared state through the server (REST) or by saving
     * `storageState` to a path that the main crawler reads.
     */
    setup?: ChaosSetupHook;
    /**
     * Surface server-side fault events into `report.serverFaults`. Phase 1:
     * `{ mode: "remote" }` reads `x-chaos-fault-*` response headers emitted
     * by `@mizchi/server-faults` running in the server process.
     */
    server?: ChaosRemoteServer;
}
export declare function chaos(options: ChaosRunOptions, events?: CrawlerEvents): Promise<ChaosResult>;
export { diffReports, loadBaseline, hasRegressions };
//# sourceMappingURL=chaos.d.ts.map