四端发布事务 / Four-Endpoint Release Transaction

本地、国内官网、GitHub、国外官网，是同一次发布的四个端点，必须按固定顺序推进。
Local, CN website, GitHub, and overseas website are the four endpoints of one release, advanced in a fixed order.

端点 / Endpoint	状态 / Status	说明 / Notes
本地 / Local	OPEN · 已启用	构建产物与内部验证的起点，不对外公开。
国内官网 / CN Website	OPEN · 已启用	面向国内用户的产品信息、版本与下载入口。
GitHub	OPEN · 已启用	社区与运营入口，不发布产品源码。
国外官网 / Overseas Website	SKIPPED_NOT_OPEN · 未开放	尚无域名、账号与部署入口；开放前不执行、不模拟、不占位任何发布动作。

唯一版本源 / Single Source of Version

每次整包发布只允许一个对外版本号；双内容通道各自维护严格递增的内容号，并以同一变更记录关联，数字不要求相同。
Each full release has one public version. The paired content channels keep independently increasing content versions linked by one change record; the numbers do not need to match.

固定顺序 / Fixed Order

1. 本地 / Local — 构建并本地校验产物；
2. 双内容热更新 / Paired content hot update — 客户端代码适用时，同一变更两边都发布并机器回读；
3. 国内官网 / CN Website — 版本与下载入口同步为同一版本；
4. GitHub — 同步公开文档（社区与运营信息）；
5. 国外官网 / Overseas Website — 当前固定为 SKIPPED_NOT_OPEN，如实登记为未开放、跳过。

双内容热更新任一边失败，整个事务失败并成对回滚。纯文档或官网变更登记 NOT_APPLICABLE_DOCS_ONLY，禁止用空内容包凑同步。
If either hot-update side fails, the transaction fails and both sides roll back. Documentation-only or website-only changes are recorded as NOT_APPLICABLE_DOCS_ONLY; empty bundles are forbidden.

铁律 8 三渠道同步更新 / Iron Rule 8: Three-Channel Sync

三渠道定义为内部内容通道、Soulmate 内容通道与 GitHub 公开仓库，固定顺序为：内部内容通道 → Soulmate 内容通道 → GitHub 公开仓库。三条渠道必须在同一事务内完成，不得调换或跳过。
The three channels are the internal content channel, Soulmate content channel, and public GitHub repository, in this fixed order: internal content channel → Soulmate content channel → public GitHub repository. All three must complete in one transaction without reordering or skipping.

三条渠道全部成功才允许机器断言 THREE_CHANNEL_SYNC=PASS；任一渠道失败则整体断言 THREE_CHANNEL_SYNC=FAIL，两条内容清单一起回滚，GitHub 公开文档还原上一版，并禁止对外通知。GitHub 必须留下公开发布说明，写明两条内容版本号与面向用户的行为变化。
Only complete success may assert THREE_CHANNEL_SYNC=PASS. Any channel failure asserts THREE_CHANNEL_SYNC=FAIL, rolls back both content manifests together, restores the previous public GitHub documents, and blocks public notice. GitHub must retain a public release note with both content versions and user-visible changes.

公开边界 / Public Boundary

公开文档（国内官网、GitHub、未来的国外官网）不得包含：本机路径、内网地址、服务器与部署细节、密钥、闭源实现与更新源内部细节。
Public documents must not contain: local machine paths, internal addresses, server/deployment details, credentials, closed-source internals, or update-source internals.

验收与回滚 / Verification & Rollback

每个端点与适用的双内容热更新都必须通过机器验收；任一已开放端点或任一热更新侧失败，整体失败。热更新回滚必须成对恢复两份清单；GitHub 仅还原公开文档；国外官网未开放，无回滚动作。
Every endpoint and each applicable hot-update side must pass machine verification. Any failure fails the transaction. Hot-update rollback restores both manifests together; GitHub restores public documents only; the overseas website has no rollback while closed.

每次发布登记交付模式、版本、双内容通道状态与清单哈希、各端点状态、验收和回滚记录；没有记录的发布视为未发布。
Each release records delivery mode, versions, paired-channel status and manifest hashes, endpoint states, verification, and rollback notes; a release without a record is not a release.