@naturali/sdk 0.56.0 → 0.56.2

package/dist/index.cjs

@@ -2205,6 +2205,7 @@ var Traces = class {
 	*
 	* Returns the trace's step payload: every step of the execution's model loop, exactly as the runtime recorded it — tool calls, their arguments, results and cost — passed through unreshaped rather than mapped to a narrower contract, since the payload is the runtime's own step shape.
 	* Saving the payload is fire-and-forget on the runtime, so a trace can report `has_steps: false` for a short window after it finishes; this route 404s with `steps_not_available` during that window rather than returning an empty list, so a caller does not mistake "not saved yet" for "no steps ran".
+	* A trace with no payload at all answers `steps_redacted` instead — its content was purged, or its agent runs in zero-retention and nothing was ever written. The distinction is the whole point of two codes: retrying `steps_not_available` succeeds once the write lands, while retrying `steps_redacted` can never succeed. The response carries `content_redacted_at` in `details`.
 	*
 	*/
 	static getTraceSteps(options) {

package/dist/index.d.cts

@@ -2882,6 +2882,7 @@ type Trace = {
   step_count: number | null;
   /**
    * Whether the serialized step payload has been saved and is fetchable with `GET /v1/projects/{project_id}/traces/{trace_id}/steps`. Saving it is fire-and-forget upstream, so a very fresh trace can report `false` alongside a non-zero `step_count`; that route 404s with `steps_not_available` until this flips to `true`.
+   * It also reads `false` when the content is not stored at all — purged, or never recorded under zero-retention. `content_redacted_at` is what tells the two apart: non-null means this will never flip, and that route answers `steps_redacted`.
    *
    */
   has_steps: boolean;
@@ -8071,7 +8072,7 @@ type GetTraceStepsErrors = {
    */
   401: ErrorResponse;
   /**
-   * The trace does not exist (or is not the caller's), or its step payload has not been saved yet (`steps_not_available`).
+   * The trace does not exist (or is not the caller's), its step payload has not been saved yet (`steps_not_available`, worth retrying), or its content is not stored at all (`steps_redacted` — purged or never recorded, never worth retrying).
    *
    */
   404: ErrorResponse;
@@ -9642,6 +9643,7 @@ declare class Traces {
    *
    * Returns the trace's step payload: every step of the execution's model loop, exactly as the runtime recorded it — tool calls, their arguments, results and cost — passed through unreshaped rather than mapped to a narrower contract, since the payload is the runtime's own step shape.
    * Saving the payload is fire-and-forget on the runtime, so a trace can report `has_steps: false` for a short window after it finishes; this route 404s with `steps_not_available` during that window rather than returning an empty list, so a caller does not mistake "not saved yet" for "no steps ran".
+   * A trace with no payload at all answers `steps_redacted` instead — its content was purged, or its agent runs in zero-retention and nothing was ever written. The distinction is the whole point of two codes: retrying `steps_not_available` succeeds once the write lands, while retrying `steps_redacted` can never succeed. The response carries `content_redacted_at` in `details`.
    *
    */
   static getTraceSteps<ThrowOnError extends boolean = false>(options: Options<GetTraceStepsData, ThrowOnError>): RequestResult<GetTraceStepsResponses, GetTraceStepsErrors, ThrowOnError>;

package/dist/index.d.mts

@@ -2882,6 +2882,7 @@ type Trace = {
   step_count: number | null;
   /**
    * Whether the serialized step payload has been saved and is fetchable with `GET /v1/projects/{project_id}/traces/{trace_id}/steps`. Saving it is fire-and-forget upstream, so a very fresh trace can report `false` alongside a non-zero `step_count`; that route 404s with `steps_not_available` until this flips to `true`.
+   * It also reads `false` when the content is not stored at all — purged, or never recorded under zero-retention. `content_redacted_at` is what tells the two apart: non-null means this will never flip, and that route answers `steps_redacted`.
    *
    */
   has_steps: boolean;
@@ -8071,7 +8072,7 @@ type GetTraceStepsErrors = {
    */
   401: ErrorResponse;
   /**
-   * The trace does not exist (or is not the caller's), or its step payload has not been saved yet (`steps_not_available`).
+   * The trace does not exist (or is not the caller's), its step payload has not been saved yet (`steps_not_available`, worth retrying), or its content is not stored at all (`steps_redacted` — purged or never recorded, never worth retrying).
    *
    */
   404: ErrorResponse;
@@ -9642,6 +9643,7 @@ declare class Traces {
    *
    * Returns the trace's step payload: every step of the execution's model loop, exactly as the runtime recorded it — tool calls, their arguments, results and cost — passed through unreshaped rather than mapped to a narrower contract, since the payload is the runtime's own step shape.
    * Saving the payload is fire-and-forget on the runtime, so a trace can report `has_steps: false` for a short window after it finishes; this route 404s with `steps_not_available` during that window rather than returning an empty list, so a caller does not mistake "not saved yet" for "no steps ran".
+   * A trace with no payload at all answers `steps_redacted` instead — its content was purged, or its agent runs in zero-retention and nothing was ever written. The distinction is the whole point of two codes: retrying `steps_not_available` succeeds once the write lands, while retrying `steps_redacted` can never succeed. The response carries `content_redacted_at` in `details`.
    *
    */
   static getTraceSteps<ThrowOnError extends boolean = false>(options: Options<GetTraceStepsData, ThrowOnError>): RequestResult<GetTraceStepsResponses, GetTraceStepsErrors, ThrowOnError>;

package/dist/index.mjs

@@ -2204,6 +2204,7 @@ var Traces = class {
 	*
 	* Returns the trace's step payload: every step of the execution's model loop, exactly as the runtime recorded it — tool calls, their arguments, results and cost — passed through unreshaped rather than mapped to a narrower contract, since the payload is the runtime's own step shape.
 	* Saving the payload is fire-and-forget on the runtime, so a trace can report `has_steps: false` for a short window after it finishes; this route 404s with `steps_not_available` during that window rather than returning an empty list, so a caller does not mistake "not saved yet" for "no steps ran".
+	* A trace with no payload at all answers `steps_redacted` instead — its content was purged, or its agent runs in zero-retention and nothing was ever written. The distinction is the whole point of two codes: retrying `steps_not_available` succeeds once the write lands, while retrying `steps_redacted` can never succeed. The response carries `content_redacted_at` in `details`.
 	*
 	*/
 	static getTraceSteps(options) {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@naturali/sdk",
-  "version": "0.56.0",
+  "version": "0.56.2",
   "description": "TypeScript SDK for the naturali.ai API, generated from its OpenAPI specs",
   "type": "module",
   "sideEffects": false,
@@ -37,7 +37,7 @@
     "tsx": "^4.23.1",
     "typescript": "~6.0.3",
     "vitest": "^4.1.10",
-    "@naturali/api": "0.56.0"
+    "@naturali/api": "0.56.2"
   },
   "scripts": {
     "generate": "tsx scripts/generate.ts",