build(release): simplify v0.1.0 visible assets

docs/guides/branch-maintenance-sop-zh.md

@@ -108,7 +108,7 @@ npm run desktop:build:app
 
 正式桌面发布构建必须从同一正式 tag 分别在 macOS 和 Windows 原生 CI job 执行。两端都必须设置 updater 签名私钥，updater 签名不可关闭。平台签名默认路径仍要求 macOS 设置 Apple 签名/公证变量并以 `REQUIRE_DESKTOP_SIGNING=true` 执行，Windows 设置 PFX、密码和 RFC 3161 时间戳变量并以 `REQUIRE_WINDOWS_SIGNING=true` 执行。只有 `frontend/desktop-release-policy.json` 对当前精确版本存在已批准例外时，workflow 才可改为 macOS ad-hoc、Windows Authenticode 未签名路径；例外制品必须标注 `UNSIGNED-PLATFORM`、生成 provenance 和风险说明。两个平台与联合 feed 校验通过后才能汇总正式 updater feed。
 
-v0.1.0 额外批准 GitHub Actions 额度不可用时的分阶段应急路径：先在受控 macOS 主机从最终、不可移动的 `v0.1.0` tag/SHA 本地构建并上传 macOS ad-hoc 制品，随附 updater `.sig`、checksum、provenance、平台未签名警告和 Windows pending 说明；Windows 恢复后必须从同一 tag/SHA 后补。macOS 先行阶段不得发布或替换生产 `latest.json`，联合 feed 必须等待 Windows `NotSigned` 实物验证完成。
+v0.1.0 额外批准 GitHub Actions 额度不可用时的分阶段应急路径：先在受控 macOS 主机从最终、不可移动的 `v0.1.0` tag/SHA 本地构建 macOS ad-hoc 制品，面向安装用户的 GitHub Release 只保留 DMG 与仅覆盖该安装包的 checksum，平台未签名警告和 Windows pending 状态写入 Release Notes。macOS updater 包及 `.sig`、完整 checksum、provenance、风险说明和 Windows pending 证据必须保存在被 Git 忽略的私有发布目录；Windows 恢复后必须从同一 tag/SHA 后补，并在联合验证通过后把 updater 制品发布到可匿名读取的独立 HTTPS 更新源。macOS 先行阶段不得发布或替换生产 `latest.json`，联合 feed 必须等待 Windows `NotSigned` 实物验证完成。
 
 后端改动应补充执行受影响模块的后端测试、迁移检查和接口回归。
 
@@ -297,9 +297,9 @@ git tag -a v1.2.0 -m "CTMS v1.2.0"
 git push origin v1.2.0
 ```
 
-网页端、macOS 和 Windows 桌面端必须从同一个 `v1.2.0` 标签构建。不得从不同分支、不同提交或本地未提交状态构建正式制品。两个平台的 updater 签名制品必须始终验证通过；macOS 签名/公证和 Windows 代码签名/RFC 3161 时间戳必须验证通过，除非 `frontend/desktop-release-policy.json` 对该精确版本记录了已批准例外。采用例外时必须验证 macOS 确为 ad-hoc、Windows 确为 `NotSigned`，并随安装包分发 `UNSIGNED-PLATFORM` 风险说明、provenance 和 checksum，之后才能最后原子替换生产 `latest.json`。
+网页端、macOS 和 Windows 桌面端必须从同一个 `v1.2.0` 标签构建。不得从不同分支、不同提交或本地未提交状态构建正式制品。两个平台的 updater 签名制品必须始终验证通过；macOS 签名/公证和 Windows 代码签名/RFC 3161 时间戳必须验证通过，除非 `frontend/desktop-release-policy.json` 对该精确版本记录了已批准例外。采用例外时必须验证 macOS 确为 ad-hoc、Windows 确为 `NotSigned`，并在 Release Notes、私有发布证据、完整 updater checksum 和 provenance 中记录 `UNSIGNED-PLATFORM` 风险；面向安装用户的 Release 可按精确版本策略只显示安装包与安装包 checksum，但 updater 制品及验证证据必须保留，之后才能最后原子替换生产 `latest.json`。
 
-若执行 v0.1.0 的已批准分阶段应急路径，首次 macOS Release 可先于 Windows 发布，但 tag/SHA 不得移动；首次 Release 不包含 `latest.json`，并必须明确标记 Windows pending。Windows 后补且联合 feed 验证通过后，才允许按上述顺序激活生产 updater feed。
+若执行 v0.1.0 的已批准分阶段应急路径，首次 macOS Release 可先于 Windows 发布，但 tag/SHA 不得移动；GitHub Release 只保留 DMG、仅覆盖该 DMG 的 checksum 和 GitHub 自动提供的源码归档，并在 Release Notes 中明确标记未签名风险与 Windows pending。updater 包、`.sig`、完整 checksum、provenance 和说明文件必须在私有发布目录留存。Windows 后补且联合 feed 验证通过后，才允许把这些 updater 制品发布到独立匿名 HTTPS 更新源并按上述顺序激活生产 updater feed。
 
 发布记录至少包含：
 
@@ -454,7 +454,7 @@ git log --oneline --decorate --graph --all -30
 - [ ] `npm run build` 通过
 - [ ] `npm run desktop:build:app` 通过
 - [ ] 正式桌面发布构建已使用 updater 签名私钥执行
-- [ ] 平台签名已验证，或当前精确版本已在 `frontend/desktop-release-policy.json` 获批例外且 `UNSIGNED-PLATFORM` 风险说明、provenance 和 checksum 齐备
+- [ ] 平台签名已验证，或当前精确版本已在 `frontend/desktop-release-policy.json` 获批例外且 Release Notes、私有 `UNSIGNED-PLATFORM` 证据、provenance 和完整 updater checksum 齐备；若 GitHub Release 采用 installer-only profile，公开 checksum 只覆盖公开安装包
 - [ ] 数据库迁移与回滚方案确认
 - [ ] 发布说明完成
 - [ ] `main -> release` 合并完成

docs/guides/client-release.md

@@ -163,26 +163,39 @@ Platform signing defaults to `signed`. An exception is allowed only when
 `frontend/desktop-release-policy.json` names the exact product version and
 records release-owner approval. The current v0.1.0 exception uses macOS ad-hoc
 signing and unsigned Windows application/installer binaries. Its artifact names
-and release directory contain `UNSIGNED-PLATFORM`; the directory must include
-`UNSIGNED-PLATFORM-RELEASE.txt`, `DESKTOP-RELEASE-PROVENANCE.json`, and
-`SHA256SUMS.txt`. This does not establish Apple or Microsoft publisher trust,
-and Gatekeeper or SmartScreen warnings are expected. Later versions return to
-the signed default unless separately approved.
+and verified updater release directory contain `UNSIGNED-PLATFORM`; the private
+evidence/update directory must include `UNSIGNED-PLATFORM-RELEASE.txt`,
+`DESKTOP-RELEASE-PROVENANCE.json`, and the full `SHA256SUMS.txt`. The
+user-facing GitHub Release may use the exact-version
+`installer-and-checksum-only` profile, with platform warnings in Release Notes
+and a separate checksum manifest covering only the displayed installer. This
+does not establish Apple or Microsoft publisher trust, and Gatekeeper or
+SmartScreen warnings are expected. Later versions return to the signed default
+unless separately approved.
 
 ### v0.1.0 staged macOS contingency
 
 The release owner approved one additional v0.1.0 contingency for unavailable
 hosted Actions capacity. A controlled local macOS host may build the macOS
 ad-hoc artifacts from the immutable final `v0.1.0` tag and publish them first.
-That initial GitHub Release must include the DMG, updater package and `.sig`,
-`SHA256SUMS.txt`, provenance, the unsigned-platform warning, and an explicit
-Windows-pending notice. Windows must later be built from the same tag and SHA.
+That initial user-facing GitHub Release contains only the DMG and a
+`SHA256SUMS.txt` that covers the DMG, in addition to GitHub's automatic source
+archives. The Release Notes must state that macOS is ad-hoc/not notarized and
+that Windows remains pending. The macOS updater package and `.sig`, full
+checksum manifest, provenance, unsigned-platform warning, and Windows-pending
+notice must be copied to a permission-restricted, Git-ignored private release
+directory before any visible asset is removed. Windows must later be built from
+the same tag and SHA.
 
 The staged macOS release is an installer distribution, not an activated
 cross-platform updater release. Do not upload or replace production
 `latest.json` until the Windows `NotSigned` installer/updater has been built and
-the combined macOS/Windows feed passes full verification. This fallback is
-limited to v0.1.0 and does not authorize local formal builds for later versions.
+the combined macOS/Windows feed passes full verification. The combined updater
+artifacts, signatures, provenance, full checksum manifest, and `latest.json`
+must use a separately configured HTTPS update origin that anonymous production
+clients can read; a private GitHub Release is not a valid production updater
+origin. This fallback is limited to v0.1.0 and does not authorize local formal
+builds for later versions.
 
 ## Windows Release and Internal Validation