@tailor-platform/sdk 2.0.1 → 2.2.0

package/docs/cli/tailordb.md

@@ -94,14 +94,16 @@ tailor tailordb migration <command>
 
 **Commands**
 
-| Command                                                       | Description                                                                                                                                                                                                                                                                            |
-| ------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| [`tailordb migration generate`](#tailordb-migration-generate) | Generate migration files by detecting schema differences between current local types and the previous migration snapshot.                                                                                                                                                              |
-| [`tailordb migration script`](#tailordb-migration-script)     | Add a migration script (migrate.ts) template to an existing migration directory, or record with --no-script that a migration intentionally has none.                                                                                                                                   |
-| [`tailordb migration set`](#tailordb-migration-set)           | Set migration checkpoint to a specific number.                                                                                                                                                                                                                                         |
-| [`tailordb migration status`](#tailordb-migration-status)     | Show the current migration status for TailorDB namespaces, including applied and pending migrations.                                                                                                                                                                                   |
-| [`tailordb migration sync`](#tailordb-migration-sync)         | Sync remote TailorDB schema to a specific migration snapshot (recovery from --no-schema-check drift).                                                                                                                                                                                  |
-| [`tailordb migration validate`](#tailordb-migration-validate) | Validate the full migration history and detect schema drift (local types vs. migration snapshot, remote schema vs. migration checkpoint) without deploying. This includes the migration and schema-drift checks used by 'deploy' and exits with a non-zero code when issues are found. |
+| Command                                                           | Description                                                                                                                                                                                                                                                                                                              |
+| ----------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| [`tailordb migration generate`](#tailordb-migration-generate)     | Generate migration files by detecting schema differences between current local types and the previous migration snapshot.                                                                                                                                                                                                |
+| [`tailordb migration rebaseline`](#tailordb-migration-rebaseline) | Collapse the full migration history into a new 0000 baseline.                                                                                                                                                                                                                                                            |
+| [`tailordb migration script`](#tailordb-migration-script)         | Add a migration script (migrate.ts) template to an existing migration directory, or record with --no-script that a migration intentionally has none.                                                                                                                                                                     |
+| [`tailordb migration set`](#tailordb-migration-set)               | Set migration checkpoint to a specific number.                                                                                                                                                                                                                                                                           |
+| [`tailordb migration status`](#tailordb-migration-status)         | Show the current migration status for TailorDB namespaces, including applied and pending migrations.                                                                                                                                                                                                                     |
+| [`tailordb migration sync`](#tailordb-migration-sync)             | Sync remote TailorDB schema to a specific migration snapshot (recovery from --no-schema-check drift).                                                                                                                                                                                                                    |
+| [`tailordb migration test`](#tailordb-migration-test)             | Test pending migrations with seed fixtures or cloned data in a temporary workspace.                                                                                                                                                                                                                                      |
+| [`tailordb migration validate`](#tailordb-migration-validate)     | Validate the full migration history, unreviewed generated migration scripts, and schema drift (local types vs. migration snapshot, remote schema vs. migration checkpoint) without deploying. This includes the migration and schema-drift checks used by 'deploy' and exits with a non-zero code when issues are found. |
 
 See [Global Options](../cli-reference.md#global-options) for options available to all commands.
 
@@ -126,6 +128,32 @@ tailor tailordb migration generate [options]
 
 See [Global Options](../cli-reference.md#global-options) for options available to all commands.
 
+#### tailordb migration rebaseline
+
+Collapse the full migration history into a new 0000 baseline.
+
+**Usage**
+
+```
+tailor tailordb migration rebaseline [options]
+```
+
+**Options**
+
+| Option                          | Alias | Description                                                       | Required | Default              | Env                            |
+| ------------------------------- | ----- | ----------------------------------------------------------------- | -------- | -------------------- | ------------------------------ |
+| `--workspace-id <WORKSPACE_ID>` | `-w`  | Workspace ID                                                      | No       | -                    | `TAILOR_PLATFORM_WORKSPACE_ID` |
+| `--profile <PROFILE>`           | `-p`  | Workspace profile                                                 | No       | -                    | `TAILOR_PLATFORM_PROFILE`      |
+| `--config <CONFIG>`             | `-c`  | Path to Tailor config file                                        | No       | `"tailor.config.ts"` | `TAILOR_CONFIG_PATH`           |
+| `--yes`                         | `-y`  | Skip confirmation prompts                                         | No       | `false`              | -                              |
+| `--namespace <NAMESPACE>`       | `-n`  | Target TailorDB namespace (required if multiple namespaces exist) | No       | -                    | -                              |
+
+See [Global Options](../cli-reference.md#global-options) for options available to all commands.
+
+**Notes**
+
+Re-baselining removes migrations after 0000 from the working tree, records a new migration history ID, and resets the connected workspace checkpoint without changing its schema or data. Every environment must already have applied the latest migration before you run this command.
+
 #### tailordb migration script
 
 Add a migration script (migrate.ts) template to an existing migration directory, or record with --no-script that a migration intentionally has none.
@@ -144,15 +172,20 @@ tailor tailordb migration script [options] <number>
 
 **Options**
 
-| Option                    | Alias | Description                                                                                  | Required | Default              | Env                  |
-| ------------------------- | ----- | -------------------------------------------------------------------------------------------- | -------- | -------------------- | -------------------- |
-| `--config <CONFIG>`       | `-c`  | Path to Tailor config file                                                                   | No       | `"tailor.config.ts"` | `TAILOR_CONFIG_PATH` |
-| `--namespace <NAMESPACE>` | `-n`  | Target TailorDB namespace (required if multiple namespaces exist)                            | No       | -                    | -                    |
-| `--no-script`             | -     | Record that this migration intentionally runs without a migration script (requires --reason) | No       | -                    | -                    |
-| `--reason <REASON>`       | -     | Reason why no migration script is needed (used with --no-script)                             | No       | -                    | -                    |
+| Option                    | Alias | Description                                                                                           | Required | Default              | Env                  |
+| ------------------------- | ----- | ----------------------------------------------------------------------------------------------------- | -------- | -------------------- | -------------------- |
+| `--config <CONFIG>`       | `-c`  | Path to Tailor config file                                                                            | No       | `"tailor.config.ts"` | `TAILOR_CONFIG_PATH` |
+| `--namespace <NAMESPACE>` | `-n`  | Target TailorDB namespace (required if multiple namespaces exist)                                     | No       | -                    | -                    |
+| `--no-script`             | -     | Record that this migration intentionally runs without a migration script (requires --reason)          | No       | -                    | -                    |
+| `--reason <REASON>`       | -     | Reason why no migration script is needed (used with --no-script)                                      | No       | -                    | -                    |
+| `--with-test`             | -     | Also add a migrate.test.ts unit-test scaffold; when migrate.ts already exists, only the test is added | No       | -                    | -                    |
 
 See [Global Options](../cli-reference.md#global-options) for options available to all commands.
 
+**Notes**
+
+When `migrate.ts` already exists, running the command clears a previously recorded `--no-script` acknowledgment.
+
 #### tailordb migration set
 
 Set migration checkpoint to a specific number.
@@ -210,7 +243,7 @@ See [Global Options](../cli-reference.md#global-options) for options available t
 
 **Notes**
 
-Metadata lookup failures (authentication, permission, or network errors) are reported per namespace and make the command exit non-zero; only a not-yet-deployed namespace is treated as having no applied migrations.
+Every local migration file is checked for a compatible format version, and deployed migration history IDs must match the local baseline. Compatibility errors, history mismatches, and metadata lookup failures are reported per namespace and make the command exit non-zero; only a not-yet-deployed namespace is treated as having no applied migrations.
 
 #### tailordb migration sync
 
@@ -240,9 +273,40 @@ tailor tailordb migration sync [options] <number>
 
 See [Global Options](../cli-reference.md#global-options) for options available to all commands.
 
+#### tailordb migration test
+
+Test pending migrations with seed fixtures or cloned data in a temporary workspace.
+
+**Usage**
+
+```
+tailor tailordb migration test [options]
+```
+
+**Options**
+
+| Option                                        | Alias | Description                                                            | Required | Default              | Env                            |
+| --------------------------------------------- | ----- | ---------------------------------------------------------------------- | -------- | -------------------- | ------------------------------ |
+| `--workspace-id <WORKSPACE_ID>`               | `-w`  | Workspace ID                                                           | No       | -                    | `TAILOR_PLATFORM_WORKSPACE_ID` |
+| `--profile <PROFILE>`                         | `-p`  | Workspace profile                                                      | No       | -                    | `TAILOR_PLATFORM_PROFILE`      |
+| `--config <CONFIG>`                           | `-c`  | Path to Tailor config file                                             | No       | `"tailor.config.ts"` | `TAILOR_CONFIG_PATH`           |
+| `--yes`                                       | `-y`  | Acknowledge that a designated target workspace may be overwritten      | No       | `false`              | -                              |
+| `--data <DATA>`                               | -     | Data source for the migration test (seed or clone)                     | No       | `"seed"`             | -                              |
+| `--target-workspace-id <TARGET_WORKSPACE_ID>` | -     | Existing throwaway workspace to retain after the test (requires --yes) | No       | -                    | -                              |
+| `--keep`                                      | -     | Keep the automatically created workspace after the test                | No       | `false`              | -                              |
+| `--assert <ASSERT>`                           | -     | Path to a TypeScript assertion script to run after migrations          | No       | -                    | -                              |
+| `--assert-namespace <ASSERT_NAMESPACE>`       | -     | TailorDB namespace exposed to the assertion script                     | No       | -                    | -                              |
+| `--machine-user <MACHINE_USER>`               | -     | Machine user for seed and assertion script execution                   | No       | -                    | -                              |
+
+See [Global Options](../cli-reference.md#global-options) for options available to all commands.
+
+**Notes**
+
+The source workspace is read-only. Without --target-workspace-id, the command creates a workspace in the source workspace's region and deletes it after success or failure; pass --keep to retain it for inspection. A designated target is retained and requires --yes. Clone mode copies TailorDB records only; it does not copy IdP users or file blobs.
+
 #### tailordb migration validate
 
-Validate the full migration history and detect schema drift (local types vs. migration snapshot, remote schema vs. migration checkpoint) without deploying. This includes the migration and schema-drift checks used by 'deploy' and exits with a non-zero code when issues are found.
+Validate the full migration history, unreviewed generated migration scripts, and schema drift (local types vs. migration snapshot, remote schema vs. migration checkpoint) without deploying. This includes the migration and schema-drift checks used by 'deploy' and exits with a non-zero code when issues are found.
 
 **Usage**
 
@@ -252,12 +316,13 @@ tailor tailordb migration validate [options]
 
 **Options**
 
-| Option                          | Alias | Description                                                           | Required | Default              | Env                            |
-| ------------------------------- | ----- | --------------------------------------------------------------------- | -------- | -------------------- | ------------------------------ |
-| `--workspace-id <WORKSPACE_ID>` | `-w`  | Workspace ID                                                          | No       | -                    | `TAILOR_PLATFORM_WORKSPACE_ID` |
-| `--profile <PROFILE>`           | `-p`  | Workspace profile                                                     | No       | -                    | `TAILOR_PLATFORM_PROFILE`      |
-| `--config <CONFIG>`             | `-c`  | Path to Tailor config file                                            | No       | `"tailor.config.ts"` | `TAILOR_CONFIG_PATH`           |
-| `--namespace <NAMESPACE>`       | `-n`  | Target TailorDB namespace (validates all namespaces if not specified) | No       | -                    | -                              |
+| Option                          | Alias | Description                                                                | Required | Default              | Env                            |
+| ------------------------------- | ----- | -------------------------------------------------------------------------- | -------- | -------------------- | ------------------------------ |
+| `--workspace-id <WORKSPACE_ID>` | `-w`  | Workspace ID                                                               | No       | -                    | `TAILOR_PLATFORM_WORKSPACE_ID` |
+| `--profile <PROFILE>`           | `-p`  | Workspace profile                                                          | No       | -                    | `TAILOR_PLATFORM_PROFILE`      |
+| `--config <CONFIG>`             | `-c`  | Path to Tailor config file                                                 | No       | `"tailor.config.ts"` | `TAILOR_CONFIG_PATH`           |
+| `--namespace <NAMESPACE>`       | `-n`  | Target TailorDB namespace (validates all namespaces if not specified)      | No       | -                    | -                              |
+| `--strict`                      | -     | Also fail when a pending migration can drop data without an acknowledgment | No       | `false`              | -                              |
 
 See [Global Options](../cli-reference.md#global-options) for options available to all commands.
 

package/docs/cli-reference.md

@@ -200,17 +200,19 @@ Commands for managing Tailor Platform applications (work with `tailor.config.ts`
 
 Commands for managing TailorDB tables, data, and schema migrations.
 
-| Command                                                                      | Description                                                                                                                                                                                                                                                                            |
-| ---------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| [tailordb](./cli/tailordb.md#tailordb)                                       | Manage TailorDB tables and data.                                                                                                                                                                                                                                                       |
-| [tailordb truncate](./cli/tailordb.md#tailordb-truncate)                     | Truncate (delete all records from) TailorDB tables.                                                                                                                                                                                                                                    |
-| [tailordb migration](./cli/tailordb.md#tailordb-migration)                   | Manage TailorDB schema migrations.                                                                                                                                                                                                                                                     |
-| [tailordb migration generate](./cli/tailordb.md#tailordb-migration-generate) | Generate migration files by detecting schema differences between current local types and the previous migration snapshot.                                                                                                                                                              |
-| [tailordb migration script](./cli/tailordb.md#tailordb-migration-script)     | Add a migration script (migrate.ts) template to an existing migration directory, or record with --no-script that a migration intentionally has none.                                                                                                                                   |
-| [tailordb migration set](./cli/tailordb.md#tailordb-migration-set)           | Set migration checkpoint to a specific number.                                                                                                                                                                                                                                         |
-| [tailordb migration status](./cli/tailordb.md#tailordb-migration-status)     | Show the current migration status for TailorDB namespaces, including applied and pending migrations.                                                                                                                                                                                   |
-| [tailordb migration sync](./cli/tailordb.md#tailordb-migration-sync)         | Sync remote TailorDB schema to a specific migration snapshot (recovery from --no-schema-check drift).                                                                                                                                                                                  |
-| [tailordb migration validate](./cli/tailordb.md#tailordb-migration-validate) | Validate the full migration history and detect schema drift (local types vs. migration snapshot, remote schema vs. migration checkpoint) without deploying. This includes the migration and schema-drift checks used by 'deploy' and exits with a non-zero code when issues are found. |
+| Command                                                                          | Description                                                                                                                                                                                                                                                                                                              |
+| -------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| [tailordb](./cli/tailordb.md#tailordb)                                           | Manage TailorDB tables and data.                                                                                                                                                                                                                                                                                         |
+| [tailordb truncate](./cli/tailordb.md#tailordb-truncate)                         | Truncate (delete all records from) TailorDB tables.                                                                                                                                                                                                                                                                      |
+| [tailordb migration](./cli/tailordb.md#tailordb-migration)                       | Manage TailorDB schema migrations.                                                                                                                                                                                                                                                                                       |
+| [tailordb migration generate](./cli/tailordb.md#tailordb-migration-generate)     | Generate migration files by detecting schema differences between current local types and the previous migration snapshot.                                                                                                                                                                                                |
+| [tailordb migration rebaseline](./cli/tailordb.md#tailordb-migration-rebaseline) | Collapse the full migration history into a new 0000 baseline.                                                                                                                                                                                                                                                            |
+| [tailordb migration script](./cli/tailordb.md#tailordb-migration-script)         | Add a migration script (migrate.ts) template to an existing migration directory, or record with --no-script that a migration intentionally has none.                                                                                                                                                                     |
+| [tailordb migration set](./cli/tailordb.md#tailordb-migration-set)               | Set migration checkpoint to a specific number.                                                                                                                                                                                                                                                                           |
+| [tailordb migration status](./cli/tailordb.md#tailordb-migration-status)         | Show the current migration status for TailorDB namespaces, including applied and pending migrations.                                                                                                                                                                                                                     |
+| [tailordb migration sync](./cli/tailordb.md#tailordb-migration-sync)             | Sync remote TailorDB schema to a specific migration snapshot (recovery from --no-schema-check drift).                                                                                                                                                                                                                    |
+| [tailordb migration test](./cli/tailordb.md#tailordb-migration-test)             | Test pending migrations with seed fixtures or cloned data in a temporary workspace.                                                                                                                                                                                                                                      |
+| [tailordb migration validate](./cli/tailordb.md#tailordb-migration-validate)     | Validate the full migration history, unreviewed generated migration scripts, and schema drift (local types vs. migration snapshot, remote schema vs. migration checkpoint) without deploying. This includes the migration and schema-drift checks used by 'deploy' and exits with a non-zero code when issues are found. |
 
 ### [Query Commands](./cli/query.md)
 

package/docs/configuration.md

@@ -69,6 +69,7 @@ export default defineConfig({
   resolver: {
     "my-resolver": {
       files: ["resolver/**/*.ts"],
+      defaultPermission: [{ conditions: [[{ user: "_loggedIn" }, "=", true]], permit: true }],
     },
   },
   executor: {
@@ -84,6 +85,8 @@ export default defineConfig({
 
 **ignores**: Glob patterns to exclude files. Optional. By default, `**/*.test.ts` and `**/*.spec.ts` are automatically ignored. If you explicitly specify `ignores`, the default patterns will not be applied. Use `ignores: []` to include all files including test files.
 
+**defaultPermission** (resolver namespaces only): Access requirement applied to every resolver in the namespace that declares no `permission` of its own. Optional, and takes the same values as a resolver's own `permission`. See [Namespace-wide default](./services/resolver.md#namespace-wide-default-defaultpermission).
+
 **Pattern resolution**: `files` and `ignores` patterns are resolved relative to the directory of the `tailor.config.ts` file that declares them, not the directory you run the command from. This matters when deploying [multiple configs](./cli/application.md#deploy) together — each config's patterns only match files under its own directory. If a config's _relative_ patterns match nothing under its own directory, the SDK falls back to resolving them from the directory you ran the command from and logs a warning (this fallback doesn't apply to already-absolute patterns, since their resolution can't change). Update such patterns to be relative to the config's own directory — this fallback will be removed in v2.
 
 ### Bundling
@@ -126,7 +129,7 @@ When using external resources:
 - The resource itself is not deployed by this project
 - The resource must be deployed and available before referencing it
 - You can combine external resources with locally-defined resources
-- TailorDB type names must remain unique across local and external TailorDB namespaces; `deploy` checks external TailorDB type names before applying changes
+- TailorDB table names must remain unique across local and external TailorDB namespaces; `deploy` checks external TailorDB table names before applying changes
 - Destructive operations like `tailordb truncate` (and `tailor seed apply --truncate`) automatically exclude external resources to prevent accidental data loss in shared resources
 - Subscribing an executor to an external resource's events requires the config that owns the resource in the same `deploy`. Publishing is then enabled automatically, and `deploy` records the dependency so a later deploy without that config asks for confirmation instead of silently turning publishing off
 

package/docs/migration/v2.md

@@ -675,7 +675,7 @@ already pass a plain value unchanged.
 
 **Migration:** Partially automatic
 
-Rename the `defineIdp` option `publishUserEvents` to `publishEvents`, matching the field name TailorDB types, resolvers, and workflows already use.
+Rename the `defineIdp` option `publishUserEvents` to `publishEvents`, matching the field name that TailorDB tables, resolvers, and workflows already use.
 
 Before:
 

package/docs/plugin/custom.md

@@ -18,7 +18,7 @@ const myPlugin: Plugin = {
 export default myPlugin; // Required: must be default export
 ```
 
-This is required so that other plugins and generation-time hooks can use plugin-generated TailorDB types via `getGeneratedType()`.
+This is required so that other plugins and generation-time hooks can use plugin-generated TailorDB tables via `getGeneratedType()`.
 
 ## Plugin Interface
 
@@ -56,38 +56,38 @@ interface Plugin<TypeConfig = unknown, PluginConfig = unknown> {
 | `id`                 | Yes                              | Unique plugin identifier (e.g., `"@my-company/soft-delete"`)                                     |
 | `description`        | Yes                              | Human-readable description                                                                       |
 | `importPath`         | When using definition-time hooks | Path resolvable from `tailor.config.ts` directory. Used for import statements in generated code. |
-| `typeConfigRequired` | No                               | Whether per-type config is required when attaching via `.plugin()`. Default: optional.           |
+| `typeConfigRequired` | No                               | Whether per-table config is required when attaching via `.plugin()`. Default: optional.          |
 | `pluginConfig`       | No                               | Plugin-level config passed via `definePlugins()`. Set via factory function.                      |
 
 ## Hook Reference
 
 ### onTypeLoaded
 
-**Trigger**: Called once for each TailorDB type that has `.plugin({ pluginId: config })` attached.
+**Trigger**: Called once for each TailorDB table that has `.plugin({ pluginId: config })` attached.
 
 **Context** (`PluginProcessContext`):
 
 | Field          | Type              | Description                                |
 | -------------- | ----------------- | ------------------------------------------ |
-| `type`         | `TailorAnyDBType` | The TailorDB type being processed          |
-| `typeConfig`   | `TypeConfig`      | Per-type config from `.plugin()`           |
+| `type`         | `TailorAnyDBType` | The TailorDB table being processed         |
+| `typeConfig`   | `TypeConfig`      | Per-table config from `.plugin()`          |
 | `pluginConfig` | `PluginConfig`    | Plugin-level config from `definePlugins()` |
-| `namespace`    | `string`          | Namespace of the TailorDB type             |
+| `namespace`    | `string`          | Namespace of the TailorDB table            |
 
 **Returns** (`TypePluginOutput`):
 
-| Field       | Type                                            | Description                                           |
-| ----------- | ----------------------------------------------- | ----------------------------------------------------- |
-| `types`     | `Record<string, TailorAnyDBType>`               | Additional TailorDB types to generate (keyed by kind) |
-| `resolvers` | `PluginGeneratedResolver[]`                     | Additional resolvers to generate                      |
-| `executors` | `PluginGeneratedExecutor[]`                     | Additional executors to generate                      |
-| `extends`   | `{ fields?: Record<string, TailorAnyDBField> }` | Fields to add to the source type                      |
+| Field       | Type                                            | Description                                            |
+| ----------- | ----------------------------------------------- | ------------------------------------------------------ |
+| `types`     | `Record<string, TailorAnyDBType>`               | Additional TailorDB tables to generate (keyed by kind) |
+| `resolvers` | `PluginGeneratedResolver[]`                     | Additional resolvers to generate                       |
+| `executors` | `PluginGeneratedExecutor[]`                     | Additional executors to generate                       |
+| `extends`   | `{ fields?: Record<string, TailorAnyDBField> }` | Fields to add to the source table                      |
 
 **Use cases**:
 
-- Generate derived types (e.g., archive tables, history tables) from user-defined types
-- Add fields to existing types (e.g., `deletedAt` for soft delete)
-- Generate executors triggered by record events on the source type
+- Generate derived tables (e.g., archive tables, history tables) from user-defined tables
+- Add fields to existing tables (e.g., `deletedAt` for soft delete)
+- Generate executors triggered by record events on the source table
 
 ```typescript
 onTypeLoaded(context) {
@@ -102,7 +102,7 @@ onTypeLoaded(context) {
 
 ### onNamespaceLoaded
 
-**Trigger**: Called once per namespace for plugins that do not require a source type.
+**Trigger**: Called once per namespace for plugins that do not require a source table.
 
 **Context** (`PluginNamespaceProcessContext`):
 
@@ -113,11 +113,11 @@ onTypeLoaded(context) {
 
 **Returns** (`PluginOutput`):
 
-Same as `TypePluginOutput` but without `extends` (namespace plugins cannot extend a source type).
+Same as `TypePluginOutput` but without `extends` (namespace plugins cannot extend a source table).
 
 **Use cases**:
 
-- Generate types that don't derive from a specific user type (e.g., audit log, settings table)
+- Generate tables that don't derive from a specific user table (e.g., audit log, settings table)
 
 ```typescript
 onNamespaceLoaded(context) {
@@ -129,26 +129,26 @@ onNamespaceLoaded(context) {
 
 ### onTailorDBReady
 
-**Trigger**: Called once after all TailorDB types are loaded and auth is resolved.
+**Trigger**: Called once after all TailorDB tables are loaded and auth is resolved.
 
 **Context** (`TailorDBReadyContext`):
 
-| Field          | Type                      | Description                                                    |
-| -------------- | ------------------------- | -------------------------------------------------------------- |
-| `tailordb`     | `TailorDBNamespaceData[]` | All namespaces with types, source info, and plugin attachments |
-| `auth`         | `GeneratorAuthInput?`     | Auth configuration (machine users, OAuth2 clients, etc.)       |
-| `baseDir`      | `string`                  | Output directory for generated files                           |
-| `configPath`   | `string`                  | Path to `tailor.config.ts`                                     |
-| `pluginConfig` | `PluginConfig`            | Plugin-level config from `definePlugins()`                     |
+| Field          | Type                      | Description                                                     |
+| -------------- | ------------------------- | --------------------------------------------------------------- |
+| `tailordb`     | `TailorDBNamespaceData[]` | All namespaces with tables, source info, and plugin attachments |
+| `auth`         | `GeneratorAuthInput?`     | Auth configuration (machine users, OAuth2 clients, etc.)        |
+| `baseDir`      | `string`                  | Output directory for generated files                            |
+| `configPath`   | `string`                  | Path to `tailor.config.ts`                                      |
+| `pluginConfig` | `PluginConfig`            | Plugin-level config from `definePlugins()`                      |
 
 `TailorDBNamespaceData` contains:
 
-| Field               | Type                                       | Description                          |
-| ------------------- | ------------------------------------------ | ------------------------------------ |
-| `namespace`         | `string`                                   | Namespace name                       |
-| `types`             | `Record<string, TailorDBType>`             | All finalized types in the namespace |
-| `sourceInfo`        | `ReadonlyMap<string, TypeSourceInfoEntry>` | Source file info for each type       |
-| `pluginAttachments` | `ReadonlyMap<string, PluginAttachment[]>`  | Plugin configs attached to each type |
+| Field               | Type                                       | Description                           |
+| ------------------- | ------------------------------------------ | ------------------------------------- |
+| `namespace`         | `string`                                   | Namespace name                        |
+| `types`             | `Record<string, TailorDBType>`             | All finalized tables in the namespace |
+| `sourceInfo`        | `ReadonlyMap<string, TypeSourceInfoEntry>` | Source file info for each table       |
+| `pluginAttachments` | `ReadonlyMap<string, PluginAttachment[]>`  | Plugin configs attached to each table |
 
 **Returns** (`GeneratorResult`):
 
@@ -159,9 +159,9 @@ onNamespaceLoaded(context) {
 
 **Use cases**:
 
-- Generate type definitions (e.g., Kysely types, enum constants)
-- Generate seed data scaffolding from type schemas
-- Generate type lists or metadata files
+- Generate table definitions (e.g., Kysely types, enum constants)
+- Generate seed data scaffolding from table schemas
+- Generate table lists or metadata files
 
 ```typescript
 onTailorDBReady(ctx) {
@@ -276,7 +276,7 @@ import type {
 
 ## getGeneratedType Helper
 
-The SDK provides an async `getGeneratedType()` helper function to retrieve plugin-generated TailorDB types. This enables plugins and other tools to work with types generated by plugins.
+The SDK provides an async `getGeneratedType()` helper function to retrieve plugin-generated TailorDB tables. This enables plugins and other tools to work with tables generated by plugins.
 
 ```typescript
 import { join } from "node:path";
@@ -285,7 +285,7 @@ import { customer } from "./tailordb/customer";
 
 const configPath = join(import.meta.dirname, "./tailor.config.ts");
 
-// Type-attached plugin
+// Table-attached plugin
 const DeletedCustomer = await getGeneratedType(
   configPath,
   "@example/soft-delete",
@@ -301,8 +301,8 @@ const AuditLog = await getGeneratedType(configPath, "@example/audit-log", null,
 
 - `configPath`: Path to `tailor.config.ts` (absolute or relative to cwd)
 - `pluginId`: The plugin's unique identifier (e.g., `"@example/soft-delete"`)
-- `sourceType`: The TailorDB type that the plugin is attached to (`null` for namespace plugins)
-- `kind`: The generated type kind (e.g., `"archive"`, `"auditLog"`)
+- `sourceType`: The TailorDB table that the plugin is attached to (`null` for namespace plugins)
+- `kind`: The generated table kind (e.g., `"archive"`, `"auditLog"`)
 
 **How it works:**
 
@@ -311,7 +311,7 @@ const AuditLog = await getGeneratedType(configPath, "@example/audit-log", null,
 3. Auto-resolves the namespace from config
 4. Calls the plugin's `onTypeLoaded()` or `onNamespaceLoaded()` method
 5. Caches the result to avoid redundant processing
-6. Returns the generated type matching the specified kind
+6. Returns the generated table matching the specified kind
 
 ## Examples
 
@@ -341,7 +341,7 @@ function processSoftDelete(
   const { type, typeConfig, pluginConfig, namespace } = context;
   const prefix = pluginConfig?.archiveTablePrefix ?? "Deleted_";
 
-  // Generate archive type
+  // Generate archive table
   const archiveType = db
     .table(`${prefix}${type.name}`, {
       originalId: db.uuid().description("ID of the deleted record"),
@@ -355,7 +355,7 @@ function processSoftDelete(
     })
     .description(`Archive for deleted ${type.name} records`);
 
-  // Extend source type with deletedAt field
+  // Extend source table with deletedAt field
   const extendFields = {
     deletedAt: db.datetime({ optional: true }).description("Soft delete timestamp"),
   };
@@ -470,7 +470,7 @@ import type { Plugin, GeneratorResult } from "@tailor-platform/sdk";
 
 const typeListPlugin: Plugin = {
   id: "@example/type-list",
-  description: "Generates a list of all TailorDB type names",
+  description: "Generates a list of all TailorDB table names",
 
   onTailorDBReady(ctx): GeneratorResult {
     const allTypes = ctx.tailordb.flatMap((ns) =>
@@ -495,15 +495,15 @@ A plugin that uses both definition-time and generation-time hooks:
 ```typescript
 const plugin: Plugin = {
   id: "@example/hybrid",
-  description: "Generates derived types and produces output files",
+  description: "Generates derived tables and produces output files",
   importPath: "./plugins/hybrid",
 
-  // Definition-time: Generate additional types from attached source types
+  // Definition-time: Generate additional tables from attached source tables
   onTypeLoaded(context) {
     return { types: { derived: createDerivedType(context.type) } };
   },
 
-  // Generation-time: Generate output files from all finalized types
+  // Generation-time: Generate output files from all finalized tables
   onTailorDBReady(ctx) {
     const allTypes = ctx.tailordb.flatMap((ns) => Object.values(ns.types).map((t) => t.name));
     return {
@@ -539,7 +539,7 @@ const plugin: Plugin<MyTypeConfig, MyPluginConfig> = {
 };
 ```
 
-### Per-type `.plugin()` type safety (declaration merging)
+### Per-table `.plugin()` type safety (declaration merging)
 
 To enable type checking when users attach plugins via `.plugin()`, provide a declaration merge
 for the `PluginConfigs` interface. Plugin authors should ship this in their package's type definitions:
@@ -556,7 +556,7 @@ declare module "@tailor-platform/sdk" {
 }
 ```
 
-The `Fields` type parameter provides field names from the type being configured, enabling field-aware configurations:
+The `Fields` type parameter provides field names from the table being configured, enabling field-aware configurations:
 
 ```typescript
 declare module "@tailor-platform/sdk" {

package/docs/plugin/index.md

@@ -2,15 +2,15 @@
 
 > **Beta Feature**: The plugin system is currently in beta. APIs may change in future releases.
 
-Plugins extend TailorDB types by automatically generating additional types, executors, and output files based on your type definitions.
+Plugins extend TailorDB tables by automatically generating additional tables, executors, and output files based on your table definitions.
 
 ## Overview
 
 When you run `tailor generate`, the SDK:
 
-1. Loads all TailorDB types with plugin attachments
-2. Passes each type to the attached plugins
-3. Generates additional types and executors based on plugin output
+1. Loads all TailorDB tables with plugin attachments
+2. Passes each table to the attached plugins
+3. Generates additional tables and executors based on plugin output
 4. Writes all generated files to the appropriate locations
 
 This enables plugins to create derived functionality based on your application's schema.
@@ -35,9 +35,9 @@ export default defineConfig({
 
 **Important**: The `plugins` export must be a named export (not default).
 
-### Attaching Plugins to Types
+### Attaching Plugins to Tables
 
-Use the `.plugin()` method to attach plugins to specific types:
+Use the `.plugin()` method to attach plugins to specific tables:
 
 ```typescript
 import { db } from "@tailor-platform/sdk";
@@ -54,7 +54,7 @@ export const user = db
 
 ### Plugin Configuration
 
-Some plugins accept per-type configuration:
+Some plugins accept per-table configuration:
 
 ```typescript
 export const customer = db
@@ -70,9 +70,9 @@ export const customer = db
   });
 ```
 
-### Per-type Config Requirement
+### Per-table Config Requirement
 
-Per-type config is optional by default. Plugin authors can change this with
+Per-table config is optional by default. Plugin authors can change this with
 `typeConfigRequired` (boolean or function). When a function is used, it receives
 the plugin-level config from `definePlugins()`.
 
@@ -97,9 +97,9 @@ export const plugins = definePlugins(
 
 Plugins can generate:
 
-- **Types**: Additional TailorDB types (e.g., `CustomerHistory`, `Deleted_Customer`)
+- **Tables**: Additional TailorDB tables (e.g., `CustomerHistory`, `Deleted_Customer`)
 - **Executors**: Event handlers triggered by record changes
-- **Field Extensions**: Additional fields added to the source type
+- **Field Extensions**: Additional fields added to the source table
 - **Output Files**: TypeScript code and other files via generation-time hooks
 
 Generated files are placed under `.tailor/<plugin-id>/` (the plugin ID is sanitized,
@@ -115,13 +115,13 @@ Plugins have 5 hooks across two lifecycle phases. Each hook fires at a specific
 ```
 tailor generate
 │
-├─ Load TailorDB types
-│   ├─ onTypeLoaded        ← per type with .plugin() attached
+├─ Load TailorDB tables
+│   ├─ onTypeLoaded        ← per table with .plugin() attached
 │   └─ onNamespaceLoaded   ← once per namespace (namespace plugins)
 │
 ├─ Resolve Auth
 │
-├─ onTailorDBReady           ← all types finalized
+├─ onTailorDBReady           ← all tables finalized
 │
 ├─ Load Resolvers
 │
@@ -134,20 +134,20 @@ tailor generate
 
 ### Definition-time hooks
 
-| Hook                | Trigger                             | Can do                                                          |
-| ------------------- | ----------------------------------- | --------------------------------------------------------------- |
-| `onTypeLoaded`      | Each type with `.plugin()` attached | Generate types, resolvers, executors; extend source type fields |
-| `onNamespaceLoaded` | Once per namespace                  | Generate types, resolvers, executors                            |
+| Hook                | Trigger                              | Can do                                                            |
+| ------------------- | ------------------------------------ | ----------------------------------------------------------------- |
+| `onTypeLoaded`      | Each table with `.plugin()` attached | Generate tables, resolvers, executors; extend source table fields |
+| `onNamespaceLoaded` | Once per namespace                   | Generate tables, resolvers, executors                             |
 
-These hooks produce TailorDB types, resolvers, and executors that become part of the application. Requires `importPath` on the plugin.
+These hooks produce TailorDB tables, resolvers, and executors that become part of the application. Requires `importPath` on the plugin.
 
 ### Generation-time hooks
 
-| Hook              | Available data                             | Can do             |
-| ----------------- | ------------------------------------------ | ------------------ |
-| `onTailorDBReady` | TailorDB types, Auth                       | Write output files |
-| `onResolverReady` | TailorDB types, Resolvers, Auth            | Write output files |
-| `onExecutorReady` | TailorDB types, Resolvers, Executors, Auth | Write output files |
+| Hook              | Available data                              | Can do             |
+| ----------------- | ------------------------------------------- | ------------------ |
+| `onTailorDBReady` | TailorDB tables, Auth                       | Write output files |
+| `onResolverReady` | TailorDB tables, Resolvers, Auth            | Write output files |
+| `onExecutorReady` | TailorDB tables, Resolvers, Executors, Auth | Write output files |
 
 These hooks receive all finalized data and produce output files (TypeScript code, etc.). No `importPath` required.