@tailor-platform/sdk 2.0.0-next.3 → 2.0.0-next.5

package/dist/vitest/workflow-local.d.mts

@@ -1,6 +1,7 @@
 import { TailorEnv } from "../runtime/types.mjs";
 import { WorkflowJob } from "../configure/services/workflow/job.mjs";
 import { Workflow } from "../configure/services/workflow/workflow.mjs";
+import "../configure/services/workflow/index.mjs";
 //#region src/vitest/workflow-local.d.ts
 type AnyWorkflowJob = WorkflowJob<string, any, any>;
 type AnyWorkflow = Workflow<AnyWorkflowJob>;

package/dist/workflow-GNuSnsTx.mjs

@@ -0,0 +1,22 @@
+//#region src/runtime/workflow.ts
+const api = () => globalThis.tailor.workflow;
+function triggerWorkflow(workflowName, args, options) {
+	if (options?.invoker === void 0) return api().triggerWorkflow(workflowName, args);
+	return api().triggerWorkflow(workflowName, args, { authInvoker: options.invoker });
+}
+const resumeWorkflow = (...args) => api().resumeWorkflow(...args);
+const triggerJobFunction = (...args) => api().triggerJobFunction(...args);
+const wait = (...args) => api().wait(...args);
+const resolve = (...args) => api().resolve(...args);
+/** Runtime wrapper namespace for `tailor.workflow`. */
+const workflow = {
+	triggerWorkflow,
+	resumeWorkflow,
+	triggerJobFunction,
+	wait,
+	resolve
+};
+
+//#endregion
+export { workflow as t };
+//# sourceMappingURL=workflow-GNuSnsTx.mjs.map

package/dist/workflow-GNuSnsTx.mjs.map

@@ -0,0 +1 @@
+{"version":3,"file":"workflow-GNuSnsTx.mjs","names":[],"sources":["../src/runtime/workflow.ts"],"sourcesContent":["/**\n * Workflow utilities.\n *\n * Thin typed wrapper around the platform-provided `tailor.workflow` runtime API.\n * At runtime this delegates to `globalThis.tailor.workflow`. Use `mockWorkflow`\n * from `@tailor-platform/sdk/vitest` to mock these calls in unit tests.\n * @example\n * import { workflow } from \"@tailor-platform/sdk/runtime\";\n *\n * const executionId = await workflow.triggerWorkflow(\"myWorkflow\", { data: \"value\" });\n */\n\n/* eslint-disable @typescript-eslint/no-explicit-any */\n\n/**\n * Specifies the machine user that should be used to execute the workflow.\n * This allows workflows to run with specific authentication context.\n */\nexport interface Invoker {\n  /** The namespace where the machine user is defined */\n  namespace: string;\n  /** The name of the machine user to use for workflow execution */\n  machineUserName: string;\n}\n\n/** Options for {@link triggerWorkflow}. */\nexport interface TriggerWorkflowOptions {\n  /** Optional invoker to specify which machine user should execute the workflow */\n  invoker?: Invoker;\n}\n\nexport interface PlatformTriggerWorkflowOptions {\n  authInvoker?: Invoker;\n}\n\ndeclare const executionPolicyKeyBrand: unique symbol;\n\n/**\n * A concrete runtime key produced by an execution policy instance — either an\n * exact-match policy's `.key`, or a wildcard policy's `.keyFor(suffix)` (see\n * `defineWorkflowExecutionPolicies`). Branded so an arbitrary string that\n * wasn't derived from a declared policy can't be passed as `executionPolicyKey`.\n */\nexport type ExecutionPolicyKey = string & { readonly [executionPolicyKeyBrand]: never };\n\n/** Options for {@link triggerJobFunction}. */\nexport interface TriggerJobFunctionOptions {\n  /**\n   * Execution policy key matched by the platform against the policies\n   * declared with `defineWorkflowExecutionPolicies` in `tailor.config.ts`.\n   */\n  executionPolicyKey?: ExecutionPolicyKey;\n}\n\n/**\n * Platform API surface for `tailor.workflow`. Describes the shape the platform\n * runtime injects on `globalThis.tailor.workflow`.\n */\nexport interface PlatformWorkflowAPI {\n  /**\n   * Triggers a workflow and returns its execution ID.\n   * @param workflowName - Workflow name as defined in tailor.config\n   * @param args - Arguments forwarded to the workflow's main job\n   * @param options - Optional platform trigger options\n   * @returns The execution ID of the triggered workflow\n   */\n  triggerWorkflow(\n    workflowName: string,\n    args?: any,\n    options?: PlatformTriggerWorkflowOptions,\n  ): Promise<string>;\n\n  /**\n   * Resumes a failed or pending-retry workflow execution and returns its execution ID.\n   * @param executionId - The execution to resume\n   * @returns The execution ID of the resumed workflow\n   */\n  resumeWorkflow(executionId: string): Promise<string>;\n\n  /**\n   * Triggers a job function and returns its result.\n   * @param jobName - Job name as defined in the workflow\n   * @param args - Arguments forwarded to the job\n   * @param options - Optional trigger options (e.g. `executionPolicyKey`)\n   * @returns The job's return value\n   */\n  triggerJobFunction(jobName: string, args?: any, options?: TriggerJobFunctionOptions): any;\n\n  /**\n   * Suspends the current workflow execution and waits for an external signal to resume.\n   * @param key - Wait point key\n   * @param payload - Optional payload to record with the wait point\n   * @returns The payload supplied by the corresponding `resolve` call\n   */\n  wait(key: string, payload?: any): any;\n\n  /**\n   * Resolves a waiting workflow execution, causing it to resume.\n   * @param executionId - The execution to resume\n   * @param key - Wait point key to resolve\n   * @param callback - Callback receiving the wait payload; its return value is forwarded to `wait`\n   * @returns A promise that resolves once the resolve has been recorded\n   */\n  resolve(executionId: string, key: string, callback: (waitPayload: any) => any): Promise<void>;\n}\n\n/** Runtime wrapper API for workflow and job control. */\nexport interface TailorWorkflowAPI extends Omit<PlatformWorkflowAPI, \"triggerWorkflow\"> {\n  /**\n   * Triggers a workflow and returns its execution ID.\n   * @param workflowName - Workflow name as defined in tailor.config\n   * @param args - Arguments forwarded to the workflow's main job\n   * @param options - Optional SDK trigger options\n   * @returns The execution ID of the triggered workflow\n   */\n  triggerWorkflow(\n    workflowName: string,\n    args?: any,\n    options?: TriggerWorkflowOptions,\n  ): Promise<string>;\n}\n\nconst api = (): PlatformWorkflowAPI =>\n  (globalThis as unknown as { tailor: { workflow: PlatformWorkflowAPI } }).tailor.workflow;\n\nfunction triggerWorkflow(\n  workflowName: string,\n  args?: any,\n  options?: TriggerWorkflowOptions,\n): Promise<string> {\n  if (options?.invoker === undefined) {\n    return api().triggerWorkflow(workflowName, args);\n  }\n  return api().triggerWorkflow(workflowName, args, { authInvoker: options.invoker });\n}\n\nconst resumeWorkflow: PlatformWorkflowAPI[\"resumeWorkflow\"] = (...args) =>\n  api().resumeWorkflow(...args);\n\nconst triggerJobFunction: PlatformWorkflowAPI[\"triggerJobFunction\"] = (...args) =>\n  api().triggerJobFunction(...args);\n\nconst wait: PlatformWorkflowAPI[\"wait\"] = (...args) => api().wait(...args);\n\nconst resolve: PlatformWorkflowAPI[\"resolve\"] = (...args) => api().resolve(...args);\n\n/** Runtime wrapper namespace for `tailor.workflow`. */\nexport const workflow = {\n  triggerWorkflow,\n  resumeWorkflow,\n  triggerJobFunction,\n  wait,\n  resolve,\n} as const satisfies TailorWorkflowAPI;\n"],"mappings":";AA0HA,MAAM,YACH,WAAwE,OAAO;AAElF,SAAS,gBACP,cACA,MACA,SACiB;CACjB,IAAI,SAAS,YAAY,QACvB,OAAO,IAAI,CAAC,CAAC,gBAAgB,cAAc,IAAI;CAEjD,OAAO,IAAI,CAAC,CAAC,gBAAgB,cAAc,MAAM,EAAE,aAAa,QAAQ,QAAQ,CAAC;AACnF;AAEA,MAAM,kBAAyD,GAAG,SAChE,IAAI,CAAC,CAAC,eAAe,GAAG,IAAI;AAE9B,MAAM,sBAAiE,GAAG,SACxE,IAAI,CAAC,CAAC,mBAAmB,GAAG,IAAI;AAElC,MAAM,QAAqC,GAAG,SAAS,IAAI,CAAC,CAAC,KAAK,GAAG,IAAI;AAEzE,MAAM,WAA2C,GAAG,SAAS,IAAI,CAAC,CAAC,QAAQ,GAAG,IAAI;;AAGlF,MAAa,WAAW;CACtB;CACA;CACA;CACA;CACA;AACF"}

package/docs/cli/auth.md

@@ -186,9 +186,9 @@ tailor machineuser token [options] [name]
 
 **Arguments**
 
-| Argument | Description                                                                 | Required |
-| -------- | --------------------------------------------------------------------------- | -------- |
-| `name`   | Machine user name. Falls back to the active profile's default machine user. | No       |
+| Argument | Description                                                                                                         | Required |
+| -------- | ------------------------------------------------------------------------------------------------------------------- | -------- |
+| `name`   | Machine user name. Falls back to TAILOR_PLATFORM_MACHINE_USER_NAME, then the active profile's default machine user. | No       |
 
 **Options**
 

package/docs/cli/setup.md

@@ -100,14 +100,14 @@ tailor setup coordinate [options]
 
 **Options**
 
-| Option                        | Alias | Description                                                                             | Required | Default |
-| ----------------------------- | ----- | --------------------------------------------------------------------------------------- | -------- | ------- |
-| `--name <NAME>`               | `-n`  | Coordinator name (used in the generated workflow file name and job names)               | Yes      | -       |
-| `--action <ACTION>`           | -     | Composite action to include (can be specified multiple times). tailor- prefix optional. | Yes      | -       |
-| `--branch <BRANCH>`           | -     | Branch target: deploy trigger branch (defaults to the detected default branch)          | No       | -       |
-| `--tag`                       | -     | Generate a tag target coordinator                                                       | No       | `false` |
-| `--environment <ENVIRONMENT>` | -     | GitHub Environment for the plan/deploy jobs                                             | No       | -       |
-| `--force`                     | -     | Discard hand edits and regenerate                                                       | No       | `false` |
+| Option                        | Alias | Description                                                                                                                                        | Required | Default |
+| ----------------------------- | ----- | -------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- |
+| `--name <NAME>`               | `-n`  | Coordinator name (used in the generated workflow file name and job names)                                                                          | Yes      | -       |
+| `--action <ACTION>`           | -     | Composite action to include. Repeat for separate deploy steps, or use commas to deploy actions as one multi-config group. tailor- prefix optional. | Yes      | -       |
+| `--branch <BRANCH>`           | -     | Branch target: deploy trigger branch (defaults to the detected default branch)                                                                     | No       | -       |
+| `--tag`                       | -     | Generate a tag target coordinator                                                                                                                  | No       | `false` |
+| `--environment <ENVIRONMENT>` | -     | GitHub Environment for the plan/deploy jobs                                                                                                        | No       | -       |
+| `--force`                     | -     | Discard hand edits and regenerate                                                                                                                  | No       | `false` |
 
 See [Global Options](../cli-reference.md#global-options) for options available to all commands.
 
@@ -174,7 +174,7 @@ tailor setup tag [options]
 | Option                        | Alias | Description                                                                  | Required | Default |
 | ----------------------------- | ----- | ---------------------------------------------------------------------------- | -------- | ------- |
 | `--name <NAME>`               | `-n`  | Name (defaults to the config 'name')                                         | No       | -       |
-| `--tag-pattern <TAG_PATTERN>` | -     | Tag glob to match (defaults to v\*)                                          | No       | `"v*"`  |
+| `--tag-pattern <TAG_PATTERN>` | -     | Tag glob to match (defaults to v*)                                           | No       | `"v*"`  |
 | `--branch <BRANCH>`           | -     | Tag-reachability guard branch (no guard when omitted)                        | No       | -       |
 | `--environment <ENVIRONMENT>` | -     | GitHub Environment for the plan/deploy jobs (defaults to the workspace name) | No       | -       |
 | `--dir <DIR>`                 | `-d`  | App directory (for monorepo setups)                                          | No       | `"."`   |

package/docs/cli-reference.md

@@ -11,12 +11,13 @@ tailor <command> [options]
 ## Global Options
 
 <a id="global-options"></a>
-| Option | Alias | Description | Required | Default |
-|--------|-------|-------------|----------|---------|
-| `--env-file <ENV_FILE>` | `-e` | Path to the environment file (error if not found) | No | - |
-| `--env-file-if-exists <ENV_FILE_IF_EXISTS>` | - | Path to the environment file (ignored if not found) | No | - |
-| `--verbose` | - | Enable verbose logging | No | `false` |
-| `--json` | `-j` | Output as JSON | No | `false` |
+
+| Option                                      | Alias | Description                                         | Required | Default |
+| ------------------------------------------- | ----- | --------------------------------------------------- | -------- | ------- |
+| `--env-file <ENV_FILE>`                     | `-e`  | Path to the environment file (error if not found)   | No       | -       |
+| `--env-file-if-exists <ENV_FILE_IF_EXISTS>` | -     | Path to the environment file (ignored if not found) | No       | -       |
+| `--verbose`                                 | -     | Enable verbose logging                              | No       | `false` |
+| `--json`                                    | `-j`  | Output as JSON                                      | No       | `false` |
 
 ### JSON Output
 

package/docs/configuration.md

@@ -286,6 +286,30 @@ export default defineConfig({
 
 **ignores**: Glob patterns to exclude files. Optional.
 
+### Workflow Execution Policies
+
+Register workspace-scoped execution policies that workflow job functions reference at runtime for per-key concurrency control. See [Execution Policies](./services/workflow.md#execution-policies) in the Workflow guide for the declaration API.
+
+```typescript
+import { defineWorkflowExecutionPolicies } from "@tailor-platform/sdk";
+
+const executionPolicies = defineWorkflowExecutionPolicies((define) => ({
+  premium: define({ concurrencyPolicy: { maxConcurrentExecutions: 5 } }),
+  tenantApi: define({
+    name: "tenant-api",
+    matchType: "prefix",
+    concurrencyPolicy: { maxConcurrentExecutions: 3 },
+  }),
+}));
+
+export default defineConfig({
+  workflow: {
+    files: ["workflows/**/*.ts"],
+    executionPolicies,
+  },
+});
+```
+
 ### Plugins
 
 Configure plugins using `definePlugins()`. Plugins must be exported as a named export.

package/docs/migration/v2.md

@@ -436,6 +436,74 @@ wrapper or global tailor.authconnection.
 
 </details>
 
+## Runtime subpath imports use namespace objects
+
+**Migration:** Partially automatic
+
+Rewrite `@tailor-platform/sdk/runtime/*` namespace-star and flat value imports to self-named namespace imports, and aggregate `file.deleteFile` calls to `file.delete`. `TailorContextAPI` and `TailorWorkflowAPI` now describe SDK wrappers; direct platform globals use `PlatformContextAPI` and `PlatformWorkflowAPI`.
+
+Before:
+
+```ts
+import * as iconv from "@tailor-platform/sdk/runtime/iconv";
+iconv.convert(value, "UTF-8", "Shift_JIS");
+```
+
+After:
+
+```ts
+import { iconv } from "@tailor-platform/sdk/runtime/iconv";
+iconv.convert(value, "UTF-8", "Shift_JIS");
+```
+
+Before:
+
+```ts
+import { get } from "@tailor-platform/sdk/runtime/aigateway";
+const gateway = await get("main");
+```
+
+After:
+
+```ts
+import { aigateway } from "@tailor-platform/sdk/runtime/aigateway";
+const gateway = await aigateway.get("main");
+```
+
+Before:
+
+```ts
+import { file } from "@tailor-platform/sdk/runtime";
+await file.deleteFile("ns", "Doc", "blob", "record-id");
+```
+
+After:
+
+```ts
+import { file } from "@tailor-platform/sdk/runtime";
+await file.delete("ns", "Doc", "blob", "record-id");
+```
+
+<details>
+<summary>Prompt for an AI agent (to finish the cases the codemod could not migrate)</summary>
+
+```text
+In Tailor SDK v2, runtime subpath modules export only a self-named namespace
+object (for example, `iconv` from `@tailor-platform/sdk/runtime/iconv`).
+Default and flat value imports such as
+`import { get } from "@tailor-platform/sdk/runtime/aigateway"` are removed.
+The codemod rewrites straightforward namespace-star imports and flat named value
+imports. It also rewrites direct `file.deleteFile` calls on the aggregate runtime
+namespace to `file.delete`. Destructured aggregate `deleteFile` references require
+manual migration. Review any remaining runtime imports manually, especially when
+a local binding or nested scope shadows an imported value, or when
+type-position namespace member references need explicit top-level type imports.
+For direct platform globals, replace `TailorContextAPI` and `TailorWorkflowAPI`
+type references with `PlatformContextAPI` and `PlatformWorkflowAPI` respectively.
+```
+
+</details>
+
 ## Tailordb → tailordb (lowercase ambient namespace)
 
 **Migration:** Partially automatic
@@ -471,6 +539,97 @@ declarations automatically on SDK import.
 
 </details>
 
+## db.type() → db.table()
+
+**Migration:** Partially automatic
+
+Rename TailorDB schema builder calls from `db.type()` to `db.table()`. TailorDB schema definitions now use table terminology in SDK projects.
+
+Before:
+
+```ts
+import { db } from "@tailor-platform/sdk";
+
+export const user = db.type("User", {
+  name: db.string(),
+});
+```
+
+After:
+
+```ts
+import { db } from "@tailor-platform/sdk";
+
+export const user = db.table("User", {
+  name: db.string(),
+});
+```
+
+<details>
+<summary>Prompt for an AI agent (to finish the cases the codemod could not migrate)</summary>
+
+```text
+In Tailor SDK v2, TailorDB schema definitions use db.table(...) instead of
+db.type(...). The codemod rewrites member accesses on db imported from
+@tailor-platform/sdk, including aliases such as `import { db as schema }`.
+It flags destructured builder aliases such as `const { type } = db` and
+local builder aliases such as `const schema = db`, `schema = db`, or
+`function make(schema = db) { ... }` for manual review because the local
+alias may require call-site renaming.
+Review any remaining db.type references and rename SDK TailorDB schema builder
+calls to db.table. Leave unrelated local objects with a .type() method unchanged.
+```
+
+</details>
+
+## TailorDB forward relation names derive from field names
+
+**Migration:** Partially automatic
+
+Review TailorDB relations that omit `toward.as`. Their forward GraphQL field names now derive from the relation field name with a trailing `ID`, `Id`, or `id` removed, instead of from the target table name.
+
+Preserve the v1 GraphQL field name by making it explicit:
+
+Before:
+
+```ts
+ownerId: db.uuid().relation({
+  type: "n-1",
+  toward: { type: user },
+}),
+```
+
+After:
+
+```ts
+ownerId: db.uuid().relation({
+  type: "n-1",
+  toward: { type: user, as: "user" },
+}),
+```
+
+<details>
+<summary>Prompt for an AI agent (to finish the cases the codemod could not migrate)</summary>
+
+```text
+Tailor SDK v2 derives a default forward GraphQL relation name from the source
+field name by removing a trailing ID, Id, or id. V1 derived it from the target
+table name. Review each reported non-self relation that omits toward.as.
+
+If consumers must keep using the v1 GraphQL field name, inspect the v1 schema and
+copy that exact field name into toward.as. Otherwise, update GraphQL operations
+and consumer code to use the new field-based name. No change is needed when the old
+and new names are identical. Relations with a guaranteed non-empty toward.as,
+self-relations, and keyOnly relations are unchanged. For an empty or dynamic
+toward.as, determine whether its runtime value can be falsy; if so, treat the
+relation as using the default name.
+
+A relation field without a trailing ID, Id, or id would default to its own scalar
+field name and therefore conflict. Give that relation an explicit toward.as.
+```
+
+</details>
+
 ## executeScript arg JSON.stringify → value
 
 **Migration:** Partially automatic
@@ -714,6 +873,164 @@ After:
 .tailor/
 ```
 
+## ValidateFn simplification and type-level validate
+
+**Migration:** Manual
+
+Field-level `ValidateFn` is simplified from `(args: { value, data, invoker }) => boolean` to `(args: { value }) => string | void` — the function now returns the error message directly instead of a separate `[fn, message]` tuple. The `ValidateConfig` tuple form and `Validators<F>` record syntax on `db.type().validate()` are removed. Type-level validation uses `db.type().validate((args, issues) => void)` with `{ newRecord, oldRecord, invoker }` args and an `issues(field, message)` callback for cross-field rules.
+
+Field-level validate: return an error message string instead of a boolean (tuple form removed):
+
+Before:
+
+```ts
+.validate(
+  [({ value }) => value.length > 5, "Name must be longer than 5 characters"],
+)
+```
+
+After:
+
+```ts
+.validate(({ value }) =>
+  value.length <= 5 ? "Name must be longer than 5 characters" : undefined,
+)
+```
+
+Type-level validate: per-field record syntax replaced by a single function with `issues()` callback:
+
+Before:
+
+```ts
+.validate({
+  name: [({ value }) => value.length > 5, "Name must be longer than 5"],
+})
+```
+
+After:
+
+```ts
+.validate(({ newRecord }, issues) => {
+  if (newRecord.name && newRecord.name.length <= 5) {
+    issues("name", "Name must be longer than 5");
+  }
+})
+```
+
+<details>
+<summary>Prompt for an AI agent (to perform this migration)</summary>
+
+```text
+The v2 SDK simplifies field validation and introduces type-level validation.
+
+Field-level `.validate()` changes:
+- Signature: `(args: { value, data, invoker }) => boolean` → `(args: { value }) => string | void`
+- The function now returns the error message string directly (or undefined/void to pass)
+  instead of returning a boolean with the message in a separate tuple.
+- The `[fn, errorMessage]` tuple form (`ValidateConfig`) is removed.
+- `data` and `invoker` are no longer available in field-level validators.
+  Use type-level `.validate()` for cross-field or invoker-dependent rules.
+
+Type-level `.validate()` on `db.type()` changes:
+- Old: `.validate({ fieldName: fn | [fn, msg] | fn[] })` (per-field record, `Validators<F>` type)
+- New: `.validate((args, issues) => void)` (single function, `TypeValidateFn<F>` type)
+- Args: `{ newRecord, oldRecord, invoker }` — `newRecord` is the record after hooks run
+- Call `issues(field, message)` to report validation errors; `field` supports dotted paths
+- Move per-field validators that need `data`/`invoker` to the type-level function
+
+For each remaining `ValidateConfig`, `Validators<`, or old-signature `.validate()` usage:
+1. Rewrite field-level validators to return the error string directly
+2. Move cross-field / invoker-dependent validators to the type-level function
+3. Remove unused `ValidateConfig` / `Validators` type imports
+```
+
+</details>
+
+## TailorDB hook redesign: field-level args and type-level hooks
+
+**Migration:** Manual
+
+Field-level `HookFn` args change from `{ value, data, invoker }` to create `{ input, invoker, now }` / update `{ input, oldValue, invoker, now }` — `value` is renamed to `input`, matching the `input` arg on type-level hooks (same pre-hook data, narrowed to one field); `data` (the full record) is removed; `oldValue` (previous field value) is added for update hooks only; `now` (operation timestamp) is shared across all hooks. Type-level hooks on `db.type().hooks()` change from per-field mapping `{ fieldName: { create, update } }` (`Hooks<F>`) to a single `{ create, update }` object (`TypeHook<F>`) — create hooks take `{ input, invoker, now }`, update hooks take `{ input, oldRecord, invoker, now }` (oldRecord is always non-null). Both return partial field overrides.
+
+Field-level hooks: `value` renamed to `input`, `data` replaced by `oldValue` and `now`; use `now` instead of `new Date()`:
+
+Before:
+
+```ts
+db.datetime().hooks({
+  create: ({ value }) => value ?? new Date(),
+  update: () => new Date(),
+})
+```
+
+After:
+
+```ts
+db.datetime().hooks({
+  create: ({ input, now }) => input ?? now,
+  update: ({ now }) => now,
+})
+```
+
+Type-level hooks: per-field mapping replaced by single create/update functions:
+
+Before:
+
+```ts
+.hooks({
+  fullAddress: {
+    create: ({ data }) => `${data.postalCode} ${data.address}`,
+    update: ({ data }) => `${data.postalCode} ${data.address}`,
+  },
+})
+```
+
+After:
+
+```ts
+.hooks({
+  create: ({ input }) => ({
+    fullAddress: `${input.postalCode} ${input.address}`,
+  }),
+  update: ({ input }) => ({
+    fullAddress: `${input.postalCode} ${input.address}`,
+  }),
+})
+```
+
+<details>
+<summary>Prompt for an AI agent (to perform this migration)</summary>
+
+```text
+The v2 SDK redesigns TailorDB hooks at both field and type levels.
+
+Field-level `.hooks()` on individual fields:
+- Create args: `{ value, data, invoker }` → `{ input, invoker, now }` (no `oldValue`)
+- Update args: `{ value, data, invoker }` → `{ input, oldValue, invoker, now }`
+- `value` is renamed to `input`, matching the type-level hook's `input` arg — both are
+  the same pre-hook data, at different granularity
+- `data` (full record) is removed; update hooks get `oldValue` (previous field value) instead
+- `now` provides the operation timestamp — use `now` instead of `new Date()`
+- If a field-level hook needs the full record (other fields), move it to a type-level hook
+
+Type-level `.hooks()` on `db.type()`:
+- Old: `.hooks({ fieldName: { create: fn, update: fn } })` (per-field mapping, `Hooks<F>` type)
+- New: `.hooks({ create: fn, update: fn })` (single object, `TypeHook<F>` type)
+- Each function: `({ input, oldRecord, invoker, now }) => ({ fieldName: value, ... })`
+- `input` is the pre-hook input (may have nullish values for optional/defaulted fields)
+- Create hooks do not receive `oldRecord`; update hooks receive `oldRecord` (always non-null)
+- Return an object with only the fields to override; unmentioned fields are unchanged
+
+Migration steps for each `.hooks()` call on a `db.type()`:
+1. If the old per-field hooks only use `value`/`invoker` and don't reference `data`,
+   convert them to field-level hooks with the new args (`value` → `input`, plus `oldValue`, `now`)
+2. If the old hooks reference `data` (cross-field access), convert to a type-level hook
+   using `input`/`oldRecord`
+3. Remove unused `Hooks<F>` / `HookFn<>` type imports
+```
+
+</details>
+
 ## Behavioral changes (no migration required)
 
 These v2 changes alter runtime or CLI behavior; no source change is needed.

package/docs/plugin/custom.md

@@ -93,7 +93,7 @@ interface Plugin<TypeConfig = unknown, PluginConfig = unknown> {
 onTypeLoaded(context) {
   const { type, typeConfig, namespace } = context;
   return {
-    types: { archive: db.type(`Deleted_${type.name}`, { ... }) },
+    types: { archive: db.table(`Deleted_${type.name}`, { ... }) },
     extends: { fields: { deletedAt: db.datetime({ optional: true }) } },
     executors: [{ name: `${type.name}-on-delete`, resolve: async () => await import("./on-delete"), context: { sourceType: type, namespace } }],
   };
@@ -122,7 +122,7 @@ Same as `TypePluginOutput` but without `extends` (namespace plugins cannot exten
 ```typescript
 onNamespaceLoaded(context) {
   return {
-    types: { auditLog: db.type("AuditLog", { action: db.string(), ... }) },
+    types: { auditLog: db.table("AuditLog", { action: db.string(), ... }) },
   };
 },
 ```
@@ -343,7 +343,7 @@ function processSoftDelete(
 
   // Generate archive type
   const archiveType = db
-    .type(`${prefix}${type.name}`, {
+    .table(`${prefix}${type.name}`, {
       originalId: db.uuid().description("ID of the deleted record"),
       originalData: db.string().description("JSON snapshot of deleted record"),
       deletedAt: db.datetime().description("When the record was deleted"),
@@ -450,7 +450,7 @@ export const plugins = definePlugins(
 
 // tailordb/customer.ts
 export const customer = db
-  .type("Customer", {
+  .table("Customer", {
     name: db.string(),
     email: db.string(),
   })

package/docs/plugin/index.md

@@ -43,7 +43,7 @@ Use the `.plugin()` method to attach plugins to specific types:
 import { db } from "@tailor-platform/sdk";
 
 export const user = db
-  .type("User", {
+  .table("User", {
     name: db.string(),
     email: db.string(),
   })
@@ -58,7 +58,7 @@ Some plugins accept per-type configuration:
 
 ```typescript
 export const customer = db
-  .type("Customer", {
+  .table("Customer", {
     name: db.string(),
     // ...
   })

package/docs/runtime.md

@@ -45,10 +45,12 @@ const { url } = await aigateway.get("my-aigateway");
 Each namespace can also be imported individually so you only pull what you need:
 
 ```ts
-import * as iconv from "@tailor-platform/sdk/runtime/iconv";
-import type { ListUsersResponse, ClientConfig } from "@tailor-platform/sdk/runtime/idp";
+import { iconv } from "@tailor-platform/sdk/runtime/iconv";
+import { idp, type ListUsersResponse, type ClientConfig } from "@tailor-platform/sdk/runtime/idp";
 ```
 
+`TailorContextAPI` and `TailorWorkflowAPI` describe the imported SDK wrapper objects. When typing direct access to the platform-provided globals or a runtime mock, use `PlatformContextAPI` or `PlatformWorkflowAPI` instead.
+
 ## Activating the global types
 
 Most users do not need to touch the globals entry — `@tailor-platform/sdk/runtime` (and its subpath modules) cover the same surface without depending on any ambient declaration.

package/docs/services/aigateway.md

@@ -111,3 +111,5 @@ const { url } = await aigateway.get("my-aigateway");
 ```
 
 Type narrowing is provided by the generated `tailor.d.ts` (the `AIGatewayNameRegistry` interface). Run `tailor generate` (or `deploy`) after defining new AI Gateways to refresh it. Before the first generate run, `get()` accepts any string.
+
+The same URL is also shown by `tailor show`, which lists the URL of each AI Gateway defined in `aiGateways` once it has been deployed.

package/docs/services/auth.md

@@ -86,7 +86,7 @@ Example TailorDB type for user profile:
 // tailordb/user.ts
 import { db } from "@tailor-platform/sdk";
 
-export const user = db.type("User", {
+export const user = db.table("User", {
   email: db.string().unique(), // usernameField must have unique constraint
   role: db.enum(["admin", "user"]),
   ...db.fields.timestamps(),
@@ -130,7 +130,7 @@ Example TailorDB type with UUID fields for attribute list:
 // tailordb/user.ts
 import { db } from "@tailor-platform/sdk";
 
-export const user = db.type("User", {
+export const user = db.table("User", {
   email: db.string().unique(),
   role: db.enum(["admin", "user"]),
   organizationId: db.uuid(), // Can be used in attributeList

package/docs/services/resolver.md

@@ -108,7 +108,7 @@ Define input/output schemas using methods of `t` object. Basic usage and support
 You can reuse fields defined with `db` object, but note that unsupported options will be ignored:
 
 ```typescript
-const user = db.type("User", {
+const user = db.table("User", {
   name: db.string().unique(),
   age: db.int(),
 });

package/docs/services/tailordb-migration.md

@@ -69,7 +69,7 @@ A typical change cycle:
 
    ```typescript
    // tailordb/user.ts
-   export const user = db.type("User", {
+   export const user = db.table("User", {
      name: db.string(),
      email: db.string(), // ← new required field
      ...db.fields.timestamps(),