qubu 0.5.1 → 0.6.0

package/docs/reference/mysql-snapshot.md

@@ -4,13 +4,13 @@
 > MySQL facts Qubu v1 can encode and the combinations that need a later server
 > version or engine policy.
 
-Import the adapter from the optional snapshot entrypoint:
+Import the adapter from the MySQL snapshot subpath:
 
 ```ts
-import { createMysqlSchemaSnapshot, tryCreateMysqlSchemaSnapshot } from "qubu/snapshot"
+import { createSchemaSnapshot, tryCreateSchemaSnapshot } from "qubu/snapshot/mysql"
 
-const snapshot = createMysqlSchemaSnapshot(appSchema)
-const result = tryCreateMysqlSchemaSnapshot(appSchema)
+const snapshot = createSchemaSnapshot(appSchema)
+const result = tryCreateSchemaSnapshot(appSchema)
 ```
 
 The snapshot dialect is named `mysql`, the same name used by Qubu's query
@@ -38,7 +38,7 @@ Capability checks run before common traversal. Use the non-throwing form when
 a schema may include a MySQL engine or version-specific feature:
 
 ```ts
-const result = tryCreateMysqlSchemaSnapshot(appSchema)
+const result = tryCreateSchemaSnapshot(appSchema)
 if (!result.ok) {
   for (const issue of result.diagnostics) {
     console.error(issue.path.join("."), issue.code, issue.message)

package/docs/reference/postgres-snapshot.md

@@ -4,16 +4,16 @@
 > PostgreSQL facts Qubu v1 can encode and the cases that need a later server
 > version policy.
 
-Import the adapter from the optional snapshot entrypoint:
+Import the adapter from the PostgreSQL snapshot subpath:
 
 ```ts
+import { createSchemaSnapshot } from "qubu/snapshot"
 import {
-  createSchemaSnapshot,
-  createPostgresSchemaSnapshot,
+  createSchemaSnapshot as createPostgresSnapshot,
   postgresSnapshotAdapter,
-} from "qubu/snapshot"
+} from "qubu/snapshot/postgres"
 
-const snapshot = createPostgresSchemaSnapshot(appSchema)
+const snapshot = createPostgresSnapshot(appSchema)
 // Equivalent: createSchemaSnapshot(appSchema, { adapter: postgresSnapshotAdapter })
 ```
 
@@ -46,9 +46,9 @@ schema and application boundaries.
 Use the non-throwing form when a schema may contain a server-specific feature:
 
 ```ts
-import { tryCreatePostgresSchemaSnapshot } from "qubu/snapshot"
+import { tryCreateSchemaSnapshot } from "qubu/snapshot/postgres"
 
-const result = tryCreatePostgresSchemaSnapshot(appSchema)
+const result = tryCreateSchemaSnapshot(appSchema)
 if (!result.ok) {
   for (const issue of result.diagnostics) {
     console.error(issue.path.join("."), issue.code, issue.message)

package/docs/reference/sqlite-snapshot.md

@@ -2,13 +2,13 @@
 
 > Use this matrix to decide which SQLite schema facts Qubu v1 can serialize and which combinations must be diagnosed before a snapshot is written.
 
-Import the adapter from the optional snapshot entrypoint:
+Import the adapter from the SQLite snapshot subpath:
 
 ```ts
-import { createSqliteSchemaSnapshot, tryCreateSqliteSchemaSnapshot } from "qubu/snapshot"
+import { createSchemaSnapshot, tryCreateSchemaSnapshot } from "qubu/snapshot/sqlite"
 
-const snapshot = createSqliteSchemaSnapshot(appSchema)
-const result = tryCreateSqliteSchemaSnapshot(appSchema)
+const snapshot = createSchemaSnapshot(appSchema)
+const result = tryCreateSchemaSnapshot(appSchema)
 ```
 
 The snapshot dialect is `sqlite`, the same name used by Qubu's query dialect.
@@ -36,7 +36,7 @@ Capability checks run before common traversal. Use the non-throwing form when a
 schema may include a feature that depends on a SQLite version or table shape:
 
 ```ts
-const result = tryCreateSqliteSchemaSnapshot(appSchema)
+const result = tryCreateSchemaSnapshot(appSchema)
 if (!result.ok) {
   for (const issue of result.diagnostics) {
     console.error(issue.path.join("."), issue.code, issue.message)

package/docs/reference/supported-surface.md

@@ -15,6 +15,9 @@
 | `qubu/postgres`                           | Runtime          | PostgreSQL query dialect helpers such as `postgresDialect()` and `ilike()`                                       |
 | `qubu/schema`                             | Runtime          | Advanced schema metadata, storage and constraint models, source models, and schema-expression extensions         |
 | `qubu/snapshot`                           | Runtime          | Canonical Snapshot v1 and v2 traversal, encoding, decoding, diagnostics, and fingerprints                        |
+| `qubu/snapshot/mysql`                     | Runtime          | MySQL snapshot adapter, schema dialect, and convenience creators                                                 |
+| `qubu/snapshot/postgres`                  | Runtime          | PostgreSQL snapshot adapter, schema dialect, and convenience creators                                            |
+| `qubu/snapshot/sqlite`                    | Runtime          | SQLite snapshot adapter, schema dialect, affinity helper, and convenience creators                               |
 | `qubu/sqlite`                             | Runtime          | The SQLite query dialect policy and native SQLite column factories                                               |
 | `qubu/vite`                               | Runtime          | The optional `qubu()` Vite compiler hint                                                                         |
 | `qubu/package.json`                       | JSON             | The published package manifest                                                                                   |

package/docs/schema/code-generation.md

@@ -49,10 +49,10 @@ baseline for the next catalog read:
 
 ```ts
 import { mapCatalogToSnapshot } from "qubu/introspection"
-import { createSqliteSchemaSnapshot } from "qubu/snapshot"
+import { createSchemaSnapshot } from "qubu/snapshot/sqlite"
 import { mainSchema } from "./schema.generated.ts"
 
-const previousSnapshot = createSqliteSchemaSnapshot(mainSchema)
+const previousSnapshot = createSchemaSnapshot(mainSchema)
 const next = mapCatalogToSnapshot(nextCatalog, {
   namespace: "main",
   previousSnapshot,

package/docs/schema/ddl-emission.md

@@ -9,7 +9,7 @@ plan returns diagnostics and no SQL.
 
 ```ts
 import { emitMigrationPlan } from "@qubu/migrate/ddl"
-import { postgresSchemaDialect } from "qubu/snapshot"
+import { postgresSchemaDialect } from "qubu/snapshot/postgres"
 
 const result = emitMigrationPlan(plan, postgresSchemaDialect)
 if (!result.ok) {

package/docs/schema/snapshots.md

@@ -65,6 +65,18 @@ envelope. A dialect adapter owns physical storage mapping, SQL literal and
 expression encoding, dialect extensions, capability checks, and any dialect
 naming policy. PostgreSQL, SQLite, and MySQL adapters can implement
 `SchemaSnapshotAdapter` without duplicating traversal or decoder rules.
+The neutral API stays at `qubu/snapshot`; built-in dialect adapters have
+dedicated subpaths so importing neutral snapshot utilities does not widen that
+API:
+
+```ts
+import { createSchemaSnapshot } from "qubu/snapshot"
+import { createSchemaSnapshot as createPostgresSnapshot } from "qubu/snapshot/postgres"
+
+const neutral = createSchemaSnapshot(appSchema)
+const postgres = createPostgresSnapshot(appSchema)
+```
+
 The PostgreSQL adapter is documented in the [PostgreSQL snapshot support
 matrix](../reference/postgres-snapshot.md). Its schema dialect extends the
 `postgresql` query dialect, and snapshot metadata uses that same identity.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "qubu",
-  "version": "0.5.1",
+  "version": "0.6.0",
   "repository": {
     "type": "git",
     "url": "https://github.com/aleclarson/qubu"
@@ -48,6 +48,18 @@
       "types": "./dist/snapshot.d.mts",
       "import": "./dist/snapshot.mjs"
     },
+    "./snapshot/mysql": {
+      "types": "./dist/snapshot/mysql.d.mts",
+      "import": "./dist/snapshot/mysql.mjs"
+    },
+    "./snapshot/postgres": {
+      "types": "./dist/snapshot/postgres.d.mts",
+      "import": "./dist/snapshot/postgres.mjs"
+    },
+    "./snapshot/sqlite": {
+      "types": "./dist/snapshot/sqlite.d.mts",
+      "import": "./dist/snapshot/sqlite.mjs"
+    },
     "./sqlite": {
       "types": "./dist/sqlite.d.mts",
       "import": "./dist/sqlite.mjs"