@tailor-platform/sdk 1.45.1 → 1.46.0

package/dist/telemetry-21afNV9_.mjs

@@ -0,0 +1,4 @@
+
+import { n as shutdownTelemetry, r as withSpan, t as initTelemetry } from "./telemetry-DcL8Fsm_.mjs";
+
+export { initTelemetry, shutdownTelemetry };

package/dist/{telemetry-DXitz4RH.mjs → telemetry-DcL8Fsm_.mjs}

@@ -82,4 +82,4 @@ async function withSpan(name, fn) {
 
 //#endregion
 export { shutdownTelemetry as n, withSpan as r, initTelemetry as t };
-//# sourceMappingURL=telemetry-DXitz4RH.mjs.map
+//# sourceMappingURL=telemetry-DcL8Fsm_.mjs.map

package/dist/{telemetry-DXitz4RH.mjs.map → telemetry-DcL8Fsm_.mjs.map}

@@ -1 +1 @@
-{"version":3,"file":"telemetry-DXitz4RH.mjs","names":[],"sources":["../src/cli/telemetry/config.ts","../src/cli/telemetry/index.ts"],"sourcesContent":["/**\n * Telemetry configuration parsed from standard OpenTelemetry environment variables.\n * Tracing is enabled when OTEL_EXPORTER_OTLP_ENDPOINT is set.\n */\nexport interface TelemetryConfig {\n  readonly enabled: boolean;\n  readonly endpoint: string;\n}\n\n/**\n * Parse telemetry configuration from standard OpenTelemetry environment variables.\n * Tracing is enabled when OTEL_EXPORTER_OTLP_ENDPOINT is set.\n * @returns Telemetry configuration\n */\nexport function parseTelemetryConfig(): TelemetryConfig {\n  const endpoint = process.env.OTEL_EXPORTER_OTLP_ENDPOINT ?? \"\";\n  const enabled = endpoint.length > 0;\n\n  return {\n    enabled,\n    endpoint,\n  };\n}\n","import { trace, SpanStatusCode, type Span } from \"@opentelemetry/api\";\nimport { parseTelemetryConfig, type TelemetryConfig } from \"./config\";\n\nlet _config: TelemetryConfig | undefined;\nlet _initialized = false;\nlet _provider: { register: () => void; shutdown: () => Promise<void> } | undefined;\n\n/**\n * Check whether telemetry is currently enabled.\n * @returns true if telemetry has been initialized and is enabled\n */\nexport function isTelemetryEnabled(): boolean {\n  return _config?.enabled ?? false;\n}\n\n/**\n * Initialize telemetry if OTEL_EXPORTER_OTLP_ENDPOINT is set.\n * When disabled, this is a no-op with zero overhead beyond reading env vars.\n * @returns Promise that resolves when initialization completes\n */\nexport async function initTelemetry(): Promise<void> {\n  if (_initialized) return;\n  _initialized = true;\n\n  _config = parseTelemetryConfig();\n  if (!_config.enabled) return;\n\n  // Dynamic imports - only loaded when tracing is enabled\n  const [\n    { NodeTracerProvider, BatchSpanProcessor },\n    { OTLPTraceExporter },\n    { resourceFromAttributes },\n    { ATTR_SERVICE_NAME, ATTR_SERVICE_VERSION },\n    { readPackageJson },\n  ] = await Promise.all([\n    import(\"@opentelemetry/sdk-trace-node\"),\n    import(\"@opentelemetry/exporter-trace-otlp-proto\"),\n    import(\"@opentelemetry/resources\"),\n    import(\"@opentelemetry/semantic-conventions\"),\n    import(\"@/cli/shared/package-json\"),\n  ]);\n\n  const packageJson = await readPackageJson();\n  const version = packageJson.version ?? \"unknown\";\n\n  const resource = resourceFromAttributes({\n    [ATTR_SERVICE_NAME]: \"tailor-sdk\",\n    [ATTR_SERVICE_VERSION]: version,\n  });\n\n  const exporter = new OTLPTraceExporter({\n    url: `${_config.endpoint}/v1/traces`,\n  });\n\n  _provider = new NodeTracerProvider({\n    resource,\n    spanProcessors: [new BatchSpanProcessor(exporter)],\n  });\n\n  _provider.register();\n}\n\n/**\n * Shutdown the telemetry provider, flushing all pending spans.\n * Must be called before process exit to ensure traces are exported.\n * @returns Promise that resolves when shutdown completes\n */\nexport async function shutdownTelemetry(): Promise<void> {\n  if (!_provider) return;\n  await _provider.shutdown();\n}\n\n/**\n * Execute a function within a new span. Records exceptions and sets span status.\n * When no TracerProvider is registered, the OTel API automatically provides\n * noop spans with zero overhead.\n * @param name - Span name\n * @param fn - Function to execute within the span\n * @returns Result of fn\n */\nexport async function withSpan<T>(name: string, fn: (span: Span) => Promise<T>): Promise<T> {\n  const tracer = trace.getTracer(\"tailor-sdk\");\n\n  return tracer.startActiveSpan(name, async (span) => {\n    try {\n      const result = await fn(span);\n      span.setStatus({ code: SpanStatusCode.OK });\n      return result;\n    } catch (error) {\n      span.setStatus({ code: SpanStatusCode.ERROR });\n      if (error instanceof Error) {\n        span.recordException(error);\n      }\n      throw error;\n    } finally {\n      span.end();\n    }\n  });\n}\n"],"mappings":";;;;;;;;;AAcA,SAAgB,uBAAwC;CACtD,MAAM,WAAW,QAAQ,IAAI,+BAA+B;AAG5D,QAAO;EACL,SAHc,SAAS,SAAS;EAIhC;EACD;;;;;AClBH,IAAI;AACJ,IAAI,eAAe;AACnB,IAAI;;;;;;AAeJ,eAAsB,gBAA+B;AACnD,KAAI,aAAc;AAClB,gBAAe;AAEf,WAAU,sBAAsB;AAChC,KAAI,CAAC,QAAQ,QAAS;CAGtB,MAAM,CACJ,EAAE,oBAAoB,sBACtB,EAAE,qBACF,EAAE,0BACF,EAAE,mBAAmB,wBACrB,EAAE,qBACA,MAAM,QAAQ,IAAI;EACpB,OAAO;EACP,OAAO;EACP,OAAO;EACP,OAAO;EACP,OAAO;EACR,CAAC;CAGF,MAAM,WAAU,MADU,iBAAiB,EACf,WAAW;AAWvC,aAAY,IAAI,mBAAmB;EACjC,UAVe,uBAAuB;IACrC,oBAAoB;IACpB,uBAAuB;GACzB,CAOS;EACR,gBAAgB,CAAC,IAAI,mBAAmB,IANrB,kBAAkB,EACrC,KAAK,GAAG,QAAQ,SAAS,aAC1B,CAIiD,CAAC,CAAC;EACnD,CAAC;AAEF,WAAU,UAAU;;;;;;;AAQtB,eAAsB,oBAAmC;AACvD,KAAI,CAAC,UAAW;AAChB,OAAM,UAAU,UAAU;;;;;;;;;;AAW5B,eAAsB,SAAY,MAAc,IAA4C;AAG1F,QAFe,MAAM,UAAU,aAElB,CAAC,gBAAgB,MAAM,OAAO,SAAS;AAClD,MAAI;GACF,MAAM,SAAS,MAAM,GAAG,KAAK;AAC7B,QAAK,UAAU,EAAE,MAAM,eAAe,IAAI,CAAC;AAC3C,UAAO;WACA,OAAO;AACd,QAAK,UAAU,EAAE,MAAM,eAAe,OAAO,CAAC;AAC9C,OAAI,iBAAiB,MACnB,MAAK,gBAAgB,MAAM;AAE7B,SAAM;YACE;AACR,QAAK,KAAK;;GAEZ"}
+{"version":3,"file":"telemetry-DcL8Fsm_.mjs","names":[],"sources":["../src/cli/telemetry/config.ts","../src/cli/telemetry/index.ts"],"sourcesContent":["/**\n * Telemetry configuration parsed from standard OpenTelemetry environment variables.\n * Tracing is enabled when OTEL_EXPORTER_OTLP_ENDPOINT is set.\n */\nexport interface TelemetryConfig {\n  readonly enabled: boolean;\n  readonly endpoint: string;\n}\n\n/**\n * Parse telemetry configuration from standard OpenTelemetry environment variables.\n * Tracing is enabled when OTEL_EXPORTER_OTLP_ENDPOINT is set.\n * @returns Telemetry configuration\n */\nexport function parseTelemetryConfig(): TelemetryConfig {\n  const endpoint = process.env.OTEL_EXPORTER_OTLP_ENDPOINT ?? \"\";\n  const enabled = endpoint.length > 0;\n\n  return {\n    enabled,\n    endpoint,\n  };\n}\n","import { trace, SpanStatusCode, type Span } from \"@opentelemetry/api\";\nimport { parseTelemetryConfig, type TelemetryConfig } from \"./config\";\n\nlet _config: TelemetryConfig | undefined;\nlet _initialized = false;\nlet _provider: { register: () => void; shutdown: () => Promise<void> } | undefined;\n\n/**\n * Check whether telemetry is currently enabled.\n * @returns true if telemetry has been initialized and is enabled\n */\nexport function isTelemetryEnabled(): boolean {\n  return _config?.enabled ?? false;\n}\n\n/**\n * Initialize telemetry if OTEL_EXPORTER_OTLP_ENDPOINT is set.\n * When disabled, this is a no-op with zero overhead beyond reading env vars.\n * @returns Promise that resolves when initialization completes\n */\nexport async function initTelemetry(): Promise<void> {\n  if (_initialized) return;\n  _initialized = true;\n\n  _config = parseTelemetryConfig();\n  if (!_config.enabled) return;\n\n  // Dynamic imports - only loaded when tracing is enabled\n  const [\n    { NodeTracerProvider, BatchSpanProcessor },\n    { OTLPTraceExporter },\n    { resourceFromAttributes },\n    { ATTR_SERVICE_NAME, ATTR_SERVICE_VERSION },\n    { readPackageJson },\n  ] = await Promise.all([\n    import(\"@opentelemetry/sdk-trace-node\"),\n    import(\"@opentelemetry/exporter-trace-otlp-proto\"),\n    import(\"@opentelemetry/resources\"),\n    import(\"@opentelemetry/semantic-conventions\"),\n    import(\"@/cli/shared/package-json\"),\n  ]);\n\n  const packageJson = await readPackageJson();\n  const version = packageJson.version ?? \"unknown\";\n\n  const resource = resourceFromAttributes({\n    [ATTR_SERVICE_NAME]: \"tailor-sdk\",\n    [ATTR_SERVICE_VERSION]: version,\n  });\n\n  const exporter = new OTLPTraceExporter({\n    url: `${_config.endpoint}/v1/traces`,\n  });\n\n  _provider = new NodeTracerProvider({\n    resource,\n    spanProcessors: [new BatchSpanProcessor(exporter)],\n  });\n\n  _provider.register();\n}\n\n/**\n * Shutdown the telemetry provider, flushing all pending spans.\n * Must be called before process exit to ensure traces are exported.\n * @returns Promise that resolves when shutdown completes\n */\nexport async function shutdownTelemetry(): Promise<void> {\n  if (!_provider) return;\n  await _provider.shutdown();\n}\n\n/**\n * Execute a function within a new span. Records exceptions and sets span status.\n * When no TracerProvider is registered, the OTel API automatically provides\n * noop spans with zero overhead.\n * @param name - Span name\n * @param fn - Function to execute within the span\n * @returns Result of fn\n */\nexport async function withSpan<T>(name: string, fn: (span: Span) => Promise<T>): Promise<T> {\n  const tracer = trace.getTracer(\"tailor-sdk\");\n\n  return tracer.startActiveSpan(name, async (span) => {\n    try {\n      const result = await fn(span);\n      span.setStatus({ code: SpanStatusCode.OK });\n      return result;\n    } catch (error) {\n      span.setStatus({ code: SpanStatusCode.ERROR });\n      if (error instanceof Error) {\n        span.recordException(error);\n      }\n      throw error;\n    } finally {\n      span.end();\n    }\n  });\n}\n"],"mappings":";;;;;;;;;AAcA,SAAgB,uBAAwC;CACtD,MAAM,WAAW,QAAQ,IAAI,+BAA+B;AAG5D,QAAO;EACL,SAHc,SAAS,SAAS;EAIhC;EACD;;;;;AClBH,IAAI;AACJ,IAAI,eAAe;AACnB,IAAI;;;;;;AAeJ,eAAsB,gBAA+B;AACnD,KAAI,aAAc;AAClB,gBAAe;AAEf,WAAU,sBAAsB;AAChC,KAAI,CAAC,QAAQ,QAAS;CAGtB,MAAM,CACJ,EAAE,oBAAoB,sBACtB,EAAE,qBACF,EAAE,0BACF,EAAE,mBAAmB,wBACrB,EAAE,qBACA,MAAM,QAAQ,IAAI;EACpB,OAAO;EACP,OAAO;EACP,OAAO;EACP,OAAO;EACP,OAAO;EACR,CAAC;CAGF,MAAM,WAAU,MADU,iBAAiB,EACf,WAAW;AAWvC,aAAY,IAAI,mBAAmB;EACjC,UAVe,uBAAuB;IACrC,oBAAoB;IACpB,uBAAuB;GACzB,CAOS;EACR,gBAAgB,CAAC,IAAI,mBAAmB,IANrB,kBAAkB,EACrC,KAAK,GAAG,QAAQ,SAAS,aAC1B,CAIiD,CAAC,CAAC;EACnD,CAAC;AAEF,WAAU,UAAU;;;;;;;AAQtB,eAAsB,oBAAmC;AACvD,KAAI,CAAC,UAAW;AAChB,OAAM,UAAU,UAAU;;;;;;;;;;AAW5B,eAAsB,SAAY,MAAc,IAA4C;AAG1F,QAFe,MAAM,UAAU,aAElB,CAAC,gBAAgB,MAAM,OAAO,SAAS;AAClD,MAAI;GACF,MAAM,SAAS,MAAM,GAAG,KAAK;AAC7B,QAAK,UAAU,EAAE,MAAM,eAAe,IAAI,CAAC;AAC3C,UAAO;WACA,OAAO;AACd,QAAK,UAAU,EAAE,MAAM,eAAe,OAAO,CAAC;AAC9C,OAAI,iBAAiB,MACnB,MAAK,gBAAgB,MAAM;AAE7B,SAAM;YACE;AACR,QAAK,KAAK;;GAEZ"}

package/dist/utils/test/index.d.mts

@@ -1,7 +1,7 @@
 /// <reference types="@tailor-platform/function-types" />
 import { Vt as TailorInvoker } from "../../tailor-db-field-Hx9OqPWY.mjs";
 import { O as TailorDBType } from "../../workflow.generated-DFljpJh7.mjs";
-import { dt as WORKFLOW_TEST_ENV_KEY, n as output, xt as TailorField } from "../../index-DUKJPEwq.mjs";
+import { dt as WORKFLOW_TEST_ENV_KEY, n as output, xt as TailorField } from "../../index-PB0otrDj.mjs";
 import { StandardSchemaV1 } from "@standard-schema/spec";
 
 //#region src/utils/test/mock.d.ts

package/docs/cli/application.md

@@ -89,29 +89,31 @@ See [Global Options](../cli-reference.md#global-options) for options available t
 
 <!-- politty:command:generate:global-options-link:end -->
 
-<!-- politty:command:apply:heading:start -->
+<!-- politty:command:deploy:heading:start -->
 
-## apply
+## deploy
 
-<!-- politty:command:apply:heading:end -->
+<!-- politty:command:deploy:heading:end -->
 
-<!-- politty:command:apply:description:start -->
+<!-- politty:command:deploy:description:start -->
 
-Apply Tailor configuration to deploy your application.
+Deploy your application by applying the Tailor configuration.
 
-<!-- politty:command:apply:description:end -->
+**Aliases:** `apply`
 
-<!-- politty:command:apply:usage:start -->
+<!-- politty:command:deploy:description:end -->
+
+<!-- politty:command:deploy:usage:start -->
 
 **Usage**
 
 ```
-tailor-sdk apply [options]
+tailor-sdk deploy [options]
 ```
 
-<!-- politty:command:apply:usage:end -->
+<!-- politty:command:deploy:usage:end -->
 
-<!-- politty:command:apply:options:start -->
+<!-- politty:command:deploy:options:start -->
 
 **Options**
 
@@ -126,17 +128,17 @@ tailor-sdk apply [options]
 | `--no-cache`                    | -     | Disable bundle caching for this run                | No       | -                    | -                                 |
 | `--clean-cache`                 | -     | Clean the bundle cache before building             | No       | -                    | -                                 |
 
-<!-- politty:command:apply:options:end -->
+<!-- politty:command:deploy:options:end -->
 
-<!-- politty:command:apply:global-options-link:start -->
+<!-- politty:command:deploy:global-options-link:start -->
 
 See [Global Options](../cli-reference.md#global-options) for options available to all commands.
 
-<!-- politty:command:apply:global-options-link:end -->
+<!-- politty:command:deploy:global-options-link:end -->
 
 **Migration Handling:**
 
-When migrations are configured (`db.tailordb.migration` in config), the `apply` command automatically:
+When migrations are configured (`db.tailordb.migration` in config), the `deploy` command automatically:
 
 1. Detects pending migration scripts that haven't been executed
 2. Applies schema changes in a safe order (pre-migration → script execution → post-migration)
@@ -147,18 +149,18 @@ See [TailorDB Commands](./tailordb.md#automatic-migration-execution) for details
 
 **Schema Check:**
 
-By default, `apply` performs two verification steps:
+By default, `deploy` performs two verification steps:
 
 1. **Local schema check**: Verifies that local schema changes match the migration files. This ensures migrations are properly generated before deployment.
 2. **Remote schema check**: Verifies that the remote schema matches the expected state based on migration history. This detects schema drift caused by manual changes or other developers.
 
-If remote schema drift is detected, the apply will fail with an error showing the differences. This helps prevent applying migrations to an inconsistent state.
+If remote schema drift is detected, the deploy will fail with an error showing the differences. This helps prevent applying migrations to an inconsistent state.
 
 Use `--no-schema-check` to skip both verifications (not recommended for production).
 
 **Plan Output:**
 
-Before applying changes, `apply` shows a preview of the planned resource changes.
+Before applying changes, `deploy` shows a preview of the planned resource changes.
 
 - `+` means the resource will be created
 - `~` means the resource will be updated

package/docs/cli/crashreport.md

@@ -0,0 +1,119 @@
+# Crash Report Commands
+
+Commands for managing crash reports.
+
+<!-- politty:command:crashreport:heading:start -->
+
+## crashreport
+
+<!-- politty:command:crashreport:heading:end -->
+
+<!-- politty:command:crashreport:description:start -->
+
+Manage crash reports.
+
+**Aliases:** `crash-report`
+
+<!-- politty:command:crashreport:description:end -->
+
+<!-- politty:command:crashreport:usage:start -->
+
+**Usage**
+
+```
+tailor-sdk crashreport [command]
+```
+
+<!-- politty:command:crashreport:usage:end -->
+
+<!-- politty:command:crashreport:global-options-link:start -->
+
+See [Global Options](../cli-reference.md#global-options) for options available to all commands.
+
+<!-- politty:command:crashreport:global-options-link:end -->
+
+<!-- politty:command:crashreport:subcommands:start -->
+
+**Commands**
+
+| Command                                 | Description                                    |
+| --------------------------------------- | ---------------------------------------------- |
+| [`crashreport list`](#crashreport-list) | List local crash report files.                 |
+| [`crashreport send`](#crashreport-send) | Submit a crash report to help improve the SDK. |
+
+<!-- politty:command:crashreport:subcommands:end -->
+<!-- politty:command:crashreport list:heading:start -->
+
+### crashreport list
+
+<!-- politty:command:crashreport list:heading:end -->
+
+<!-- politty:command:crashreport list:description:start -->
+
+List local crash report files.
+
+<!-- politty:command:crashreport list:description:end -->
+
+<!-- politty:command:crashreport list:usage:start -->
+
+**Usage**
+
+```
+tailor-sdk crashreport list [options]
+```
+
+<!-- politty:command:crashreport list:usage:end -->
+
+<!-- politty:command:crashreport list:options:start -->
+
+**Options**
+
+| Option            | Alias | Description                                              | Required | Default  |
+| ----------------- | ----- | -------------------------------------------------------- | -------- | -------- |
+| `--order <ORDER>` | -     | Sort order (asc or desc)                                 | No       | `"desc"` |
+| `--limit <LIMIT>` | `-l`  | Maximum number of items to return (0 or omit: unlimited) | No       | -        |
+
+<!-- politty:command:crashreport list:options:end -->
+
+<!-- politty:command:crashreport list:global-options-link:start -->
+
+See [Global Options](../cli-reference.md#global-options) for options available to all commands.
+
+<!-- politty:command:crashreport list:global-options-link:end -->
+<!-- politty:command:crashreport send:heading:start -->
+
+### crashreport send
+
+<!-- politty:command:crashreport send:heading:end -->
+
+<!-- politty:command:crashreport send:description:start -->
+
+Submit a crash report to help improve the SDK.
+
+<!-- politty:command:crashreport send:description:end -->
+
+<!-- politty:command:crashreport send:usage:start -->
+
+**Usage**
+
+```
+tailor-sdk crashreport send [options]
+```
+
+<!-- politty:command:crashreport send:usage:end -->
+
+<!-- politty:command:crashreport send:options:start -->
+
+**Options**
+
+| Option          | Alias | Description                   | Required | Default |
+| --------------- | ----- | ----------------------------- | -------- | ------- |
+| `--file <FILE>` | -     | Path to the crash report file | Yes      | -       |
+
+<!-- politty:command:crashreport send:options:end -->
+
+<!-- politty:command:crashreport send:global-options-link:start -->
+
+See [Global Options](../cli-reference.md#global-options) for options available to all commands.
+
+<!-- politty:command:crashreport send:global-options-link:end -->

package/docs/cli/executor.md

@@ -151,7 +151,7 @@ List or get executor jobs.
 **Usage**
 
 ```
-tailor-sdk executor jobs [options] <executorName> [jobId]
+tailor-sdk executor jobs [options] <executor-name> [job-id]
 ```
 
 <!-- politty:command:executor jobs:usage:end -->
@@ -160,10 +160,10 @@ tailor-sdk executor jobs [options] <executorName> [jobId]
 
 **Arguments**
 
-| Argument       | Description                             | Required |
-| -------------- | --------------------------------------- | -------- |
-| `executorName` | Executor name                           | Yes      |
-| `jobId`        | Job ID (if provided, shows job details) | No       |
+| Argument        | Description                             | Required |
+| --------------- | --------------------------------------- | -------- |
+| `executor-name` | Executor name                           | Yes      |
+| `job-id`        | Job ID (if provided, shows job details) | No       |
 
 <!-- politty:command:executor jobs:arguments:end -->
 
@@ -256,7 +256,7 @@ Trigger an executor manually.
 **Usage**
 
 ```
-tailor-sdk executor trigger [options] <executorName>
+tailor-sdk executor trigger [options] <executor-name>
 ```
 
 <!-- politty:command:executor trigger:usage:end -->
@@ -265,9 +265,9 @@ tailor-sdk executor trigger [options] <executorName>
 
 **Arguments**
 
-| Argument       | Description   | Required |
-| -------------- | ------------- | -------- |
-| `executorName` | Executor name | Yes      |
+| Argument        | Description   | Required |
+| --------------- | ------------- | -------- |
+| `executor-name` | Executor name | Yes      |
 
 <!-- politty:command:executor trigger:arguments:end -->
 

package/docs/cli/function.md

@@ -139,7 +139,7 @@ List or get function execution logs.
 **Usage**
 
 ```
-tailor-sdk function logs [options] [executionId]
+tailor-sdk function logs [options] [execution-id]
 ```
 
 <!-- politty:command:function logs:usage:end -->
@@ -148,9 +148,9 @@ tailor-sdk function logs [options] [executionId]
 
 **Arguments**
 
-| Argument      | Description                                         | Required |
-| ------------- | --------------------------------------------------- | -------- |
-| `executionId` | Execution ID (if provided, shows details with logs) | No       |
+| Argument       | Description                                         | Required |
+| -------------- | --------------------------------------------------- | -------- |
+| `execution-id` | Execution ID (if provided, shows details with logs) | No       |
 
 <!-- politty:command:function logs:arguments:end -->
 
@@ -209,7 +209,7 @@ $ tailor-sdk function logs <execution-id> --json
 
 When viewing a specific execution that failed, the command displays error details with the stack trace mapped back to original source files via the inline sourcemap (clickable file links and code snippets, matching `function test-run` output).
 
-When the deployed script cannot be downloaded or the function has been redeployed since the execution, the command falls back to a plain-text error display to avoid showing misleading source locations.
+The download is pinned to the bundle that actually ran using the execution's content hash, so stack traces stay accurate across redeploys when the server retains old bundles. The command falls back to a plain-text error display when the pinned bundle cannot be retrieved, or when the execution was recorded before content hashes started being tracked and the function was redeployed after it ran.
 
 <!-- politty:command:function logs:notes:end -->
 

package/docs/cli/tailordb.md

@@ -135,7 +135,7 @@ Manage TailorDB schema migrations.
 
 <!-- politty:command:tailordb migration:description:end -->
 
-Note: Migration scripts are automatically executed during `tailor-sdk apply`. See [Automatic Migration Execution](../services/tailordb-migration.md#automatic-migration-execution) for details.
+Note: Migration scripts are automatically executed during `tailor-sdk deploy`. See [Automatic Migration Execution](../services/tailordb-migration.md#automatic-migration-execution) for details.
 
 <!-- politty:command:tailordb migration:usage:start -->
 

package/docs/cli/workflow.md

@@ -202,7 +202,7 @@ List or get workflow executions.
 **Usage**
 
 ```
-tailor-sdk workflow executions [options] [executionId]
+tailor-sdk workflow executions [options] [execution-id]
 ```
 
 <!-- politty:command:workflow executions:usage:end -->
@@ -211,9 +211,9 @@ tailor-sdk workflow executions [options] [executionId]
 
 **Arguments**
 
-| Argument      | Description                               | Required |
-| ------------- | ----------------------------------------- | -------- |
-| `executionId` | Execution ID (if provided, shows details) | No       |
+| Argument       | Description                               | Required |
+| -------------- | ----------------------------------------- | -------- |
+| `execution-id` | Execution ID (if provided, shows details) | No       |
 
 <!-- politty:command:workflow executions:arguments:end -->
 
@@ -257,7 +257,7 @@ Resume a failed or pending workflow execution.
 **Usage**
 
 ```
-tailor-sdk workflow resume [options] <executionId>
+tailor-sdk workflow resume [options] <execution-id>
 ```
 
 <!-- politty:command:workflow resume:usage:end -->
@@ -266,9 +266,9 @@ tailor-sdk workflow resume [options] <executionId>
 
 **Arguments**
 
-| Argument      | Description         | Required |
-| ------------- | ------------------- | -------- |
-| `executionId` | Failed execution ID | Yes      |
+| Argument       | Description         | Required |
+| -------------- | ------------------- | -------- |
+| `execution-id` | Failed execution ID | Yes      |
 
 <!-- politty:command:workflow resume:arguments:end -->
 

package/docs/cli-reference.md

@@ -43,10 +43,10 @@ Both `--env-file` and `--env-file-if-exists` can be specified multiple times and
 
 ```bash
 # Load .env (required) and .env.local (optional, if exists)
-tailor-sdk apply --env-file .env --env-file-if-exists .env.local
+tailor-sdk deploy --env-file .env --env-file-if-exists .env.local
 
 # Load multiple files
-tailor-sdk apply --env-file .env --env-file .env.production
+tailor-sdk deploy --env-file .env --env-file .env.production
 ```
 
 ## Environment Variables
@@ -99,7 +99,7 @@ Commands for managing Tailor Platform applications (work with `tailor.config.ts`
 | ----------------------------------------------- | ------------------------------------------------------------------- |
 | [init](./cli/application.md#init)               | Initialize a new project using create-sdk.                          |
 | [generate](./cli/application.md#generate)       | Generate files using Tailor configuration.                          |
-| [apply](./cli/application.md#apply)             | Apply Tailor configuration to deploy your application.              |
+| [deploy](./cli/application.md#deploy)           | Deploy your application by applying the Tailor configuration.       |
 | [remove](./cli/application.md#remove)           | Remove all resources managed by the application from the workspace. |
 | [show](./cli/application.md#show)               | Show information about the deployed application.                    |
 | [open](./cli/application.md#open)               | Open Tailor Platform Console.                                       |
@@ -255,14 +255,14 @@ Commands for managing and deploying static websites.
 | [staticwebsite list](./cli/staticwebsite.md#staticwebsite-list)     | List all static websites in a workspace.              |
 | [staticwebsite get](./cli/staticwebsite.md#staticwebsite-get)       | Get details of a specific static website.             |
 
-### [Crash Report Commands](./cli/crash-report.md)
+### [Crash Report Commands](./cli/crashreport.md)
 
 Commands for managing crash reports.
 
-| Command                                                      | Description                                    |
-| ------------------------------------------------------------ | ---------------------------------------------- |
-| [crash-report list](./cli/crash-report.md#crash-report-list) | List local crash report files.                 |
-| [crash-report send](./cli/crash-report.md#crash-report-send) | Submit a crash report to help improve the SDK. |
+| Command                                                   | Description                                    |
+| --------------------------------------------------------- | ---------------------------------------------- |
+| [crashreport list](./cli/crashreport.md#crashreport-list) | List local crash report files.                 |
+| [crashreport send](./cli/crashreport.md#crashreport-send) | Submit a crash report to help improve the SDK. |
 
 ### [Setup Commands](./cli/setup.md)
 

package/docs/generator/builtin.md

@@ -57,6 +57,42 @@ body: async (input, { env }) => {
 };
 ```
 
+### Raw SQL
+
+For queries that the Kysely query builder can't express, use the `sql` tag re-exported from `@tailor-platform/sdk/kysely`. Plain value substitutions (`${...}`) are sent as bound parameters, so user-supplied values are parameterized safely. SQL fragments produced by Kysely helpers (for example `sql.raw(...)`, identifiers, refs) are inlined into the generated SQL string by design — do not pass untrusted input through those.
+
+```typescript
+import { sql } from "@tailor-platform/sdk/kysely";
+import { getDB } from "./generated/tailordb";
+
+createResolver({
+  name: "supplierCountByState",
+  operation: "query",
+  input: { country: t.string() },
+  output: t.object({
+    rows: t.array(t.object({ state: t.string(), count: t.int() })),
+  }),
+  body: async ({ input }) => {
+    const db = getDB("tailordb");
+    const { rows } = await sql<{ state: string; count: number }>`
+      SELECT state, COUNT(*) AS count
+        FROM "Supplier"
+       WHERE country = ${input.country}
+    GROUP BY state
+    `.execute(db);
+    return { rows };
+  },
+});
+```
+
+The same `sql` tag works inside `db.transaction().execute(async (trx) => ...)` by passing `trx` to `.execute()`:
+
+```typescript
+await db.transaction().execute(async (trx) => {
+  await sql`UPDATE "Supplier" SET state = ${state} WHERE id = ${id}`.execute(trx);
+});
+```
+
 ## @tailor-platform/enum-constants
 
 Extracts enum constants from TailorDB type definitions.

package/docs/quickstart.md

@@ -16,7 +16,7 @@ The SDK requires Node.js 22 or later. Install Node.js via your package manager b
 
 Alternatively, you can use [Bun](https://bun.sh/) as the runtime.
 
-> **Note:** Bun has a known issue with HTTP/2 connections that may cause intermittent failures during `apply` or `generate` commands ([bun#14249](https://github.com/oven-sh/bun/issues/14249), [bun#26719](https://github.com/oven-sh/bun/issues/26719)). If you encounter a connection error, retry the command.
+> **Note:** Bun has a known issue with HTTP/2 connections that may cause intermittent failures during `deploy` or `generate` commands ([bun#14249](https://github.com/oven-sh/bun/issues/14249), [bun#26719](https://github.com/oven-sh/bun/issues/26719)). If you encounter a connection error, retry the command.
 
 ### Create an Example App
 
@@ -46,7 +46,7 @@ npx tailor-sdk workspace list
 
 ### Deploy Your App
 
-Run the apply command to deploy your project:
+Run the deploy command to deploy your project:
 
 ```bash
 cd example-app

package/docs/services/auth.md

@@ -388,7 +388,7 @@ export const auth = defineAuth("my-auth", {
 });
 ```
 
-After `tailor-sdk apply`, authorize the connection:
+After `tailor-sdk deploy`, authorize the connection:
 
 ```bash
 tailor-sdk authconnection authorize --name google-connection \
@@ -448,7 +448,7 @@ tailor-sdk authconnection list
 tailor-sdk authconnection revoke --name google-connection
 ```
 
-Connection creation is handled by `tailor-sdk apply` via the config.
+Connection creation is handled by `tailor-sdk deploy` via the config.
 
 See [Auth Resource Commands](../cli/auth.md) for full CLI documentation.
 

package/docs/services/secret.md

@@ -34,11 +34,11 @@ Secrets are key-value pairs stored within a vault. Secret values are encrypted a
 
 ## Managing Secrets
 
-There are two ways to manage secrets: declaratively via `defineSecretManager()` in `tailor.config.ts`, or imperatively via the [CLI](#cli-management). Management is scoped per vault — **do not mix both approaches for the same vault**. When a vault is defined in config, the config becomes the source of truth: any secrets in that vault not present in the config will be deleted on `tailor-sdk apply`.
+There are two ways to manage secrets: declaratively via `defineSecretManager()` in `tailor.config.ts`, or imperatively via the [CLI](#cli-management). Management is scoped per vault — **do not mix both approaches for the same vault**. When a vault is defined in config, the config becomes the source of truth: any secrets in that vault not present in the config will be deleted on `tailor-sdk deploy`.
 
 ### Declarative Configuration
 
-Define your secrets in `tailor.config.ts` using `defineSecretManager()`. Each key is a vault name, and its value is a record of secret names to their values. These values are deployed to each vault on `tailor-sdk apply`.
+Define your secrets in `tailor.config.ts` using `defineSecretManager()`. Each key is a vault name, and its value is a record of secret names to their values. These values are deployed to each vault on `tailor-sdk deploy`.
 
 Since secret values should not be committed to source control, use environment variables:
 
@@ -87,7 +87,7 @@ When `ignoreNullishValues: true`:
 - Skipped secrets are shown in the deploy output for visibility
 - Secrets removed from the config entirely are still deleted (orphan cleanup)
 
-This allows you to set secret values once (e.g., via local `tailor-sdk apply` or the CLI) and then deploy from CI without needing the actual values in CI environment variables.
+This allows you to set secret values once (e.g., via local `tailor-sdk deploy` or the CLI) and then deploy from CI without needing the actual values in CI environment variables.
 
 ## Using Secrets
 
@@ -175,7 +175,7 @@ At runtime, these references are replaced with the actual secret values.
 
 Use the CLI to manage vaults that are **not** defined in `defineSecretManager()`. If you attempt to modify a vault that is managed by the config, the CLI will show a warning and ask for confirmation. Once confirmed, the CLI releases the vault's ownership label so it is no longer managed by config.
 
-After ownership is released, the next `tailor-sdk apply` will treat the vault as an unmanaged resource and prompt for confirmation before taking any action on it.
+After ownership is released, the next `tailor-sdk deploy` will treat the vault as an unmanaged resource and prompt for confirmation before taking any action on it.
 
 ### Create a Vault
 

package/docs/services/tailordb-migration.md

@@ -12,7 +12,7 @@ For the CLI command reference, see [`tailordb migration`](../cli/tailordb.md#tai
 
 - **Local snapshot–based diff detection** — each migration is generated by diffing your current type definitions against the previous snapshot stored in `migrations/<NNNN>/`.
 - **Transaction-wrapped data migrations** — each `migrate.ts` script runs inside a database transaction on the platform; if the script throws, all changes in that migration roll back.
-- **Automatic execution during `apply`** — `tailor-sdk apply` detects pending migrations, runs the two-stage type update (pre-migration → script → post-migration), and updates the migration checkpoint label.
+- **Automatic execution during `apply`** — `tailor-sdk deploy` detects pending migrations, runs the two-stage type update (pre-migration → script → post-migration), and updates the migration checkpoint label.
 - **Type-safe scripts** — the generated `db.ts` provides Kysely types that reflect the schema state **before** the migration runs, so transformations are written against the actual data shape.
 
 **Files in `migrations/`**
@@ -45,7 +45,7 @@ When you start with no `migrations/` directory:
    tailor-sdk tailordb migration generate
    ```
    This creates `migrations/0000/schema.json` from your current types.
-4. Run `tailor-sdk apply`. The migration label is set to `0000` on the deployed namespace.
+4. Run `tailor-sdk deploy`. The migration label is set to `0000` on the deployed namespace.
 
 ### Adding migrations to an existing project
 
@@ -53,7 +53,7 @@ If you already have a deployed workspace whose schema matches your local type de
 
 1. Add the `migration` block to `tailor.config.ts`.
 2. Run `tailor-sdk tailordb migration generate` to create `0000/schema.json` from current local types.
-3. Run `tailor-sdk apply`. Because remote schema already matches, no script runs; only the migration label is set.
+3. Run `tailor-sdk deploy`. Because remote schema already matches, no script runs; only the migration label is set.
 
 If your local types and remote schema have **diverged**, reconcile them before introducing migrations — either update local types to match remote, or accept that the first non-`0000` migration will reflect that gap.
 
@@ -109,7 +109,7 @@ A typical change cycle:
 
 4. **Apply.**
    ```bash
-   tailor-sdk apply
+   tailor-sdk deploy
    ```
    The pre-migration phase relaxes the new field to optional, the script runs and populates values, then the post-migration phase enforces `required: true`.
 
@@ -210,7 +210,7 @@ The same pattern works for switching between scalar and array.
 
 ## Automatic Migration Execution
 
-When you run `tailor-sdk apply`, the SDK detects pending migrations (anything past the current `sdk-migration` label on the deployed namespace) and runs them in order before continuing with the rest of the apply.
+When you run `tailor-sdk deploy`, the SDK detects pending migrations (anything past the current `sdk-migration` label on the deployed namespace) and runs them in order before continuing with the rest of the apply.
 
 ### Per-migration phases
 
@@ -243,7 +243,7 @@ Namespace: tailordb
 To bypass both checks (not recommended outside of recovery scenarios):
 
 ```bash
-tailor-sdk apply --no-schema-check
+tailor-sdk deploy --no-schema-check
 ```
 
 ### Example output
@@ -299,7 +299,7 @@ Migration numbers are assigned sequentially, so two developers branching off the
 
 1. Run `migration generate --init` to start over from `0000`.
 2. Run `tailor-sdk tailordb migration set 0` against the deployed namespace.
-3. Run `tailor-sdk apply` — the new `0000` becomes the baseline.
+3. Run `tailor-sdk deploy` — the new `0000` becomes the baseline.
 
 Coordinate this with your team because everyone else's local migrations will be invalidated.
 
@@ -315,7 +315,7 @@ After a failure:
 
 1. Read the `Logs:` block in the apply output to find the cause.
 2. Fix `migrate.ts` (or the data it depends on).
-3. Re-run `tailor-sdk apply`. The same migration runs again because its label was never bumped.
+3. Re-run `tailor-sdk deploy`. The same migration runs again because its label was never bumped.
 4. If the pre-migration relaxation is causing problems for application code in the meantime, accept the temporary optionality or roll forward with a fix; do not try to manually re-tighten the schema, or you'll create remote drift.
 
 If a migration **succeeds in script** but the post-migration phase fails (rare; usually due to constraint violation that the script should have prevented), the situation is the same as above plus the data changes from the script are persisted. Investigate, fix, and re-run.
@@ -345,7 +345,7 @@ The machine user needs read/write access to every type the migration script touc
 
 If you see `No machine user available for migration execution`, either:
 
-- Add `machineUsers: { ... }` to your auth config and `tailor-sdk apply` it, or
+- Add `machineUsers: { ... }` to your auth config and `tailor-sdk deploy` it, or
 - Set `migration.machineUser` to an existing machine user name in the db config.
 
 ## Multi-Namespace Coordination
@@ -409,7 +409,7 @@ For genuinely different schemas across environments, prefer separate workspaces
 
 **Cause:** Runtime error in your `migrate.ts`, a permission error from the machine user, or a constraint violation when post-migration tightens types.
 
-**Resolution:** Read the `Logs:` block. Fix the script or the data assumption it relies on, and re-run `tailor-sdk apply`. The label is not bumped on failure, so the same migration retries.
+**Resolution:** Read the `Logs:` block. Fix the script or the data assumption it relies on, and re-run `tailor-sdk deploy`. The label is not bumped on failure, so the same migration retries.
 
 ### `migrate.ts` not found for a migration that needs one
 

package/docs/services/tailordb.md

@@ -589,6 +589,6 @@ db.type("User", {
 
 ## Migrations
 
-When you change a TailorDB type definition, the SDK can generate a migration that captures the diff and, for breaking changes, runs a data transformation script during `tailor-sdk apply`. See the [TailorDB Migrations guide](./tailordb-migration.md) for the full workflow, configuration, supported change types, team coordination, and troubleshooting.
+When you change a TailorDB type definition, the SDK can generate a migration that captures the diff and, for breaking changes, runs a data transformation script during `tailor-sdk deploy`. See the [TailorDB Migrations guide](./tailordb-migration.md) for the full workflow, configuration, supported change types, team coordination, and troubleshooting.
 
 For the CLI command reference, see [`tailordb migration`](../cli/tailordb.md#tailordb-migration).