AIT-68714: update ac CLI manual docs (#615)

* AIT-68714: update ac CLI manual docs

Signed-off-by: Tianpeng Wang <tpwang@alauda.io>

* docs: update AC manual sync branch parameter docs

* docs(upgrade): add AC global entrypoint and remove --cvo guidance

* docs(upgrade): add workload preflight step before upgrade request

Signed-off-by: Tianpeng Wang <tpwang@alauda.io>

---------

Signed-off-by: Tianpeng Wang <tpwang@alauda.io>

Author: timonwong

.gitignore

@@ -1,3 +1,4 @@
+/.vscode
 **/node_modules
 **/dist
 local/*

README.md

@@ -37,10 +37,10 @@ yarn update-ac-manual
 This command runs:
 
 ```bash
-node scripts/update-ac-manual.js release-1.0
+node scripts/update-ac-manual.js
 ```
 
-When you use `yarn update-ac-manual`, the repository sync pulls the `release-1.0` branch from `git@gitlab-ce.alauda.cn:alauda/ac.git` because the project script explicitly passes that branch name.
+When you use `yarn update-ac-manual`, the repository sync pulls the `release-1.0` branch from `git@gitlab-ce.alauda.cn:alauda/ac.git` by default.
 
 ### What the Sync Script Does
 
@@ -62,15 +62,21 @@ The workflow is:
 
 ### Updating from a Different Branch
 
-If you need to sync from a branch other than `release-1.0`, run the script directly:
+If you need to sync from a branch other than `release-1.0`, pass the branch name as an argument:
+
+```bash
+yarn update-ac-manual <branch>
+```
+
+This is equivalent to running the script directly:
 
 ```bash
 node scripts/update-ac-manual.js <branch>
 ```
 
 Replace `<branch>` with the branch name you want to pull from.
 
-If you run `node scripts/update-ac-manual.js` without a branch argument, the script itself defaults to `main`.
+If you run `node scripts/update-ac-manual.js` without a branch argument, the script defaults to `release-1.0`.
 
 ### Recommended Verification Steps
 

docs/en/ui/cli_tools/ac/administrator-command-reference.md

@@ -172,6 +172,34 @@ Assign a kubernetes role to a user in current context cluster
 ac adm policy add-role-to-user view alice -n my-namespace
 ```
 
+## ac adm release
+
+Manage release metadata and related administrative workflows
+
+### Example usage
+
+```bash
+# Import a ProductManifest for a release version
+ac adm release import-manifest --version 4.20.0
+```
+
+## ac adm release import-manifest
+
+Import release metadata as a ProductManifest
+
+### Example usage
+
+```bash
+# Import release metadata for version 4.20.0
+ac adm release import-manifest --version 4.20.0
+
+# Import metadata and wait for the ProductManifest to become Ready
+ac adm release import-manifest --version 4.20.0 --wait
+
+# Override the wait timeout
+ac adm release import-manifest --version 4.20.0 --wait --timeout=10m
+```
+
 ## ac adm taint
 
 Update the taints on one or more nodes
@@ -205,4 +233,44 @@ Mark node as schedulable
 ```bash
 # Mark node "foo" as schedulable
 ac adm uncordon foo
+```
+
+## ac adm upgrade
+
+Review or request a cluster upgrade
+
+### Example usage
+
+```bash
+# View the update status and available cluster updates
+ac adm upgrade
+
+# View summary for a specific cluster
+ac adm upgrade --cluster=workload-a
+
+# Update to the latest version
+ac adm upgrade --to-latest
+
+# Update to a specific version from available updates
+ac adm upgrade --cluster=workload-a --to=4.15.0
+
+# Allow an explicit version outside available updates
+ac adm upgrade --to=4.15.0 --allow-explicit-upgrade
+```
+
+## ac adm upgrade status
+
+Review preflight and stage details for the target cluster upgrade
+
+### Example usage
+
+```bash
+# Review the status of the Cluster Version Operator for default cluster
+ac adm upgrade status
+
+# Review the status of a specific cluster
+ac adm upgrade status --cluster=workload-a
+
+# Review the full controller-reported details
+ac adm upgrade status --verbose
 ```

docs/en/ui/cli_tools/ac/developer-command-reference.md

@@ -1395,6 +1395,12 @@ ac login https://example.com --name prod --cluster=my-cluster --namespace=my-nam
 
 # Login with custom kubeconfig file
 ac login https://example.com --name prod --kubeconfig=/path/to/kubeconfig
+
+# Login with workload cluster LDAP identity provider
+ac login https://192.168.1.2:11780 --idp ldap-test --workload --auth-type ldap --username 'xx' --password 'xx'
+
+# Login with workload cluster OIDC identity provider
+ac login https://192.168.1.2:11780 --idp oidc --workload --auth-type oidc
 ```
 
 ## ac logout