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

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,49 @@ 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>
+
 ## executeScript arg JSON.stringify → value
 
 **Migration:** Partially automatic

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/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(),

package/docs/services/tailordb.md

@@ -29,7 +29,7 @@ Define TailorDB Types in files matching glob patterns specified in `tailor.confi
 import { db } from "@tailor-platform/sdk";
 
 // Export both value and type
-export const user = db.type("User", {
+export const user = db.table("User", {
   name: db.string(),
   email: db.string().unique(),
   age: db.int(),
@@ -38,7 +38,7 @@ export const user = db.type("User", {
 export type user = typeof user;
 
 // You can define multiple types in the same file
-export const role = db.type("Role", {
+export const role = db.table("Role", {
   name: db.string().unique(),
 });
 export type role = typeof role;
@@ -47,7 +47,7 @@ export type role = typeof role;
 Specify plural form by passing an array as first argument:
 
 ```typescript
-db.type(["User", "UserList"], {
+db.table(["User", "UserList"], {
   name: db.string(),
 });
 ```
@@ -55,7 +55,7 @@ db.type(["User", "UserList"], {
 Pass a description as second argument:
 
 ```typescript
-db.type("User", "User in the system", {
+db.table("User", "User in the system", {
   name: db.string(),
 });
 ```
@@ -174,11 +174,11 @@ db.string().unique();
 Add a relation to field with automatic index and foreign key constraint:
 
 ```typescript
-const role = db.type("Role", {
+const role = db.table("Role", {
   name: db.string(),
 });
 
-const user = db.type("User", {
+const user = db.table("User", {
   name: db.string(),
   roleId: db.uuid().relation({
     type: "n-1",
@@ -190,7 +190,7 @@ const user = db.type("User", {
 For one-to-one relations, use `type: "1-1"`:
 
 ```typescript
-const userProfile = db.type("UserProfile", {
+const userProfile = db.table("UserProfile", {
   userId: db.uuid().relation({
     type: "1-1",
     toward: { type: user },
@@ -202,7 +202,7 @@ const userProfile = db.type("UserProfile", {
 For foreign key constraint without creating a relation, use `type: "keyOnly"`:
 
 ```typescript
-const user = db.type("User", {
+const user = db.table("User", {
   roleId: db.uuid().relation({
     type: "keyOnly",
     toward: { type: role },
@@ -213,11 +213,11 @@ const user = db.type("User", {
 Create relations against different fields using `toward.key`:
 
 ```typescript
-const user = db.type("User", {
+const user = db.table("User", {
   email: db.string().unique(),
 });
 
-const userProfile = db.type("UserProfile", {
+const userProfile = db.table("UserProfile", {
   userEmail: db.string().relation({
     type: "1-1",
     toward: { type: user, key: "email" },
@@ -228,7 +228,7 @@ const userProfile = db.type("UserProfile", {
 Customize relation names using `toward.as` / `backward` options:
 
 ```typescript
-const userProfile = db.type("UserProfile", {
+const userProfile = db.table("UserProfile", {
   userId: db.uuid().relation({
     type: "1-1",
     toward: { type: user, as: "base" },
@@ -260,7 +260,7 @@ on the same type point to the same target type, because their default forward na
 from the target type name:
 
 ```typescript
-const post = db.type("Post", {
+const post = db.table("Post", {
   authorID: db.uuid().relation({
     type: "n-1",
     toward: { type: user, as: "author" },
@@ -300,11 +300,11 @@ db.string().hooks({
 
 #### Type-level Hooks
 
-Set hooks for multiple fields at once using `db.type().hooks()`:
+Set hooks for multiple fields at once using `db.table().hooks()`:
 
 ```typescript
 export const customer = db
-  .type("Customer", {
+  .table("Customer", {
     firstName: db.string(),
     lastName: db.string(),
     fullName: db.string(),
@@ -322,7 +322,7 @@ export const customer = db
 ```typescript
 // Compile error - cannot set hooks on the same field twice
 export const user = db
-  .type("User", {
+  .table("User", {
     name: db.string().hooks({ create: ({ data }) => data.firstName }), // Field-level
   })
   .hooks({
@@ -331,7 +331,7 @@ export const user = db
 
 // OK - set hooks on different fields
 export const user = db
-  .type("User", {
+  .table("User", {
     firstName: db.string().hooks({ create: () => "John" }), // Field-level on firstName
     lastName: db.string(),
   })
@@ -363,11 +363,11 @@ db.string().validate(
 
 #### Type-level Validation
 
-Set validators for multiple fields at once using `db.type().validate()`:
+Set validators for multiple fields at once using `db.table().validate()`:
 
 ```typescript
 export const user = db
-  .type("User", {
+  .table("User", {
     name: db.string(),
     email: db.string(),
   })
@@ -385,7 +385,7 @@ export const user = db
 ```typescript
 // Compile error - cannot set validation on the same field twice
 export const user = db
-  .type("User", {
+  .table("User", {
     name: db.string().validate(({ value }) => value.length > 0), // Field-level
   })
   .validate({
@@ -394,7 +394,7 @@ export const user = db
 
 // OK - set validation on different fields
 export const user = db
-  .type("User", {
+  .table("User", {
     name: db.string().validate(({ value }) => value.length > 0), // Field-level on name
     email: db.string(),
   })
@@ -426,7 +426,7 @@ db.string().serial({
 ### Common Fields
 
 ```typescript
-export const user = db.type("User", {
+export const user = db.table("User", {
   name: db.string(),
   ...db.fields.timestamps(),
 });
@@ -439,7 +439,7 @@ export const user = db.type("User", {
 ### Composite Indexes
 
 ```typescript
-db.type("User", {
+db.table("User", {
   firstName: db.string(),
   lastName: db.string(),
 }).indexes({
@@ -452,7 +452,7 @@ db.type("User", {
 ### File Fields
 
 ```typescript
-db.type("User", {
+db.table("User", {
   name: db.string(),
 }).files({
   avatar: "profile image",
@@ -462,7 +462,7 @@ db.type("User", {
 ### Features
 
 ```typescript
-db.type("User", {
+db.table("User", {
   name: db.string(),
 }).features({
   aggregation: true,
@@ -475,7 +475,7 @@ db.type("User", {
 Enable event publishing for a type to trigger executors on record changes:
 
 ```typescript
-db.type("User", {
+db.table("User", {
   name: db.string(),
 }).features({
   publishEvents: true,
@@ -494,7 +494,7 @@ db.type("User", {
 
    ```typescript
    // publishEvents is automatically enabled because an executor uses this type
-   export const order = db.type("Order", {
+   export const order = db.table("Order", {
      status: db.string(),
    });
 
@@ -508,7 +508,7 @@ db.type("User", {
 2. **Manual enable**: Enable event publishing for external consumers or debugging
 
    ```typescript
-   db.type("AuditLog", {
+   db.table("AuditLog", {
      action: db.string(),
    }).features({
      publishEvents: true, // Enable even without executor triggers
@@ -518,7 +518,7 @@ db.type("User", {
 3. **Explicit disable**: Disable event publishing for a type that doesn't need it (error if executor uses it)
 
    ```typescript
-   db.type("TempData", {
+   db.table("TempData", {
      data: db.string(),
    }).features({
      publishEvents: false, // Explicitly disable
@@ -534,7 +534,7 @@ Extract subsets of fields from a `TailorDBType` for reuse in resolvers, executor
 Select specific fields and optionally modify their properties:
 
 ```typescript
-const user = db.type("User", {
+const user = db.table("User", {
   id: db.uuid(),
   name: db.string(),
   email: db.string().unique(),
@@ -604,7 +604,7 @@ Configure Permission and GQLPermission. For details, see the [TailorDB Permissio
 **Important**: Following the secure-by-default principle, all operations are denied if permissions are not configured. You must explicitly grant permissions for each operation (create, read, update, delete).
 
 ```typescript
-db.type("User", {
+db.table("User", {
   name: db.string(),
   role: db.enum(["admin", "user"]).index(),
 })
@@ -634,7 +634,7 @@ import {
   unsafeAllowAllGqlPermission,
 } from "@tailor-platform/sdk";
 
-db.type("User", {
+db.table("User", {
   name: db.string(),
 })
   .permission(unsafeAllowAllTypePermission)

package/docs/services/workflow.md

@@ -351,6 +351,84 @@ export default createWorkflow({
 });
 ```
 
+## Execution Policies
+
+Execution policies apply a per-key concurrency cap to workflow job function dispatches. Declare them at the workspace level and pass a matching key when triggering a job; the platform serializes dispatches that resolve to the same key and suspends any that would exceed the cap until slots free up.
+
+### Declaring Policies
+
+Use `defineWorkflowExecutionPolicies` with a builder callback. Property names supply the workspace-unique name and default key prefix verbatim, matching the mental model of `defineWaitPoints`. Override `name` or `key` in the body when the property identifier is not valid execution policy grammar or the key prefix needs to differ. Set `matchType: "prefix"` to register the prefix as a wildcard that matches every dispatch key starting with it (the default, `"exact"`, matches only a dispatch key equal to it).
+
+```typescript
+import { defineWorkflowExecutionPolicies } from "@tailor-platform/sdk";
+
+export const executionPolicies = defineWorkflowExecutionPolicies((define) => ({
+  /** Shared cap across every "premium" worker dispatch. */
+  premium: define({ concurrencyPolicy: { maxConcurrentExecutions: 5 } }),
+  /** Per-tenant cap: one pool per resolved tenant key. */
+  tenantApi: define({
+    name: "tenant-api",
+    matchType: "prefix",
+    concurrencyPolicy: { maxConcurrentExecutions: 3 },
+  }),
+}));
+```
+
+For a single policy, use `defineWorkflowExecutionPolicy(name, def?)`; the key prefix defaults to `name` when `key` is omitted.
+
+`concurrencyPolicy` is optional; when omitted, the policy registers the key as valid without a user-defined limit (platform safety nets still apply).
+
+Register the policies on your config so the SDK creates them on the workspace during deploy:
+
+```typescript
+// tailor.config.ts
+import { defineConfig } from "@tailor-platform/sdk";
+import { executionPolicies } from "./workflows/policies";
+
+export default defineConfig({
+  workflow: {
+    files: ["workflows/**/*.ts"],
+    executionPolicies,
+  },
+});
+```
+
+### Key Grammar
+
+`key` accepts `[a-z0-9_:.-]` and must start with `[a-z0-9]`. An exact key must also end with `[a-z0-9]`; a wildcard prefix (`matchType: "prefix"`) may end with any of those characters, since the platform appends a trailing `*` after it. The platform-registered key — including that trailing `*` when wildcarded — is 2 to 64 characters long, so a wildcard prefix must be at most 63 characters. `foo:bar` is a valid exact key; `tenant-api` with `matchType: "prefix"` registers `tenant-api*` as a wildcard prefix.
+
+An exact-key policy applies to dispatches whose runtime key equals the policy key. A wildcard policy applies to every dispatch whose runtime key begins with the prefix; each concrete resolved key gets its own independent pool of the declared size (a `cap = 3` wildcard yields three concurrent dispatches per resolved key, not three across every match). The longest matching prefix wins when a dispatch could match more than one wildcard.
+
+### Referencing a Policy from a Workflow
+
+Pass the runtime key through the `executionPolicyKey` option on `job.trigger()` or `tailor.workflow.triggerJobFunction()`. For exact-key policies, use `<policy>.key` directly — it's typed so only a value that came from a declared policy can be passed. For wildcard policies (`matchType: "prefix"`), there is no `<policy>.key` — call `<policy>.keyFor(suffix)` to build the concrete key. `keyFor` joins the prefix and suffix with `.` by default; override it with `separator` — the second argument to `defineWorkflowExecutionPolicies` (applies to every policy in the group), or a `def` field on a single `defineWorkflowExecutionPolicy`.
+
+```typescript
+import { createWorkflowJob } from "@tailor-platform/sdk";
+import { executionPolicies } from "./policies";
+import { sendNotification } from "./jobs/send-notification";
+import { fetchTenant } from "./jobs/fetch-tenant";
+
+export const mainJob = createWorkflowJob({
+  name: "main-job",
+  body: async (input: { tenantId: string }) => {
+    // Exact key policy: pass .key directly.
+    await sendNotification.trigger(
+      { message: "Order processed" },
+      { executionPolicyKey: executionPolicies.premium.key },
+    );
+
+    // Wildcard policy: build the concrete key with keyFor().
+    await fetchTenant.trigger(
+      { tenantId: input.tenantId },
+      { executionPolicyKey: executionPolicies.tenantApi.keyFor(input.tenantId) },
+    );
+  },
+});
+```
+
+The same `executionPolicyKey` option is available on `tailor.workflow.triggerJobFunction(name, args, options)` for jobs invoked by name.
+
 ## Triggering a Workflow from a Resolver
 
 You can start a workflow execution from a resolver using `workflow.trigger()`.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@tailor-platform/sdk",
-  "version": "2.0.0-next.3",
+  "version": "2.0.0-next.4",
   "description": "Tailor Platform SDK - The SDK to work with Tailor Platform",
   "license": "MIT",
   "repository": {

package/dist/aigateway-B3oZZE6v.mjs

@@ -1,15 +0,0 @@
-import { t as __exportAll } from "./rolldown-runtime-DXywRVcq.mjs";
-
-//#region src/runtime/aigateway.ts
-var aigateway_exports = /* @__PURE__ */ __exportAll({ get: () => get });
-const api = () => globalThis.tailor.aigateway;
-/**
-* See {@link TailorAigatewayAPI.get}.
-* @param args - Forwarded to {@link TailorAigatewayAPI.get}
-* @returns The resolved AI Gateway's platform-assigned URL
-*/
-const get = (...args) => api().get(...args);
-
-//#endregion
-export { get as n, aigateway_exports as t };
-//# sourceMappingURL=aigateway-B3oZZE6v.mjs.map

package/dist/application-D2hSK1ZL.mjs

@@ -1,3 +0,0 @@
-import { n as generatePluginFilesIfNeeded, r as loadApplication, t as defineApplication } from "./application-eHp9jXld.mjs";
-
-export { defineApplication, generatePluginFilesIfNeeded };