@tailor-platform/sdk 2.3.0 → 2.5.0

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,13 @@ 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 script`](#function-script) | -          | Scaffold a one-off script to run with `function run`.           |
 
 ### function get
 
@@ -119,18 +120,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**
@@ -149,6 +152,7 @@ tailor function test-run [options] <file>
 | `--arg <ARG>`                   | `-a`  | JSON argument to pass to the function                                                          | No       | -                    | -                                   |
 | `--machine-user <MACHINE_USER>` | `-m`  | Machine user name for authentication. Falls back to the active profile's default machine user. | No       | -                    | `TAILOR_PLATFORM_MACHINE_USER_NAME` |
 | `--config <CONFIG>`             | `-c`  | Path to SDK config file                                                                        | No       | `"tailor.config.ts"` | -                                   |
+| `--allow-schema-drift`          | -     | Run a scaffolded script even when its schema snapshot no longer matches                        | No       | `false`              | -                                   |
 
 See [Global Options](../cli-reference.md#global-options) for options available to all commands.
 
@@ -157,19 +161,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 +181,66 @@ $ 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.
 
+A script scaffolded by `function script` with a generated `db.ts` is checked against its `db.snapshot.json` before execution and refused on schema drift; pass `--allow-schema-drift` to run it anyway. The check compares table and field structure; hook and validator code changes are not detected.
+
+`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.
+
+### function script
+
+Scaffold a one-off script to run with `function run`.
+
+**Usage**
+
+```
+tailor function script [options] <file>
+```
+
+**Arguments**
+
+| Argument | Description                                      | Required |
+| -------- | ------------------------------------------------ | -------- |
+| `file`   | Path to create the script at (must end with .ts) | Yes      |
+
+**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>`       | -     | Target TailorDB namespace (required when the config does not pin one) | No       | -                    | -                              |
+| `--remote`                      | -     | Generate script-scoped DB types from the deployed schema              | No       | `false`              | -                              |
+
+See [Global Options](../cli-reference.md#global-options) for options available to all commands.
+
+**Examples**
+
+**Scaffold a one-off script (single-namespace project)**
+
+```bash
+$ tailor function script scripts/fix-prices.ts
+```
+
+**Scaffold a script targeting a specific namespace**
+
+```bash
+$ tailor function script scripts/fix-prices.ts --namespace tailordb
+```
+
+**Scaffold from a deployed or external namespace**
+
+```bash
+$ tailor function script scripts/fix-prices.ts --namespace shared --remote
+```
+
+**Notes**
+
+The scaffolded script is a plain default-exported function; execute it with `tailor function run <file>`.
+
+By default, when the project configures `kyselyTypePlugin`, the skeleton imports `getDB()` from the plugin's generated types. Without the plugin, the command uses the namespace's local table definitions to write a script-scoped `db.ts` plus a `db.snapshot.json` next to the script; `function run` refuses to run the script when that snapshot no longer matches the deployed or locally defined table and field structure.
+
+Pass `--remote` to generate the script-scoped files from the deployed schema instead, even when `kyselyTypePlugin` is configured. This is required for an external namespace. Re-running the command refreshes `db.ts` and `db.snapshot.json` from the selected source and leaves the script itself untouched.

package/docs/cli/setup.md

@@ -23,7 +23,7 @@ See [Global Options](../cli-reference.md#global-options) for options available t
 | [`setup preview`](#setup-preview)       | Generate a preview workflow (PR open/sync triggers deploy to a per-PR workspace).                |
 | [`setup action`](#setup-action)         | Generate a per-app composite action for use with setup coordinate (monorepo multi-app deploys).  |
 | [`setup coordinate`](#setup-coordinate) | Generate a coordinator workflow that orchestrates multiple --action-generated composite actions. |
-| [`setup renovate`](#setup-renovate)     | Generate a Renovate config for Tailor dependency and workflow updates.                           |
+| [`setup deps`](#setup-deps)             | Generate a dependency update config for Tailor dependency and workflow updates.                  |
 | [`setup check`](#setup-check)           | Audit generated workflows for drift against the current config/repo (read-only).                 |
 | [`setup delete`](#setup-delete)         | Delete managed workflow/action file(s) and their .github/tailor.lock entries.                    |
 
@@ -63,7 +63,7 @@ tailor setup branch [options]
 | Option                        | Alias | Description                                                                    | Required | Default |
 | ----------------------------- | ----- | ------------------------------------------------------------------------------ | -------- | ------- |
 | `--name <NAME>`               | `-n`  | Name (defaults to the config 'name')                                           | No       | -       |
-| `--branch <BRANCH>`           | -     | Deploy trigger branch (defaults to the detected default branch)                | No       | -       |
+| `--target <TARGET>`           | -     | Deploy trigger branch (defaults to the detected default branch)                | No       | -       |
 | `--environment <ENVIRONMENT>` | -     | GitHub Environment for the plan/deploy jobs (defaults to the workspace name)   | No       | -       |
 | `--erd-preview`               | -     | Add PR ERD viewer artifacts with current/diff previews for TailorDB namespaces | No       | `false` |
 | `--dir <DIR>`                 | `-d`  | App directory (for monorepo setups)                                            | No       | `"."`   |
@@ -71,6 +71,10 @@ tailor setup branch [options]
 
 See [Global Options](../cli-reference.md#global-options) for options available to all commands.
 
+**Notes**
+
+`--branch` is a deprecated alias of `--target` and will be removed in v3.
+
 ### setup check
 
 Audit generated workflows for drift against the current config/repo (read-only).
@@ -136,6 +140,24 @@ tailor setup delete [options] <files>
 
 See [Global Options](../cli-reference.md#global-options) for options available to all commands.
 
+### setup deps
+
+Generate a dependency update config for Tailor dependency and workflow updates.
+
+**Usage**
+
+```
+tailor setup deps [options]
+```
+
+**Options**
+
+| Option                  | Alias | Description                             | Required | Default      |
+| ----------------------- | ----- | --------------------------------------- | -------- | ------------ |
+| `--provider <PROVIDER>` | -     | Dependency update provider to configure | No       | `"renovate"` |
+
+See [Global Options](../cli-reference.md#global-options) for options available to all commands.
+
 ### setup preview
 
 Generate a preview workflow (PR open/sync triggers deploy to a per-PR workspace).
@@ -160,18 +182,6 @@ tailor setup preview [options]
 
 See [Global Options](../cli-reference.md#global-options) for options available to all commands.
 
-### setup renovate
-
-Generate a Renovate config for Tailor dependency and workflow updates.
-
-**Usage**
-
-```
-tailor setup renovate
-```
-
-See [Global Options](../cli-reference.md#global-options) for options available to all commands.
-
 ### setup tag
 
 Generate a tag-target deploy workflow (tag push triggers deploy).

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,17 @@ 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`              | -                    |
+| `--data-only`                         | -     | Create a migration with no schema changes whose migration script runs a standalone data transformation                                                                                          | No       | `false`              | -                    |
+| `--namespace <NAMESPACE>`             | -     | Target TailorDB namespace for --data-only (required if multiple namespaces exist)                                                                                                               | No       | -                    | -                    |
+| `--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 +311,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,14 @@ 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. |
+| [function script](./cli/function.md#function-script) | Scaffold a one-off script to run with `function run`.           |
 
 ### [Executor Commands](./cli/executor.md)
 
@@ -397,8 +398,8 @@ Commands for setting up project infrastructure.
 | [setup check](./cli/setup.md#setup-check)           | Audit generated workflows for drift against the current config/repo (read-only).                 |
 | [setup coordinate](./cli/setup.md#setup-coordinate) | Generate a coordinator workflow that orchestrates multiple --action-generated composite actions. |
 | [setup delete](./cli/setup.md#setup-delete)         | Delete managed workflow/action file(s) and their .github/tailor.lock entries.                    |
+| [setup deps](./cli/setup.md#setup-deps)             | Generate a dependency update config for Tailor dependency and workflow updates.                  |
 | [setup preview](./cli/setup.md#setup-preview)       | Generate a preview workflow (PR open/sync triggers deploy to a per-PR workspace).                |
-| [setup renovate](./cli/setup.md#setup-renovate)     | Generate a Renovate config for Tailor dependency and workflow updates.                           |
 | [setup tag](./cli/setup.md#setup-tag)               | Generate a tag-target deploy workflow (tag push triggers deploy).                                |
 
 ### [Upgrade Commands](./cli/upgrade.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/github-actions.md

@@ -38,12 +38,13 @@ Run `setup` once per target.
 ### Branch target (recommended for staging)
 
 The branch target fires on pull requests and pushes to the branch you specify
-(defaulting to the repository's default branch when `--branch` is omitted):
+(defaulting to the repository's default branch when `--target` is
+omitted):
 
 ```bash
 tailor setup branch --name my-app-stg
 # Equivalent to:
-tailor setup branch --name my-app-stg --branch main
+tailor setup branch --name my-app-stg --target main
 ```
 
 What it does:
@@ -120,12 +121,12 @@ What it does:
 
 ### Choosing `--branch` for the tag target
 
-`--branch` has two different roles depending on the target kind:
+The branch each target reads plays a different role, under a different flag:
 
-| Target | Role of `--branch`                                                                             |
-| ------ | ---------------------------------------------------------------------------------------------- |
-| Branch | The branch that triggers the workflow (push + PR base). Defaults to the repo's default branch. |
-| Tag    | The branch whose history the tag must be reachable from. Omit to disable the guard entirely.   |
+| Target | Flag       | Role                                                                                           |
+| ------ | ---------- | ---------------------------------------------------------------------------------------------- |
+| Branch | `--target` | The branch that triggers the workflow (push + PR base). Defaults to the repo's default branch. |
+| Tag    | `--branch` | The branch whose history the tag must be reachable from. Omit to disable the guard entirely.   |
 
 The workspace name (`--name`, or the config `name` when omitted) must
 be 3–63 characters of lowercase letters, numbers, and hyphens, and cannot start
@@ -365,7 +366,7 @@ Commit both workflow files and `.github/tailor.lock`.
 Run this command once from the repository root to add Renovate configuration:
 
 ```bash
-tailor setup renovate
+tailor setup deps
 ```
 
 It generates `renovate.json`, which extends Tailor's shared Renovate preset. The
@@ -387,7 +388,7 @@ cannot be edited without losing those comments, so the command leaves it
 unchanged and asks you to add the preset to its `extends` array yourself.
 
 `renovate.json` is yours to edit — it is not tracked in `.github/tailor.lock`.
-Add your own rules freely; re-running `tailor setup renovate` does not overwrite
+Add your own rules freely; re-running `tailor setup deps` does not overwrite
 them. To remove it, delete the file.
 
 Renovate updates the SDK dependency and action pins, but it does not regenerate

package/docs/migration/v2.md

@@ -878,6 +878,10 @@ Also review, and migrate by hand:
 - An invoker option passed via a variable or spread (not a literal object) —
   the codemod only inspects literal object arguments; rename the invoker key
   to authInvoker in the options object's own definition.
+- A renamed triggerJobFunction call whose target is another workflow job —
+  rewrite it further to that job's own .start() method (e.g. worker.start(args)).
+  Calling execJobFunction directly is not detected as a build-time dependency
+  and fails the build.
 ```
 
 </details>
@@ -924,6 +928,10 @@ Also review, and migrate by hand:
   instead; the alias was the same mock function.
 - A file that already imports ExecJobFunctionOptions alongside the removed type —
   rename the remaining references by hand and drop the duplicate specifier.
+- A renamed call whose target is another workflow job — rewrite it further to
+  that job's own .start() method (e.g. worker.start(args)). Calling
+  execJobFunction directly is not detected as a build-time dependency and fails
+  the build.
 ```
 
 </details>
@@ -1422,7 +1430,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 +1456,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,8 +1671,12 @@ 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 that crashes `tailor seed validate` when requiring `node:`-scheme-only builtins such as `node:sqlite`, fixed upstream by [nodejs/node#58612](https://github.com/nodejs/node/pull/58612) 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
 
 `tailor deploy` no longer deletes on-disk bundle artifacts (`.entry.js` files, workflow-job bundles, and the `hooks-validate-scripts/` directory) left in the SDK output directory (`.tailor` by default) by SDK versions that predate the current in-memory bundling approach. Current bundlers no longer write these files. No source change is required; if such stale files remain from a very old SDK version, delete only those specific files/directories manually — do not delete the output directory itself, since it also holds deploy state (e.g. `secrets-state/`, `*.context.json`) that existing secrets and Auth Connections depend on.
+
+### First v2 deploy to a v1-deployed environment needs migration sync
+
+The pre-v2 CLI never wrote a script hash into deployed schemas, so the first `tailor deploy` against an environment last deployed with it reports `Remote schema drift detected` with every scripted type showing `has no script hash on remote`. Run `tailor tailordb migration sync <current migration number>` once for that environment to write the missing hashes, then `tailor deploy` as usual. Preview/PR workspaces don't hit this, since they're built with v2 from the start. No source change is required.