[建议 / Feature] Publish v3.14.4 sources and release to zai-org/ZCode (website already ships 3.14.4) #902

提交前确认 · Pre-submission checklist

• 我已搜索过现有 issue，确认这不是重复提议 / I searched existing issues and confirmed this isn't a duplicate.
• 我已阅读 CONTRIBUTING.md / I've read CONTRIBUTING.md.

问题类别 · Category

其他 / 不确定 · Other / Not sure

涉及的 Agent 框架 · Agent framework

不涉及框架 · Not framework-specific

使用场景 · Use case

The download page (https://zcode.z.ai/en#all-downloads) already ships v3.14.4 installers (e.g. cdn-zcode.z.ai/zcode/electron/releases/3.14.4/...), and users are already reporting against 3.14.4 (e.g. #894). But the open-source repository zai-org/ZCode still stops at v3.14.3: latest tag v3.14.3, latest release v3.14.3 (2026-09-24) and main at 29628c9 feat: update v3.14.3.

So the code people can read, build and contribute to is behind what everyone installs. Community forks and contributions (localization in #151, fixes like #760, #812) have to target an outdated base and then rebase blindly.

官网下载页已提供 v3.14.4，但开源仓库 zai-org/ZCode 的 tag、release 和 main 仍停留在 v3.14.3。

建议方案 · Proposal

1. Push the v3.14.4 sources to zai-org/ZCode (main + tag v3.14.4) and publish the matching GitHub release with the changelog.
2. Ideally, keep the repo in step with each public desktop release (same day as the CDN update), as happened for v3.14.3.

请将 v3.14.4 源码与 release 推送到开源仓库，并尽量让后续版本与官网同步发布。

预期价值 · Expected value

• Users can audit and build exactly the version they run.
• Contributors can base fixes / translations on the current code instead of rebasing later.
• Bug reports against 3.14.4 can be traced to source.

你认为的优先级 · Your perceived priority

中 · Medium

你使用的 ZCode 版本 / 环境 · ZCode version / environment

Website: v3.14.4 · GitHub: v3.14.3 · Windows 11

补充材料 · Additional context

Related: localization contribution waiting on the current base in #151.