turbine-orm 0.50.0 → 0.51.0

package/dist/adapters/yugabytedb.d.ts

@@ -1,5 +1,5 @@
 /**
- * turbine-orm — YugabyteDB adapter
+ * turbine-orm, YugabyteDB adapter
  *
  * YugabyteDB is a distributed SQL database that speaks the PostgreSQL wire
  * protocol. It supports most PostgreSQL features including json_agg,
@@ -7,28 +7,28 @@
  *
  * Key differences from PostgreSQL that this adapter addresses:
  *
- * 1. **Advisory locks are per-node** — `pg_try_advisory_lock()` is supported
+ * 1. **Advisory locks are per-node**, `pg_try_advisory_lock()` is supported
  *    but only scoped to the tserver node handling the connection. In a
  *    multi-node cluster, two concurrent `turbine migrate` runs routed to
  *    different nodes would both acquire the "same" advisory lock. This adapter
  *    provides a table-based distributed lock using `SELECT FOR UPDATE NOWAIT`
  *    which is cluster-wide via YugabyteDB's distributed transactions.
  *
- * 2. **Sequences may have gaps** — YugabyteDB uses distributed sequences.
+ * 2. **Sequences may have gaps**, YugabyteDB uses distributed sequences.
  *    SERIAL/BIGSERIAL columns work correctly but may produce non-contiguous
  *    IDs under concurrent inserts. This is purely cosmetic and does not affect
  *    Turbine's behavior.
  *
- * 3. **pg_catalog** — Mostly complete. `pg_indexes`, `pg_type`, `pg_enum`,
+ * 3. **pg_catalog**, Mostly complete. `pg_indexes`, `pg_type`, `pg_enum`,
  *    `information_schema.columns` all work. Row estimate via `pg_class.reltuples`
  *    may be stale or zero on recently created tables (YugabyteDB's stats
  *    collection is asynchronous). This adapter provides an override that
  *    falls back to `yb_table_properties` when available.
  *
  * Features that work identically to PostgreSQL (no adapter override needed):
- * - `json_agg` / `json_build_object` — fully supported
- * - Correlated subqueries — fully supported
- * - `COALESCE`, `LIMIT`, `OFFSET`, `ORDER BY` — fully supported
+ * - `json_agg` / `json_build_object`, fully supported
+ * - Correlated subqueries, fully supported
+ * - `COALESCE`, `LIMIT`, `OFFSET`, `ORDER BY`, fully supported
  * - `information_schema` for table/column/constraint introspection
  * - Extended query protocol (parameterized queries, pipeline batching)
  * - Transactions with `SAVEPOINT` (nested transactions)

package/dist/adapters/yugabytedb.js

@@ -1,5 +1,5 @@
 /**
- * turbine-orm — YugabyteDB adapter
+ * turbine-orm, YugabyteDB adapter
  *
  * YugabyteDB is a distributed SQL database that speaks the PostgreSQL wire
  * protocol. It supports most PostgreSQL features including json_agg,
@@ -7,28 +7,28 @@
  *
  * Key differences from PostgreSQL that this adapter addresses:
  *
- * 1. **Advisory locks are per-node** — `pg_try_advisory_lock()` is supported
+ * 1. **Advisory locks are per-node**, `pg_try_advisory_lock()` is supported
  *    but only scoped to the tserver node handling the connection. In a
  *    multi-node cluster, two concurrent `turbine migrate` runs routed to
  *    different nodes would both acquire the "same" advisory lock. This adapter
  *    provides a table-based distributed lock using `SELECT FOR UPDATE NOWAIT`
  *    which is cluster-wide via YugabyteDB's distributed transactions.
  *
- * 2. **Sequences may have gaps** — YugabyteDB uses distributed sequences.
+ * 2. **Sequences may have gaps**, YugabyteDB uses distributed sequences.
  *    SERIAL/BIGSERIAL columns work correctly but may produce non-contiguous
  *    IDs under concurrent inserts. This is purely cosmetic and does not affect
  *    Turbine's behavior.
  *
- * 3. **pg_catalog** — Mostly complete. `pg_indexes`, `pg_type`, `pg_enum`,
+ * 3. **pg_catalog**, Mostly complete. `pg_indexes`, `pg_type`, `pg_enum`,
  *    `information_schema.columns` all work. Row estimate via `pg_class.reltuples`
  *    may be stale or zero on recently created tables (YugabyteDB's stats
  *    collection is asynchronous). This adapter provides an override that
  *    falls back to `yb_table_properties` when available.
  *
  * Features that work identically to PostgreSQL (no adapter override needed):
- * - `json_agg` / `json_build_object` — fully supported
- * - Correlated subqueries — fully supported
- * - `COALESCE`, `LIMIT`, `OFFSET`, `ORDER BY` — fully supported
+ * - `json_agg` / `json_build_object`, fully supported
+ * - Correlated subqueries, fully supported
+ * - `COALESCE`, `LIMIT`, `OFFSET`, `ORDER BY`, fully supported
  * - `information_schema` for table/column/constraint introspection
  * - Extended query protocol (parameterized queries, pipeline batching)
  * - Transactions with `SAVEPOINT` (nested transactions)
@@ -105,7 +105,7 @@ export const yugabytedb = {
             await client.query(`SELECT lock_id FROM "${LOCK_TABLE}" WHERE lock_id = $1 FOR UPDATE NOWAIT`, [lockId]);
             // Update acquisition metadata for observability
             await client.query(`UPDATE "${LOCK_TABLE}" SET acquired_at = now(), acquired_by = current_user WHERE lock_id = $1`, [lockId]);
-            // Leave the transaction open — lock is held until releaseLock()
+            // Leave the transaction open, lock is held until releaseLock()
             return true;
         }
         catch (err) {
@@ -120,7 +120,7 @@ export const yugabytedb = {
                 }
                 return false;
             }
-            // Any other error — rollback and re-throw
+            // Any other error, rollback and re-throw
             try {
                 await client.query('ROLLBACK');
             }
@@ -136,7 +136,7 @@ export const yugabytedb = {
             await client.query('COMMIT');
         }
         catch {
-            // If commit fails, try rollback — either way the lock is released
+            // If commit fails, try rollback, either way the lock is released
             try {
                 await client.query('ROLLBACK');
             }

package/dist/cjs/adapters/cockroachdb.d.ts

@@ -1,20 +1,20 @@
 /**
- * turbine-orm — CockroachDB adapter
+ * turbine-orm, CockroachDB adapter
  *
  * CockroachDB speaks the PostgreSQL wire protocol but has key differences:
  *
- * 1. **No advisory locks** — `pg_try_advisory_lock()` is not supported.
+ * 1. **No advisory locks**, `pg_try_advisory_lock()` is not supported.
  *    This adapter uses a `_turbine_lock` table with `SELECT FOR UPDATE NOWAIT`
  *    as a concurrency mechanism for migrations.
  *
- * 2. **No `SET LOCAL statement_timeout`** — CockroachDB uses
+ * 2. **No `SET LOCAL statement_timeout`**, CockroachDB uses
  *    `SET transaction_timeout` (v23.1+) for per-transaction time limits.
  *
- * 3. **`pg_indexes` view** — CockroachDB supports `pg_indexes` since v22.1
+ * 3. **`pg_indexes` view**, CockroachDB supports `pg_indexes` since v22.1
  *    but the `indexdef` column may not match Postgres exactly. We use
  *    `SHOW INDEXES` as a more reliable alternative.
  *
- * 4. **`pg_class.reltuples`** — Not reliable in CockroachDB. We use
+ * 4. **`pg_class.reltuples`**, Not reliable in CockroachDB. We use
  *    `crdb_internal.table_row_statistics` for row estimates.
  *
  * Known limitations with Turbine on CockroachDB:

package/dist/cjs/adapters/cockroachdb.js

@@ -1,21 +1,21 @@
 "use strict";
 /**
- * turbine-orm — CockroachDB adapter
+ * turbine-orm, CockroachDB adapter
  *
  * CockroachDB speaks the PostgreSQL wire protocol but has key differences:
  *
- * 1. **No advisory locks** — `pg_try_advisory_lock()` is not supported.
+ * 1. **No advisory locks**, `pg_try_advisory_lock()` is not supported.
  *    This adapter uses a `_turbine_lock` table with `SELECT FOR UPDATE NOWAIT`
  *    as a concurrency mechanism for migrations.
  *
- * 2. **No `SET LOCAL statement_timeout`** — CockroachDB uses
+ * 2. **No `SET LOCAL statement_timeout`**, CockroachDB uses
  *    `SET transaction_timeout` (v23.1+) for per-transaction time limits.
  *
- * 3. **`pg_indexes` view** — CockroachDB supports `pg_indexes` since v22.1
+ * 3. **`pg_indexes` view**, CockroachDB supports `pg_indexes` since v22.1
  *    but the `indexdef` column may not match Postgres exactly. We use
  *    `SHOW INDEXES` as a more reliable alternative.
  *
- * 4. **`pg_class.reltuples`** — Not reliable in CockroachDB. We use
+ * 4. **`pg_class.reltuples`**, Not reliable in CockroachDB. We use
  *    `crdb_internal.table_row_statistics` for row estimates.
  *
  * Known limitations with Turbine on CockroachDB:
@@ -72,7 +72,7 @@ const SQL_INDEXES_CRDB = `
 `;
 /**
  * Row estimates using crdb_internal. Falls back gracefully if the view
- * doesn't exist (permissions issue) — returns 0 rows in that case.
+ * doesn't exist (permissions issue), returns 0 rows in that case.
  */
 const SQL_ROW_ESTIMATES_CRDB = `
   SELECT
@@ -85,7 +85,7 @@ const SQL_ROW_ESTIMATES_CRDB = `
     AND t.database_name = current_database()
 `;
 /**
- * Enum introspection — CockroachDB supports pg_type/pg_enum since v20.2.
+ * Enum introspection, CockroachDB supports pg_type/pg_enum since v20.2.
  * The standard query works, but we include it explicitly so the override
  * mechanism is complete.
  */
@@ -110,13 +110,13 @@ exports.cockroachdb = {
         await client.query(CREATE_LOCK_TABLE_SQL);
         // Insert the lock row if it doesn't exist (idempotent)
         await client.query(`INSERT INTO "${LOCK_TABLE}" (lock_id) VALUES ($1) ON CONFLICT (lock_id) DO NOTHING`, [lockId]);
-        // Try to acquire the row lock with NOWAIT — fails immediately if held
+        // Try to acquire the row lock with NOWAIT, fails immediately if held
         try {
             await client.query('BEGIN');
             await client.query(`SELECT lock_id FROM "${LOCK_TABLE}" WHERE lock_id = $1 FOR UPDATE NOWAIT`, [lockId]);
             // Update the acquired metadata
             await client.query(`UPDATE "${LOCK_TABLE}" SET acquired_at = now(), acquired_by = current_user WHERE lock_id = $1`, [lockId]);
-            // Note: we leave the transaction OPEN — the lock is held until
+            // Note: we leave the transaction OPEN, the lock is held until
             // releaseLock() commits or rolls back.
             return true;
         }
@@ -132,7 +132,7 @@ exports.cockroachdb = {
                 }
                 return false;
             }
-            // Any other error — rollback and re-throw
+            // Any other error, rollback and re-throw
             try {
                 await client.query('ROLLBACK');
             }

package/dist/cjs/adapters/index.d.ts

@@ -1,9 +1,9 @@
 /**
- * turbine-orm — Database adapter interface
+ * turbine-orm, Database adapter interface
  *
  * Adapters allow Turbine to work with PostgreSQL-compatible databases that
  * have subtle differences (e.g. CockroachDB, YugabyteDB). The default
- * behavior remains standard PostgreSQL — adapters only override specific
+ * behavior remains standard PostgreSQL, adapters only override specific
  * operations where compatibility gaps exist.
  *
  * @example
@@ -57,9 +57,9 @@ export interface DatabaseAdapter {
      * Generate the SQL to set a statement timeout within a transaction.
      * PostgreSQL uses `SELECT set_config('statement_timeout', $1, true)`.
      * CockroachDB uses `SELECT set_config('transaction_timeout', $1, true)` (v23.1+).
-     * (`SET LOCAL ... = $1` is a syntax error — SET takes no bind params.)
+     * (`SET LOCAL ... = $1` is a syntax error, SET takes no bind params.)
      *
-     * @param seconds — timeout in seconds
+     * @param seconds, timeout in seconds
      * @returns an object with the parameterized SQL and its bound values
      */
     statementTimeout?(seconds: number): {
@@ -79,7 +79,7 @@ export interface DatabaseAdapter {
 export declare const postgresql: DatabaseAdapter;
 /**
  * Google AlloyDB adapter. AlloyDB is PostgreSQL with Google's columnar storage
- * engine. It is wire-protocol and catalog-compatible — no adapter overrides
+ * engine. It is wire-protocol and catalog-compatible, no adapter overrides
  * are needed. All Turbine features (json_agg, advisory locks, introspection,
  * migrations) work identically to standard PostgreSQL.
  *

package/dist/cjs/adapters/index.js

@@ -1,10 +1,10 @@
 "use strict";
 /**
- * turbine-orm — Database adapter interface
+ * turbine-orm, Database adapter interface
  *
  * Adapters allow Turbine to work with PostgreSQL-compatible databases that
  * have subtle differences (e.g. CockroachDB, YugabyteDB). The default
- * behavior remains standard PostgreSQL — adapters only override specific
+ * behavior remains standard PostgreSQL, adapters only override specific
  * operations where compatibility gaps exist.
  *
  * @example
@@ -18,7 +18,7 @@
 Object.defineProperty(exports, "__esModule", { value: true });
 exports.yugabytedb = exports.cockroachdb = exports.timescale = exports.alloydb = exports.postgresql = void 0;
 // ---------------------------------------------------------------------------
-// Default PostgreSQL adapter (no-op — standard behavior)
+// Default PostgreSQL adapter (no-op, standard behavior)
 // ---------------------------------------------------------------------------
 /**
  * The default PostgreSQL adapter. Uses pg_try_advisory_lock, standard
@@ -34,18 +34,18 @@ exports.postgresql = {
         await client.query(`SELECT pg_advisory_unlock($1)`, [lockId]);
     },
     statementTimeout(seconds) {
-        // `SET LOCAL ... = $1` is a Postgres syntax error — SET does not accept
+        // `SET LOCAL ... = $1` is a Postgres syntax error, SET does not accept
         // bind parameters. `set_config(name, value, is_local=true)` is the
         // parameterizable, transaction-local equivalent.
         return { sql: `SELECT set_config('statement_timeout', $1, true)`, params: [`${seconds}s`] };
     },
 };
 // ---------------------------------------------------------------------------
-// AlloyDB — fully PostgreSQL-compatible, no adapter logic needed
+// AlloyDB, fully PostgreSQL-compatible, no adapter logic needed
 // ---------------------------------------------------------------------------
 /**
  * Google AlloyDB adapter. AlloyDB is PostgreSQL with Google's columnar storage
- * engine. It is wire-protocol and catalog-compatible — no adapter overrides
+ * engine. It is wire-protocol and catalog-compatible, no adapter overrides
  * are needed. All Turbine features (json_agg, advisory locks, introspection,
  * migrations) work identically to standard PostgreSQL.
  *
@@ -61,7 +61,7 @@ exports.alloydb = {
     name: 'alloydb',
 };
 // ---------------------------------------------------------------------------
-// TimescaleDB — PostgreSQL extension, fully compatible
+// TimescaleDB, PostgreSQL extension, fully compatible
 // ---------------------------------------------------------------------------
 /**
  * TimescaleDB adapter. Timescale is a PostgreSQL extension that adds

package/dist/cjs/adapters/yugabytedb.d.ts

@@ -1,5 +1,5 @@
 /**
- * turbine-orm — YugabyteDB adapter
+ * turbine-orm, YugabyteDB adapter
  *
  * YugabyteDB is a distributed SQL database that speaks the PostgreSQL wire
  * protocol. It supports most PostgreSQL features including json_agg,
@@ -7,28 +7,28 @@
  *
  * Key differences from PostgreSQL that this adapter addresses:
  *
- * 1. **Advisory locks are per-node** — `pg_try_advisory_lock()` is supported
+ * 1. **Advisory locks are per-node**, `pg_try_advisory_lock()` is supported
  *    but only scoped to the tserver node handling the connection. In a
  *    multi-node cluster, two concurrent `turbine migrate` runs routed to
  *    different nodes would both acquire the "same" advisory lock. This adapter
  *    provides a table-based distributed lock using `SELECT FOR UPDATE NOWAIT`
  *    which is cluster-wide via YugabyteDB's distributed transactions.
  *
- * 2. **Sequences may have gaps** — YugabyteDB uses distributed sequences.
+ * 2. **Sequences may have gaps**, YugabyteDB uses distributed sequences.
  *    SERIAL/BIGSERIAL columns work correctly but may produce non-contiguous
  *    IDs under concurrent inserts. This is purely cosmetic and does not affect
  *    Turbine's behavior.
  *
- * 3. **pg_catalog** — Mostly complete. `pg_indexes`, `pg_type`, `pg_enum`,
+ * 3. **pg_catalog**, Mostly complete. `pg_indexes`, `pg_type`, `pg_enum`,
  *    `information_schema.columns` all work. Row estimate via `pg_class.reltuples`
  *    may be stale or zero on recently created tables (YugabyteDB's stats
  *    collection is asynchronous). This adapter provides an override that
  *    falls back to `yb_table_properties` when available.
  *
  * Features that work identically to PostgreSQL (no adapter override needed):
- * - `json_agg` / `json_build_object` — fully supported
- * - Correlated subqueries — fully supported
- * - `COALESCE`, `LIMIT`, `OFFSET`, `ORDER BY` — fully supported
+ * - `json_agg` / `json_build_object`, fully supported
+ * - Correlated subqueries, fully supported
+ * - `COALESCE`, `LIMIT`, `OFFSET`, `ORDER BY`, fully supported
  * - `information_schema` for table/column/constraint introspection
  * - Extended query protocol (parameterized queries, pipeline batching)
  * - Transactions with `SAVEPOINT` (nested transactions)

package/dist/cjs/adapters/yugabytedb.js

@@ -1,6 +1,6 @@
 "use strict";
 /**
- * turbine-orm — YugabyteDB adapter
+ * turbine-orm, YugabyteDB adapter
  *
  * YugabyteDB is a distributed SQL database that speaks the PostgreSQL wire
  * protocol. It supports most PostgreSQL features including json_agg,
@@ -8,28 +8,28 @@
  *
  * Key differences from PostgreSQL that this adapter addresses:
  *
- * 1. **Advisory locks are per-node** — `pg_try_advisory_lock()` is supported
+ * 1. **Advisory locks are per-node**, `pg_try_advisory_lock()` is supported
  *    but only scoped to the tserver node handling the connection. In a
  *    multi-node cluster, two concurrent `turbine migrate` runs routed to
  *    different nodes would both acquire the "same" advisory lock. This adapter
  *    provides a table-based distributed lock using `SELECT FOR UPDATE NOWAIT`
  *    which is cluster-wide via YugabyteDB's distributed transactions.
  *
- * 2. **Sequences may have gaps** — YugabyteDB uses distributed sequences.
+ * 2. **Sequences may have gaps**, YugabyteDB uses distributed sequences.
  *    SERIAL/BIGSERIAL columns work correctly but may produce non-contiguous
  *    IDs under concurrent inserts. This is purely cosmetic and does not affect
  *    Turbine's behavior.
  *
- * 3. **pg_catalog** — Mostly complete. `pg_indexes`, `pg_type`, `pg_enum`,
+ * 3. **pg_catalog**, Mostly complete. `pg_indexes`, `pg_type`, `pg_enum`,
  *    `information_schema.columns` all work. Row estimate via `pg_class.reltuples`
  *    may be stale or zero on recently created tables (YugabyteDB's stats
  *    collection is asynchronous). This adapter provides an override that
  *    falls back to `yb_table_properties` when available.
  *
  * Features that work identically to PostgreSQL (no adapter override needed):
- * - `json_agg` / `json_build_object` — fully supported
- * - Correlated subqueries — fully supported
- * - `COALESCE`, `LIMIT`, `OFFSET`, `ORDER BY` — fully supported
+ * - `json_agg` / `json_build_object`, fully supported
+ * - Correlated subqueries, fully supported
+ * - `COALESCE`, `LIMIT`, `OFFSET`, `ORDER BY`, fully supported
  * - `information_schema` for table/column/constraint introspection
  * - Extended query protocol (parameterized queries, pipeline batching)
  * - Transactions with `SAVEPOINT` (nested transactions)
@@ -108,7 +108,7 @@ exports.yugabytedb = {
             await client.query(`SELECT lock_id FROM "${LOCK_TABLE}" WHERE lock_id = $1 FOR UPDATE NOWAIT`, [lockId]);
             // Update acquisition metadata for observability
             await client.query(`UPDATE "${LOCK_TABLE}" SET acquired_at = now(), acquired_by = current_user WHERE lock_id = $1`, [lockId]);
-            // Leave the transaction open — lock is held until releaseLock()
+            // Leave the transaction open, lock is held until releaseLock()
             return true;
         }
         catch (err) {
@@ -123,7 +123,7 @@ exports.yugabytedb = {
                 }
                 return false;
             }
-            // Any other error — rollback and re-throw
+            // Any other error, rollback and re-throw
             try {
                 await client.query('ROLLBACK');
             }
@@ -139,7 +139,7 @@ exports.yugabytedb = {
             await client.query('COMMIT');
         }
         catch {
-            // If commit fails, try rollback — either way the lock is released
+            // If commit fails, try rollback, either way the lock is released
             try {
                 await client.query('ROLLBACK');
             }

package/dist/cjs/cli/config.d.ts

@@ -1,5 +1,5 @@
 /**
- * turbine-orm CLI — Configuration file support
+ * turbine-orm CLI, Configuration file support
  *
  * Loads turbine.config.ts (or .js/.mjs) via dynamic import.
  * Falls back to CLI args and environment variables.
@@ -15,6 +15,15 @@ export interface TurbineCliConfig {
     include?: string[];
     /** Tables to exclude */
     exclude?: string[];
+    /**
+     * Rename derived relations, as `{ table: { derivedName: desiredName } }`.
+     *
+     * Relation names are composed by introspection (a database does not name its
+     * relationships), so two foreign keys to the same table produce names nobody
+     * would predict, and a port from another ORM that named them differently has
+     * to hand-edit every call site. A typo here is an error, not a silent no-op.
+     */
+    relationNames?: Record<string, Record<string, string>>;
     /**
      * Extension for the generated `index.ts` sibling imports (F3):
      * `'js'` (`./types.js`), `'none'` (`./types`), or `'auto'` (default:
@@ -69,7 +78,7 @@ export type TurbineConfig = TurbineCliConfig;
  * path rather than a Postgres schema name? `schema` is the Postgres namespace
  * to introspect (default `public`); the schema-builder file goes in `schemaFile`.
  * A value containing a path separator or a JS/TS extension is almost certainly a
- * mis-set `schemaFile` — introspecting `WHERE table_schema = './turbine/schema.ts'`
+ * mis-set `schemaFile`, introspecting `WHERE table_schema = './turbine/schema.ts'`
  * silently matches zero tables. Used by `turbine generate` to fail loudly.
  */
 export declare function looksLikeSchemaFilePath(schema: string): boolean;
@@ -156,6 +165,8 @@ export interface ResolvedConfig {
     keepColumnNames: boolean;
     /** Resolved opt-out of the unique-FK → hasOne introspection flip (F2). */
     legacyToManyUniques: boolean;
+    /** Resolved derived-relation rename map, or undefined when none is declared. */
+    relationNames?: Record<string, Record<string, string>>;
 }
 export interface CliOverrides {
     url?: string;

package/dist/cjs/cli/config.js

@@ -1,6 +1,6 @@
 "use strict";
 /**
- * turbine-orm CLI — Configuration file support
+ * turbine-orm CLI, Configuration file support
  *
  * Loads turbine.config.ts (or .js/.mjs) via dynamic import.
  * Falls back to CLI args and environment variables.
@@ -57,7 +57,7 @@ const node_url_1 = require("node:url");
  * path rather than a Postgres schema name? `schema` is the Postgres namespace
  * to introspect (default `public`); the schema-builder file goes in `schemaFile`.
  * A value containing a path separator or a JS/TS extension is almost certainly a
- * mis-set `schemaFile` — introspecting `WHERE table_schema = './turbine/schema.ts'`
+ * mis-set `schemaFile`, introspecting `WHERE table_schema = './turbine/schema.ts'`
  * silently matches zero tables. Used by `turbine generate` to fail loudly.
  */
 function looksLikeSchemaFilePath(schema) {
@@ -203,6 +203,7 @@ function resolveConfig(fileConfig, overrides) {
         out: overrides.out ?? fileConfig.out ?? './generated/turbine',
         schema: overrides.schema ?? fileConfig.schema ?? 'public',
         include: overrides.include ?? fileConfig.include ?? [],
+        relationNames: fileConfig.relationNames,
         exclude: overrides.exclude ?? fileConfig.exclude ?? [],
         migrationsDir: fileConfig.migrationsDir ?? './turbine/migrations',
         // `seedFile` is canonical (what the docs and `turbine init` use); `seed` is a

package/dist/cjs/cli/destructive.d.ts

@@ -23,7 +23,7 @@
  */
 export type DestructiveKind = 'drop-table' | 'drop-schema' | 'drop-database' | 'drop-owned' | 'drop-matview' | 'drop-column' | 'truncate' | 'delete' | 'update-without-where' | 'alter-column-type' | 'merge-delete';
 export interface DestructiveStatement {
-    /** The offending SQL statement (trimmed, possibly long — display truncated) */
+    /** The offending SQL statement (trimmed, possibly long, display truncated) */
     statement: string;
     kind: DestructiveKind;
     /** Best-effort extracted object name (table, schema, or table.column) */

package/dist/cjs/cli/destructive.js

@@ -133,7 +133,7 @@ function isEscapeStringPrefix(sql, quoteAt) {
 /** Unquote a "quoted" identifier for display. */
 const ident = (raw) => (raw ?? '?').replace(/^"|"$/g, '');
 const IDENT = String.raw `("[^"]+"|[a-zA-Z_][\w$]*)(\.("[^"]+"|[a-zA-Z_][\w$]*))?`;
-/** Ordered rules — first match per statement wins. */
+/** Ordered rules, first match per statement wins. */
 const RULES = [
     {
         kind: 'drop-table',

package/dist/cjs/cli/index.d.ts

@@ -3,21 +3,21 @@
  * turbine-orm CLI
  *
  * Commands:
- *   turbine init                  — Initialize a Turbine project
- *   turbine generate | pull       — Introspect database and generate TypeScript types
+ *   turbine init                 , Initialize a Turbine project
+ *   turbine generate | pull      , Introspect database and generate TypeScript types
  *   turbine migrate-from-prisma   - Parse a schema.prisma and emit a Prisma->Turbine name map + report
  *   turbine push                  - Apply schema-builder definitions to database (destructive ops gated)
  *   turbine migrate create <name> - Create a new SQL migration file (--auto | --from-diff | --recipe <name>)
- *   turbine migrate up            — Apply pending migrations
- *   turbine migrate deploy        — Apply pending migrations without prompts
- *   turbine migrate down          — Rollback last migration
- *   turbine migrate status        — Show migration status
- *   turbine seed                  — Run seed file
- *   turbine status                — Show schema summary
+ *   turbine migrate up           , Apply pending migrations
+ *   turbine migrate deploy       , Apply pending migrations without prompts
+ *   turbine migrate down         , Rollback last migration
+ *   turbine migrate status       , Show migration status
+ *   turbine seed                 , Run seed file
+ *   turbine status               , Show schema summary
  *   turbine doctor                - Cost-aware missing-FK-index triage (--fix, --json, --no-concurrently, --unused, --audit)
  *   turbine studio                : Launch local read-only web UI (--demo for a seeded sample DB)
- *   turbine mcp                   — Start read-only MCP server over JSON-RPC stdio
- *   turbine observe               — Launch metrics dashboard (requires TURBINE_OBSERVE_URL)
+ *   turbine mcp                  , Start read-only MCP server over JSON-RPC stdio
+ *   turbine observe              , Launch metrics dashboard (requires TURBINE_OBSERVE_URL)
  *
  * Usage:
  *   DATABASE_URL=postgres://... npx turbine generate