import type { ResolvedMigrateConfig } from "../lib/config.js";
import type { OutputFormat } from "../lib/format.js";
import { type WranglerRunner } from "../lib/wrangler.js";
export declare function migrateCommand(args: string[], cwd: string, 
/** Injectable wrangler runner — tests pass a mock; production uses the default. */
wranglerRunner?: WranglerRunner, fmt?: OutputFormat): Promise<number>;
/**
 * `meta migrate baseline [--from-db]` — seed the committed reference snapshot.
 * `--from-metadata` (default) derives it from metadata; `--from-db` introspects
 * an existing database once. Emits no migration.
 */
export declare function runBaseline(config: ResolvedMigrateConfig, metaRoot: string, fmt?: OutputFormat): Promise<number>;
/**
 * `meta migrate apply-pending` — replay the committed migration files against the
 * target DB, ledger-tracked and transactional (no diff, no metadata load). This is the
 * fresh-DB / CI provisioning path the diff-first `--apply` cannot serve. postgres/sqlite
 * only (d1 replays via `wrangler d1 migrations apply`). See #242.
 */
export declare function runApplyPending(config: ResolvedMigrateConfig, metaRoot: string, fmt?: OutputFormat): Promise<number>;
/**
 * Default `meta migrate` generate path — fully offline. Diffs metadata against
 * the committed snapshot (no DB), writes up/down.sql, and advances the snapshot.
 * The live-introspection path is used only with --from-db or --apply.
 *
 * Scope: table/column/index/FK changes. Projection-view migrations stay on the
 * introspection path (offline-view parity is a follow-up).
 */
export declare function runOfflineGenerate(config: ResolvedMigrateConfig, metaRoot: string, fmt?: OutputFormat): Promise<number>;
//# sourceMappingURL=migrate.d.ts.map