@soat/sdk 0.18.4 → 0.18.6

package/dist/index.mjs

@@ -2149,7 +2149,7 @@ var Generations = class {
 	/**
 	* Update generation metadata
 	*
-	* Attaches caller-supplied key/value metadata to a generation record for per-run audit attribution (e.g. recording which knowledge-corpus version produced an AI action). The provided keys are shallow-merged over the existing metadata, so repeated patches accumulate and system-owned keys are preserved. Reserved keys (`action_id`, `trigger_id`, `orchestration_run_id`, `node_id`, `extraction`, and internal recovery state) cannot be set and are rejected with 400.
+	* Attaches caller-supplied key/value metadata to a generation record for per-run audit attribution (e.g. recording which knowledge-corpus version produced an AI action). The provided keys are shallow-merged over the existing `metadata`, so repeated patches accumulate. The bag is caller-owned and no key is reserved: server-owned state (usage attribution, the served agent version, the route's record, the extraction summary) lives in its own top-level fields and cannot be written from here.
 	*
 	*/
 	static updateGeneration(options) {
@@ -2162,6 +2162,24 @@ var Generations = class {
 			}
 		});
 	}
+	/**
+	* Purge generation content
+	*
+	* Clears the generation's content — `metadata`, `error`, `extraction`, and the internal recovery state of a paused run — and stamps `content_redacted_at`.
+	*
+	* The usage and audit skeleton is preserved: ids, timestamps, status, stop reason, and the attribution fields (`action_id`, `trigger_id`, `orchestration_run_id`, `node_id`, `agent_version`, `routing`) the billing ledger reads. A purged generation reads back as that skeleton, not a 404.
+	*
+	* This does **not** delete the parent trace's steps object, which holds this generation's content alongside its siblings'. To erase the run's content completely, purge the trace (`DELETE /api/v1/traces/{trace_id}/content`), which cascades here.
+	*
+	* Idempotent — purging an already-purged generation succeeds and leaves the original `content_redacted_at` in place.
+	*
+	*/
+	static purgeGenerationContent(options) {
+		return (options.client ?? client).delete({
+			url: "/api/v1/generations/{generation_id}/content",
+			...options
+		});
+	}
 };
 var Guardrails = class {
 	/**
@@ -3172,7 +3190,7 @@ var Tasks = class {
 	/**
 	* Create a task
 	*
-	* Creates a task bound to a workflow. The task is placed in the workflow's initial state and that state's `on_enter` automation fires.
+	* Creates a task bound to a workflow. By default the task is placed in the workflow's initial state; passing `state` places it directly in that named state instead — an alternate entry point for starting a task mid-flow (e.g. "a new recorte for an existing theme by id"), rather than re-submitting from the initial state and hoping a guard or similarity gate recognizes it. Entering the resulting state, initial or named, behaves identically: that state's `on_enter` automation fires and its `stalled_after` clock arms.
 	*/
 	static createTask(options) {
 		return (options.client ?? client).post({
@@ -3209,7 +3227,7 @@ var Tasks = class {
 	/**
 	* Update a task
 	*
-	* Updates a task's payload, title, or assignee. `state` is never directly writable — move it with a transition; sending a `state` field is rejected as an unknown field (`VALIDATION_FAILED`). `payload` is shallow-merged over the existing payload (PATCH semantics): keys the request omits are preserved, so setting one field never discards values an on_enter automation wrote (e.g. `last_result`). The merged payload is validated against the workflow's `payload_schema`.
+	* Updates a task's payload, title, or assignee. `state` is never directly writable — move it with a transition; sending a `state` field is rejected as an unknown field (`VALIDATION_FAILED`). `payload` is shallow-merged over the existing payload (PATCH semantics): keys the request omits are preserved. The payload is caller-owned; the automation result lives in the read-only `last_result` field, which no patch can reach. The merged payload is validated against the workflow's `payload_schema`.
 	*/
 	static updateTask(options) {
 		return (options.client ?? client).patch({
@@ -3366,6 +3384,22 @@ var Traces = class {
 			...options
 		});
 	}
+	/**
+	* Purge trace content
+	*
+	* Deletes the trace's steps object from storage and clears its content columns (`file_id`, `error`), cascading to every descendant trace and to all of their generations. A descendant holds its own steps object covering the same run, so the cascade is what makes the erasure complete rather than merely partial.
+	*
+	* The rows survive as auditable skeletons with `content_redacted_at` set — ids, timestamps, step counts, and the generations' usage-attribution fields are preserved, because the billing and audit ledger must outlive a tenant's erasure of the content. A purged trace therefore reads back as a skeleton, not a 404: a 404 would prove nothing.
+	*
+	* Idempotent — purging an already-purged trace succeeds and leaves the original `content_redacted_at` in place.
+	*
+	*/
+	static purgeTraceContent(options) {
+		return (options.client ?? client).delete({
+			url: "/api/v1/traces/{trace_id}/content",
+			...options
+		});
+	}
 };
 var Triggers = class {
 	/**

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@soat/sdk",
-  "version": "0.18.4",
+  "version": "0.18.6",
   "description": "TypeScript SDK for the SOAT API",
   "type": "module",
   "main": "dist/index.mjs",