/**
 * Confirmation for actions that cannot be undone.
 *
 * The prompt import stays lazy (matching `agents setup`) and the policy lives here
 * rather than in the commands, so every destructive command shares one behaviour
 * instead of each inventing its own. `encoding jobs delete` and `encoding jobs stop`
 * can adopt {@link confirmDestructive} without a fourth variant.
 */
/** `--yes` / `-y` (alias `--confirm`) for any command guarded by {@link confirmDestructive}. */
export declare const yesFlag: import("@oclif/core/interfaces").BooleanFlag<boolean>;
/** Whether an interactive prompt can be shown at all. */
export declare function canPrompt(): boolean;
/** Resolves to true only on an explicit yes; defaults to no. */
export declare function confirmAction(message: string): Promise<boolean>;
/**
 * The outcome of the gate.
 *
 * `unconfirmable` means we could not ask and were not told to proceed — the caller
 * must fail rather than act. Keeping that a distinct outcome (instead of `false`) is
 * deliberate: "the user said no" and "nobody could be asked" deserve different exit
 * codes, and collapsing them is how a scripted run ends up filing something silently.
 */
export type ConfirmOutcome = 'proceed' | 'declined' | 'unconfirmable';
/**
 * Decides whether a destructive action may proceed.
 *
 * Fails closed: without `--yes`, a non-TTY (either direction) or JSON mode yields
 * `unconfirmable`, never `proceed`.
 */
export declare function confirmDestructive(options: {
    jsonMode: boolean;
    yes: boolean;
    question: string;
}): Promise<ConfirmOutcome>;
//# sourceMappingURL=confirm.d.ts.map