@tailor-platform/sdk 2.2.0 → 2.4.0

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/application.md

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

package/docs/cli/function.md

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

package/docs/cli/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

@@ -28,14 +28,14 @@ Truncate (delete all records from) TailorDB tables.
 **Usage**
 
 ```
-tailor tailordb truncate [options] [types]
+tailor tailordb truncate [options] [tables]
 ```
 
 **Arguments**
 
-| Argument | Description            | Required |
-| -------- | ---------------------- | -------- |
-| `types`  | Type names to truncate | No       |
+| Argument | Description             | Required |
+| -------- | ----------------------- | -------- |
+| `tables` | Table names to truncate | No       |
 
 **Options**
 
@@ -62,21 +62,21 @@ tailor tailordb truncate --all --yes
 # Truncate all tables in a specific namespace
 tailor tailordb truncate --namespace myNamespace
 
-# Truncate specific types (namespace is auto-detected)
+# Truncate specific tables (namespace is auto-detected)
 tailor tailordb truncate User Post Comment
 
-# Truncate specific types with confirmation skipped
+# Truncate specific tables with confirmation skipped
 tailor tailordb truncate User Post --yes
 ```
 
 **Notes:**
 
-- You must specify exactly one of: `--all`, `--namespace`, or type names
-- When truncating specific types, the namespace is automatically detected from your config
+- You must specify exactly one of: `--all`, `--namespace`, or table names
+- When truncating specific tables, the namespace is automatically detected from your config
 - Confirmation prompts vary based on the operation:
   - `--all`: requires typing `truncate all`
   - `--namespace`: requires typing `truncate <namespace-name>`
-  - Specific types: requires typing `yes`
+  - Specific tables: requires typing `yes`
 - Use `--yes` flag to skip confirmation prompts (useful for scripts and CI/CD)
 - Namespaces declared with `{ external: true }` are skipped by `--all` and rejected with a dedicated error when targeted by `--namespace`. Run truncate from the app that owns the namespace.
 
@@ -94,22 +94,22 @@ tailor tailordb migration <command>
 
 **Commands**
 
-| Command                                                           | Description                                                                                                                                                                                                                                                                                                              |
-| ----------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
-| [`tailordb migration generate`](#tailordb-migration-generate)     | Generate migration files by detecting schema differences between current local types and the previous migration snapshot.                                                                                                                                                                                                |
-| [`tailordb migration rebaseline`](#tailordb-migration-rebaseline) | Collapse the full migration history into a new 0000 baseline.                                                                                                                                                                                                                                                            |
-| [`tailordb migration script`](#tailordb-migration-script)         | Add a migration script (migrate.ts) template to an existing migration directory, or record with --no-script that a migration intentionally has none.                                                                                                                                                                     |
-| [`tailordb migration set`](#tailordb-migration-set)               | Set migration checkpoint to a specific number.                                                                                                                                                                                                                                                                           |
-| [`tailordb migration status`](#tailordb-migration-status)         | Show the current migration status for TailorDB namespaces, including applied and pending migrations.                                                                                                                                                                                                                     |
-| [`tailordb migration sync`](#tailordb-migration-sync)             | Sync remote TailorDB schema to a specific migration snapshot (recovery from --no-schema-check drift).                                                                                                                                                                                                                    |
-| [`tailordb migration test`](#tailordb-migration-test)             | Test pending migrations with seed fixtures or cloned data in a temporary workspace.                                                                                                                                                                                                                                      |
-| [`tailordb migration validate`](#tailordb-migration-validate)     | Validate the full migration history, unreviewed generated migration scripts, and schema drift (local types vs. migration snapshot, remote schema vs. migration checkpoint) without deploying. This includes the migration and schema-drift checks used by 'deploy' and exits with a non-zero code when issues are found. |
+| Command                                                           | Description                                                                                                                                                                                                                                                                                                               |
+| ----------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| [`tailordb migration generate`](#tailordb-migration-generate)     | Generate migration files by detecting schema differences between current local tables and the previous migration snapshot.                                                                                                                                                                                                |
+| [`tailordb migration rebaseline`](#tailordb-migration-rebaseline) | Collapse the full migration history into a new 0000 baseline.                                                                                                                                                                                                                                                             |
+| [`tailordb migration script`](#tailordb-migration-script)         | Add a migration script (migrate.ts) template to an existing migration directory, or record with --no-script that a migration intentionally has none.                                                                                                                                                                      |
+| [`tailordb migration set`](#tailordb-migration-set)               | Set migration checkpoint to a specific number.                                                                                                                                                                                                                                                                            |
+| [`tailordb migration status`](#tailordb-migration-status)         | Show the current migration status for TailorDB namespaces, including applied and pending migrations.                                                                                                                                                                                                                      |
+| [`tailordb migration sync`](#tailordb-migration-sync)             | Sync remote TailorDB schema to a specific migration snapshot (recovery from --no-schema-check drift).                                                                                                                                                                                                                     |
+| [`tailordb migration test`](#tailordb-migration-test)             | Test pending migrations with seed fixtures or cloned data in a temporary workspace.                                                                                                                                                                                                                                       |
+| [`tailordb migration validate`](#tailordb-migration-validate)     | Validate the full migration history, unreviewed generated migration scripts, and schema drift (local tables vs. migration snapshot, remote schema vs. migration checkpoint) without deploying. This includes the migration and schema-drift checks used by 'deploy' and exits with a non-zero code when issues are found. |
 
 See [Global Options](../cli-reference.md#global-options) for options available to all commands.
 
 #### tailordb migration generate
 
-Generate migration files by detecting schema differences between current local types and the previous migration snapshot.
+Generate migration files by detecting schema differences between current local tables and the previous migration snapshot.
 
 **Usage**
 
@@ -119,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 table rename instead of remove + add (format: "Table.oldField:newField" or "OldTable:NewTable"; repeatable). Renames require a migration script that copies the data.         | No       | -                    | -                    |
+| `--drop <DROP>`                       | -     | Confirm that a removed field or table is a genuine removal, not a rename (format: "Table.field" or "Table"; repeatable). Required in non-interactive runs for a removal with rename candidates. | No       | -                    | -                    |
+| `--expand-contract <EXPAND_CONTRACT>` | -     | Convert a field type through a temporary field (format: "Table.field"; repeatable). Generates two migrations.                                                                                   | No       | -                    | -                    |
 
 See [Global Options](../cli-reference.md#global-options) for options available to all commands.
 
@@ -306,7 +309,7 @@ The source workspace is read-only. Without --target-workspace-id, the command cr
 
 #### tailordb migration validate
 
-Validate the full migration history, unreviewed generated migration scripts, and schema drift (local types vs. migration snapshot, remote schema vs. migration checkpoint) without deploying. This includes the migration and schema-drift checks used by 'deploy' and exits with a non-zero code when issues are found.
+Validate the full migration history, unreviewed generated migration scripts, and schema drift (local tables vs. migration snapshot, remote schema vs. migration checkpoint) without deploying. This includes the migration and schema-drift checks used by 'deploy' and exits with a non-zero code when issues are found.
 
 **Usage**
 

package/docs/cli/workspace.md

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

package/docs/cli-reference.md

@@ -76,7 +76,7 @@ You can use environment variables to configure workspace and authentication:
 | `TAILOR_DTS_PATH`                            | Output path for generated `tailor.d.ts` type definition file                                          |
 | `TAILOR_PLATFORM_MACHINE_USER_CLIENT_ID`     | Client ID for `login --machine-user`                                                                  |
 | `TAILOR_PLATFORM_MACHINE_USER_CLIENT_SECRET` | Client secret for `login --machine-user`                                                              |
-| `TAILOR_PLATFORM_MACHINE_USER_NAME`          | Default machine user name for `query`, `workflow start`, `function test-run`, `machineuser token`     |
+| `TAILOR_PLATFORM_MACHINE_USER_NAME`          | Default machine user name for `query`, `workflow start`, `function run`, `machineuser token`          |
 | `TAILOR_PLATFORM_URL`                        | Platform API base URL. Saved into profiles created with `profile create --platform-url`               |
 | `TAILOR_PLATFORM_OAUTH2_CLIENT_ID`           | OAuth2 client ID for user login. Saved into profiles created with `profile create --oauth2-client-id` |
 | `TAILOR_PLATFORM_CONSOLE_URL`                | Console base URL. Saved into profiles created with `profile create --console-url`                     |
@@ -200,19 +200,19 @@ Commands for managing Tailor Platform applications (work with `tailor.config.ts`
 
 Commands for managing TailorDB tables, data, and schema migrations.
 
-| Command                                                                          | Description                                                                                                                                                                                                                                                                                                              |
-| -------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
-| [tailordb](./cli/tailordb.md#tailordb)                                           | Manage TailorDB tables and data.                                                                                                                                                                                                                                                                                         |
-| [tailordb truncate](./cli/tailordb.md#tailordb-truncate)                         | Truncate (delete all records from) TailorDB tables.                                                                                                                                                                                                                                                                      |
-| [tailordb migration](./cli/tailordb.md#tailordb-migration)                       | Manage TailorDB schema migrations.                                                                                                                                                                                                                                                                                       |
-| [tailordb migration generate](./cli/tailordb.md#tailordb-migration-generate)     | Generate migration files by detecting schema differences between current local types and the previous migration snapshot.                                                                                                                                                                                                |
-| [tailordb migration rebaseline](./cli/tailordb.md#tailordb-migration-rebaseline) | Collapse the full migration history into a new 0000 baseline.                                                                                                                                                                                                                                                            |
-| [tailordb migration script](./cli/tailordb.md#tailordb-migration-script)         | Add a migration script (migrate.ts) template to an existing migration directory, or record with --no-script that a migration intentionally has none.                                                                                                                                                                     |
-| [tailordb migration set](./cli/tailordb.md#tailordb-migration-set)               | Set migration checkpoint to a specific number.                                                                                                                                                                                                                                                                           |
-| [tailordb migration status](./cli/tailordb.md#tailordb-migration-status)         | Show the current migration status for TailorDB namespaces, including applied and pending migrations.                                                                                                                                                                                                                     |
-| [tailordb migration sync](./cli/tailordb.md#tailordb-migration-sync)             | Sync remote TailorDB schema to a specific migration snapshot (recovery from --no-schema-check drift).                                                                                                                                                                                                                    |
-| [tailordb migration test](./cli/tailordb.md#tailordb-migration-test)             | Test pending migrations with seed fixtures or cloned data in a temporary workspace.                                                                                                                                                                                                                                      |
-| [tailordb migration validate](./cli/tailordb.md#tailordb-migration-validate)     | Validate the full migration history, unreviewed generated migration scripts, and schema drift (local types vs. migration snapshot, remote schema vs. migration checkpoint) without deploying. This includes the migration and schema-drift checks used by 'deploy' and exits with a non-zero code when issues are found. |
+| Command                                                                          | Description                                                                                                                                                                                                                                                                                                               |
+| -------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| [tailordb](./cli/tailordb.md#tailordb)                                           | Manage TailorDB tables and data.                                                                                                                                                                                                                                                                                          |
+| [tailordb truncate](./cli/tailordb.md#tailordb-truncate)                         | Truncate (delete all records from) TailorDB tables.                                                                                                                                                                                                                                                                       |
+| [tailordb migration](./cli/tailordb.md#tailordb-migration)                       | Manage TailorDB schema migrations.                                                                                                                                                                                                                                                                                        |
+| [tailordb migration generate](./cli/tailordb.md#tailordb-migration-generate)     | Generate migration files by detecting schema differences between current local tables and the previous migration snapshot.                                                                                                                                                                                                |
+| [tailordb migration rebaseline](./cli/tailordb.md#tailordb-migration-rebaseline) | Collapse the full migration history into a new 0000 baseline.                                                                                                                                                                                                                                                             |
+| [tailordb migration script](./cli/tailordb.md#tailordb-migration-script)         | Add a migration script (migrate.ts) template to an existing migration directory, or record with --no-script that a migration intentionally has none.                                                                                                                                                                      |
+| [tailordb migration set](./cli/tailordb.md#tailordb-migration-set)               | Set migration checkpoint to a specific number.                                                                                                                                                                                                                                                                            |
+| [tailordb migration status](./cli/tailordb.md#tailordb-migration-status)         | Show the current migration status for TailorDB namespaces, including applied and pending migrations.                                                                                                                                                                                                                      |
+| [tailordb migration sync](./cli/tailordb.md#tailordb-migration-sync)             | Sync remote TailorDB schema to a specific migration snapshot (recovery from --no-schema-check drift).                                                                                                                                                                                                                     |
+| [tailordb migration test](./cli/tailordb.md#tailordb-migration-test)             | Test pending migrations with seed fixtures or cloned data in a temporary workspace.                                                                                                                                                                                                                                       |
+| [tailordb migration validate](./cli/tailordb.md#tailordb-migration-validate)     | Validate the full migration history, unreviewed generated migration scripts, and schema drift (local tables vs. migration snapshot, remote schema vs. migration checkpoint) without deploying. This includes the migration and schema-drift checks used by 'deploy' and exits with a non-zero code when issues are found. |
 
 ### [Query Commands](./cli/query.md)
 
@@ -323,13 +323,13 @@ Commands for managing workflows and executions.
 
 Commands for managing function registries and viewing function execution logs.
 
-| Command                                                  | Description                                                     |
-| -------------------------------------------------------- | --------------------------------------------------------------- |
-| [function](./cli/function.md#function)                   | Manage functions                                                |
-| [function get](./cli/function.md#function-get)           | Get a function registry by name                                 |
-| [function list](./cli/function.md#function-list)         | List function registries in a workspace                         |
-| [function logs](./cli/function.md#function-logs)         | List or get function execution logs.                            |
-| [function test-run](./cli/function.md#function-test-run) | Run a function on the Tailor Platform server without deploying. |
+| Command                                          | Description                                                     |
+| ------------------------------------------------ | --------------------------------------------------------------- |
+| [function](./cli/function.md#function)           | Manage functions                                                |
+| [function get](./cli/function.md#function-get)   | Get a function registry by name                                 |
+| [function list](./cli/function.md#function-list) | List function registries in a workspace                         |
+| [function logs](./cli/function.md#function-logs) | List or get function execution logs.                            |
+| [function run](./cli/function.md#function-run)   | Run a function on the Tailor Platform server without deploying. |
 
 ### [Executor Commands](./cli/executor.md)
 
@@ -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)