export interface MigrateCommandOptions {
    db: string | undefined;
    cwd: string;
    confirm: boolean | undefined;
    allowDestructive: boolean | undefined;
    acknowledgeLock: boolean | undefined;
}
export declare function migrate(options: MigrateCommandOptions): Promise<void>;
/**
 * `--allow-destructive` / `--acknowledge-lock` authorized an *invocation*, so
 * the first destructive migration that had to ship put them into a deploy
 * workflow permanently and every migration after that was pre-approved by a
 * decision nobody revisits. Authorization is per-migration now, declared in
 * the file that raises the hazard, where review can see it.
 *
 * Failing loudly rather than ignoring them is the point: a pipeline still
 * passing these is a pipeline that has been running ungated.
 *
 * Returns the error text, or null when neither flag was passed.
 */
export declare function rejectRetiredFlags(options: {
    allowDestructive: boolean | undefined;
    acknowledgeLock: boolean | undefined;
}): string | null;
//# sourceMappingURL=migrate.d.ts.map