docs(desktop): confirm release version before packaging

apps/desktop/README.i18n.yaml

@@ -2,5 +2,5 @@
 # side as of the last confirmed-consistent state. Both languages carry equal authority;
 # after editing either side, bring the other along and re-record with:
 #   pnpm run verify-translation-pairing --write apps/desktop/README.md
-README.md: be780edcc49d9bc8457ced37fe6d8cc78e7928fa
-README.zh.md: d32fb67bf91a89ea1150741e70449ead19324545
+README.md: 528efff5c89e8c195dcf27ed922ff8e0dc478355
+README.zh.md: 089cfb1f3c120fbe7a7d1c3d9ae88350c3f8cbe7

apps/desktop/README.md

@@ -92,6 +92,8 @@ Workspace development runs the current CLI and private Desktop Host packages und
 
 ### Release versions
 
+Before each Desktop packaging run, first confirm the complete version string with the current user. Check the selected deployment, dsh base version, retained release records, and published objects, then propose the exact version for approval. Do not change release-family manifests or start packaging until the user confirms that version; the deployment setting alone does not authorize a version choice.
+
 Record the current dsh version as the base before changing any manifests. A production Desktop release uses that exact version, including any `alpha`, `beta`, or `rc` identifiers. A test release preserves the complete prerelease base and appends `.YYYYMMDD.index`; a stable base uses `-test.YYYYMMDD.index` instead.
 
 | dsh base | Production Desktop | Test Desktop example |

apps/desktop/README.zh.md

@@ -92,6 +92,8 @@ Workspace 开发使用 Electron RunAsNode 运行当前 CLI 与私有 Desktop Hos
 
 ### 发布版本
 
+每次 Desktop 打包前，第一步都要与当前用户确认完整版本号。检查所选部署环境、dsh 基础版本、保留的发布记录和已发布对象，再提出准确版本供用户确认。用户确认前，不得修改发布家族清单或启动打包；仅选择部署环境不代表用户已认可版本号。
+
 修改任何清单前，记录当前 dsh 版本作为基础版本。production Desktop 使用完全相同的版本，包括其中的 `alpha`、`beta` 或 `rc` 标识。test 发布保留完整的预发布基础版本并追加 `.YYYYMMDD.index`；稳定基础版本则追加 `-test.YYYYMMDD.index`。
 
 | dsh 基础版本 | production Desktop | test Desktop 示例 |