@naturali/cli 0.55.0 → 0.56.0

package/dist/index.mjs

@@ -14,7 +14,7 @@ var __exportAll = (all, no_symbols) => {
 };
 //#endregion
 //#region package.json
-var version = "0.55.0";
+var version = "0.56.0";
 //#endregion
 //#region ../sdk/src/generated/core/bodySerializer.gen.ts
 const jsonBodySerializer = { bodySerializer: (body) => JSON.stringify(body, (_key, value) => typeof value === "bigint" ? value.toString() : value) };
@@ -1349,6 +1349,22 @@ var Generations = class {
 		});
 	}
 	/**
+	* Purge a generation's content
+	*
+	* Clears the generation's content — `metadata`, `error`, `extraction` and the internal recovery state of a paused run — and stamps `content_redacted_at` as verifiable proof the content is gone.
+	* The billing and audit skeleton is preserved: ids, timestamps, status, stop reason and the attribution fields (`action_id`, `trigger_id`) the usage ledger reads. A purged generation still reads back with `GET /v1/projects/{project_id}/generations/{generation_id}` — a `404` there would prove nothing about what was erased.
+	* This is the narrow erasure, scoped to one model turn. It does **not** delete the parent trace's step payload, which holds this generation's content alongside its siblings'. To erase a whole run's content, purge the trace with `DELETE /v1/projects/{project_id}/traces/{trace_id}/content`, which cascades to every descendant trace and all of their generations.
+	* Idempotent: purging an already-purged generation succeeds and leaves the original `content_redacted_at` in place.
+	* A generation belonging to another project responds `404`, not `403`, and nothing is purged.
+	*
+	*/
+	static purgeGenerationContent(options) {
+		return (options.client ?? client).delete({
+			url: "/v1/projects/{project_id}/generations/{generation_id}/content",
+			...options
+		});
+	}
+	/**
 	* Get a generation's cost
 	*
 	* What this one generation cost, and the tokens it was charged on — the billing-grade receipt the runtime froze at write time, per model line item.
@@ -1819,7 +1835,9 @@ var Projects = class {
 	/**
 	* Update a project
 	*
-	* Rename or archive a project. Archiving is reversible; resources are retained.
+	* Rename or archive a project, and/or change its content-retention settings (`trace_content_retention_days`, `trace_content_mode`). Archiving is reversible; resources are retained.
+	* The two retention controls answer different questions. The window bounds how long content *stays* — a daily sweep purges anything past it, leaving auditable skeletons behind. `trace_content_mode: none` means content is never *written*, which is the stronger guarantee: it cannot be missed by a sweep or survive in a backup.
+	*
 	*/
 	static updateProject(options) {
 		return (options.client ?? client).patch({
@@ -2040,7 +2058,7 @@ var Tasks = class {
 	* Update a task
 	*
 	* Edit the card's `title`, `assignee` or `payload`. At least one is required.
-	* `payload` is **shallow-merged** over what is there: keys the request omits are preserved, so setting one field never discards what a column's automation wrote (`payload.last_result`). The merged result is validated against the board's `payload_schema`.
+	* `payload` is **shallow-merged** over what is there: keys the request omits are preserved. The merged result is validated against the board's `payload_schema`. `last_result` is read-only and lives in its own field — a payload write can never discard or forge it.
 	* `state` and `board_id` are rejected — a card moves only through `:transition`, and it never changes boards.
 	*
 	*/
@@ -3420,6 +3438,13 @@ const routes = {
 				"required": false,
 				"type": "object",
 				"in": "body"
+			},
+			{
+				"name": "trace_content_mode",
+				"description": "Zero-retention opt-in for this agent. Omit or send `null` to inherit the project's setting; `none` means this agent's trace and generation content is never written. `full` under a zero-retention project is refused with `400 invalid_trace_content_mode` — an agent may tighten the project's floor but never loosen it.\n",
+				"required": false,
+				"type": "string",
+				"in": "body"
 			}
 		]
 	},
@@ -3545,6 +3570,13 @@ const routes = {
 				"type": "object",
 				"in": "body"
 			},
+			{
+				"name": "trace_content_mode",
+				"description": "Change this agent's zero-retention setting. `null` falls back to inheriting the project's mode; `none` means content is never written. `full` under a zero-retention project is refused with `400 invalid_trace_content_mode`.\nTightening to `none` stops future writes; it does not erase content already recorded — purge that explicitly.\n",
+				"required": false,
+				"type": "string",
+				"in": "body"
+			},
 			{
 				"name": "status",
 				"description": "",
@@ -4948,6 +4980,28 @@ const routes = {
 			"in": "path"
 		}]
 	},
+	"purge-generation-content": {
+		serviceClass: "Generations",
+		operationId: "purgeGenerationContent",
+		description: "Clears the generation's content — `metadata`, `error`, `extraction` and the internal recovery state of a paused run — and stamps `content_redacted_at` as verifiable proof the content is gone. The billing and audit skeleton is preserved: ids, timestamps, status, stop reason and the attribution fields (`action_id`, `trigger_id`) the usage ledger reads. A purged generation still reads back with `GET /v1/projects/{project_id}/generations/{generation_id}` — a `404` there would prove nothing about what was erased. This is the narrow erasure, scoped to one model turn. It does **not** delete the parent trace's step payload, which holds this generation's content alongside its siblings'. To erase a whole run's content, purge the trace with `DELETE /v1/projects/{project_id}/traces/{trace_id}/content`, which cascades to every descendant trace and all of their generations. Idempotent: purging an already-purged generation succeeds and leaves the original `content_redacted_at` in place. A generation belonging to another project responds `404`, not `403`, and nothing is purged.",
+		moduleDocsUrl: "https://docs.naturali.ai/docs/modules/generations",
+		httpMethod: "delete",
+		pathParams: ["project_id", "generation_id"],
+		queryParams: [],
+		flags: [{
+			"name": "project_id",
+			"description": "Project public ID (proj_ prefix).",
+			"required": true,
+			"type": "string",
+			"in": "path"
+		}, {
+			"name": "generation_id",
+			"description": "Generation public ID (gen_ prefix).",
+			"required": true,
+			"type": "string",
+			"in": "path"
+		}]
+	},
 	"get-generation-usage": {
 		serviceClass: "Generations",
 		operationId: "getGenerationUsage",
@@ -6192,7 +6246,7 @@ const routes = {
 	"update-project": {
 		serviceClass: "Projects",
 		operationId: "updateProject",
-		description: "Rename or archive a project. Archiving is reversible; resources are retained.",
+		description: "Rename or archive a project, and/or change its content-retention settings (`trace_content_retention_days`, `trace_content_mode`). Archiving is reversible; resources are retained. The two retention controls answer different questions. The window bounds how long content *stays* — a daily sweep purges anything past it, leaving auditable skeletons behind. `trace_content_mode: none` means content is never *written*, which is the stronger guarantee: it cannot be missed by a sweep or survive in a backup.",
 		moduleDocsUrl: "https://docs.naturali.ai/docs/modules/projects",
 		httpMethod: "patch",
 		pathParams: ["project_id"],
@@ -6218,6 +6272,20 @@ const routes = {
 				"required": false,
 				"type": "string",
 				"in": "body"
+			},
+			{
+				"name": "trace_content_retention_days",
+				"description": "Days of trace and generation content retention before the daily sweep purges it. Send `null` to disable retention (content is then kept until purged on demand). Omitting the field leaves the current window unchanged — `null` and absent are different instructions.\n",
+				"required": false,
+				"type": "integer",
+				"in": "body"
+			},
+			{
+				"name": "trace_content_mode",
+				"description": "Set `none` for zero-retention: content is never written for any agent in this project. Tightening to `none` does not erase content already on disk — purge it explicitly, or set a retention window to have the sweep do it.\n",
+				"required": false,
+				"type": "string",
+				"in": "body"
 			}
 		]
 	},
@@ -6904,7 +6972,7 @@ const routes = {
 	"update-task": {
 		serviceClass: "Tasks",
 		operationId: "updateTask",
-		description: "Edit the card's `title`, `assignee` or `payload`. At least one is required. `payload` is **shallow-merged** over what is there: keys the request omits are preserved, so setting one field never discards what a column's automation wrote (`payload.last_result`). The merged result is validated against the board's `payload_schema`. `state` and `board_id` are rejected — a card moves only through `:transition`, and it never changes boards.",
+		description: "Edit the card's `title`, `assignee` or `payload`. At least one is required. `payload` is **shallow-merged** over what is there: keys the request omits are preserved. The merged result is validated against the board's `payload_schema`. `last_result` is read-only and lives in its own field — a payload write can never discard or forge it. `state` and `board_id` are rejected — a card moves only through `:transition`, and it never changes boards.",
 		moduleDocsUrl: "https://docs.naturali.ai/docs/modules/tasks",
 		httpMethod: "patch",
 		pathParams: ["project_id", "task_id"],

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@naturali/cli",
-  "version": "0.55.0",
+  "version": "0.56.0",
   "description": "Command-line interface for the naturali.ai API, generated from its OpenAPI specs",
   "type": "module",
   "bin": {
@@ -30,7 +30,7 @@
     "tsx": "^4.23.1",
     "typescript": "~6.0.3",
     "vitest": "^4.1.10",
-    "@naturali/sdk": "0.55.0"
+    "@naturali/sdk": "0.56.0"
   },
   "scripts": {
     "generate": "tsx scripts/generate.ts",