/** * Per spec 03 § 5.7 + spec 04 § 9.5: one open draft changeset per * (admin user, theme). The draft is named `pb-draft-` and reused * until the user publishes it (which sets `published_at`), saves it as a * rollout plan, or explicitly discards it. * * Theme is part of the draft identity, not the name: the same admin editing * under theme A and under theme B gets two distinct `pb-draft-` * rows, one per theme bucket. The caller captures the active theme once * (`getActiveTheme()`) and passes it in; it is stamped at creation and never * updated for the life of the draft (the "sticky theme" contract, § 9.5). * * The caller still tracks the current route in editor state — that is a * UI concern, not part of the draft identity. A single changeset can * carry operations against multiple routes (each `changeset_operation` * row carries its own `route` column). */ export declare function getOrCreateDraftChangeset(opts: { userId: number; theme: string | null; }): Promise<{ changeset_id: number; uuid: string; token: string; theme: string | null; }>;