/**
 * Render an unexpected CLI failure as one legible stderr message instead of a V8 stack trace.
 *
 * `node-version-bootstrap.ts` already holds the line for an unsupported Node: "one legible
 * stderr line and a stable exit code, never a stack trace". Everything else had no such line.
 * A throw from any command action — Commander awaits them, so a rejection became an unhandled
 * rejection — printed the raw trace: the absolute path of a file inside `dist/`, the internal
 * frame list, and the Node version banner. The most common way a real user met it was a
 * path-confinement refusal during `install` (a `CLAUDE.md` symlinked out to a dotfiles
 * repository), where the trace named `path-confinement.js` and nothing a user could act on.
 *
 * This module stays pure so the rendering is unit-testable; `crash-reporter.ts` is the
 * bootstrap that binds it to the process.
 */
/**
 * The actionable explanation for a failure shape we recognize, or null when there is nothing
 * honest to add. Deliberately short: a cause and the choices, never a guess at intent.
 */
export declare function explainFailure(message: string): string | null;
/**
 * The stderr text for an unexpected failure. `verbose` adds the stack, which is the only place
 * it belongs: the message tells a user what happened, the stack tells us where.
 */
export declare function renderCrash(error: unknown, opts?: {
    command?: string;
    verbose?: boolean;
}): string;
//# sourceMappingURL=crash-report.d.ts.map