@tailor-platform/sdk 2.2.0 → 2.3.0

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

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

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

@@ -2,7 +2,7 @@ import { TailorEnv } from "../../runtime/types.mjs";
 import { ExecJobFunctionOptions, StartWorkflowOptions } from "../../runtime/workflow.mjs";
 import { WorkflowJob } from "../../configure/services/workflow/job.mjs";
 import { Workflow } from "../../configure/services/workflow/workflow.mjs";
-import { WaitPointInstance } from "../../configure/services/workflow/wait-point.mjs";
+import { ParameterizedWaitPointInstance, WaitPointInstance } from "../../configure/services/workflow/wait-point.mjs";
 import { Mock } from "vitest";
 //#region src/vitest/mocks/workflow.d.ts
 type JobHandler = (jobName: string, args: unknown, options?: ExecJobFunctionOptions) => unknown;
@@ -72,6 +72,18 @@ declare function mockWorkflow(): {
     resolve: Mock<WaitPointInstance<Payload, Result>["resolve"]>;
     setResolvePayload(payload: WaitPayload<Payload>): void;
   };
+  /**
+   * Get stable, typed mocks for one param binding of a parameterized wait point.
+   * Calls made with other bindings fall through to the platform mock.
+   * @param definition - Parameterized wait point definition to mock
+   * @param params - Param binding to intercept, as passed to `.with()`
+   * @returns Typed wait point mock control object
+   */
+  waitPointWith<Params extends object, Payload, Result>(definition: ParameterizedWaitPointInstance<Params, Payload, Result>, params: Params): {
+    wait: Mock<WaitPointInstance<Payload, Result>["wait"]>;
+    resolve: Mock<WaitPointInstance<Payload, Result>["resolve"]>;
+    setResolvePayload(payload: WaitPayload<Payload>): void;
+  };
   /**
    * Set a fallback job handler. Called when the enqueue queue is empty.
    * @param handler - Function returning a result for a job name, args, and options

package/dist/wait-point-invoker-__oE88_P.mjs

@@ -0,0 +1,148 @@
+import { AsyncLocalStorage } from "node:async_hooks";
+
+//#region src/configure/services/workflow/test-env-key.ts
+/**
+* Typed accessors for the test-time globalThis slot used to pass `env` from
+* `mockWorkflow().setEnv()` (in `@tailor-platform/sdk/vitest`) to
+* `runWorkflowLocally()` job bodies. The slot key is private to this
+* module; callers go through the get/set/clear functions below so both sides
+* share the same access path.
+*
+* Lives in its own file (with no `@/` imports) so `vitest/mock.ts` can load
+* it from nested Vitest configs that do not resolve `@/` aliases.
+* @internal
+*/
+const SLOT_KEY = "__tailorWorkflowTestEnv";
+let invokerStorage;
+function workflowInvokerStorage() {
+	if (!invokerStorage) invokerStorage = new AsyncLocalStorage();
+	return invokerStorage;
+}
+/**
+* Read the test-time env slot.
+* @returns Current env, or `undefined` when unset.
+* @internal
+*/
+function readWorkflowTestEnv() {
+	return globalThis[SLOT_KEY];
+}
+/**
+* Write the test-time env slot.
+* @param env - Env value to expose to `runWorkflowLocally()` job bodies.
+* @internal
+*/
+function writeWorkflowTestEnv(env) {
+	globalThis[SLOT_KEY] = env;
+}
+/**
+* Clear the test-time env slot.
+* @internal
+*/
+function clearWorkflowTestEnv() {
+	delete globalThis[SLOT_KEY];
+}
+function withWorkflowTestInvoker(invoker, run) {
+	return workflowInvokerStorage().run(invoker, run);
+}
+function readRuntimeInvoker() {
+	const runtime = globalThis.tailor?.context?.getInvoker;
+	const raw = runtime?.();
+	if (!raw) return null;
+	return {
+		id: raw.id,
+		type: raw.type,
+		workspaceId: raw.workspaceId,
+		attributes: raw.attributeMap ?? (Array.isArray(raw.attributes) ? {} : raw.attributes ?? {}),
+		attributeList: raw.attributeList ?? (Array.isArray(raw.attributes) ? raw.attributes : [])
+	};
+}
+function buildJobContext() {
+	const storedInvoker = invokerStorage?.getStore();
+	const invoker = storedInvoker === void 0 ? readRuntimeInvoker() : storedInvoker;
+	const fromGlobal = readWorkflowTestEnv();
+	if (fromGlobal !== void 0) return {
+		env: { ...fromGlobal },
+		invoker
+	};
+	return {
+		env: {},
+		invoker
+	};
+}
+
+//#endregion
+//#region src/configure/services/workflow/wait-point-invoker.ts
+const WAIT_POINT_INVOKER = Symbol.for("tailor-platform/sdk:wait-point-invoker");
+const WAIT_POINT_KEY = Symbol.for("tailor-platform/sdk:wait-point-key");
+function getPlatformWorkflow() {
+	const workflow = globalThis.tailor?.workflow;
+	if (!workflow) throw new Error("tailor.workflow is not available. Run tests in the `tailor-runtime` Vitest environment, or acquire mockWorkflow() from @tailor-platform/sdk/vitest and set a wait/resolve handler.");
+	return workflow;
+}
+/**
+* Create the invoker a single wait point definition delegates to.
+* @returns An invoker bound to the platform runtime
+*/
+function createWaitPointInvoker() {
+	return {
+		wait(key, payload) {
+			return getPlatformWorkflow().wait(key, payload);
+		},
+		async resolve(key, executionId, callback) {
+			await getPlatformWorkflow().resolve(executionId, key, callback);
+		}
+	};
+}
+/**
+* Attach an invoker to a wait point definition so test doubles can intercept it.
+*
+* The slot itself is fixed once attached; a double swaps the invoker's `wait` /
+* `resolve` methods rather than the invoker object.
+* @param target - Wait point definition to attach to
+* @param invoker - Invoker the definition delegates to
+* @returns The same definition
+*/
+function attachWaitPointInvoker(target, invoker) {
+	Object.defineProperty(target, WAIT_POINT_INVOKER, {
+		value: invoker,
+		enumerable: false,
+		configurable: false,
+		writable: false
+	});
+	return target;
+}
+/**
+* Read the invoker attached to a wait point definition.
+* @param target - Wait point definition to read from
+* @returns The attached invoker, or undefined when the value is not a wait point
+*/
+function getWaitPointInvoker(target) {
+	return target[WAIT_POINT_INVOKER];
+}
+/**
+* Record the resolved key on a wait point bound by `.with()`.
+* @param target - Bound wait point to attach to
+* @param key - Resolved runtime key
+* @returns The same bound wait point
+*/
+function attachWaitPointKey(target, key) {
+	Object.defineProperty(target, WAIT_POINT_KEY, {
+		value: key,
+		enumerable: false,
+		configurable: false,
+		writable: false
+	});
+	return target;
+}
+/**
+* Read the resolved key recorded on a bound wait point.
+* @param target - Bound wait point to read from
+* @returns The resolved key, or undefined when the value is not a bound wait point
+*/
+function getWaitPointKey(target) {
+	return target[WAIT_POINT_KEY];
+}
+
+//#endregion
+export { getWaitPointKey as a, readWorkflowTestEnv as c, getWaitPointInvoker as i, withWorkflowTestInvoker as l, attachWaitPointKey as n, buildJobContext as o, createWaitPointInvoker as r, clearWorkflowTestEnv as s, attachWaitPointInvoker as t, writeWorkflowTestEnv as u };
+//# sourceMappingURL=wait-point-invoker-__oE88_P.mjs.map

package/dist/wait-point-invoker-__oE88_P.mjs.map

@@ -0,0 +1 @@
+{"version":3,"file":"wait-point-invoker-__oE88_P.mjs","names":["platform"],"sources":["../src/configure/services/workflow/test-env-key.ts","../src/configure/services/workflow/wait-point-invoker.ts"],"sourcesContent":["/**\n * Typed accessors for the test-time globalThis slot used to pass `env` from\n * `mockWorkflow().setEnv()` (in `@tailor-platform/sdk/vitest`) to\n * `runWorkflowLocally()` job bodies. The slot key is private to this\n * module; callers go through the get/set/clear functions below so both sides\n * share the same access path.\n *\n * Lives in its own file (with no `@/` imports) so `vitest/mock.ts` can load\n * it from nested Vitest configs that do not resolve `@/` aliases.\n * @internal\n */\nimport { AsyncLocalStorage } from \"node:async_hooks\";\nimport type { TailorEnv, TailorPrincipal } from \"../../../runtime/types\";\n\nconst SLOT_KEY = \"__tailorWorkflowTestEnv\";\n\ntype AsyncLocalStorageLike<T> = {\n  getStore(): T | undefined;\n  run<R>(store: T, callback: () => R): R;\n};\n\nlet invokerStorage: AsyncLocalStorageLike<TailorPrincipal | null> | undefined;\n\nfunction workflowInvokerStorage(): AsyncLocalStorageLike<TailorPrincipal | null> {\n  if (!invokerStorage) {\n    invokerStorage = new AsyncLocalStorage<TailorPrincipal | null>();\n  }\n  return invokerStorage;\n}\n\n/**\n * Read the test-time env slot.\n * @returns Current env, or `undefined` when unset.\n * @internal\n */\nexport function readWorkflowTestEnv(): TailorEnv | undefined {\n  return (globalThis as unknown as Record<string, TailorEnv | undefined>)[SLOT_KEY];\n}\n\n/**\n * Write the test-time env slot.\n * @param env - Env value to expose to `runWorkflowLocally()` job bodies.\n * @internal\n */\nexport function writeWorkflowTestEnv(env: TailorEnv): void {\n  (globalThis as unknown as Record<string, TailorEnv>)[SLOT_KEY] = env;\n}\n\n/**\n * Clear the test-time env slot.\n * @internal\n */\nexport function clearWorkflowTestEnv(): void {\n  delete (globalThis as unknown as Record<string, unknown>)[SLOT_KEY];\n}\n\nexport function withWorkflowTestInvoker<T>(invoker: TailorPrincipal | null, run: () => T): T {\n  return workflowInvokerStorage().run(invoker, run);\n}\n\ntype RuntimeInvoker = {\n  id: string;\n  type: \"user\" | \"machine_user\";\n  workspaceId: string;\n  attributes?: string[] | TailorPrincipal[\"attributes\"];\n  attributeMap?: TailorPrincipal[\"attributes\"];\n  attributeList?: TailorPrincipal[\"attributeList\"];\n};\n\nfunction readRuntimeInvoker(): TailorPrincipal | null {\n  const runtime = (\n    globalThis as unknown as {\n      tailor?: { context?: { getInvoker?: () => RuntimeInvoker | null } };\n    }\n  ).tailor?.context?.getInvoker;\n  const raw = runtime?.();\n  if (!raw) return null;\n  return {\n    id: raw.id,\n    type: raw.type,\n    workspaceId: raw.workspaceId,\n    attributes: raw.attributeMap ?? (Array.isArray(raw.attributes) ? {} : (raw.attributes ?? {})),\n    attributeList: (raw.attributeList ??\n      (Array.isArray(raw.attributes) ? raw.attributes : [])) as TailorPrincipal[\"attributeList\"],\n  };\n}\n\n// Shallow-copied to isolate against cross-trigger mutation.\nexport function buildJobContext(): { env: TailorEnv; invoker: TailorPrincipal | null } {\n  const storedInvoker = invokerStorage?.getStore();\n  const invoker = storedInvoker === undefined ? readRuntimeInvoker() : storedInvoker;\n  const fromGlobal = readWorkflowTestEnv();\n  if (fromGlobal !== undefined) return { env: { ...fromGlobal }, invoker };\n  return { env: {} as TailorEnv, invoker };\n}\n","import type { PlatformWorkflowAPI } from \"#/runtime/workflow\";\n\n// Not re-exported from the workflow barrel: the slot exists so the Vitest mock\n// can intercept parameterized wait points, whose `wait`/`resolve` live on\n// short-lived objects returned by `.with()` rather than on the definition.\nconst WAIT_POINT_INVOKER: unique symbol = Symbol.for(\"tailor-platform/sdk:wait-point-invoker\");\nconst WAIT_POINT_KEY: unique symbol = Symbol.for(\"tailor-platform/sdk:wait-point-key\");\n\n/** Indirection every wait point call routes through, keyed by resolved key. */\nexport interface WaitPointInvoker {\n  wait(key: string, payload: unknown): unknown;\n  resolve(\n    key: string,\n    executionId: string,\n    callback: (payload: unknown) => unknown | Promise<unknown>,\n  ): Promise<void>;\n}\n\nfunction getPlatformWorkflow(): PlatformWorkflowAPI {\n  const platform = globalThis as { tailor?: { workflow?: PlatformWorkflowAPI } };\n  const workflow = platform.tailor?.workflow;\n  if (!workflow) {\n    throw new Error(\n      \"tailor.workflow is not available. Run tests in the `tailor-runtime` Vitest environment, \" +\n        \"or acquire mockWorkflow() from @tailor-platform/sdk/vitest and set a wait/resolve handler.\",\n    );\n  }\n  return workflow;\n}\n\n/**\n * Create the invoker a single wait point definition delegates to.\n * @returns An invoker bound to the platform runtime\n */\nexport function createWaitPointInvoker(): WaitPointInvoker {\n  return {\n    wait(key, payload) {\n      return getPlatformWorkflow().wait(key, payload);\n    },\n    async resolve(key, executionId, callback) {\n      await getPlatformWorkflow().resolve(executionId, key, callback);\n    },\n  };\n}\n\n/**\n * Attach an invoker to a wait point definition so test doubles can intercept it.\n *\n * The slot itself is fixed once attached; a double swaps the invoker's `wait` /\n * `resolve` methods rather than the invoker object.\n * @param target - Wait point definition to attach to\n * @param invoker - Invoker the definition delegates to\n * @returns The same definition\n */\nexport function attachWaitPointInvoker<T extends object>(target: T, invoker: WaitPointInvoker): T {\n  Object.defineProperty(target, WAIT_POINT_INVOKER, {\n    value: invoker,\n    enumerable: false,\n    configurable: false,\n    writable: false,\n  });\n  return target;\n}\n\n/**\n * Read the invoker attached to a wait point definition.\n * @param target - Wait point definition to read from\n * @returns The attached invoker, or undefined when the value is not a wait point\n */\nexport function getWaitPointInvoker(target: object): WaitPointInvoker | undefined {\n  return (target as Record<symbol, WaitPointInvoker | undefined>)[WAIT_POINT_INVOKER];\n}\n\n/**\n * Record the resolved key on a wait point bound by `.with()`.\n * @param target - Bound wait point to attach to\n * @param key - Resolved runtime key\n * @returns The same bound wait point\n */\nexport function attachWaitPointKey<T extends object>(target: T, key: string): T {\n  Object.defineProperty(target, WAIT_POINT_KEY, {\n    value: key,\n    enumerable: false,\n    configurable: false,\n    writable: false,\n  });\n  return target;\n}\n\n/**\n * Read the resolved key recorded on a bound wait point.\n * @param target - Bound wait point to read from\n * @returns The resolved key, or undefined when the value is not a bound wait point\n */\nexport function getWaitPointKey(target: object): string | undefined {\n  return (target as Record<symbol, string | undefined>)[WAIT_POINT_KEY];\n}\n"],"mappings":";;;;;;;;;;;;;;AAcA,MAAM,WAAW;AAOjB,IAAI;AAEJ,SAAS,yBAAwE;CAC/E,IAAI,CAAC,gBACH,iBAAiB,IAAI,kBAA0C;CAEjE,OAAO;AACT;;;;;;AAOA,SAAgB,sBAA6C;CAC3D,OAAQ,WAAgE;AAC1E;;;;;;AAOA,SAAgB,qBAAqB,KAAsB;CACzD,AAAC,WAAoD,YAAY;AACnE;;;;;AAMA,SAAgB,uBAA6B;CAC3C,OAAQ,WAAkD;AAC5D;AAEA,SAAgB,wBAA2B,SAAiC,KAAiB;CAC3F,OAAO,uBAAuB,CAAC,CAAC,IAAI,SAAS,GAAG;AAClD;AAWA,SAAS,qBAA6C;CACpD,MAAM,UACJ,WAGA,QAAQ,SAAS;CACnB,MAAM,MAAM,UAAU;CACtB,IAAI,CAAC,KAAK,OAAO;CACjB,OAAO;EACL,IAAI,IAAI;EACR,MAAM,IAAI;EACV,aAAa,IAAI;EACjB,YAAY,IAAI,iBAAiB,MAAM,QAAQ,IAAI,UAAU,IAAI,CAAC,IAAK,IAAI,cAAc,CAAC;EAC1F,eAAgB,IAAI,kBACjB,MAAM,QAAQ,IAAI,UAAU,IAAI,IAAI,aAAa,CAAC;CACvD;AACF;AAGA,SAAgB,kBAAuE;CACrF,MAAM,gBAAgB,gBAAgB,SAAS;CAC/C,MAAM,UAAU,kBAAkB,SAAY,mBAAmB,IAAI;CACrE,MAAM,aAAa,oBAAoB;CACvC,IAAI,eAAe,QAAW,OAAO;EAAE,KAAK,EAAE,GAAG,WAAW;EAAG;CAAQ;CACvE,OAAO;EAAE,KAAK,CAAC;EAAgB;CAAQ;AACzC;;;;ACzFA,MAAM,qBAAoC,OAAO,IAAI,wCAAwC;AAC7F,MAAM,iBAAgC,OAAO,IAAI,oCAAoC;AAYrF,SAAS,sBAA2C;CAElD,MAAM,WAAWA,WAAS,QAAQ;CAClC,IAAI,CAAC,UACH,MAAM,IAAI,MACR,oLAEF;CAEF,OAAO;AACT;;;;;AAMA,SAAgB,yBAA2C;CACzD,OAAO;EACL,KAAK,KAAK,SAAS;GACjB,OAAO,oBAAoB,CAAC,CAAC,KAAK,KAAK,OAAO;EAChD;EACA,MAAM,QAAQ,KAAK,aAAa,UAAU;GACxC,MAAM,oBAAoB,CAAC,CAAC,QAAQ,aAAa,KAAK,QAAQ;EAChE;CACF;AACF;;;;;;;;;;AAWA,SAAgB,uBAAyC,QAAW,SAA8B;CAChG,OAAO,eAAe,QAAQ,oBAAoB;EAChD,OAAO;EACP,YAAY;EACZ,cAAc;EACd,UAAU;CACZ,CAAC;CACD,OAAO;AACT;;;;;;AAOA,SAAgB,oBAAoB,QAA8C;CAChF,OAAQ,OAAwD;AAClE;;;;;;;AAQA,SAAgB,mBAAqC,QAAW,KAAgB;CAC9E,OAAO,eAAe,QAAQ,gBAAgB;EAC5C,OAAO;EACP,YAAY;EACZ,cAAc;EACd,UAAU;CACZ,CAAC;CACD,OAAO;AACT;;;;;;AAOA,SAAgB,gBAAgB,QAAoC;CAClE,OAAQ,OAA8C;AACxD"}

package/dist/wait-point-registry-TL99zotw.mjs

@@ -0,0 +1,47 @@
+//#region src/utils/wait-point-registry.ts
+const WAIT_POINT_REGISTRY_KEY = Symbol.for("tailor-platform/sdk:wait-point-registry");
+function registry() {
+	const g = globalThis;
+	let state = g[WAIT_POINT_REGISTRY_KEY];
+	if (!state) {
+		state = {
+			entries: [],
+			scopeStart: 0
+		};
+		g[WAIT_POINT_REGISTRY_KEY] = state;
+	}
+	return state;
+}
+/**
+* Record a declared wait point key so the CLI can check it against the key
+* rules once the declaring module has loaded.
+* @param entry - The key and the declaration it came from
+*/
+function registerWaitPoint(entry) {
+	registry().entries.push(entry);
+}
+/**
+* Start a scope here, so what a run declares can be told apart from what an
+* earlier one left behind.
+*
+* The registry is process-wide, and a run that fails partway still leaves its
+* keys in it. Without a scope, a second run in the same process would be judged
+* on the first run's keys as well as its own.
+*/
+function beginWaitPointScope() {
+	const state = registry();
+	state.scopeStart = state.entries.length;
+}
+/**
+* Read the wait points declared since {@link beginWaitPointScope}, or every one
+* of them when no scope was started.
+* @returns The wait points registered in the current scope, in declaration order
+*/
+function getScopedWaitPoints() {
+	const state = registry();
+	return state.entries.slice(state.scopeStart);
+}
+
+//#endregion
+export { getScopedWaitPoints as n, registerWaitPoint as r, beginWaitPointScope as t };
+//# sourceMappingURL=wait-point-registry-TL99zotw.mjs.map

package/dist/wait-point-registry-TL99zotw.mjs.map

@@ -0,0 +1 @@
+{"version":3,"file":"wait-point-registry-TL99zotw.mjs","names":[],"sources":["../src/utils/wait-point-registry.ts"],"sourcesContent":["/**\n * How a wait point key reached the SDK. The declaration decides what the key\n * may contain: only `define` sees the key as a literal type, so only it can\n * type the `$params` a key carries.\n */\nexport type WaitPointDeclaration = \"createWaitPoint\" | \"define\" | \"property\";\n\n/** A wait point key as declared, before the deploy-time key rules run. */\nexport interface RegisteredWaitPoint {\n  key: string;\n  declaredBy: WaitPointDeclaration;\n}\n\nconst WAIT_POINT_REGISTRY_KEY: unique symbol = Symbol.for(\n  \"tailor-platform/sdk:wait-point-registry\",\n);\n\ninterface Registry {\n  entries: RegisteredWaitPoint[];\n  scopeStart: number;\n}\n\ntype GlobalWithRegistry = typeof globalThis & {\n  [WAIT_POINT_REGISTRY_KEY]?: Registry;\n};\n\nfunction registry(): Registry {\n  const g = globalThis as GlobalWithRegistry;\n  let state = g[WAIT_POINT_REGISTRY_KEY];\n  if (!state) {\n    state = { entries: [], scopeStart: 0 };\n    g[WAIT_POINT_REGISTRY_KEY] = state;\n  }\n  return state;\n}\n\n/**\n * Record a declared wait point key so the CLI can check it against the key\n * rules once the declaring module has loaded.\n * @param entry - The key and the declaration it came from\n */\nexport function registerWaitPoint(entry: RegisteredWaitPoint): void {\n  registry().entries.push(entry);\n}\n\n/**\n * Read every wait point declared by the modules loaded so far.\n * @returns The registered wait points, in declaration order\n */\nexport function getRegisteredWaitPoints(): readonly RegisteredWaitPoint[] {\n  return registry().entries;\n}\n\n/**\n * Start a scope here, so what a run declares can be told apart from what an\n * earlier one left behind.\n *\n * The registry is process-wide, and a run that fails partway still leaves its\n * keys in it. Without a scope, a second run in the same process would be judged\n * on the first run's keys as well as its own.\n */\nexport function beginWaitPointScope(): void {\n  const state = registry();\n  state.scopeStart = state.entries.length;\n}\n\n/**\n * Read the wait points declared since {@link beginWaitPointScope}, or every one\n * of them when no scope was started.\n * @returns The wait points registered in the current scope, in declaration order\n */\nexport function getScopedWaitPoints(): readonly RegisteredWaitPoint[] {\n  const state = registry();\n  return state.entries.slice(state.scopeStart);\n}\n\n/**\n * Drop everything registered after a mark, where the mark is the length\n * {@link getRegisteredWaitPoints} returned earlier.\n *\n * The registry is process-wide, so a test that declares a key `deploy` rejects\n * would otherwise leave it for the deploy-time check another test file runs.\n * Nothing outside a test needs this: a CLI run declares one project's keys and\n * checks all of them.\n * @param mark - The registry length to return to\n */\nexport function restoreWaitPointRegistry(mark: number): void {\n  const state = registry();\n  state.entries.length = mark;\n  if (state.scopeStart > mark) state.scopeStart = mark;\n}\n"],"mappings":";AAaA,MAAM,0BAAyC,OAAO,IACpD,yCACF;AAWA,SAAS,WAAqB;CAC5B,MAAM,IAAI;CACV,IAAI,QAAQ,EAAE;CACd,IAAI,CAAC,OAAO;EACV,QAAQ;GAAE,SAAS,CAAC;GAAG,YAAY;EAAE;EACrC,EAAE,2BAA2B;CAC/B;CACA,OAAO;AACT;;;;;;AAOA,SAAgB,kBAAkB,OAAkC;CAClE,SAAS,CAAC,CAAC,QAAQ,KAAK,KAAK;AAC/B;;;;;;;;;AAkBA,SAAgB,sBAA4B;CAC1C,MAAM,QAAQ,SAAS;CACvB,MAAM,aAAa,MAAM,QAAQ;AACnC;;;;;;AAOA,SAAgB,sBAAsD;CACpE,MAAM,QAAQ,SAAS;CACvB,OAAO,MAAM,QAAQ,MAAM,MAAM,UAAU;AAC7C"}

package/docs/cli/setup.md

@@ -4,7 +4,7 @@ Commands for setting up project infrastructure.
 
 ## setup
 
-Generate CI deploy workflows for your project. (beta)
+Set up repository automation for your project. (beta)
 
 **Usage**
 
@@ -23,6 +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 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.                    |
 
@@ -159,6 +160,18 @@ 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

@@ -119,12 +119,15 @@ tailor tailordb migration generate [options]
 
 **Options**
 
-| Option              | Alias | Description                                | Required | Default              | Env                  |
-| ------------------- | ----- | ------------------------------------------ | -------- | -------------------- | -------------------- |
-| `--yes`             | `-y`  | Skip confirmation prompts                  | No       | `false`              | -                    |
-| `--config <CONFIG>` | `-c`  | Path to Tailor config file                 | No       | `"tailor.config.ts"` | `TAILOR_CONFIG_PATH` |
-| `--name <NAME>`     | `-n`  | Optional description for the migration     | No       | -                    | -                    |
-| `--init`            | -     | Delete existing migrations and start fresh | No       | `false`              | -                    |
+| 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       | -                    | -                    |
 
 See [Global Options](../cli-reference.md#global-options) for options available to all commands.
 

package/docs/cli-reference.md

@@ -391,13 +391,14 @@ Commands for setting up project infrastructure.
 
 | Command                                             | Description                                                                                      |
 | --------------------------------------------------- | ------------------------------------------------------------------------------------------------ |
-| [setup](./cli/setup.md#setup)                       | Generate CI deploy workflows for your project. (beta)                                            |
+| [setup](./cli/setup.md#setup)                       | Set up repository automation for your project. (beta)                                            |
 | [setup action](./cli/setup.md#setup-action)         | Generate a per-app composite action for use with setup coordinate (monorepo multi-app deploys).  |
 | [setup branch](./cli/setup.md#setup-branch)         | Generate a branch-target deploy workflow (push to branch triggers deploy).                       |
 | [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 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/github-actions.md

@@ -1,7 +1,7 @@
 # GitHub Actions Integration
 
-`tailor setup` generates a GitHub Actions workflow that deploys your
-Tailor Platform application automatically on push or tag.
+`tailor setup` generates GitHub repository automation for your Tailor Platform
+application, including deploy workflows and Renovate configuration.
 
 > **Beta:** This command is under active development. CLI flags, the generated
 > workflow, and the `.github/tailor.lock` schema may change before general
@@ -14,16 +14,13 @@ lives):
 
 ```bash
 # Branch target: deploy to stg on every push to main
-tailor setup -n my-app-stg
+tailor setup branch --name my-app-stg
 
 # Tag target: deploy to production when a tag is pushed, with an approval gate
-tailor setup -n my-app-prod \
-  --tag --branch main --environment production
+tailor setup tag --name my-app-prod \
+  --branch main --environment production
 ```
 
-`setup` defaults to the GitHub provider; `--provider github` (`-p github`) is
-accepted but optional, and other providers are not yet supported.
-
 After running the command, follow the **Next steps** printed to the terminal to
 set the required secrets, set the `TAILOR_PLATFORM_WORKSPACE_ID` variable, and
 commit the generated files.
@@ -44,9 +41,9 @@ 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):
 
 ```bash
-tailor setup -n my-app-stg
+tailor setup branch --name my-app-stg
 # Equivalent to:
-tailor setup -n my-app-stg --branch main
+tailor setup branch --name my-app-stg --branch main
 ```
 
 What it does:
@@ -69,7 +66,7 @@ Pass `--erd-preview` on a branch target to add TailorDB ERD preview artifacts
 to pull requests:
 
 ```bash
-tailor setup -n my-app-stg --erd-preview
+tailor setup branch --name my-app-stg --erd-preview
 ```
 
 The generated workflow runs `tailor tailordb erd`, which is provided by the
@@ -90,11 +87,10 @@ ERD preview does not use Tailor Platform credentials. Fork pull requests still
 build artifacts, but the comment step is skipped because fork tokens cannot
 write PR comments.
 
-`--erd-preview` is only available for branch targets with the plan job enabled;
-it cannot be combined with `--tag` or `--no-plan`. The namespace list is
-recorded in `.github/tailor.lock`; the pull request workflow compares the
-head and base lock files so newly added or removed namespaces can still produce
-all-added or all-removed viewer artifacts. Re-run `setup` after adding or
+`--erd-preview` is only available for branch targets. The namespace list is
+recorded in `.github/tailor.lock`; the pull request workflow compares the head
+and base lock files so newly added or removed namespaces can still produce
+all-added or all-removed viewer artifacts. Re-run `setup branch` after adding or
 removing TailorDB namespaces. `setup check` reports drift when the recorded ERD
 preview namespaces no longer match the current config.
 
@@ -104,8 +100,8 @@ The tag target fires when a tag matching `--tag-pattern` (default `v*`) is
 pushed:
 
 ```bash
-tailor setup -n my-app-prod \
-  --tag --tag-pattern "v*" --branch main --environment production
+tailor setup tag --name my-app-prod \
+  --tag-pattern "v*" --branch main --environment production
 ```
 
 What it does:
@@ -131,7 +127,7 @@ What it does:
 | 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.   |
 
-The workspace name (`--workspace-name`, or the config `name` when omitted) must
+The workspace name (`--name`, or the config `name` when omitted) must
 be 3–63 characters of lowercase letters, numbers, and hyphens, and cannot start
 or end with a hyphen. It is used for the generated file name, the workflow
 `name:`, the plan label, and the default GitHub Environment name; it does not
@@ -174,7 +170,7 @@ environment is planned.)
 
 ## Generated files
 
-Running `setup` creates or updates:
+Running a workflow setup subcommand creates or updates:
 
 ### `.github/workflows/tailor-<workspace-name>.yml`
 
@@ -276,7 +272,7 @@ you can deploy any commit regardless of branch membership.
 For a monorepo where your SDK app lives in a subdirectory, pass `--dir`:
 
 ```bash
-tailor setup -n my-app --dir apps/backend
+tailor setup branch --name my-app --dir apps/backend
 ```
 
 The generated workflow adds a `paths` filter on `apps/backend/**` so the
@@ -341,11 +337,11 @@ A typical setup with staging and production:
 
 ```bash
 # Staging: main → stg (deploy on every push to main)
-tailor setup -n my-app-stg
+tailor setup branch --name my-app-stg
 
 # Production: tagged commits → prod, with approval gate and branch guard
-tailor setup -n my-app-prod \
-  --tag --branch main --environment production
+tailor setup tag --name my-app-prod \
+  --branch main --environment production
 ```
 
 Then provision each workspace and set its id on the matching environment (the
@@ -364,6 +360,41 @@ gh secret set TAILOR_PLATFORM_MACHINE_USER_CLIENT_SECRET --env production
 
 Commit both workflow files and `.github/tailor.lock`.
 
+## Keeping dependencies and actions updated
+
+Run this command once from the repository root to add Renovate configuration:
+
+```bash
+tailor setup renovate
+```
+
+It generates `renovate.json`, which extends Tailor's shared Renovate preset. The
+preset groups `@tailor-platform/*` package updates into one pull request and
+lets Renovate update the SHA-pinned GitHub Actions used by generated workflows.
+Enable Renovate for the repository by following the
+[Renovate onboarding guide](https://docs.renovatebot.com/getting-started/installing-onboarding/),
+then commit the generated file.
+
+If the repository already has Renovate configuration, the command adds
+`github>tailor-inc/renovate-config` to its `extends` array in place instead of
+writing a new file, leaving your other settings untouched. It checks Renovate's
+standard root, `.github`, `.gitlab`, and `.renovaterc` locations, including the
+deprecated `package.json` configuration. When that configuration already extends
+the preset, the command reports that Renovate is set up and changes nothing.
+
+Configuration written in JSON5 or JSONC — with comments or trailing commas —
+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
+them. To remove it, delete the file.
+
+Renovate updates the SDK dependency and action pins, but it does not regenerate
+the workflow template. After an SDK update, `tailor setup check --ci` reports a
+template-version warning until you re-run the relevant workflow setup
+subcommand.
+
 ## Checking for drift
 
 `tailor setup check` audits the workflows recorded in
@@ -374,12 +405,26 @@ newer template is available, `tailor.config.ts` is no longer under the recorded
 trigger. It exits non-zero when it finds drift, so you can run it in CI. Each
 finding names a stable rule key for future suppression.
 
+Workflows generated by `setup branch`, `setup tag`, `setup preview`, and
+`setup coordinate` self-audit: each contains a `tailor-drift-check` step that
+runs the check in CI. Preview workflows run it alongside each preview deploy,
+so pull requests that deploy no preview (drafts, fork PRs, and unlabeled PRs
+in label-triggered mode) skip the check. A single run audits every target
+recorded in `.github/tailor.lock`, so per-app composite actions generated by
+`setup action` are covered by their coordinator's step and do not carry one of
+their own.
+
+Drift findings are advisory by default. Set the repository variable
+`TAILOR_PLATFORM_FAIL_ON_DRIFT` to `true` to make unsuppressed findings fail
+the job. Execution and configuration errors fail regardless of this variable.
+
 ## Updating the generated workflow
 
-When you upgrade the SDK, re-run `setup` with the same flags to pick up
-template improvements. If the SDK detects that you have hand-edited a managed
-section, it stops and asks you to use `--force` to overwrite your edits, or to
-move your customizations into your own steps before regenerating.
+When you upgrade the SDK, re-run the relevant workflow setup subcommand with
+the same flags to pick up template improvements. If the SDK detects that you
+have hand-edited a managed section, it stops and asks you to use `--force` to
+overwrite your edits, or to move your customizations into your own steps before
+regenerating.
 
 The `.github/tailor.lock` file records the flags used at generation time,
 so you can check what arguments were used previously.

package/docs/migration/v2.md

@@ -8,6 +8,60 @@ Run the codemods, then finish anything reported as not migrated automatically:
 npx @tailor-platform/sdk-codemod --from <current-version> --to <target-version>
 ```
 
+## Type-only imports → `import type`
+
+**Migration:** Manual
+
+The v2 CLI runs TypeScript by stripping types from each file in isolation,
+with no cross-file type information. A plain (non-`type`) import of a
+type-only export therefore survives stripping and fails when the module
+loads:
+
+```
+SyntaxError: The requested module './types.ts' does not provide an export named 'Row'
+```
+
+`tailor generate` / `tailor deploy` stop at this error before doing any work.
+Import types with `import type` (or the inline `type` modifier), and
+re-export them with `export type`, in every module the CLI loads. Generated
+Kysely types (`DB`, `Insertable`, `Selectable`, table row types) are almost
+entirely type-only, so v1 projects typically hit this in many files at once.
+Set `"verbatimModuleSyntax": true` in tsconfig.json to catch every violation
+at typecheck; projects scaffolded by v2 `tailor init` enable it by default.
+
+Before:
+
+```ts
+import { DB, getDB } from "./generated/db";
+```
+
+After:
+
+```ts
+import { type DB, getDB } from "./generated/db";
+```
+
+<details>
+<summary>Prompt for an AI agent (to perform this migration)</summary>
+
+```text
+In Tailor SDK v2 the CLI loads TypeScript by stripping types from each file
+in isolation, so type-only exports do not exist at runtime and plain imports
+of them fail to load with "does not provide an export named '<name>'".
+Migrate the project so every type-only import and re-export is marked:
+
+1. Add `"verbatimModuleSyntax": true` to compilerOptions in tsconfig.json.
+2. Run `tsc --noEmit` and fix every reported violation: add the `type`
+   modifier to type-only named imports (`import type { Row }` or
+   `import { type Row, marker }`) and change type-only re-exports to
+   `export type { ... }`.
+
+Only add `type` modifiers; do not reorder, remove, or otherwise change
+imports that are used as values.
+```
+
+</details>
+
 ## defineGenerators → definePlugins
 
 **Migration:** Partially automatic