Proposal: update the existing Qwen profile to QwenCloud while preserving the ccm qwen workflow

[evelyn-jialin-zhang]

Context

QwenCloud is the current AI model platform for international Qwen developers. The project already exposes ccm qwen with global and China configurations using existing DashScope-compatible endpoints.

We would like new users to see the current QwenCloud brand and official setup pages without breaking the ccm qwen command, saved profiles, environment variables, or existing endpoint compatibility.

Proposal

Would the maintainers prefer to:

1. update only the user-visible documentation and provider description to QwenCloud;
2. add QwenCloud as a visible alias while preserving qwen; or
3. wait until endpoint and plan-specific behavior is confirmed before changing the preset?

Official references

• Website: https://www.qwencloud.com/
• API keys: https://home.qwencloud.com/api-keys
• Developer docs: https://docs.qwencloud.com/developer-guides/getting-started/introduction
• Models: https://www.qwencloud.com/models

The QwenCloud team can provide the approved display copy and validate the global/China configuration after the preferred compatibility path is confirmed.

QwenCloud contact: Jialing / QwenCloud Product Manager / https://github.com/evelyn-jialin-zhang