@tailor-platform/sdk 2.3.0 → 2.4.0

package/dist/vitest/mocks/file.d.mts

@@ -46,10 +46,10 @@ declare function mockFile(options?: MockFileOptions): {
   calls: FileCall[];
   clear(): void;
   reset(): void;
+  delete: Mock<(namespace: string, typeName: string, fieldName: string, recordId: string) => Promise<void>>;
   upload: Mock<(namespace: string, typeName: string, fieldName: string, recordId: string, data: string | ArrayBuffer | Uint8Array | number[], options?: FileUploadOptions) => Promise<FileUploadResponse>>;
   download: Mock<(namespace: string, typeName: string, fieldName: string, recordId: string) => Promise<FileDownloadResponse>>;
   downloadAsBase64: Mock<(namespace: string, typeName: string, fieldName: string, recordId: string) => Promise<FileDownloadAsBase64Response>>;
-  delete: Mock<(namespace: string, typeName: string, fieldName: string, recordId: string) => Promise<void>>;
   getMetadata: Mock<(namespace: string, typeName: string, fieldName: string, recordId: string) => Promise<FileMetadata>>;
   downloadStream: Mock<(namespace: string, typeName: string, fieldName: string, recordId: string) => Promise<FileDownloadStreamResponse>>;
   uploadStream: Mock<(namespace: string, typeName: string, fieldName: string, recordId: string, readableStream: ReadableStream<Uint8Array | ArrayBuffer>, options?: FileUploadStreamOptions) => Promise<FileUploadResponse>>;

package/docs/cli/application.md

@@ -190,7 +190,9 @@ Pass the global `--json` / `-j` flag to get machine-readable output.
 ```json
 {
   "summary": { "create": 2, "update": 1, "delete": 0, "replace": 0 },
-  "changes": [{ "action": "create", "name": "Order", "labels": ["type"], "namespace": "tailordb" }],
+  "changes": [
+    { "action": "create", "name": "Order", "labels": ["table"], "namespace": "tailordb" }
+  ],
   "warnings": [
     { "type": "unmanaged", "resourceType": "tailorDB", "name": "LegacyType" },
     { "type": "skippedSecret", "resourceType": "secret", "name": "DB_PASSWORD" }

package/docs/cli/function.md

@@ -16,12 +16,12 @@ See [Global Options](../cli-reference.md#global-options) for options available t
 
 **Commands**
 
-| Command                                   | Description                                                     |
-| ----------------------------------------- | --------------------------------------------------------------- |
-| [`function get`](#function-get)           | Get a function registry by name                                 |
-| [`function list`](#function-list)         | List function registries in a workspace                         |
-| [`function logs`](#function-logs)         | List or get function execution logs.                            |
-| [`function test-run`](#function-test-run) | Run a function on the Tailor Platform server without deploying. |
+| Command                           | Aliases    | Description                                                     |
+| --------------------------------- | ---------- | --------------------------------------------------------------- |
+| [`function get`](#function-get)   | -          | Get a function registry by name                                 |
+| [`function list`](#function-list) | -          | List function registries in a workspace                         |
+| [`function logs`](#function-logs) | -          | List or get function execution logs.                            |
+| [`function run`](#function-run)   | `test-run` | Run a function on the Tailor Platform server without deploying. |
 
 ### function get
 
@@ -119,18 +119,20 @@ $ tailor function logs <execution-id> --json
 
 **Notes**
 
-When viewing a specific execution that failed, the command displays error details with the stack trace mapped back to your original source files (clickable file links and code snippets, matching `function test-run` output).
+When viewing a specific execution that failed, the command displays error details with the stack trace mapped back to your original source files (clickable file links and code snippets, matching `function run` output).
 
 Stack traces are mapped only when the execution includes a content hash for the exact build that ran. If the content hash is missing or the build is no longer available, the command falls back to a plain-text error display.
 
-### function test-run
+### function run
 
 Run a function on the Tailor Platform server without deploying.
 
+**Aliases:** `test-run`
+
 **Usage**
 
 ```
-tailor function test-run [options] <file>
+tailor function run [options] <file>
 ```
 
 **Arguments**
@@ -157,19 +159,19 @@ See [Global Options](../cli-reference.md#global-options) for options available t
 **Run a resolver with input arguments**
 
 ```bash
-$ tailor function test-run resolvers/add.ts --arg '{"a":1,"b":2}'
+$ tailor function run resolvers/add.ts --arg '{"a":1,"b":2}'
 ```
 
 **Run a specific workflow job by name**
 
 ```bash
-$ tailor function test-run workflows/sample.ts --name validate-order
+$ tailor function run workflows/sample.ts --name validate-order
 ```
 
 **Run a pre-bundled .js file directly**
 
 ```bash
-$ tailor function test-run build/resolvers/add.js --arg '{"a":1,"b":2}'
+$ tailor function run build/resolvers/add.js --arg '{"a":1,"b":2}'
 ```
 
 **Notes**
@@ -177,6 +179,8 @@ $ tailor function test-run build/resolvers/add.js --arg '{"a":1,"b":2}'
 You can pass either a source file (`.ts`) or a pre-bundled file (`.js`).
 When a `.js` file is provided, detection and bundling are skipped and the file is executed as-is.
 
+`test-run` is a deprecated alias of this command and will be removed in v3.
+
 > [!WARNING]
-> Workflow job `.start()` calls do not work in test-run mode.
+> Workflow job `.start()` calls do not work in this mode.
 > Started jobs are not executed; only the target job's `body` function runs in isolation.

package/docs/cli/tailordb.md

@@ -28,14 +28,14 @@ Truncate (delete all records from) TailorDB tables.
 **Usage**
 
 ```
-tailor tailordb truncate [options] [types]
+tailor tailordb truncate [options] [tables]
 ```
 
 **Arguments**
 
-| Argument | Description            | Required |
-| -------- | ---------------------- | -------- |
-| `types`  | Type names to truncate | No       |
+| Argument | Description             | Required |
+| -------- | ----------------------- | -------- |
+| `tables` | Table names to truncate | No       |
 
 **Options**
 
@@ -62,21 +62,21 @@ tailor tailordb truncate --all --yes
 # Truncate all tables in a specific namespace
 tailor tailordb truncate --namespace myNamespace
 
-# Truncate specific types (namespace is auto-detected)
+# Truncate specific tables (namespace is auto-detected)
 tailor tailordb truncate User Post Comment
 
-# Truncate specific types with confirmation skipped
+# Truncate specific tables with confirmation skipped
 tailor tailordb truncate User Post --yes
 ```
 
 **Notes:**
 
-- You must specify exactly one of: `--all`, `--namespace`, or type names
-- When truncating specific types, the namespace is automatically detected from your config
+- You must specify exactly one of: `--all`, `--namespace`, or table names
+- When truncating specific tables, the namespace is automatically detected from your config
 - Confirmation prompts vary based on the operation:
   - `--all`: requires typing `truncate all`
   - `--namespace`: requires typing `truncate <namespace-name>`
-  - Specific types: requires typing `yes`
+  - Specific tables: requires typing `yes`
 - Use `--yes` flag to skip confirmation prompts (useful for scripts and CI/CD)
 - Namespaces declared with `{ external: true }` are skipped by `--all` and rejected with a dedicated error when targeted by `--namespace`. Run truncate from the app that owns the namespace.
 
@@ -94,22 +94,22 @@ 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 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. |
+| Command                                                           | Description                                                                                                                                                                                                                                                                                                               |
+| ----------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| [`tailordb migration generate`](#tailordb-migration-generate)     | Generate migration files by detecting schema differences between current local tables 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 tables 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.
 
 #### tailordb migration generate
 
-Generate migration files by detecting schema differences between current local types and the previous migration snapshot.
+Generate migration files by detecting schema differences between current local tables and the previous migration snapshot.
 
 **Usage**
 
@@ -119,15 +119,15 @@ tailor tailordb migration generate [options]
 
 **Options**
 
-| Option                                | Alias | Description                                                                                                                                                                                  | Required | Default              | Env                  |
-| ------------------------------------- | ----- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | -------------------- | -------------------- |
-| `--yes`                               | `-y`  | Skip confirmation prompts                                                                                                                                                                    | No       | `false`              | -                    |
-| `--config <CONFIG>`                   | `-c`  | Path to Tailor config file                                                                                                                                                                   | No       | `"tailor.config.ts"` | `TAILOR_CONFIG_PATH` |
-| `--name <NAME>`                       | `-n`  | Optional description for the migration                                                                                                                                                       | No       | -                    | -                    |
-| `--init`                              | -     | Delete existing migrations and start fresh                                                                                                                                                   | No       | `false`              | -                    |
-| `--rename <RENAME>`                   | -     | Record a field or type rename instead of remove + add (format: "Type.oldField:newField" or "OldType:NewType"; repeatable). Renames require a migration script that copies the data.          | No       | -                    | -                    |
-| `--drop <DROP>`                       | -     | Confirm that a removed field or type is a genuine removal, not a rename (format: "Type.field" or "Type"; repeatable). Required in non-interactive runs for a removal with rename candidates. | No       | -                    | -                    |
-| `--expand-contract <EXPAND_CONTRACT>` | -     | Convert a field type through a temporary field (format: "Type.field"; repeatable). Generates two migrations.                                                                                 | No       | -                    | -                    |
+| Option                                | Alias | Description                                                                                                                                                                                     | Required | Default              | Env                  |
+| ------------------------------------- | ----- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | -------------------- | -------------------- |
+| `--yes`                               | `-y`  | Skip confirmation prompts                                                                                                                                                                       | No       | `false`              | -                    |
+| `--config <CONFIG>`                   | `-c`  | Path to Tailor config file                                                                                                                                                                      | No       | `"tailor.config.ts"` | `TAILOR_CONFIG_PATH` |
+| `--name <NAME>`                       | `-n`  | Optional description for the migration                                                                                                                                                          | No       | -                    | -                    |
+| `--init`                              | -     | Delete existing migrations and start fresh                                                                                                                                                      | No       | `false`              | -                    |
+| `--rename <RENAME>`                   | -     | Record a field or table rename instead of remove + add (format: "Table.oldField:newField" or "OldTable:NewTable"; repeatable). Renames require a migration script that copies the data.         | No       | -                    | -                    |
+| `--drop <DROP>`                       | -     | Confirm that a removed field or table is a genuine removal, not a rename (format: "Table.field" or "Table"; repeatable). Required in non-interactive runs for a removal with rename candidates. | No       | -                    | -                    |
+| `--expand-contract <EXPAND_CONTRACT>` | -     | Convert a field type through a temporary field (format: "Table.field"; repeatable). Generates two migrations.                                                                                   | No       | -                    | -                    |
 
 See [Global Options](../cli-reference.md#global-options) for options available to all commands.
 
@@ -309,7 +309,7 @@ The source workspace is read-only. Without --target-workspace-id, the command cr
 
 #### 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.
+Validate the full migration history, unreviewed generated migration scripts, and schema drift (local tables 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**
 

package/docs/cli/workspace.md

@@ -338,7 +338,7 @@ tailor profile create [options] <name>
 | `--user <USER>`                                   | `-u`  | User email address or machine user client ID                                                                                           | Yes      | -         | -                                  |
 | `--workspace-id <WORKSPACE_ID>`                   | `-w`  | Workspace ID                                                                                                                           | Yes      | -         | -                                  |
 | `--permission <PERMISSION>`                       | -     | Profile permission. 'read' blocks all write commands while the profile is active.                                                      | No       | `"write"` | -                                  |
-| `--machine-user <MACHINE_USER>`                   | `-m`  | Default machine user name for application-data commands (query, workflow start, function test-run, machineuser token).                 | No       | -         | -                                  |
+| `--machine-user <MACHINE_USER>`                   | `-m`  | Default machine user name for application-data commands (query, workflow start, function run, machineuser token).                      | No       | -         | -                                  |
 | `--machine-user-override <MACHINE_USER_OVERRIDE>` | -     | Whether the command line or TAILOR_PLATFORM_MACHINE_USER_NAME may override the profile's machine user. 'deny' requires --machine-user. | No       | -         | -                                  |
 | `--platform-url <PLATFORM_URL>`                   | -     | Platform API base URL for this profile.                                                                                                | No       | -         | `TAILOR_PLATFORM_URL`              |
 | `--oauth2-client-id <OAUTH2_CLIENT_ID>`           | -     | OAuth2 client ID for logging in to this profile's platform.                                                                            | No       | -         | `TAILOR_PLATFORM_OAUTH2_CLIENT_ID` |
@@ -399,7 +399,7 @@ tailor profile update [options] <name>
 | `--user <USER>`                                   | `-u`  | New user email address or machine user client ID                                                                                                                      | No       | -       |
 | `--workspace-id <WORKSPACE_ID>`                   | `-w`  | New workspace ID                                                                                                                                                      | No       | -       |
 | `--permission <PERMISSION>`                       | -     | Profile permission. 'read' blocks all write commands; 'write' lifts the restriction.                                                                                  | No       | -       |
-| `--machine-user <MACHINE_USER>`                   | `-m`  | Default machine user name for application-data commands (query, workflow start, function test-run, machineuser token). Pass an empty string to clear.                 | No       | -       |
+| `--machine-user <MACHINE_USER>`                   | `-m`  | Default machine user name for application-data commands (query, workflow start, function run, machineuser token). Pass an empty string to clear.                      | No       | -       |
 | `--machine-user-override <MACHINE_USER_OVERRIDE>` | -     | Whether the command line or TAILOR_PLATFORM_MACHINE_USER_NAME may override the profile's machine user. 'deny' requires --machine-user; 'allow' lifts the restriction. | No       | -       |
 | `--platform-url <PLATFORM_URL>`                   | -     | Platform API base URL for this profile. Pass an empty string to clear.                                                                                                | No       | -       |
 | `--oauth2-client-id <OAUTH2_CLIENT_ID>`           | -     | OAuth2 client ID for logging in to this profile's platform. Pass an empty string to clear.                                                                            | No       | -       |

package/docs/cli-reference.md

@@ -76,7 +76,7 @@ You can use environment variables to configure workspace and authentication:
 | `TAILOR_DTS_PATH`                            | Output path for generated `tailor.d.ts` type definition file                                          |
 | `TAILOR_PLATFORM_MACHINE_USER_CLIENT_ID`     | Client ID for `login --machine-user`                                                                  |
 | `TAILOR_PLATFORM_MACHINE_USER_CLIENT_SECRET` | Client secret for `login --machine-user`                                                              |
-| `TAILOR_PLATFORM_MACHINE_USER_NAME`          | Default machine user name for `query`, `workflow start`, `function test-run`, `machineuser token`     |
+| `TAILOR_PLATFORM_MACHINE_USER_NAME`          | Default machine user name for `query`, `workflow start`, `function run`, `machineuser token`          |
 | `TAILOR_PLATFORM_URL`                        | Platform API base URL. Saved into profiles created with `profile create --platform-url`               |
 | `TAILOR_PLATFORM_OAUTH2_CLIENT_ID`           | OAuth2 client ID for user login. Saved into profiles created with `profile create --oauth2-client-id` |
 | `TAILOR_PLATFORM_CONSOLE_URL`                | Console base URL. Saved into profiles created with `profile create --console-url`                     |
@@ -200,19 +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 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. |
+| 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 tables 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 tables 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)
 
@@ -323,13 +323,13 @@ Commands for managing workflows and executions.
 
 Commands for managing function registries and viewing function execution logs.
 
-| Command                                                  | Description                                                     |
-| -------------------------------------------------------- | --------------------------------------------------------------- |
-| [function](./cli/function.md#function)                   | Manage functions                                                |
-| [function get](./cli/function.md#function-get)           | Get a function registry by name                                 |
-| [function list](./cli/function.md#function-list)         | List function registries in a workspace                         |
-| [function logs](./cli/function.md#function-logs)         | List or get function execution logs.                            |
-| [function test-run](./cli/function.md#function-test-run) | Run a function on the Tailor Platform server without deploying. |
+| Command                                          | Description                                                     |
+| ------------------------------------------------ | --------------------------------------------------------------- |
+| [function](./cli/function.md#function)           | Manage functions                                                |
+| [function get](./cli/function.md#function-get)   | Get a function registry by name                                 |
+| [function list](./cli/function.md#function-list) | List function registries in a workspace                         |
+| [function logs](./cli/function.md#function-logs) | List or get function execution logs.                            |
+| [function run](./cli/function.md#function-run)   | Run a function on the Tailor Platform server without deploying. |
 
 ### [Executor Commands](./cli/executor.md)
 

package/docs/configuration.md

@@ -243,7 +243,7 @@ export default defineConfig({
 
 If the same config defines an auth before-login hook, make sure the config module can be evaluated without Node-only globals in the platform runtime. Avoid arbitrary `process.env` reads in that module; pass literal values, or values generated into a config module before deployment, and read them from the hook's `env` argument.
 
-When the SDK deploys application code or runs detected service code with `function test-run`, it passes the resolved values as the `env` argument. Do not read `process.env` from deployed resolvers, executors, workflow jobs, auth hooks, or migration scripts; Node-side environment variables are not available there. Put sensitive values in [Secret Manager](./services/secret.md) instead of `env`.
+When the SDK deploys application code or runs detected service code with `function run`, it passes the resolved values as the `env` argument. Do not read `process.env` from deployed resolvers, executors, workflow jobs, auth hooks, or migration scripts; Node-side environment variables are not available there. Put sensitive values in [Secret Manager](./services/secret.md) instead of `env`.
 
 | Code location             | Runtime access                                                                                                                            |
 | ------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------- |
@@ -252,7 +252,7 @@ When the SDK deploys application code or runs detected service code with `functi
 | Workflow job body         | `body: (input, { env }) => ...`                                                                                                           |
 | Auth before-login hook    | `handler: async ({ env }) => ...`                                                                                                         |
 | TailorDB migration script | `main(trx, { env }: MigrationContext)`                                                                                                    |
-| `function test-run`       | Same `env` argument shape as the detected resolver, executor, or workflow job                                                             |
+| `function run`            | Same `env` argument shape as the detected resolver, executor, or workflow job                                                             |
 
 ```typescript
 // In resolvers

package/docs/migration/v2.md

@@ -1422,7 +1422,7 @@ single generation pass and resolves once it completes.
 
 **Migration:** Partially automatic
 
-`seedPlugin` no longer generates the `exec.mjs` seed runner. Seeding and validation move to the `tailor seed` commands provided by the `@tailor-platform/sdk-plugin-seed` CLI plugin: install it as a devDependency, replace `node <distPath>/exec.mjs` invocations with `tailor seed apply` and `node <distPath>/exec.mjs validate` with `tailor seed validate`, and delete the stale generated `<distPath>/exec.mjs` file. Seed data and schema generation (`data/*.jsonl`, `data/*.schema.ts`) is unchanged, and the `tailor seed apply` options mirror the old script (`--machine-user`, `--namespace`, `--skip-idp`, `--truncate`, `--yes`, type-name arguments), plus a new `--upsert` flag to update existing rows instead of failing on duplicate ids.
+`seedPlugin` no longer generates the `exec.mjs` seed runner. Seeding and validation move to the `tailor seed` commands provided by the `@tailor-platform/sdk-plugin-seed` CLI plugin: install it as a devDependency, replace `node <distPath>/exec.mjs` invocations with `tailor seed apply` and `node <distPath>/exec.mjs validate` with `tailor seed validate`, and delete the stale generated `<distPath>/exec.mjs` file. Seed data and schema generation (`data/*.jsonl`, `data/*.schema.ts`) is unchanged, and the `tailor seed apply` options mirror the old script (`--machine-user`, `--namespace`, `--skip-idp`, `--truncate`, `--yes`, entity-name arguments), plus a new `--upsert` flag to update existing rows instead of failing on duplicate ids.
 
 Before:
 
@@ -1448,8 +1448,8 @@ CLI plugin (@tailor-platform/sdk-plugin-seed) replaces it:
 - Install @tailor-platform/sdk-plugin-seed as a devDependency next to
   @tailor-platform/sdk.
 - Replace `node <distPath>/exec.mjs [options] [types...]` invocations with
-  `tailor seed apply [options] [types...]` (same options: --machine-user/-m,
-  --namespace/-n, --skip-idp, --truncate, --yes, and type-name arguments,
+  `tailor seed apply [options] [entities...]` (same options: --machine-user/-m,
+  --namespace/-n, --skip-idp, --truncate, --yes, and entity-name arguments,
   plus a new --upsert flag to update existing rows instead of failing on
   duplicate ids).
 - Replace `node <distPath>/exec.mjs validate [path]` with
@@ -1663,7 +1663,7 @@ The CLI stores human users by their stable subject ID instead of email (email is
 
 ### Node.js minimum version raised to 22.15.0
 
-v2 requires Node.js **22.15.0** or later. This is the first version that includes `module.registerHooks()`, which the SDK uses to register its TypeScript loader hook synchronously in the main thread. No source change is required; ensure your environment runs Node.js 22.15.0+.
+v2 requires Node.js **22.15.0** or later. This is the first version that includes `module.registerHooks()`, which the SDK uses to register its TypeScript loader hook synchronously in the main thread. The actual floor is now **22.18.0**: Node 22.15.0–22.17.x has a bug ([nodejs/node#58607](https://github.com/nodejs/node/issues/58607)) that crashes `tailor seed validate` when requiring `node:`-scheme-only builtins such as `node:sqlite`, fixed upstream in 22.18.0. No source change is required; ensure your environment runs Node.js 22.18.0+.
 
 ### Legacy bundle artifact cleanup removed from deploy
 

package/docs/migration/v3.md

@@ -0,0 +1,41 @@
+# Migrating to v3
+
+<!-- Generated from the sdk-codemod registry. Run `pnpm codemod:docs:update` and edit `packages/sdk-codemod/src/registry.ts` instead of this file. -->
+
+Run the codemods, then finish anything reported as not migrated automatically:
+
+```sh
+npx @tailor-platform/sdk-codemod --from <current-version> --to <target-version>
+```
+
+## function test-run → function run
+
+**Migration:** Partially automatic
+
+Rename `tailor function test-run` invocations to `tailor function run`. `test-run` remains as a deprecated alias until it is removed in v3.
+
+Before:
+
+```sh
+tailor function test-run resolvers/add.ts --arg '{"a":1,"b":2}'
+```
+
+After:
+
+```sh
+tailor function run resolvers/add.ts --arg '{"a":1,"b":2}'
+```
+
+<details>
+<summary>Prompt for an AI agent (to finish the cases the codemod could not migrate)</summary>
+
+```text
+The `tailor function test-run` subcommand is renamed to `tailor function run`;
+the old name is removed in v3. Replace any remaining `function test-run`
+invocations the codemod did not rewrite (e.g. wrapped across lines or invoked
+through a package runner such as `npx @tailor-platform/sdk`) with
+`function run`. Leave prose that merely mentions the old subcommand name
+unchanged unless it documents a command to type.
+```
+
+</details>

package/docs/quickstart.md

@@ -12,7 +12,7 @@ Contact us [here](https://www.tailor.tech/demo) to get started.
 
 ### Install Node.js
 
-The SDK requires Node.js 22.15.0 or later. Install Node.js via your package manager by following the official Node.js instructions.
+The SDK requires Node.js 22.18.0 or later. Install Node.js via your package manager by following the official Node.js instructions.
 
 Alternatively, you can use [Bun](https://bun.sh/) as the runtime.
 

package/docs/services/aigateway.md

@@ -26,9 +26,7 @@ Configure an AI Gateway using `defineAIGateway()`:
 ```typescript
 import { defineAIGateway, defineConfig } from "@tailor-platform/sdk";
 
-const aiGateway = defineAIGateway("my-aigateway", {
-  authNamespace: "default",
-});
+const aiGateway = defineAIGateway("my-aigateway", {});
 
 export default defineConfig({
   name: "my-app",
@@ -40,14 +38,42 @@ export default defineConfig({
 
 ### authNamespace
 
-The auth namespace used to resolve request tokens against your workspace's auth configuration. Must match an existing auth namespace.
+The auth namespace used to resolve request tokens against your workspace's auth configuration. Optional — when omitted, it defaults to your application's own Auth service (local or external, the name passed to `defineAuth()`), which is what most AI Gateways need. Omitting it without an Auth service configured is rejected by `deploy`/`generate`, asking you to either define one or set `authNamespace` explicitly:
 
 ```typescript
-defineAIGateway("my-aigateway", {
-  authNamespace: "default",
+import { defineAIGateway, defineAuth, defineConfig } from "@tailor-platform/sdk";
+
+const auth = defineAuth("my-auth", {
+  // ...auth configuration...
+});
+
+const aiGateway = defineAIGateway("my-aigateway", {}); // defaults to "my-auth"
+
+export default defineConfig({
+  name: "my-app",
+  auth,
+  aiGateways: [aiGateway],
 });
 ```
 
+Type-checked and autocompleted against your own Auth service name via the generated `tailor.d.ts` (the `AuthNamespaceNameRegistry` interface). Run `tailor generate` (or `deploy`) after defining an Auth service to refresh it. Before the first generate run, `authNamespace` accepts any string.
+
+To authenticate against a **different** application's Auth service, reference it as an [external resource](../configuration.md#external-resources) in your own config — `authNamespace` then defaults to it like any other Auth service:
+
+```typescript
+import { defineAIGateway, defineConfig } from "@tailor-platform/sdk";
+
+const aiGateway = defineAIGateway("my-aigateway", {}); // defaults to "shared-auth"
+
+export default defineConfig({
+  name: "my-app",
+  auth: { name: "shared-auth", external: true },
+  aiGateways: [aiGateway],
+});
+```
+
+An `authNamespace` that doesn't match any auth namespace in your workspace surfaces only at runtime, as `401 Unauthorized` on every request to the gateway.
+
 ### cors
 
 Optional list of allowed origins for browser-based clients. Each entry is one of:
@@ -61,7 +87,6 @@ An optional `:port` may be appended in all URL forms. Omitting `cors` (or passin
 
 ```typescript
 defineAIGateway("my-aigateway", {
-  authNamespace: "default",
   cors: ["https://app.example.com", "https://*.example.com"],
 });
 ```
@@ -81,8 +106,7 @@ const website = defineStaticWebSite("my-frontend", {
 });
 
 const aiGateway = defineAIGateway("my-aigateway", {
-  // Name of an auth namespace in your workspace; request tokens are resolved against it.
-  authNamespace: "default",
+  // authNamespace omitted: defaults to this app's own Auth service, declared below.
   cors: [website.url],
 });
 

package/docs/services/executor.md

@@ -374,7 +374,7 @@ must return the same input type.
 
 ### Authentication for Operations
 
-GraphQL and Workflow operations can specify an `invoker` to execute with machine user credentials. Pass the machine user name as a plain string — it is type-narrowed to the names defined in your auth config:
+`graphql`, `function`, `jobFunction`, and `workflow` operations can specify an `invoker` to execute with machine user credentials. Pass the machine user name as a plain string — it is type-narrowed to the names defined in your auth config:
 
 ```typescript
 import { createExecutor, scheduleTrigger } from "@tailor-platform/sdk";
@@ -390,6 +390,10 @@ export default createExecutor({
 });
 ```
 
+The machine user is resolved in your application's auth namespace — the name of your Auth service, local or external. `webhook` is the only operation kind that does not accept `invoker`, since it calls an external URL rather than acting inside your workspace.
+
+Without an `invoker`, the operation runs as whoever raised the trigger event, or anonymously when there is no such principal — as with a `schedule` trigger. Declare an `invoker` whenever the operation needs an identity of its own.
+
 ## Event Payloads
 
 Each trigger type provides specific context data in the callback functions.