@adaptive-ds/zitadel-cli 0.1.0

package/dist/v2/userVerifyPasskeyRegistrationRequestParse.js

@@ -0,0 +1,11 @@
+import { VerifyPasskeyRegistrationRequestSchema } from "../generated/zitadel/user/v2/user_service_pb.js";
+import { endpointRequestParse } from "./internal/endpointRequestParse.js";
+export async function userVerifyPasskeyRegistrationRequestParse(options = {}) {
+    return endpointRequestParse({
+        file: options.file,
+        json: options.json,
+        operation: "userVerifyPasskeyRegistrationRequestParse",
+        schema: VerifyPasskeyRegistrationRequestSchema,
+    });
+}
+//# sourceMappingURL=userVerifyPasskeyRegistrationRequestParse.js.map

package/dist/v2/userVerifyPasskeyRegistrationRequestParse.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"userVerifyPasskeyRegistrationRequestParse.js","sourceRoot":"","sources":["../../src/v2/userVerifyPasskeyRegistrationRequestParse.ts"],"names":[],"mappings":"AAEA,OAAO,EAAE,sCAAsC,EAAE,MAAM,iDAAiD,CAAA;AACxG,OAAO,EAAE,oBAAoB,EAAE,MAAM,oCAAoC,CAAA;AASzE,MAAM,CAAC,KAAK,UAAU,yCAAyC,CAC7D,UAA4D,EAAE;IAE9D,OAAO,oBAAoB,CAAC;QAC1B,IAAI,EAAE,OAAO,CAAC,IAAI;QAClB,IAAI,EAAE,OAAO,CAAC,IAAI;QAClB,SAAS,EAAE,2CAA2C;QACtD,MAAM,EAAE,sCAAsC;KAC/C,CAAC,CAAA;AACJ,CAAC"}

package/dist/v2/userVerifyPhoneRequestParse.d.ts

@@ -0,0 +1,11 @@
+import type { MessageInitShape } from "@bufbuild/protobuf";
+import type { PromiseResult } from "#result";
+import { VerifyPhoneRequestSchema } from "../generated/zitadel/user/v2/user_service_pb.js";
+type UserVerifyPhoneRequestParseOptions = {
+    readonly json?: string;
+    readonly file?: string;
+};
+export type UserVerifyPhoneRequest = MessageInitShape<typeof VerifyPhoneRequestSchema>;
+export declare function userVerifyPhoneRequestParse(options?: UserVerifyPhoneRequestParseOptions): PromiseResult<UserVerifyPhoneRequest>;
+export {};
+//# sourceMappingURL=userVerifyPhoneRequestParse.d.ts.map

package/dist/v2/userVerifyPhoneRequestParse.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"userVerifyPhoneRequestParse.d.ts","sourceRoot":"","sources":["../../src/v2/userVerifyPhoneRequestParse.ts"],"names":[],"mappings":"AAAA,OAAO,KAAK,EAAE,gBAAgB,EAAE,MAAM,oBAAoB,CAAA;AAC1D,OAAO,KAAK,EAAE,aAAa,EAAE,MAAM,SAAS,CAAA;AAC5C,OAAO,EAAE,wBAAwB,EAAE,MAAM,iDAAiD,CAAA;AAG1F,KAAK,kCAAkC,GAAG;IACxC,QAAQ,CAAC,IAAI,CAAC,EAAE,MAAM,CAAA;IACtB,QAAQ,CAAC,IAAI,CAAC,EAAE,MAAM,CAAA;CACvB,CAAA;AAED,MAAM,MAAM,sBAAsB,GAAG,gBAAgB,CAAC,OAAO,wBAAwB,CAAC,CAAA;AAEtF,wBAAsB,2BAA2B,CAC/C,OAAO,GAAE,kCAAuC,GAC/C,aAAa,CAAC,sBAAsB,CAAC,CAOvC"}

package/dist/v2/userVerifyPhoneRequestParse.js

@@ -0,0 +1,11 @@
+import { VerifyPhoneRequestSchema } from "../generated/zitadel/user/v2/user_service_pb.js";
+import { endpointRequestParse } from "./internal/endpointRequestParse.js";
+export async function userVerifyPhoneRequestParse(options = {}) {
+    return endpointRequestParse({
+        file: options.file,
+        json: options.json,
+        operation: "userVerifyPhoneRequestParse",
+        schema: VerifyPhoneRequestSchema,
+    });
+}
+//# sourceMappingURL=userVerifyPhoneRequestParse.js.map

package/dist/v2/userVerifyPhoneRequestParse.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"userVerifyPhoneRequestParse.js","sourceRoot":"","sources":["../../src/v2/userVerifyPhoneRequestParse.ts"],"names":[],"mappings":"AAEA,OAAO,EAAE,wBAAwB,EAAE,MAAM,iDAAiD,CAAA;AAC1F,OAAO,EAAE,oBAAoB,EAAE,MAAM,oCAAoC,CAAA;AASzE,MAAM,CAAC,KAAK,UAAU,2BAA2B,CAC/C,UAA8C,EAAE;IAEhD,OAAO,oBAAoB,CAAC;QAC1B,IAAI,EAAE,OAAO,CAAC,IAAI;QAClB,IAAI,EAAE,OAAO,CAAC,IAAI;QAClB,SAAS,EAAE,6BAA6B;QACxC,MAAM,EAAE,wBAAwB;KACjC,CAAC,CAAA;AACJ,CAAC"}

package/dist/v2/userVerifyTOTPRegistrationRequestParse.d.ts

@@ -0,0 +1,11 @@
+import type { MessageInitShape } from "@bufbuild/protobuf";
+import type { PromiseResult } from "#result";
+import { VerifyTOTPRegistrationRequestSchema } from "../generated/zitadel/user/v2/user_service_pb.js";
+type UserVerifyTOTPRegistrationRequestParseOptions = {
+    readonly json?: string;
+    readonly file?: string;
+};
+export type UserVerifyTOTPRegistrationRequest = MessageInitShape<typeof VerifyTOTPRegistrationRequestSchema>;
+export declare function userVerifyTOTPRegistrationRequestParse(options?: UserVerifyTOTPRegistrationRequestParseOptions): PromiseResult<UserVerifyTOTPRegistrationRequest>;
+export {};
+//# sourceMappingURL=userVerifyTOTPRegistrationRequestParse.d.ts.map

package/dist/v2/userVerifyTOTPRegistrationRequestParse.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"userVerifyTOTPRegistrationRequestParse.d.ts","sourceRoot":"","sources":["../../src/v2/userVerifyTOTPRegistrationRequestParse.ts"],"names":[],"mappings":"AAAA,OAAO,KAAK,EAAE,gBAAgB,EAAE,MAAM,oBAAoB,CAAA;AAC1D,OAAO,KAAK,EAAE,aAAa,EAAE,MAAM,SAAS,CAAA;AAC5C,OAAO,EAAE,mCAAmC,EAAE,MAAM,iDAAiD,CAAA;AAGrG,KAAK,6CAA6C,GAAG;IACnD,QAAQ,CAAC,IAAI,CAAC,EAAE,MAAM,CAAA;IACtB,QAAQ,CAAC,IAAI,CAAC,EAAE,MAAM,CAAA;CACvB,CAAA;AAED,MAAM,MAAM,iCAAiC,GAAG,gBAAgB,CAAC,OAAO,mCAAmC,CAAC,CAAA;AAE5G,wBAAsB,sCAAsC,CAC1D,OAAO,GAAE,6CAAkD,GAC1D,aAAa,CAAC,iCAAiC,CAAC,CAOlD"}

package/dist/v2/userVerifyTOTPRegistrationRequestParse.js

@@ -0,0 +1,11 @@
+import { VerifyTOTPRegistrationRequestSchema } from "../generated/zitadel/user/v2/user_service_pb.js";
+import { endpointRequestParse } from "./internal/endpointRequestParse.js";
+export async function userVerifyTOTPRegistrationRequestParse(options = {}) {
+    return endpointRequestParse({
+        file: options.file,
+        json: options.json,
+        operation: "userVerifyTOTPRegistrationRequestParse",
+        schema: VerifyTOTPRegistrationRequestSchema,
+    });
+}
+//# sourceMappingURL=userVerifyTOTPRegistrationRequestParse.js.map

package/dist/v2/userVerifyTOTPRegistrationRequestParse.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"userVerifyTOTPRegistrationRequestParse.js","sourceRoot":"","sources":["../../src/v2/userVerifyTOTPRegistrationRequestParse.ts"],"names":[],"mappings":"AAEA,OAAO,EAAE,mCAAmC,EAAE,MAAM,iDAAiD,CAAA;AACrG,OAAO,EAAE,oBAAoB,EAAE,MAAM,oCAAoC,CAAA;AASzE,MAAM,CAAC,KAAK,UAAU,sCAAsC,CAC1D,UAAyD,EAAE;IAE3D,OAAO,oBAAoB,CAAC;QAC1B,IAAI,EAAE,OAAO,CAAC,IAAI;QAClB,IAAI,EAAE,OAAO,CAAC,IAAI;QAClB,SAAS,EAAE,wCAAwC;QACnD,MAAM,EAAE,mCAAmC;KAC5C,CAAC,CAAA;AACJ,CAAC"}

package/dist/v2/userVerifyU2FRegistrationRequestParse.d.ts

@@ -0,0 +1,11 @@
+import type { MessageInitShape } from "@bufbuild/protobuf";
+import type { PromiseResult } from "#result";
+import { VerifyU2FRegistrationRequestSchema } from "../generated/zitadel/user/v2/user_service_pb.js";
+type UserVerifyU2FRegistrationRequestParseOptions = {
+    readonly json?: string;
+    readonly file?: string;
+};
+export type UserVerifyU2FRegistrationRequest = MessageInitShape<typeof VerifyU2FRegistrationRequestSchema>;
+export declare function userVerifyU2FRegistrationRequestParse(options?: UserVerifyU2FRegistrationRequestParseOptions): PromiseResult<UserVerifyU2FRegistrationRequest>;
+export {};
+//# sourceMappingURL=userVerifyU2FRegistrationRequestParse.d.ts.map

package/dist/v2/userVerifyU2FRegistrationRequestParse.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"userVerifyU2FRegistrationRequestParse.d.ts","sourceRoot":"","sources":["../../src/v2/userVerifyU2FRegistrationRequestParse.ts"],"names":[],"mappings":"AAAA,OAAO,KAAK,EAAE,gBAAgB,EAAE,MAAM,oBAAoB,CAAA;AAC1D,OAAO,KAAK,EAAE,aAAa,EAAE,MAAM,SAAS,CAAA;AAC5C,OAAO,EAAE,kCAAkC,EAAE,MAAM,iDAAiD,CAAA;AAGpG,KAAK,4CAA4C,GAAG;IAClD,QAAQ,CAAC,IAAI,CAAC,EAAE,MAAM,CAAA;IACtB,QAAQ,CAAC,IAAI,CAAC,EAAE,MAAM,CAAA;CACvB,CAAA;AAED,MAAM,MAAM,gCAAgC,GAAG,gBAAgB,CAAC,OAAO,kCAAkC,CAAC,CAAA;AAE1G,wBAAsB,qCAAqC,CACzD,OAAO,GAAE,4CAAiD,GACzD,aAAa,CAAC,gCAAgC,CAAC,CAOjD"}

package/dist/v2/userVerifyU2FRegistrationRequestParse.js

@@ -0,0 +1,11 @@
+import { VerifyU2FRegistrationRequestSchema } from "../generated/zitadel/user/v2/user_service_pb.js";
+import { endpointRequestParse } from "./internal/endpointRequestParse.js";
+export async function userVerifyU2FRegistrationRequestParse(options = {}) {
+    return endpointRequestParse({
+        file: options.file,
+        json: options.json,
+        operation: "userVerifyU2FRegistrationRequestParse",
+        schema: VerifyU2FRegistrationRequestSchema,
+    });
+}
+//# sourceMappingURL=userVerifyU2FRegistrationRequestParse.js.map

package/dist/v2/userVerifyU2FRegistrationRequestParse.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"userVerifyU2FRegistrationRequestParse.js","sourceRoot":"","sources":["../../src/v2/userVerifyU2FRegistrationRequestParse.ts"],"names":[],"mappings":"AAEA,OAAO,EAAE,kCAAkC,EAAE,MAAM,iDAAiD,CAAA;AACpG,OAAO,EAAE,oBAAoB,EAAE,MAAM,oCAAoC,CAAA;AASzE,MAAM,CAAC,KAAK,UAAU,qCAAqC,CACzD,UAAwD,EAAE;IAE1D,OAAO,oBAAoB,CAAC;QAC1B,IAAI,EAAE,OAAO,CAAC,IAAI;QAClB,IAAI,EAAE,OAAO,CAAC,IAAI;QAClB,SAAS,EAAE,uCAAuC;QAClD,MAAM,EAAE,kCAAkC;KAC3C,CAAC,CAAA;AACJ,CAAC"}

package/docs/action-activate-public-key.md

@@ -0,0 +1,16 @@
+# `ActionService.ActivatePublicKey`
+
+This slice exposes the stable v2 `ActionService.ActivatePublicKey` operation through the typed library and the endpoint-owned `actions targets activate-public-key` command.
+
+Official reference: <https://zitadel.com/docs/reference/api/action/zitadel.action.v2.ActionService.ActivatePublicKey>
+
+## Request discovery
+
+The request is the generated `ActivatePublicKeyRequest` protobuf shape; no CLI field schema is duplicated. Discover its current fields from the generated descriptor/types, then pass protobuf JSON directly:
+
+```sh
+zitadel-cli actions targets activate-public-key \
+  --request-json '{"targetId":"target-1","keyId":"key-1"}'
+```
+
+Use `--request-file path/to/request.json` for a checked-in request. The flags `--base-url`, `--token`, and `--env-file` override the corresponding `ZITADEL_BASE_URL` and `ZITADEL_TOKEN` values with precedence: flags, process environment, then the explicitly selected `.env` file. Output defaults to JSON; use `--output yaml` for YAML.

package/docs/action-add-public-key.md

@@ -0,0 +1,16 @@
+# `ActionService.AddPublicKey`
+
+This slice exposes the stable v2 `ActionService.AddPublicKey` operation through the typed library and the endpoint-owned `actions targets add-public-key` command.
+
+Official reference: <https://zitadel.com/docs/reference/api/action/zitadel.action.v2.ActionService.AddPublicKey>
+
+## Request discovery
+
+The request is the generated `AddPublicKeyRequest` protobuf shape; no CLI field schema is duplicated. Discover its current fields from the generated descriptor/types, then pass protobuf JSON directly. `publicKey` is a base64-encoded PEM public key in protobuf JSON:
+
+```sh
+zitadel-cli actions targets add-public-key \
+  --request-json '{"targetId":"target-1","publicKey":"<base64-encoded-PEM>","expirationDate":"2030-01-01T00:00:00Z"}'
+```
+
+Use `--request-file path/to/request.json` for a checked-in request. The flags `--base-url`, `--token`, and `--env-file` override the corresponding `ZITADEL_BASE_URL` and `ZITADEL_TOKEN` values with precedence: flags, process environment, then the explicitly selected `.env` file. Output defaults to JSON; use `--output yaml` for YAML.

package/docs/action-create-target.md

@@ -0,0 +1,16 @@
+# `ActionService.CreateTarget`
+
+This slice exposes the stable v2 `ActionService.CreateTarget` operation through the typed library and the endpoint-owned `actions targets create` command.
+
+Official reference: <https://zitadel.com/docs/reference/api/action/zitadel.action.v2.ActionService.CreateTarget>
+
+## Request discovery
+
+The request is the generated `CreateTargetRequest` protobuf shape; no CLI field schema is duplicated. Discover its current fields from the generated descriptor/types, then pass protobuf JSON directly:
+
+```sh
+zitadel-cli actions targets create \
+  --request-json '{"name":"Example","restWebhook":{"interruptOnError":true},"endpoint":"https://example.test/action","payloadType":"PAYLOAD_TYPE_JSON"}'
+```
+
+Use `--request-file path/to/request.json` for a checked-in request. The flags `--base-url`, `--token`, and `--env-file` override the corresponding `ZITADEL_BASE_URL` and `ZITADEL_TOKEN` values with precedence: flags, process environment, then the explicitly selected `.env` file. Output defaults to JSON; use `--output yaml` for YAML.

package/docs/action-deactivate-public-key.md

@@ -0,0 +1,16 @@
+# `ActionService.DeactivatePublicKey`
+
+This slice exposes the stable v2 `ActionService.DeactivatePublicKey` operation through the typed library and the endpoint-owned `actions targets deactivate-public-key` command.
+
+Official reference: <https://zitadel.com/docs/reference/api/action/zitadel.action.v2.ActionService.DeactivatePublicKey>
+
+## Request discovery
+
+The request is the generated `DeactivatePublicKeyRequest` protobuf shape; no CLI field schema is duplicated. Discover its current fields from the generated descriptor/types, then pass protobuf JSON directly:
+
+```sh
+zitadel-cli actions targets deactivate-public-key \
+  --request-json '{"targetId":"target-1","keyId":"key-1"}'
+```
+
+Use `--request-file path/to/request.json` for a checked-in request. The flags `--base-url`, `--token`, and `--env-file` override the corresponding `ZITADEL_BASE_URL` and `ZITADEL_TOKEN` values with precedence: flags, process environment, then the explicitly selected `.env` file. Output defaults to JSON; use `--output yaml` for YAML.

package/docs/action-delete-target.md

@@ -0,0 +1,16 @@
+# `ActionService.DeleteTarget`
+
+This slice exposes the stable v2 `ActionService.DeleteTarget` operation through the typed library and the endpoint-owned `actions targets delete` command.
+
+Official reference: <https://zitadel.com/docs/reference/api/action/zitadel.action.v2.ActionService.DeleteTarget>
+
+## Request discovery
+
+The request is the generated `DeleteTargetRequest` protobuf shape; no CLI field schema is duplicated. Discover its current fields from the generated descriptor/types, then pass protobuf JSON directly:
+
+```sh
+zitadel-cli actions targets delete \
+  --request-json '{"id":"target-id"}'
+```
+
+Use `--request-file path/to/request.json` for a checked-in request. The flags `--base-url`, `--token`, and `--env-file` override the corresponding `ZITADEL_BASE_URL` and `ZITADEL_TOKEN` values with precedence: flags, process environment, then the explicitly selected `.env` file. Output defaults to JSON; use `--output yaml` for YAML.

package/docs/action-get-target.md

@@ -0,0 +1,16 @@
+# `ActionService.GetTarget`
+
+This slice exposes the stable v2 `ActionService.GetTarget` operation through the typed library and endpoint command.
+
+Official reference: <https://zitadel.com/docs/reference/api/action/zitadel.action.v2.ActionService.GetTarget>
+
+## Request discovery
+
+The request is the generated `GetTargetRequest` protobuf shape; no CLI field schema is duplicated. Discover its current fields from the generated descriptor/types, then pass protobuf JSON directly:
+
+```sh
+zitadel-cli actions targets get \
+  --request-json '{"id":"target-1"}'
+```
+
+Use `--request-file path/to/request.json` for a checked-in request. The flags `--base-url`, `--token`, and `--env-file` override the corresponding `ZITADEL_BASE_URL` and `ZITADEL_TOKEN` values with precedence: flags, process environment, then the explicitly selected `.env` file. Output defaults to JSON; use `--output yaml` for YAML.

package/docs/action-list-execution-functions.md

@@ -0,0 +1,15 @@
+# `ActionService.ListExecutionFunctions`
+
+This slice exposes the stable v2 `ActionService.ListExecutionFunctions` operation through the typed library and the endpoint-owned `actions execution-functions list` command.
+
+Official reference: <https://zitadel.com/docs/reference/api/action/zitadel.action.v2.ActionService.ListExecutionFunctions>
+
+## Request discovery
+
+The request is the generated `ListExecutionFunctionsRequest` protobuf shape and is empty today. Discover its current fields from the generated descriptor/types, then pass protobuf JSON directly:
+
+```sh
+zitadel-cli actions execution-functions list --request-json '{}'
+```
+
+Use `--request-file path/to/request.json` for a checked-in request. The flags `--base-url`, `--token`, and `--env-file` override the corresponding `ZITADEL_BASE_URL` and `ZITADEL_TOKEN` values with precedence: flags, process environment, then the explicitly selected `.env` file. Output defaults to JSON; use `--output yaml` for YAML.

package/docs/action-list-execution-methods.md

@@ -0,0 +1,15 @@
+# `ActionService.ListExecutionMethods`
+
+This slice exposes the stable v2 `ActionService.ListExecutionMethods` operation through the typed library and the endpoint-owned `actions execution-methods list` command.
+
+Official reference: <https://zitadel.com/docs/reference/api/action/zitadel.action.v2.ActionService.ListExecutionMethods>
+
+## Request discovery
+
+The request is the generated `ListExecutionMethodsRequest` protobuf shape; no CLI field schema is duplicated. The request has no fields, so invoke it with an empty protobuf JSON object:
+
+```sh
+zitadel-cli actions execution-methods list --request-json '{}'
+```
+
+Use `--request-file path/to/request.json` for a checked-in request. The flags `--base-url`, `--token`, and `--env-file` override the corresponding `ZITADEL_BASE_URL` and `ZITADEL_TOKEN` values with precedence: flags, process environment, then the explicitly selected `.env` file. Output defaults to JSON; use `--output yaml` for YAML.

package/docs/action-list-execution-services.md

@@ -0,0 +1,13 @@
+# `ActionService.ListExecutionServices`
+
+This slice exposes the stable v2 `ActionService.ListExecutionServices` operation through the typed library and the endpoint-owned `actions execution-services list` command.
+
+Official reference: <https://zitadel.com/docs/reference/api/action/zitadel.action.v2.ActionService.ListExecutionServices>
+
+The generated `ListExecutionServicesRequest` has no fields. Invoke it without a request or pass the empty protobuf JSON object:
+
+```sh
+zitadel-cli actions execution-services list --request-json '{}'
+```
+
+The flags `--base-url`, `--token`, and `--env-file` override the corresponding `ZITADEL_BASE_URL` and `ZITADEL_TOKEN` values with precedence: flags, process environment, then the explicitly selected `.env` file. Output defaults to JSON; use `--output yaml` for YAML.

package/docs/action-list-executions.md

@@ -0,0 +1,16 @@
+# `ActionService.ListExecutions`
+
+This slice exposes the stable v2 `ActionService.ListExecutions` operation through the typed library and the endpoint-owned `actions executions list` command.
+
+Official reference: <https://zitadel.com/docs/reference/api/action/zitadel.action.v2.ActionService.ListExecutions>
+
+## Request discovery
+
+The request is the generated `ListExecutionsRequest` protobuf shape; no CLI field schema is duplicated. Discover its current fields from the generated descriptor/types, then pass protobuf JSON directly:
+
+```sh
+zitadel-cli actions executions list \
+  --request-json '{"pagination":{"limit":25},"sortingColumn":"EXECUTION_FIELD_NAME_CHANGED_DATE"}'
+```
+
+Use `--request-file path/to/request.json` for a checked-in request. The flags `--base-url`, `--token`, and `--env-file` override the corresponding `ZITADEL_BASE_URL` and `ZITADEL_TOKEN` values with precedence: flags, process environment, then the explicitly selected `.env` file. Output defaults to JSON; use `--output yaml` for YAML.

package/docs/action-list-public-keys.md

@@ -0,0 +1,16 @@
+# `ActionService.ListPublicKeys`
+
+This slice exposes the stable v2 `ActionService.ListPublicKeys` operation through the typed library and the endpoint-owned `actions public-keys list` command.
+
+Official reference: <https://zitadel.com/docs/reference/api/action/zitadel.action.v2.ActionService.ListPublicKeys>
+
+## Request discovery
+
+The request is the generated `ListPublicKeysRequest` protobuf shape; no CLI field schema is duplicated. Discover its current fields from the generated descriptor/types, then pass protobuf JSON directly:
+
+```sh
+zitadel-cli actions public-keys list \
+  --request-json '{"targetId":"target-1","pagination":{"limit":25},"sortingColumn":"PUBLIC_KEY_FIELD_NAME_EXPIRATION_DATE"}'
+```
+
+Use `--request-file path/to/request.json` for a checked-in request. The flags `--base-url`, `--token`, and `--env-file` override the corresponding `ZITADEL_BASE_URL` and `ZITADEL_TOKEN` values with precedence: flags, process environment, then the explicitly selected `.env` file. Output defaults to JSON; use `--output yaml` for YAML.

package/docs/action-list-targets.md

@@ -0,0 +1,16 @@
+# `ActionService.ListTargets`
+
+This slice exposes the stable v2 `ActionService.ListTargets` operation through the typed library and the endpoint-owned `actions targets list` command.
+
+Official reference: <https://zitadel.com/docs/reference/api/action/zitadel.action.v2.ActionService.ListTargets>
+
+## Request discovery
+
+The request is the generated `ListTargetsRequest` protobuf shape; no CLI field schema is duplicated. Discover its current fields from the generated descriptor/types, then pass protobuf JSON directly:
+
+```sh
+zitadel-cli actions targets list \
+  --request-json '{"pagination":{"limit":25},"sortingColumn":"TARGET_FIELD_NAME_NAME"}'
+```
+
+Use `--request-file path/to/request.json` for a checked-in request. The flags `--base-url`, `--token`, and `--env-file` override the corresponding `ZITADEL_BASE_URL` and `ZITADEL_TOKEN` values with precedence: flags, process environment, then the explicitly selected `.env` file. Output defaults to JSON; use `--output yaml` for YAML.

package/docs/action-remove-public-key.md

@@ -0,0 +1,18 @@
+# `ActionService.RemovePublicKey`
+
+This slice exposes the stable v2 `ActionService.RemovePublicKey` operation through the typed library and `zitadel-cli actions remove-public-key`.
+
+Official reference: <https://zitadel.com/docs/reference/api/action/zitadel.action.v2.ActionService.RemovePublicKey>
+
+Only inactive public keys can be removed. Removing a non-existing key is a no-op.
+
+## Request discovery
+
+The request is the generated `RemovePublicKeyRequest` protobuf shape; no CLI field schema is duplicated. Discover its current fields from the generated descriptor/types, then pass protobuf JSON directly:
+
+```sh
+zitadel-cli actions remove-public-key \
+  --request-json '{"targetId":"target-1","keyId":"key-1"}'
+```
+
+Use `--request-file path/to/request.json` for a checked-in request. The flags `--base-url`, `--token`, and `--env-file` override the corresponding `ZITADEL_BASE_URL` and `ZITADEL_TOKEN` values with precedence: flags, process environment, then the explicitly selected `.env` file. Output defaults to JSON; use `--output yaml` for YAML.

package/docs/action-set-execution.md

@@ -0,0 +1,16 @@
+# `ActionService.SetExecution`
+
+This slice exposes the stable v2 `ActionService.SetExecution` operation through the typed library and the endpoint-owned `actions executions set` command.
+
+Official reference: <https://zitadel.com/docs/reference/api/action/zitadel.action.v2.ActionService.SetExecution>
+
+## Request discovery
+
+The request is the generated `SetExecutionRequest` protobuf shape; no CLI field schema is duplicated. Discover its current fields from the generated descriptor/types, then pass protobuf JSON directly:
+
+```sh
+zitadel-cli actions executions set \
+  --request-json '{"condition":{"request":{"method":"zitadel.user.v2.UserService.GetUserByID"}},"targets":["target-1"]}'
+```
+
+Use `--request-file path/to/request.json` for a checked-in request. The flags `--base-url`, `--token`, and `--env-file` override the corresponding `ZITADEL_BASE_URL` and `ZITADEL_TOKEN` values with precedence: flags, process environment, then the explicitly selected `.env` file. Output defaults to JSON; use `--output yaml` for YAML.

package/docs/action-update-target.md

@@ -0,0 +1,16 @@
+# `ActionService.UpdateTarget`
+
+This slice exposes the stable v2 `ActionService.UpdateTarget` operation through the typed library and endpoint-owned `actions targets update` command.
+
+Official reference: <https://zitadel.com/docs/reference/api/action/zitadel.action.v2.ActionService.UpdateTarget>
+
+## Request discovery
+
+The request is the generated `UpdateTargetRequest` protobuf shape; no CLI field schema is duplicated. Discover its current fields from the generated descriptor/types, then pass protobuf JSON directly:
+
+```sh
+zitadel-cli actions targets update \
+  --request-json '{"id":"target-id","name":"Updated target","endpoint":"https://example.test/action"}'
+```
+
+Use `--request-file path/to/request.json` for a checked-in request. The flags `--base-url`, `--token`, and `--env-file` override the corresponding `ZITADEL_BASE_URL` and `ZITADEL_TOKEN` values with precedence: flags, process environment, then the explicitly selected `.env` file. Output defaults to JSON; use `--output yaml` for YAML.

package/docs/admin-add-google-provider.md

@@ -0,0 +1,17 @@
+# `AdminService.AddGoogleProvider`
+
+This isolated compatibility slice exposes the legacy v1 `zitadel.admin.v1.AdminService.AddGoogleProvider` operation through the typed library and a standalone Stricli command.
+
+Official reference: <https://zitadel.com/docs/reference/api/admin/zitadel.admin.v1.AdminService.AddGoogleProvider>
+
+> **Compatibility notice:** This is a legacy v1 operation retained for existing integrations. Prefer a supported current API when migrating from v1, and do not assume it is available on every ZITADEL deployment.
+
+## Request discovery
+
+The request is the generated `AddGoogleProviderRequest` protobuf JSON shape. All generated fields, including nested `providerOptions`, are accepted without duplicating the schema as CLI flags:
+
+```sh
+zitadel-cli --help
+```
+
+When composing the standalone `adminAddGoogleProviderCommand` into a Stricli route, pass the complete request with `--request-json` or `--request-file`. Credentials use `--base-url` and `--token`, or `ZITADEL_BASE_URL` and `ZITADEL_TOKEN`; output defaults to JSON and also supports YAML.

package/docs/admin-list-idps.md

@@ -0,0 +1,15 @@
+# `AdminService.ListIDPs`
+
+This isolated compatibility slice exposes the legacy v1 `zitadel.admin.v1.AdminService.ListIDPs` operation through
+the typed library and a standalone Stricli command.
+
+Official reference: <https://zitadel.com/docs/reference/api/admin/zitadel.admin.v1.AdminService.ListIDPs>
+
+> **Compatibility notice:** This is a legacy v1 operation retained for existing integrations. Prefer a supported
+> current API when migrating from v1, and do not assume it is available on every ZITADEL deployment.
+
+## Request discovery
+
+The request is the generated `ListIDPsRequest` protobuf JSON shape. When composing the standalone command, pass the
+complete request with `--request-json` or `--request-file`. Credentials use `--base-url` and `--token`, or
+`ZITADEL_BASE_URL` and `ZITADEL_TOKEN`; output defaults to JSON and also supports YAML.

package/docs/api-discovery.md

@@ -0,0 +1,39 @@
+# API discovery
+
+The CLI exposes the policy-filtered catalog through `api list`, `api describe`, and `api call`. This is the
+recommended workflow for people and automation—including AI agents—because it discovers the generated protobuf
+request shape instead of guessing or duplicating fields. Output is pretty JSON by default; add `--output yaml` for
+YAML.
+
+```sh
+zitadel-cli api list
+zitadel-cli api list --api-version v2 --service ProjectService
+zitadel-cli api describe ProjectService.ListProjects
+zitadel-cli api describe zitadel.project.v2.ProjectService.ListProjects --output yaml
+```
+
+Use `--api-version v2` and `--service ProjectService` to narrow a large list. `describe` accepts a service or
+method name and reports the generated protobuf request/response descriptors, official ZITADEL reference URL, API
+version, and deprecation policy. Deprecated, beta, alpha, and unapproved v1 methods are absent from the catalog.
+
+Call a catalog-supported unary method with the complete protobuf JSON request. Requests may be
+inline or read from a file, but not both:
+
+```sh
+ZITADEL_BASE_URL=https://instance.zitadel.cloud \
+ZITADEL_TOKEN="$TOKEN" \
+zitadel-cli api call ProjectService.ListProjects \
+  --request-json '{"pagination":{"limit":25}}'
+
+zitadel-cli api call ProjectService.ListProjects \
+  --request-file ./list-projects.json \
+  --base-url https://instance.zitadel.cloud \
+  --token "$TOKEN" \
+  --output yaml
+```
+
+`--request-json` and `--request-file` are mutually exclusive. Use the complete generated protobuf JSON request;
+the CLI does not maintain a second, hand-written field schema. Configuration precedence is explicit flags,
+process environment, then the selected `.env` file (`--env-file`), with no implicit `.env` loading. The catalog
+includes only the two approved `legacy_v1` AdminService methods; other legacy methods are rejected and the
+dedicated `legacy-v1` commands remain available for compatibility.

package/docs/application-create-application-key.md

@@ -0,0 +1,18 @@
+# `ApplicationService.CreateApplicationKey`
+
+This slice exposes the stable v2 `ApplicationService.CreateApplicationKey` operation through the typed library and `zitadel-cli applications create-key` command.
+
+Official reference: <https://zitadel.com/docs/reference/api/application/zitadel.application.v2.ApplicationService.CreateApplicationKey>
+
+The authenticated caller requires the `project.app.write` permission. Key details are returned only once and must be stored safely.
+
+## Request discovery
+
+The request is the generated `CreateApplicationKeyRequest` protobuf shape; no CLI field schema is duplicated. Discover its current fields from the generated descriptor/types, then pass protobuf JSON directly:
+
+```sh
+zitadel-cli applications create-key \
+  --request-json '{"applicationId":"application-id","projectId":"project-id","expirationDate":"2030-01-01T00:00:00Z"}'
+```
+
+Use `--request-file path/to/request.json` for a checked-in request. The flags `--base-url`, `--token`, and `--env-file` override the corresponding `ZITADEL_BASE_URL` and `ZITADEL_TOKEN` values with precedence: flags, process environment, then the explicitly selected `.env` file. Output defaults to JSON; use `--output yaml` for YAML.

package/docs/application-create-application.md

@@ -0,0 +1,16 @@
+# `ApplicationService.CreateApplication`
+
+This slice exposes the stable v2 `ApplicationService.CreateApplication` operation through the typed library and endpoint command.
+
+Official reference: <https://zitadel.com/docs/reference/api/application/zitadel.application.v2.ApplicationService.CreateApplication>
+
+## Request discovery
+
+The request is the generated `CreateApplicationRequest` protobuf shape; no CLI field schema is duplicated. Discover its current fields from the generated descriptor/types, then pass protobuf JSON directly:
+
+```sh
+zitadel-cli applications create \
+  --request-json '{"projectId":"project-id","name":"Console","oidcConfiguration":{"redirectUris":["https://example.test/callback"]}}'
+```
+
+Use `--request-file path/to/request.json` for a checked-in request. The flags `--base-url`, `--token`, and `--env-file` override the corresponding `ZITADEL_BASE_URL` and `ZITADEL_TOKEN` values with precedence: flags, process environment, then the explicitly selected `.env` file. Output defaults to JSON; use `--output yaml` for YAML.

package/docs/application-deactivate-application.md

@@ -0,0 +1,16 @@
+# `ApplicationService.DeactivateApplication`
+
+This slice exposes the stable v2 `ApplicationService.DeactivateApplication` operation through the typed library and `zitadel-cli applications deactivate` command.
+
+Official reference: <https://zitadel.com/docs/reference/api/application/zitadel.application.v2.ApplicationService.DeactivateApplication>
+
+## Request discovery
+
+The request is the generated `DeactivateApplicationRequest` protobuf shape; no CLI field schema is duplicated. Discover its current fields from the generated descriptor/types, then pass protobuf JSON directly:
+
+```sh
+zitadel-cli applications deactivate \
+  --request-json '{"applicationId":"application-id","projectId":"project-id"}'
+```
+
+Use `--request-file path/to/request.json` for a checked-in request. The flags `--base-url`, `--token`, and `--env-file` override the corresponding `ZITADEL_BASE_URL` and `ZITADEL_TOKEN` values with precedence: flags, process environment, then the explicitly selected `.env` file. Output defaults to JSON; use `--output yaml` for YAML.

package/docs/application-delete-application-key.md

@@ -0,0 +1,16 @@
+# `ApplicationService.DeleteApplicationKey`
+
+This slice exposes the stable v2 `ApplicationService.DeleteApplicationKey` operation through the typed library and its CLI command.
+
+Official reference: <https://zitadel.com/docs/reference/api/application/zitadel.application.v2.ApplicationService.DeleteApplicationKey>
+
+## Request discovery
+
+The request is the generated `DeleteApplicationKeyRequest` protobuf shape. Pass the application key, application, and project IDs as protobuf JSON:
+
+```sh
+zitadel-cli applications delete-application-key \
+  --request-json '{"keyId":"key-1","applicationId":"application-1","projectId":"project-1"}'
+```
+
+Use `--request-file path/to/request.json` for a checked-in request. The flags `--base-url`, `--token`, and `--env-file` override the corresponding `ZITADEL_BASE_URL` and `ZITADEL_TOKEN` values with precedence: flags, process environment, then the explicitly selected `.env` file. Output defaults to JSON; use `--output yaml` for YAML.

package/docs/application-delete-application.md

@@ -0,0 +1,16 @@
+# `ApplicationService.DeleteApplication`
+
+This slice exposes the stable v2 `ApplicationService.DeleteApplication` operation through the typed library and `zitadel-cli applications delete` command.
+
+Official reference: <https://zitadel.com/docs/reference/api/application/zitadel.application.v2.ApplicationService.DeleteApplication>
+
+## Request discovery
+
+The request is the generated `DeleteApplicationRequest` protobuf shape; no CLI field schema is duplicated. Discover its current fields from the generated descriptor/types, then pass protobuf JSON directly:
+
+```sh
+zitadel-cli applications delete \
+  --request-json '{"applicationId":"application-id","projectId":"project-id"}'
+```
+
+Use `--request-file path/to/request.json` for a checked-in request. The flags `--base-url`, `--token`, and `--env-file` override the corresponding `ZITADEL_BASE_URL` and `ZITADEL_TOKEN` values with precedence: flags, process environment, then the explicitly selected `.env` file. Output defaults to JSON; use `--output yaml` for YAML.

package/docs/application-generate-client-secret.md

@@ -0,0 +1,16 @@
+# `ApplicationService.GenerateClientSecret`
+
+This slice exposes the stable v2 `ApplicationService.GenerateClientSecret` operation through the typed library and CLI endpoint command.
+
+Official reference: <https://zitadel.com/docs/reference/api/application/zitadel.application.v2.ApplicationService.GenerateClientSecret>
+
+## Request discovery
+
+The request is the generated `GenerateClientSecretRequest` protobuf shape; no CLI field schema is duplicated. Discover its current fields from the generated descriptor/types, then pass protobuf JSON directly:
+
+```sh
+zitadel-cli applications generate-client-secret \
+  --request-json '{"applicationId":"application-id","projectId":"project-id"}'
+```
+
+Use `--request-file path/to/request.json` for a checked-in request. The flags `--base-url`, `--token`, and `--env-file` override the corresponding `ZITADEL_BASE_URL` and `ZITADEL_TOKEN` values with precedence: flags, process environment, then the explicitly selected `.env` file. Output defaults to JSON; use `--output yaml` for YAML.

package/docs/application-get-application-key.md

@@ -0,0 +1,16 @@
+# `ApplicationService.GetApplicationKey`
+
+This slice exposes the stable v2 `ApplicationService.GetApplicationKey` operation through the typed library and CLI endpoint command.
+
+Official reference: <https://zitadel.com/docs/reference/api/application/zitadel.application.v2.ApplicationService.GetApplicationKey>
+
+## Request discovery
+
+The request is the generated `GetApplicationKeyRequest` protobuf shape; no CLI field schema is duplicated. Discover its current fields from the generated descriptor/types, then pass protobuf JSON directly:
+
+```sh
+zitadel-cli applications get-application-key \
+  --request-json '{"keyId":"key-id"}'
+```
+
+Use `--request-file path/to/request.json` for a checked-in request. The flags `--base-url`, `--token`, and `--env-file` override the corresponding `ZITADEL_BASE_URL` and `ZITADEL_TOKEN` values with precedence: flags, process environment, then the explicitly selected `.env` file. Output defaults to JSON; use `--output yaml` for YAML.

package/docs/application-get-application.md

@@ -0,0 +1,16 @@
+# `ApplicationService.GetApplication`
+
+This slice exposes the stable v2 `ApplicationService.GetApplication` operation through the typed library and `zitadel-cli applications get` command.
+
+Official reference: <https://zitadel.com/docs/reference/api/application/zitadel.application.v2.ApplicationService.GetApplication>
+
+## Request discovery
+
+The request is the generated `GetApplicationRequest` protobuf shape; no CLI field schema is duplicated. Discover its current fields from the generated descriptor/types, then pass protobuf JSON directly:
+
+```sh
+zitadel-cli applications get \
+  --request-json '{"applicationId":"application-id"}'
+```
+
+Use `--request-file path/to/request.json` for a checked-in request. The flags `--base-url`, `--token`, and `--env-file` override the corresponding `ZITADEL_BASE_URL` and `ZITADEL_TOKEN` values with precedence: flags, process environment, then the explicitly selected `.env` file. Output defaults to JSON; use `--output yaml` for YAML.