@naturali/cli 0.122.0 → 0.123.1

package/dist/index.mjs

@@ -14,7 +14,7 @@ var __exportAll = (all, no_symbols) => {
 };
 //#endregion
 //#region package.json
-var version = "0.122.0";
+var version = "0.123.1";
 //#endregion
 //#region ../sdk/src/generated/core/bodySerializer.gen.ts
 const serializeFormDataPair = (data, key, value) => {
@@ -3560,7 +3560,7 @@ var Projects = class {
 	* List project members
 	*
 	* Lists who may act in the project, and with what role. Readable by every member, including a read-only `member`: who else is in the project is not a privileged fact, and hiding it makes "why can that person see my agents?" unanswerable.
-	* Read-only for now — adding and removing members arrives with the invitation flow, since an invitee may not have an account yet.
+	* Somebody invited who has never signed in is listed too, with status `pending` — the invitation is already a grant, so hiding it until they arrive would hide access that exists.
 	*
 	*/
 	static listProjectMembers(options) {
@@ -3570,6 +3570,62 @@ var Projects = class {
 		});
 	}
 	/**
+	* Add a project member
+	*
+	* Adds a colleague to the project by email address. Free and uncapped on every plan: a member adds no run, no channel, no trigger and no byte, so every cost they cause is already billed through the project's owner. Members are counted nowhere.
+	*
+	* **The address does not need an account.** Inviting one that has none creates it unverified and records the membership beside it, so the invitee is already a member with status `pending`. Their first sign-in code — which they request themselves, from the link in the invitation — is what makes them `active`. There is no separate acceptance step and no invitation to expire: the address is the credential, and the invitation reached it.
+	*
+	* An `owner` may grant `admin` or `member`; an `admin` may grant `member` only, so administration cannot hand out its own authority. `role: owner` is refused — that is the billing owner, and transferring it is a different act.
+	*
+	* The invitation email is a courtesy, not the grant: if it cannot be sent the membership still stands, and the response still says `pending`. Requires an account-wide credential — a project-scoped key cannot grant access that would outlive its own revocation.
+	*
+	*/
+	static addProjectMember(options) {
+		return (options.client ?? client).post({
+			url: "/v1/projects/{project_id}/members",
+			...options,
+			headers: {
+				"Content-Type": "application/json",
+				...options.headers
+			}
+		});
+	}
+	/**
+	* Remove a project member
+	*
+	* Removes a member, or leaves the project yourself.
+	*
+	* **Anyone may remove themselves**, whatever their role: a colleague who no longer wants access should not have to ask for it, and leaving takes nothing from anybody else. Removing *somebody else* needs authority — an `owner` may remove anyone, an `admin` may remove a read-only `member` and not another `admin`.
+	*
+	* The owner's own row is refused: a project with no owner is unreachable, and the row names who pays.
+	*
+	*/
+	static removeProjectMember(options) {
+		return (options.client ?? client).delete({
+			url: "/v1/projects/{project_id}/members/{member_id}",
+			...options
+		});
+	}
+	/**
+	* Change a member's role
+	*
+	* Moves a member between `admin` and `member`. The project `owner` only: promoting somebody to `admin` hands them every write in the project, and an `admin` who could do that could erase the difference between the two roles for themselves.
+	*
+	* The owner's own row is refused in either direction — it names who pays, so changing it is a transfer rather than a role change.
+	*
+	*/
+	static updateProjectMember(options) {
+		return (options.client ?? client).patch({
+			url: "/v1/projects/{project_id}/members/{member_id}",
+			...options,
+			headers: {
+				"Content-Type": "application/json",
+				...options.headers
+			}
+		});
+	}
+	/**
 	* Get per-project usage
 	*
 	* The per-project meter — the re-billing view (A11/C12/P3). Aggregates the project's usage over an optional [from, to] window, bucketed by a single dimension. Costs are the billing-grade cost_usd the runtime freezes at write time; null means nothing in the bucket was priced (never that it was free). Only managed providers are priced (on the runtime), so cost reflects managed usage; BYOK usage carries no LLM cost.
@@ -4337,9 +4393,13 @@ var Users = class {
 	*
 	* Counted across the projects this account is the billing owner of, over the current UTC calendar month, from the meter itself. Archived projects are included: the runs they already made were made.
 	*
-	* **Nothing is refused against this.** The allowance is published, not enforced — an account past it keeps running. What does stop a managed-model generation is a negative credit balance, which is `GET /v1/users/me/billing`.
+	* **On the `free` plan the allowance is enforced.** An account that has used it is refused `403 plan_limit_reached` with `resource: "runs"` on everything that starts a generation — on its own provider credential as much as on a managed model, because a run is a run — until the billing month turns or it upgrades. On `pro` and `business` nothing is refused: runs past the allowance are billed at the overage rate those plans are sold with. A contract plan is not counted.
 	*
-	* This read is more expensive than the balance one: it asks the meter once per project. Poll it on the order of minutes, not seconds.
+	* The other thing that stops a managed-model generation is a negative credit balance, which is `GET /v1/users/me/billing`, and it never applies to your own credential.
+	*
+	* **This route counts live; the refusal reads a figure counted every few minutes.** So the two can differ by a burst: this is the more current number, and a refusal quotes the one it actually enforced.
+	*
+	* It is also more expensive than the balance read: it asks the meter once per project. Poll it on the order of minutes, not seconds.
 	*
 	*/
 	static getCurrentUserUsage(options) {
@@ -13418,7 +13478,7 @@ const routes = {
 	"list-project-members": {
 		serviceClass: "Projects",
 		operationId: "listProjectMembers",
-		description: "Lists who may act in the project, and with what role. Readable by every member, including a read-only `member`: who else is in the project is not a privileged fact, and hiding it makes \"why can that person see my agents?\" unanswerable. Read-only for now — adding and removing members arrives with the invitation flow, since an invitee may not have an account yet.",
+		description: "Lists who may act in the project, and with what role. Readable by every member, including a read-only `member`: who else is in the project is not a privileged fact, and hiding it makes \"why can that person see my agents?\" unanswerable. Somebody invited who has never signed in is listed too, with status `pending` — the invitation is already a grant, so hiding it until they arrive would hide access that exists.",
 		moduleDocsUrl: "https://docs.naturali.ai/docs/modules/projects",
 		httpMethod: "get",
 		pathParams: ["project_id"],
@@ -13431,6 +13491,92 @@ const routes = {
 			"in": "path"
 		}]
 	},
+	"add-project-member": {
+		serviceClass: "Projects",
+		operationId: "addProjectMember",
+		description: "Adds a colleague to the project by email address. Free and uncapped on every plan: a member adds no run, no channel, no trigger and no byte, so every cost they cause is already billed through the project's owner. Members are counted nowhere. **The address does not need an account.** Inviting one that has none creates it unverified and records the membership beside it, so the invitee is already a member with status `pending`. Their first sign-in code — which they request themselves, from the link in the invitation — is what makes them `active`. There is no separate acceptance step and no invitation to expire: the address is the credential, and the invitation reached it. An `owner` may grant `admin` or `member`; an `admin` may grant `member` only, so administration cannot hand out its own authority. `role: owner` is refused — that is the billing owner, and transferring it is a different act. The invitation email is a courtesy, not the grant: if it cannot be sent the membership still stands, and the response still says `pending`. Requires an account-wide credential — a project-scoped key cannot grant access that would outlive its own revocation.",
+		moduleDocsUrl: "https://docs.naturali.ai/docs/modules/projects",
+		httpMethod: "post",
+		pathParams: ["project_id"],
+		queryParams: [],
+		flags: [
+			{
+				"name": "project_id",
+				"description": "Project public ID (proj_ prefix).",
+				"required": true,
+				"type": "string",
+				"in": "path"
+			},
+			{
+				"name": "email",
+				"description": "The colleague's address, lower-cased before lookup. It does not need an account yet.\n",
+				"required": true,
+				"type": "string",
+				"in": "body"
+			},
+			{
+				"name": "role",
+				"description": "The roles a membership write may name. `owner` is absent by construction: it is the billing owner, so granting it would change who pays, and transferring that is a different act with its own decision.\n",
+				"required": true,
+				"type": "string",
+				"in": "body"
+			}
+		]
+	},
+	"update-project-member": {
+		serviceClass: "Projects",
+		operationId: "updateProjectMember",
+		description: "Moves a member between `admin` and `member`. The project `owner` only: promoting somebody to `admin` hands them every write in the project, and an `admin` who could do that could erase the difference between the two roles for themselves. The owner's own row is refused in either direction — it names who pays, so changing it is a transfer rather than a role change.",
+		moduleDocsUrl: "https://docs.naturali.ai/docs/modules/projects",
+		httpMethod: "patch",
+		pathParams: ["project_id", "member_id"],
+		queryParams: [],
+		flags: [
+			{
+				"name": "project_id",
+				"description": "Project public ID (proj_ prefix).",
+				"required": true,
+				"type": "string",
+				"in": "path"
+			},
+			{
+				"name": "member_id",
+				"description": "The membership ID (`pmem_` prefix), not the user ID.",
+				"required": true,
+				"type": "string",
+				"in": "path"
+			},
+			{
+				"name": "role",
+				"description": "The roles a membership write may name. `owner` is absent by construction: it is the billing owner, so granting it would change who pays, and transferring that is a different act with its own decision.\n",
+				"required": true,
+				"type": "string",
+				"in": "body"
+			}
+		]
+	},
+	"remove-project-member": {
+		serviceClass: "Projects",
+		operationId: "removeProjectMember",
+		description: "Removes a member, or leaves the project yourself. **Anyone may remove themselves**, whatever their role: a colleague who no longer wants access should not have to ask for it, and leaving takes nothing from anybody else. Removing *somebody else* needs authority — an `owner` may remove anyone, an `admin` may remove a read-only `member` and not another `admin`. The owner's own row is refused: a project with no owner is unreachable, and the row names who pays.",
+		moduleDocsUrl: "https://docs.naturali.ai/docs/modules/projects",
+		httpMethod: "delete",
+		pathParams: ["project_id", "member_id"],
+		queryParams: [],
+		flags: [{
+			"name": "project_id",
+			"description": "Project public ID (proj_ prefix).",
+			"required": true,
+			"type": "string",
+			"in": "path"
+		}, {
+			"name": "member_id",
+			"description": "The membership ID (`pmem_` prefix), not the user ID.",
+			"required": true,
+			"type": "string",
+			"in": "path"
+		}]
+	},
 	"get-project-usage": {
 		serviceClass: "Projects",
 		operationId: "getProjectUsage",
@@ -15665,7 +15811,7 @@ const routes = {
 	"get-current-user-usage": {
 		serviceClass: "Users",
 		operationId: "getCurrentUserUsage",
-		description: "How many runs the account has made this billing cycle, and how many its plan includes. A **run is one agent generation** — the unit every rung is priced in. Counted across the projects this account is the billing owner of, over the current UTC calendar month, from the meter itself. Archived projects are included: the runs they already made were made. **Nothing is refused against this.** The allowance is published, not enforced — an account past it keeps running. What does stop a managed-model generation is a negative credit balance, which is `GET /v1/users/me/billing`. This read is more expensive than the balance one: it asks the meter once per project. Poll it on the order of minutes, not seconds.",
+		description: "How many runs the account has made this billing cycle, and how many its plan includes. A **run is one agent generation** — the unit every rung is priced in. Counted across the projects this account is the billing owner of, over the current UTC calendar month, from the meter itself. Archived projects are included: the runs they already made were made. **On the `free` plan the allowance is enforced.** An account that has used it is refused `403 plan_limit_reached` with `resource: \"runs\"` on everything that starts a generation — on its own provider credential as much as on a managed model, because a run is a run — until the billing month turns or it upgrades. On `pro` and `business` nothing is refused: runs past the allowance are billed at the overage rate those plans are sold with. A contract plan is not counted. The other thing that stops a managed-model generation is a negative credit balance, which is `GET /v1/users/me/billing`, and it never applies to your own credential. **This route counts live; the refusal reads a figure counted every few minutes.** So the two can differ by a burst: this is the more current number, and a refusal quotes the one it actually enforced. It is also more expensive than the balance read: it asks the meter once per project. Poll it on the order of minutes, not seconds.",
 		moduleDocsUrl: "https://docs.naturali.ai/docs/modules/users",
 		httpMethod: "get",
 		pathParams: [],

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@naturali/cli",
-  "version": "0.122.0",
+  "version": "0.123.1",
   "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.122.0"
+    "@naturali/sdk": "0.123.1"
   },
   "scripts": {
     "generate": "tsx scripts/generate.ts",