import type { EmitResult } from "./types.js";
export interface WriteMigrationFlywayOptions {
    /** Flyway migrations dir (e.g. "src/main/resources/db/migration"). Created if missing. */
    dir: string;
    /** Human-readable slug; sanitized to lowercase + underscores. */
    slug: string;
}
export interface WriteMigrationFlywayResult {
    /** Full path to the versioned (V) migration. */
    upPath: string;
    /** Full path to the undo (U) migration. */
    downPath: string;
    /** Assigned version number (e.g. 1, 2, 11). */
    version: number;
}
/**
 * #192 — the ADR-0015 Flyway-prefix output adapter.
 *
 * Emits the engine's already-computed up/down SQL in Flyway's envelope:
 * `V<N>__<slug>.sql` plus `U<N>__<slug>.sql`. Undo is a paid Flyway edition
 * feature — Community IGNORES `U__` files rather than failing on them — so the
 * undo file is inert-but-correct there and becomes live on Teams/Enterprise.
 *
 * Applying is deliberately NOT our job here: Flyway owns apply and its
 * `flyway_schema_history`. The CLI refuses --apply / apply-pending / --rollback
 * under this format rather than desyncing that history.
 */
export declare function writeMigrationFlyway(result: Pick<EmitResult, "up" | "down">, opts: WriteMigrationFlywayOptions): Promise<WriteMigrationFlywayResult>;
//# sourceMappingURL=write-migration-flyway.d.ts.map