/**
 * Type envelope for the `peaks slice check` CLI command.
 *
 * `peaks slice check` is the boundary check for the RD micro-cycle
 * (see `skills/peaks-code/references/micro-cycle.md`). It bundles the
 * 4 self-checks that must pass at slice end before the slice is handed
 * off to peaks-qa:
 *
 *   1. typecheck — the project-local TypeScript entry
 *      (`node_modules/typescript/bin/tsc`) run as `node <entry>`: no
 *      `npx`, no shell. Gates on `-p tsconfig.build.json --noEmit`; the
 *      wider `-p tsconfig.json --noEmit` count is reported against
 *      `TYPECHECK_PREEXISTING_BASELINE` and gates only if it grows.
 *   2. unit tests — by default the **changed-only** suite
 *      (`vitest run --changed`, same `node <entry>` shape via
 *      `node_modules/vitest/vitest.mjs`). Pass `--run-tests` to opt in to
 *      the full suite (`vitest run`); pass `--skip-tests` to skip
 *      entirely (e.g. docs-only or config-only slices).
 *   3. 3-way review fan-out (code-review + security-review + perf-baseline)
 *   4. gate machinery (`peaks workflow verify-pipeline --rid <rid>`)
 *
 * The micro-cycle itself (per-bug TDD) runs OUTSIDE slice check — only
 * single-test runs (`vitest -t "<name>"`) are allowed in micro-cycles.
 * This command is for the BOUNDARY, not the inner loop.
 *
 * The unit-test stage emits a `unitTestsRunMode` field on the result
 * envelope so downstream tooling and the QA test-report can record
 * which mode actually ran: `"changed"` (default), `"full"` (with
 * `--run-tests`), `"skipped"` (with `--skip-tests`), or `"overridden"`
 * (with `--allow-pre-existing-failures` when the run failed and the
 * stage was downgraded to `skipped` with a reason).
 */
export type SliceCheckStageStatus = 'pass' | 'fail' | 'skipped';
export type SliceCheckStage = {
    /** Stable id for the stage (matches the runbook's check list). */
    name: 'typecheck' | 'unit-tests' | 'review-fanout' | 'gate-verify-pipeline' | 'mock-placement' | 'audit-regression';
    /** Human-readable description. */
    description: string;
    status: SliceCheckStageStatus;
    /** Wall-clock duration in ms; null if skipped. */
    durationMs: number | null;
    /** Free-form detail (summary line + last error line). */
    detail: string;
    /** Optional structured data (e.g. test counts, gate counts). */
    data?: Record<string, unknown>;
};
export type SliceCheckResult = {
    /** Absolute project root the command operated on. */
    projectRoot: string;
    /** Request id the boundary check applies to; null if no slice is active. */
    rid: string | null;
    /** All stages in execution order. */
    stages: SliceCheckStage[];
    /**
     * Which unit-test mode actually ran. One of:
     * - `"changed"` — default: `vitest run --changed` (tests for git-changed files only)
     * - `"full"` — opt-in via `--run-tests`: `vitest run` (full suite)
     * - `"skipped"` — opt-in via `--skip-tests` (stage not executed)
     * - `"overridden"` — full mode + `--allow-pre-existing-failures` and the run failed;
     *   stage downgraded to `skipped` with the pre-existing-failure reason
     */
    unitTestsRunMode: 'changed' | 'full' | 'skipped' | 'overridden';
    /** True iff every stage passed (or was skipped) and the boundary is OK to hand off. */
    boundaryReady: boolean;
    /** Total wall-clock duration in ms. */
    totalDurationMs: number;
    /** Next steps suggested when boundaryReady is false. */
    nextActions: string[];
};
export type SliceCheckOptions = {
    projectRoot: string;
    rid?: string;
    /**
     * When true, re-run the 3-way review fan-out (peaks-rd's code-review +
     * security-review + perf-baseline sub-agents) even if the review files
     * already exist. The default is to verify presence and skip if all 3 are present.
     */
    refreshFanout: boolean;
    /**
     * When true, run the **full** `vitest run` suite at the boundary.
     * When false (the default), run the **changed-only** suite
     * (`vitest run --changed`) which only exercises tests related to
     * git-changed files. The changed-only mode is the new default as of
     * run 017 — full suite costs 30s+ on this repo; the changed-only
     * mode costs ~1-3s in steady state and is what catches the
     * regressions that actually matter. The service treats `undefined`
     * the same as `false`.
     */
    runTests?: boolean;
    /**
     * When true, skip the unit-test stage entirely. Useful when a slice
     * has no test surface (e.g. a docs-only or config-only slice), or
     * when the user wants a "typecheck + review + gate" boundary check
     * without any test execution.
     */
    skipTests: boolean;
    /**
     * When true, an `unit-tests` stage that fails is reported as `skipped`
     * (with a `reason` naming the pre-existing failure count) instead of
     * `failed`. Used to opt in to bypassing the 28 pre-existing Windows
     * test failures documented in dogfood-2-f1-f4.md F17. Only meaningful
     * when the unit-test stage actually runs (i.e. not when `skipTests`
     * is true). Does NOT affect the other 3 stages (typecheck /
     * review-fanout / gate-verify-pipeline). Default: false. The service
     * treats `undefined` the same as `false`.
     */
    allowPreExistingFailures?: boolean;
};