@thinkingai/ae-cli 6.1.20 → 6.1.21

package/skills/ae-analysis/references/plan_change_log_list.md

@@ -1,24 +1,22 @@
 # tracking plan-change-log list
 
-Use when list tracking plan change logs.
-
-Do not use for commands listed under the sheet's non-CLI section or for unrelated metadata/report operations. If the command needs a complex JSON object, read the backend schema or existing asset first and send snake_case fields only.
+Use only when the user asks to list tracking plan change logs.
 
 Command:
 
 ```bash
-ae-cli tracking plan-change-log list [options]
+ae-cli tracking plan-change-log list --project-id <project_id>
 ```
 
 Capability id: `tracking.plan_change_log.list`
 
 Input sends `project_id`. Do not send camelCase aliases.
 
-Output is the capability gateway envelope: success is `ok=true,data,meta`; failure is `ok=false,error`. Export commands return lifecycle data such as `run_id` and `artifact_id` for inspect/download.
+Output is the capability gateway envelope: success is `ok=true,data,meta`; failure is `ok=false,error`.
 
 Parameters:
 
 | Parameter | Description | Required |
 | --- | --- | --- |
-| `--project-id` | See command help | Yes |
+| `--project-id` | Numeric project ID. | Yes |
 

package/skills/ae-analysis/references/plan_delete_items.md

@@ -1,8 +1,6 @@
 # tracking plan delete-items
 
-Use when delete tracking plan items.
-
-Do not use for commands listed under the sheet's non-CLI section or for unrelated metadata/report operations. If the command needs a complex JSON object, read the backend schema or existing asset first and send snake_case fields only.
+Use only when the user asks to delete tracking plan items.
 
 Command:
 
@@ -16,7 +14,7 @@ Capability id: `tracking.plan.delete_items`
 
 Input sends `project_id`, the provided name arrays, and `yes` mapped from `--confirm`. At least one name array must be non-empty. Do not send camelCase aliases.
 
-Output is the capability gateway envelope: success is `ok=true,data,meta`; failure is `ok=false,error`. Export commands return lifecycle data such as `run_id` and `artifact_id` for inspect/download.
+Output is the capability gateway envelope: success is `ok=true,data,meta`; failure is `ok=false,error`.
 
 Parameters:
 

package/skills/ae-analysis/references/plan_export.md

@@ -1,26 +1,26 @@
 # tracking plan export
 
-Use when export the tracking plan as an artifact.
-
-Do not use for commands listed under the sheet's non-CLI section or for unrelated metadata/report operations. If the command needs a complex JSON object, read the backend schema or existing asset first and send snake_case fields only.
+Use only when the user asks to export the tracking plan as an artifact.
 
 Command:
 
 ```bash
-ae-cli tracking plan export [options]
+ae-cli tracking plan export --project-id <project_id> --output <file>
 ```
 
 Capability id: `tracking.plan.export`
 
 Input sends `project_id`. Do not send camelCase aliases.
 
-Output is the capability gateway envelope: success is `ok=true,data,meta`; failure is `ok=false,error`. Export commands return lifecycle data such as `run_id` and `artifact_id` for inspect/download.
+Output is the capability gateway envelope: success is `ok=true,data,meta`; failure is `ok=false,error`.
+
+Use `--output` to wait and download the completed artifact. To resume an interrupted export, use [`analysis run wait`](run_wait.md) with its returned `run_id`.
 
 Parameters:
 
 | Parameter | Description | Required |
 | --- | --- | --- |
-| `--project-id` | See command help | Yes |
-| `--request-id` | See command help | No |
-| `--async-timeout-seconds` | See command help | No |
-
+| `--project-id` | Numeric project ID. | Yes |
+| `--request-id` | Optional caller-supplied cli_<32 lowercase hex> lifecycle ID. ae-cli generates and prints one before dispatch when omitted. | No |
+| `--timeout-seconds` | Async runtime in seconds. Default and max: 21600 (6 hours); cancel earlier with analysis query cancel --run-id <run_id>. | No |
+| `--output` | Wait and download to this local file. | No |

package/skills/ae-analysis/references/plan_generate.md

@@ -1,8 +1,6 @@
 # tracking plan generate
 
-Use when submit an AI tracking plan generation task.
-
-Do not use for commands listed under the sheet's non-CLI section or for unrelated metadata/report operations. If the command needs a complex JSON object, read the backend schema or existing asset first and send snake_case fields only.
+Use only when the user asks to submit an AI tracking plan generation task.
 
 Command:
 
@@ -14,7 +12,7 @@ Capability id: `tracking.plan.generate`
 
 Input sends `project_id`, `language`, `form_data`, optional `development_carrier`, and optional `predefined_event`. The backend resolves `company_id` from the authorized project. `form_data` is the intentionally open business-context object; all surrounding fields are explicit. Do not send camelCase aliases.
 
-Output is the capability gateway envelope: success is `ok=true,data,meta`; failure is `ok=false,error`. Export commands return lifecycle data such as `run_id` and `artifact_id` for inspect/download.
+Output is the capability gateway envelope: success is `ok=true,data,meta`; failure is `ok=false,error`.
 
 Parameters:
 

package/skills/ae-analysis/references/plan_get.md

@@ -1,24 +1,22 @@
 # tracking plan get
 
-Use when get the tracking plan for one project.
-
-Do not use for commands listed under the sheet's non-CLI section or for unrelated metadata/report operations. If the command needs a complex JSON object, read the backend schema or existing asset first and send snake_case fields only.
+Use only when the user asks to get the tracking plan for one project.
 
 Command:
 
 ```bash
-ae-cli tracking plan get [options]
+ae-cli tracking plan get --project-id <project_id>
 ```
 
 Capability id: `tracking.plan.get`
 
 Input sends `project_id`. Do not send camelCase aliases.
 
-Output is the capability gateway envelope: success is `ok=true,data,meta`; failure is `ok=false,error`. Export commands return lifecycle data such as `run_id` and `artifact_id` for inspect/download.
+Output is the capability gateway envelope: success is `ok=true,data,meta`; failure is `ok=false,error`.
 
 Parameters:
 
 | Parameter | Description | Required |
 | --- | --- | --- |
-| `--project-id` | See command help | Yes |
+| `--project-id` | Numeric project ID. | Yes |
 

package/skills/ae-analysis/references/plan_import_excel.md

@@ -1,26 +1,24 @@
 # tracking plan import-excel
 
-Use when import a tracking plan Excel file that was uploaded as an input file.
-
-Do not use for commands listed under the sheet's non-CLI section or for unrelated metadata/report operations. If the command needs a complex JSON object, read the backend schema or existing asset first and send snake_case fields only.
+Use only when the user asks to import a tracking plan Excel file that was uploaded as an input file.
 
 Command:
 
 ```bash
-ae-cli tracking plan import-excel [options]
+ae-cli tracking plan import-excel --project-id <project_id>
 ```
 
 Capability id: `tracking.plan.import_excel`
 
 Input sends `project_id`, `input_file_id`, and optional `lang`. Do not send camelCase aliases.
 
-Output is the capability gateway envelope: success is `ok=true,data,meta`; failure is `ok=false,error`. Export commands return lifecycle data such as `run_id` and `artifact_id` for inspect/download.
+Output is the capability gateway envelope: success is `ok=true,data,meta`; failure is `ok=false,error`.
 
 Parameters:
 
 | Parameter | Description | Required |
 | --- | --- | --- |
-| `--project-id` | See command help | Yes |
-| `--input-file-id` | See command help | Yes |
-| `--lang` | See command help | No |
+| `--project-id` | Numeric project ID. | Yes |
+| `--input-file-id` | Existing input_file_id returned by `analysis input-file upload --purpose track.program.xlsx`. | Yes |
+| `--lang` | Excel language: zh, en, ja, ko, zh_CN, en_US, ja_JP, or ko_KR. | No |
 

package/skills/ae-analysis/references/plan_save_items.md

@@ -1,8 +1,6 @@
 # tracking plan save-items
 
-Use when save tracking plan items.
-
-Do not use for commands listed under the sheet's non-CLI section or for unrelated metadata/report operations. If the command needs a complex JSON object, read the backend schema or existing asset first and send snake_case fields only.
+Use only when the user asks to save tracking plan items.
 
 Command:
 
@@ -14,7 +12,7 @@ Capability id: `tracking.plan.save_items`
 
 Input sends `project_id` and the provided `events`, `event_props`, `user_props`, and `common_event_props` arrays. At least one item array must be non-empty. Event/property objects use the existing tracking-plan snake_case contract; do not send camelCase aliases.
 
-Output is the capability gateway envelope: success is `ok=true,data,meta`; failure is `ok=false,error`. Export commands return lifecycle data such as `run_id` and `artifact_id` for inspect/download.
+Output is the capability gateway envelope: success is `ok=true,data,meta`; failure is `ok=false,error`.
 
 Parameters:
 

package/skills/ae-analysis/references/plan_sync_from_meta.md

@@ -1,24 +1,22 @@
 # tracking plan sync-from-meta
 
-Use when synchronize tracking plan from project metadata.
-
-Do not use for commands listed under the sheet's non-CLI section or for unrelated metadata/report operations. If the command needs a complex JSON object, read the backend schema or existing asset first and send snake_case fields only.
+Use only when the user asks to synchronize tracking plan from project metadata.
 
 Command:
 
 ```bash
-ae-cli tracking plan sync-from-meta [options]
+ae-cli tracking plan sync-from-meta --project-id <project_id>
 ```
 
 Capability id: `tracking.plan.sync_from_meta`
 
 Input sends `project_id`. Do not send camelCase aliases.
 
-Output is the capability gateway envelope: success is `ok=true,data,meta`; failure is `ok=false,error`. Export commands return lifecycle data such as `run_id` and `artifact_id` for inspect/download.
+Output is the capability gateway envelope: success is `ok=true,data,meta`; failure is `ok=false,error`.
 
 Parameters:
 
 | Parameter | Description | Required |
 | --- | --- | --- |
-| `--project-id` | See command help | Yes |
+| `--project-id` | Numeric project ID. | Yes |
 

package/skills/ae-analysis/references/project_access_detail_get.md

@@ -8,7 +8,6 @@ Command:
 
 ```bash
 ae-cli project access-detail get --company-id <company_id>
-ae-cli project access-detail get --dry-run --company-id <company_id>
 ```
 
 Capability id: `project.access_detail.get`.

package/skills/ae-analysis/references/project_data_power_get.md

@@ -8,7 +8,6 @@ Command:
 
 ```bash
 ae-cli project data-power get --project-id <project_id> --data-power-id <data_power_id>
-ae-cli project data-power get --dry-run --project-id <project_id> --data-power-id <data_power_id>
 ```
 
 Capability id: `project.data_power.get`.

package/skills/ae-analysis/references/project_data_power_list.md

@@ -8,7 +8,6 @@ Command:
 
 ```bash
 ae-cli project data-power list --project-id <project_id>
-ae-cli project data-power list --dry-run --project-id <project_id>
 ```
 
 Capability id: `project.data_power.list`.

package/skills/ae-analysis/references/project_data_power_upsert.md

@@ -8,7 +8,6 @@ Command:
 
 ```bash
 ae-cli project data-power upsert --project-id <project_id> --payload <payload>
-ae-cli project data-power upsert --dry-run --project-id <project_id> --payload <payload>
 ```
 
 Capability id: `project.data_power.upsert`.

package/skills/ae-analysis/references/project_entity_create.md

@@ -8,7 +8,6 @@ Command:
 
 ```bash
 ae-cli project entity create --project-id <project_id> --entity-name <entity_name> --column-name <column_name> --table-type <table_type> --order <order>
-ae-cli project entity create --dry-run --project-id <project_id> --entity-name <entity_name> --column-name <column_name> --table-type <table_type>
 ```
 
 Capability id: `project.entity.create`.

package/skills/ae-analysis/references/project_entity_event_list.md

@@ -8,7 +8,6 @@ Command:
 
 ```bash
 ae-cli project entity-event list --project-id <project_id> --event-names <event_names>
-ae-cli project entity-event list --dry-run --project-id <project_id>
 ```
 
 Capability id: `project.entity_event.list`.

package/skills/ae-analysis/references/project_entity_get.md

@@ -8,7 +8,6 @@ Command:
 
 ```bash
 ae-cli project entity get --project-id <project_id> --entity-id <entity_id>
-ae-cli project entity get --dry-run --project-id <project_id> --entity-id <entity_id>
 ```
 
 Capability id: `project.entity.get`.

package/skills/ae-analysis/references/project_entity_list.md

@@ -8,7 +8,6 @@ Command:
 
 ```bash
 ae-cli project entity list --project-id <project_id> --query <query> --fields <fields> --limit <limit> --offset <offset> --event-name <event_name>
-ae-cli project entity list --dry-run --project-id <project_id>
 ```
 
 Capability id: `project.entity.list`.

package/skills/ae-analysis/references/project_entity_update.md

@@ -8,7 +8,6 @@ Command:
 
 ```bash
 ae-cli project entity update --project-id <project_id> --entity-id <entity_id> --entity-name <entity_name> --column-name <column_name> --table-type <table_type> --order <order>
-ae-cli project entity update --dry-run --project-id <project_id> --entity-id <entity_id> --entity-name <entity_name> --column-name <column_name> --table-type <table_type>
 ```
 
 Capability id: `project.entity.update`.

package/skills/ae-analysis/references/project_function_list.md

@@ -8,7 +8,6 @@ Command:
 
 ```bash
 ae-cli project function list --company-id <company_id> --project-id <project_id>
-ae-cli project function list --dry-run
 ```
 
 Capability id: `project.function.list`.

package/skills/ae-analysis/references/project_info_get.md

@@ -8,7 +8,6 @@ Command:
 
 ```bash
 ae-cli project info get --project-id <project_id>
-ae-cli project info get --dry-run --project-id <project_id>
 ```
 
 Capability id: `project.info.get`.

package/skills/ae-analysis/references/project_info_list.md

@@ -8,7 +8,6 @@ Command:
 
 ```bash
 ae-cli project info list --query <query> --fields <fields> --limit <limit> --offset <offset>
-ae-cli project info list --dry-run
 ```
 
 Capability id: `project.info.list`.

package/skills/ae-analysis/references/project_info_update.md

@@ -8,7 +8,6 @@ Command:
 
 ```bash
 ae-cli project info update --project-id <project_id> --project-name <project_name> --project-remark <project_remark>
-ae-cli project info update --dry-run --project-id <project_id> --project-name <project_name>
 ```
 
 Capability id: `project.info.update`.

package/skills/ae-analysis/references/project_mark_time_create.md

@@ -8,7 +8,6 @@ Command:
 
 ```bash
 ae-cli project mark-time create --project-id <project_id> --marked-at <marked_at> --zone-offset <zone_offset> --content <content> --is-visible <is_visible>
-ae-cli project mark-time create --dry-run --project-id <project_id> --marked-at <marked_at> --content <content>
 ```
 
 Capability id: `project.mark_time.create`.

package/skills/ae-analysis/references/project_mark_time_list.md

@@ -8,7 +8,6 @@ Command:
 
 ```bash
 ae-cli project mark-time list --project-id <project_id> --query <query> --fields <fields> --limit <limit> --offset <offset> --zone-offset <zone_offset>
-ae-cli project mark-time list --dry-run --project-id <project_id>
 ```
 
 Capability id: `project.mark_time.list`.

package/skills/ae-analysis/references/project_mark_time_update.md

@@ -8,7 +8,6 @@ Command:
 
 ```bash
 ae-cli project mark-time update --project-id <project_id> --mark-time-id <mark_time_id> --marked-at <marked_at> --zone-offset <zone_offset> --content <content> --is-visible <is_visible>
-ae-cli project mark-time update --dry-run --project-id <project_id> --mark-time-id <mark_time_id> --marked-at <marked_at> --content <content>
 ```
 
 Capability id: `project.mark_time.update`.

package/skills/ae-analysis/references/project_member_add.md

@@ -1,14 +1,15 @@
 # project member add
 
-Use when the user needs to add project members.
+Use when the user needs to add project members. Use `--type 0` to create a company member from project management, or `--type 1` to add an existing company member to the project.
 
 Do not use it for unrelated project-management actions or for fields not present in the common-service capability schema. Do not send camelCase aliases.
 
+When the company disables project-level member creation, `--type 0` is rejected by both dry-run and execute. Create the member through system management first, then use `--type 1`. The company setting does not block system-management member creation.
+
 Command:
 
 ```bash
-ae-cli project member add --project-id <project_id> --payload <payload> --type <type>
-ae-cli project member add --dry-run --project-id <project_id> --payload <payload> --type <type>
+ae-cli project member add --project-id <project_id> --payload '{"user_roles":[{"user_id":<user_id>,"role_list":["<role_name>"]}]}' --type 1
 ```
 
 Capability id: `project.member.add`.
@@ -21,5 +22,5 @@ Output uses the gateway envelope: success is `ok=true,data,meta`; failure is `ok
 | Parameter | Required | Description |
 |---|---|---|
 | `--project-id` | Yes | Numeric project ID. |
-| `--payload` | Yes | Member add payload. Must include user_roles array matching UserRolePo in snake_case. |
-| `--type` | Yes | Add type accepted by ProjMemberAddTypeEnum. |
+| `--payload` | Yes | JSON object with `user_roles`. For an existing company member, each item uses `user_id` and `role_list` (verified project role names); optional `data_power_id` selects data permissions. For a new user (`--type 0`), use `login_name`, `password`, and `role_list` instead of an existing `user_id`; `user_name` is optional. |
+| `--type` | Yes | `0`: create a company member from project management; `1`: add an existing company member. Type `0` may be disabled by company configuration. |

package/skills/ae-analysis/references/project_member_batch_update.md

@@ -8,7 +8,6 @@ Command:
 
 ```bash
 ae-cli project member batch-update --project-id <project_id> --payload <payload>
-ae-cli project member batch-update --dry-run --project-id <project_id> --payload <payload>
 ```
 
 Capability id: `project.member.batch_update`.

package/skills/ae-analysis/references/project_member_candidate_list.md

@@ -1,14 +1,15 @@
 # project member-candidate list
 
-Use when the user needs to list candidate users and role/data-power options for adding project members.
+Use when the user needs to list candidate users and role/data-power options for adding project members. Use `--type 0` with `--login-names` to check prospective new company members, or `--type 1` to list existing company members that can be added to the project.
 
 Do not use it for unrelated project-management actions or for fields not present in the common-service capability schema. Do not send camelCase aliases.
 
+When the company disables project-level member creation, `--type 0` is rejected by both dry-run and execute. Use system management to create the member and then query with `--type 1`.
+
 Command:
 
 ```bash
 ae-cli project member-candidate list --project-id <project_id> --type <type> --login-names <login_names>
-ae-cli project member-candidate list --dry-run --project-id <project_id> --type <type>
 ```
 
 Capability id: `project.member_candidate.list`.
@@ -21,5 +22,5 @@ Output uses the gateway envelope: success is `ok=true,data,meta`; failure is `ok
 | Parameter | Required | Description |
 |---|---|---|
 | `--project-id` | Yes | Numeric project ID. |
-| `--type` | Yes | Add type accepted by ProjMemberAddTypeEnum. |
+| `--type` | Yes | `0`: check prospective new company members; `1`: list existing company members. Type `0` may be disabled by company configuration. |
 | `--login-names` | No | Comma-separated login names when checking new users. |

package/skills/ae-analysis/references/project_member_handover_run.md

@@ -7,8 +7,7 @@ Do not use it for unrelated project-management actions or for fields not present
 Command:
 
 ```bash
-ae-cli project member-handover run --project-id <project_id> --payload <payload>
-ae-cli project member-handover run --dry-run --project-id <project_id> --payload <payload>
+ae-cli project member-handover run --project-id <project_id> --payload '{"to_user_id":<user_id>,"single_submit":true,"asset_list":[{"asset_id":<asset_id>,"asset_type":"report","asset_name":"<asset_name>"}]}'
 ```
 
 Capability id: `project.member_handover.run`.
@@ -21,4 +20,4 @@ Output uses the gateway envelope: success is `ok=true,data,meta`; failure is `ok
 | Parameter | Required | Description |
 |---|---|---|
 | `--project-id` | Yes | Numeric project ID. |
-| `--payload` | Yes | Asset handover payload matching AssetBatchHandoverReq in snake_case. |
+| `--payload` | Yes | JSON object with `to_user_id`, `single_submit`, and `asset_list`. `single_submit=true` requires exactly one asset; false allows a non-empty batch. Each asset uses `asset_id`, `asset_type`, and `asset_name` from the selected asset. Types: `report`, `dashboard`, `space`, `folder`, `bi_panel`, `thirdparty`. |

package/skills/ae-analysis/references/project_member_list.md

@@ -8,7 +8,6 @@ Command:
 
 ```bash
 ae-cli project member list --project-id <project_id>
-ae-cli project member list --dry-run --project-id <project_id>
 ```
 
 Capability id: `project.member.list`.

package/skills/ae-analysis/references/project_member_receiver_list.md

@@ -8,7 +8,6 @@ Command:
 
 ```bash
 ae-cli project member-receiver list --project-id <project_id>
-ae-cli project member-receiver list --dry-run --project-id <project_id>
 ```
 
 Capability id: `project.member_receiver.list`.

package/skills/ae-analysis/references/project_member_update.md

@@ -8,7 +8,6 @@ Command:
 
 ```bash
 ae-cli project member update --project-id <project_id> --payload <payload> --target-user-id <target_user_id>
-ae-cli project member update --dry-run --project-id <project_id> --payload <payload> --target-user-id <target_user_id>
 ```
 
 Capability id: `project.member.update`.

package/skills/ae-analysis/references/project_owner_update.md

@@ -8,7 +8,6 @@ Command:
 
 ```bash
 ae-cli project owner update --project-id <project_id> --company-id <company_id> --owner-user-id <owner_user_id> --project-name <project_name> --project-remark <project_remark>
-ae-cli project owner update --dry-run --project-id <project_id> --company-id <company_id>
 ```
 
 Capability id: `project.owner.update`.

package/skills/ae-analysis/references/project_permission_binding_list.md

@@ -8,7 +8,6 @@ Command:
 
 ```bash
 ae-cli project permission-binding list --company-id <company_id> --project-ids <project_ids>
-ae-cli project permission-binding list --dry-run --company-id <company_id> --project-ids <project_ids>
 ```
 
 Capability id: `project.permission_binding.list`.

package/skills/ae-analysis/references/project_role_function_list.md

@@ -8,7 +8,6 @@ Command:
 
 ```bash
 ae-cli project role-function list --company-id <company_id> --project-id <project_id> --role-name <role_name> --role-names <role_names> --show-system-func <show_system_func>
-ae-cli project role-function list --dry-run
 ```
 
 Capability id: `project.role_function.list`.

package/skills/ae-analysis/references/project_role_get.md

@@ -8,7 +8,6 @@ Command:
 
 ```bash
 ae-cli project role get --project-id <project_id> --role-name <role_name>
-ae-cli project role get --dry-run --project-id <project_id> --role-name <role_name>
 ```
 
 Capability id: `project.role.get`.

package/skills/ae-analysis/references/project_role_list.md

@@ -8,7 +8,6 @@ Command:
 
 ```bash
 ae-cli project role list --company-id <company_id> --project-id <project_id> --visible-only <visible_only>
-ae-cli project role list --dry-run
 ```
 
 Capability id: `project.role.list`.

package/skills/ae-analysis/references/project_role_upsert.md

@@ -8,12 +8,42 @@ Command:
 
 ```bash
 ae-cli project role upsert --project-id <project_id> --payload <payload>
+ae-cli project role upsert --validate --project-id <project_id> --payload <payload>
 ae-cli project role upsert --dry-run --project-id <project_id> --payload <payload>
 ```
 
 Capability id: `project.role.upsert`.
 
-Input sends `project_id`, `payload`. Payload keys, JSON arrays, and projection fields must follow the common-service snake_case input schema.
+Input sends `project_id`, `payload`. Payload keys must use snake_case.
+
+## Payload contract
+
+`role_func_list` is required and must be a non-empty array of objects. Every item requires:
+
+- `function_name`: non-empty string. Resolve valid values with `ae-cli project function list` instead of guessing IDs or sending numeric function IDs.
+- `has_power`: integer `0` or `1` only. Use `1` to select the function and `0` to leave it unselected.
+
+For role creation, omit `role_name` and provide `role_desc` with 1 to 80 characters. For an update, provide the existing `role_name`; `role_desc` may remain omitted for compatibility.
+
+Functions omitted from `role_func_list` are completed by the service with their permission metadata and `has_power=0`. Do not attempt to replace an object item with a number or string.
+
+Create example:
+
+```bash
+ae-cli project role upsert \
+  --project-id 196 \
+  --payload '{"role_desc":"Data analyst","role_func_list":[{"function_name":"viewReport","has_power":1}]}'
+```
+
+Update example:
+
+```bash
+ae-cli project role upsert \
+  --project-id 196 \
+  --payload '{"role_name":"custom_role","role_func_list":[{"function_name":"viewReport","has_power":1}]}'
+```
+
+Run with `--validate` first when constructing the payload dynamically. Invalid item types, missing fields, an empty list, or a `has_power` value outside `0` and `1` return a validation error before the role is saved.
 
 Output uses the gateway envelope: success is `ok=true,data,meta`; failure is `ok=false,error`. Preserve `request_id` and `invocation_id` when present.
 
@@ -21,4 +51,4 @@ Output uses the gateway envelope: success is `ok=true,data,meta`; failure is `ok
 | Parameter | Required | Description |
 |---|---|---|
 | `--project-id` | Yes | Numeric project ID. |
-| `--payload` | Yes | Role save payload matching RoleSaveRequestDTO in snake_case. |
+| `--payload` | Yes | Role payload with a non-empty `role_func_list` object array; each item contains `function_name` and `has_power` (`0` or `1`). |

package/skills/ae-analysis/references/project_role_user_list.md

@@ -8,7 +8,6 @@ Command:
 
 ```bash
 ae-cli project role-user list --project-id <project_id> --role-name <role_name>
-ae-cli project role-user list --dry-run --project-id <project_id> --role-name <role_name>
 ```
 
 Capability id: `project.role_user.list`.