<!-- Title: type(scope): outcome. One accepted phase per squash PR. 标题遵循提交命名，一次 PR 完成一个阶段。 -->

## Problem and outcome / 问题与结果

<!-- Describe the trigger and resulting behavior. Link a related issue or decision when useful. 说明问题、结果及相关依据。 -->

## Release notes

<!-- Required for product-changing PRs; omit this section for standalone website/docs/maintenance work. Public copy, automatically published in GitHub Releases. Keep this exact heading; use ### for subsections. Describe user benefits, fixes and required upgrade actions in concise Chinese and English. Omit internal logs, audit prompts and unverified claims. 产品改动需填写公开的中英文更新说明；仅官网、文档或外围维护可删去此节。 -->

<!-- Start each language with a short introduction: what kind of update this is, its emphasis and who benefits. Then group relevant highlights/fixes/upgrade notes; omit empty headings. Use ### for languages and #### for categories. An internal refactor is not automatically a breaking change. Review the final release as one coherent description, including any earlier unpublished changes. 中英文分别先介绍本次更新的性质和重点，再按需分组写新功能、修复与升级事项；别用提交日志代替版本介绍。 -->

## Verification / 验证

<!-- List exact local checks and results, relevant environments, and material untested cases. 列出检查命令、结果与未验证项。 -->

## Impact / 影响

<!-- Note relevant compatibility, release interruption/recovery, and updated owner docs. Explain any breaking change marked by ! in the title; write “None” if not applicable. 说明兼容、发布及文档影响，解释标题中 ! 标记的破坏性变更；不适用填“无”。 -->