@beignet/provider-db-drizzle 0.0.23 → 0.0.25

package/CHANGELOG.md

@@ -1,5 +1,13 @@
 # @beignet/provider-db-drizzle
 
+## 0.0.25
+
+### Patch Changes
+
+- 1f84b39: Add provider table metadata diagnostics, Drizzle operational schema exports, and `beignet db schema generate` for app-owned migration flows.
+
+## 0.0.24
+
 ## 0.0.23
 
 ### Patch Changes

package/README.md

@@ -97,6 +97,26 @@ export const todos = sqliteTable("todos", {
 export { todos } from "./todos";
 ```
 
+If the app uses Beignet's Drizzle-backed operational ports for audit,
+idempotency, or outbox, generate the provider-owned table exports into the app
+schema:
+
+```bash
+bun beignet db schema generate
+```
+
+That writes `infra/db/schema/beignet.ts` and adds
+`export * from "./beignet";` to `infra/db/schema/index.ts`. After that, run the
+normal app-owned migration flow:
+
+```bash
+bun beignet db generate
+bun beignet db migrate
+```
+
+Use `--tables audit,idempotency,outbox` to select a subset when adopting one
+operational port at a time.
+
 ### 2. Configure Drizzle CLI (build-time)
 
 Create `drizzle.config.ts` in your app root for the Drizzle CLI:
@@ -1079,6 +1099,19 @@ All exports below come from `@beignet/provider-db-drizzle/sqlite`. The
 provider options (`pool`, and `mode` for MySQL), the `DbPort` escape hatch
 (`pool` instead of `client`), and the mutation error class names.
 
+### Schema subpaths
+
+Each backend also exports canonical Beignet operational table definitions:
+
+- `@beignet/provider-db-drizzle/sqlite/schema`
+- `@beignet/provider-db-drizzle/postgres/schema`
+- `@beignet/provider-db-drizzle/mysql/schema`
+
+Each schema subpath exports `auditLog`, `idempotencyRecords`, and
+`outboxMessages`. Prefer `beignet db schema generate` in apps so the selected
+exports are re-exported from your app schema index before Drizzle Kit generates
+migrations.
+
 ### `DbPort<TSchema>`
 
 The port interface exposed on `ctx.ports.db`: