/**
 * Cloud Postgres migrations for the shortlinks serve service.
 *
 * PURE REMOTE (Amendment A1): these run against the shared RDS Postgres via the
 * vendored storage kit's MigrationLedger. The service reads and writes the same
 * cloud database — there is no local mirror, cache, or sync engine here.
 *
 * The domains/links/clicks schema uses SQLite-parity TEXT/INTEGER shapes so the
 * existing SaaS-remnant tables are matched exactly
 * (every statement is `IF NOT EXISTS` — applying the ledger never clobbers data).
 * The api_keys table migrations come from @hasna/contracts/auth so the API-key
 * middleware and the `contracts issue-key` issuer share one schema.
 */
import { type Migration } from "../generated/storage-kit/migrations.js";
/**
 * Ordered migrations for the shortlinks cloud schema, including the shared
 * api_keys table from @hasna/contracts. Feed straight into the kit's
 * MigrationLedger.
 */
export declare const SHORTLINKS_MIGRATIONS: readonly Migration[];