Docs: VS Code extension getting-started page still claims new CLI (TS) users cannot install the extension

[DarknessChaser]

What version of Kimi Code is running?

0.27.0

Which open platform/subscription were you using?

Kimi Code membership (managed service, logged in via /login)

Which model were you using?

kimi-for-coding

What platform is your computer?

Darwin 25.2.0 arm64 arm

What issue are you seeing?

The Kimi Code for VS Code getting-started pages still show a compatibility banner that is no longer true:

• Chinese: https://www.kimi.com/code/docs/kimi-code-for-vscode/getting-started.html — "Kimi Code for VS Code 目前仅对旧版 Python CLI 用户开放新增安装……其他 TS 版本 CLI 用户暂不支持安装。"
• English: https://www.kimi.com/code/docs/en/kimi-code-for-vscode/getting-started.html — "Kimi Code for VS Code is currently only open for new installations to legacy Python CLI users. ... new installations are not supported for TS version CLI users."

This stopped being true when the extension migrated to the in-process Node SDK (v0.6.0+, e.g. #1769, released on 2026-07-17 with v0.6.3 / #1856) — the extension now runs the same engine as the new TS CLI and no longer requires a legacy Python CLI. I am running extension 0.6.3 (darwin-arm64) together with CLI 0.27.0 and it works fine.

The banner has been stale for over a month (present since at least 2026-06-18 per web.archive.org snapshots) and may discourage new-CLI users from installing the extension.

What steps can reproduce the bug?

1. Install the new (Node.js / TS) Kimi Code CLI 0.27.0 and log in.
2. Install Kimi Code for VS Code extension 0.6.3 from the Marketplace — installation and usage work.
3. Open the docs pages listed above: they still claim installation is not supported for TS-version CLI users.

What is the expected behavior?

The compatibility banner is removed or updated to reflect the current state, e.g. requiring extension >= 0.6.0 for the new Node.js CLI, in both the Chinese and English pages.

Additional information

Related closed issues about the extension compatibility itself: #1600, #1725 (fixed by the v0.6.3 release). This issue is only about the documentation not being updated afterwards.