/**
 * Release-time creation of every framework-owned table.
 *
 * The list is `store-registry.generated.ts`, produced from every
 * `defineStore()` export. Its imports are dynamic so a request cold start never
 * loads the store modules this step walks; `guard:release-schema-complete`
 * fails when a module defines schema outside a registered store or the
 * generated file is stale.
 */
type SchemaEnsure = readonly [name: string, run: () => Promise<void>];
export declare function frameworkSchemaEnsureNames(): string[];
/**
 * Create every framework-owned table, in one pass, before the app serves
 * traffic. Callers must hold migration duty via `withMigrationRuntime`; without
 * it a store only verifies or replays and nothing is recorded in the ledger.
 *
 * Sequential on purpose: these run against one database at release time, where
 * total wall clock does not matter and concurrent `CREATE TABLE` on a shared
 * Neon instance contends for `ACCESS EXCLUSIVE` locks.
 *
 * A failure aborts the release rather than being collected and reported at the
 * end. A half-created schema that reports success is the failure mode this
 * module exists to remove.
 */
export declare function runFrameworkSchemaEnsures(ensures?: readonly SchemaEnsure[]): Promise<void>;
export {};