@naturali/sdk 0.104.0 → 0.106.0

package/dist/index.cjs

@@ -3450,6 +3450,8 @@ var Projects = class {
 	*
 	* Your plan limits how many projects you may own. At the limit this responds `403` with `plan_limit_reached`, whose `details` carry the `plan` and the `limit`. An archived project still counts — archiving keeps every resource, so it frees nothing; deleting a project does.
 	*
+	* A new project starts at the content-retention window your plan sets (`trace_content_retention_days`); `PATCH` it to anything shorter.
+	*
 	*/
 	static createProject(options) {
 		return (options.client ?? client).post({
@@ -3494,6 +3496,8 @@ var Projects = class {
 	* Requires the `admin` role in the project (an `owner` has it too).
 	* 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.
 	*
+	* Your plan sets the longest window you may keep content for. A wider one — `null` included, which keeps content indefinitely — responds `403` with `plan_limit_reached`, whose `details` carry the `plan` and the `limit` in days. Anything shorter is always allowed. Moving to a plan with a shorter window takes effect at the end of the billing cycle, and content already stored is then purged by age like everything else.
+	*
 	*/
 	static updateProject(options) {
 		return (options.client ?? client).patch({

package/dist/index.d.cts

@@ -5337,6 +5337,8 @@ type ProjectUpdate = {
   /**
    * 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.
    *
+   * Bounded by your plan: a window longer than the plan allows, and `null` on any plan that sets a window, respond `403` `plan_limit_reached`.
+   *
    */
   trace_content_retention_days?: number | null;
   /**
@@ -20296,6 +20298,8 @@ declare class Projects {
    *
    * Your plan limits how many projects you may own. At the limit this responds `403` with `plan_limit_reached`, whose `details` carry the `plan` and the `limit`. An archived project still counts — archiving keeps every resource, so it frees nothing; deleting a project does.
    *
+   * A new project starts at the content-retention window your plan sets (`trace_content_retention_days`); `PATCH` it to anything shorter.
+   *
    */
   static createProject<ThrowOnError extends boolean = false>(options: Options<CreateProjectData, ThrowOnError>): RequestResult<CreateProjectResponses, CreateProjectErrors, ThrowOnError>;
   /**
@@ -20321,6 +20325,8 @@ declare class Projects {
    * Requires the `admin` role in the project (an `owner` has it too).
    * 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.
    *
+   * Your plan sets the longest window you may keep content for. A wider one — `null` included, which keeps content indefinitely — responds `403` with `plan_limit_reached`, whose `details` carry the `plan` and the `limit` in days. Anything shorter is always allowed. Moving to a plan with a shorter window takes effect at the end of the billing cycle, and content already stored is then purged by age like everything else.
+   *
    */
   static updateProject<ThrowOnError extends boolean = false>(options: Options<UpdateProjectData, ThrowOnError>): RequestResult<UpdateProjectResponses, UpdateProjectErrors, ThrowOnError>;
   /**

package/dist/index.d.mts

@@ -5337,6 +5337,8 @@ type ProjectUpdate = {
   /**
    * 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.
    *
+   * Bounded by your plan: a window longer than the plan allows, and `null` on any plan that sets a window, respond `403` `plan_limit_reached`.
+   *
    */
   trace_content_retention_days?: number | null;
   /**
@@ -20296,6 +20298,8 @@ declare class Projects {
    *
    * Your plan limits how many projects you may own. At the limit this responds `403` with `plan_limit_reached`, whose `details` carry the `plan` and the `limit`. An archived project still counts — archiving keeps every resource, so it frees nothing; deleting a project does.
    *
+   * A new project starts at the content-retention window your plan sets (`trace_content_retention_days`); `PATCH` it to anything shorter.
+   *
    */
   static createProject<ThrowOnError extends boolean = false>(options: Options<CreateProjectData, ThrowOnError>): RequestResult<CreateProjectResponses, CreateProjectErrors, ThrowOnError>;
   /**
@@ -20321,6 +20325,8 @@ declare class Projects {
    * Requires the `admin` role in the project (an `owner` has it too).
    * 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.
    *
+   * Your plan sets the longest window you may keep content for. A wider one — `null` included, which keeps content indefinitely — responds `403` with `plan_limit_reached`, whose `details` carry the `plan` and the `limit` in days. Anything shorter is always allowed. Moving to a plan with a shorter window takes effect at the end of the billing cycle, and content already stored is then purged by age like everything else.
+   *
    */
   static updateProject<ThrowOnError extends boolean = false>(options: Options<UpdateProjectData, ThrowOnError>): RequestResult<UpdateProjectResponses, UpdateProjectErrors, ThrowOnError>;
   /**

package/dist/index.mjs

@@ -3449,6 +3449,8 @@ var Projects = class {
 	*
 	* Your plan limits how many projects you may own. At the limit this responds `403` with `plan_limit_reached`, whose `details` carry the `plan` and the `limit`. An archived project still counts — archiving keeps every resource, so it frees nothing; deleting a project does.
 	*
+	* A new project starts at the content-retention window your plan sets (`trace_content_retention_days`); `PATCH` it to anything shorter.
+	*
 	*/
 	static createProject(options) {
 		return (options.client ?? client).post({
@@ -3493,6 +3495,8 @@ var Projects = class {
 	* Requires the `admin` role in the project (an `owner` has it too).
 	* 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.
 	*
+	* Your plan sets the longest window you may keep content for. A wider one — `null` included, which keeps content indefinitely — responds `403` with `plan_limit_reached`, whose `details` carry the `plan` and the `limit` in days. Anything shorter is always allowed. Moving to a plan with a shorter window takes effect at the end of the billing cycle, and content already stored is then purged by age like everything else.
+	*
 	*/
 	static updateProject(options) {
 		return (options.client ?? client).patch({

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@naturali/sdk",
-  "version": "0.104.0",
+  "version": "0.106.0",
   "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.104.0"
+    "@naturali/api": "0.106.0"
   },
   "scripts": {
     "generate": "tsx scripts/generate.ts",