/**
 * `quickback canary <env>` — Neon branch-canary migration verification.
 *
 * Opt-in, additive step for Neon (Postgres) projects. Given a target
 * environment mapped to a Neon branch (via `providers.database.environments.
 * <env>.branch` in quickback.config.ts), it:
 *
 *   1. Branches the env's Neon branch (copy-on-write).
 *   2. Applies the pending drizzle migrations to the branch.
 *   3. Diffs the branch schema vs its parent and prints the DDL that would land.
 *   4. With `--apply`, applies the verified migrations to the real env DB.
 *   5. Always discards the canary branch.
 *
 * When branching is NOT configured (no env mapping, no NEON_PROJECT_ID, or no
 * NEON_API_KEY) the command is a no-op that points the user at the plain deploy
 * path — existing behavior is untouched.
 *
 * Requires `NEON_API_KEY` (and `NEON_PROJECT_ID` unless `neon.projectId` is in
 * config) in the environment. This is the CI-native gate: run it as a required
 * check on the deploy workflow before `wrangler deploy`.
 */
export declare function canary(args: string[]): Promise<void>;
//# sourceMappingURL=canary.d.ts.map