完善桌面端界面、发布检查与邮箱域名同步

docs/branch-governance.md

@@ -89,11 +89,13 @@ Rules:
   `desktop-release` branches.
 - Web and Desktop changes both follow `feature/*` -> `dev` -> `main` ->
   `release`.
-- A platform-specific feature branch is allowed while work is in progress, for
-  example `feature/desktop-file-picker`, but it must merge back into `dev`.
-- `codex/ctms-desktop` is a temporary desktop integration branch. After the
-  Tauri baseline is accepted into `dev`, new desktop work must use short-lived
-  feature branches from the current `dev`.
+- A platform-specific feature or agent task branch is allowed while work is in
+  progress, for example `feature/desktop-file-picker` or
+  `codex/desktop-menu-polish`, but it must merge back into `dev`.
+- `codex/ctms-desktop` was the temporary desktop integration branch for the
+  Tauri baseline. It is no longer a current desktop mainline. Do not commit,
+  rebase, or push new desktop work to it unless explicitly cleaning up the
+  historical branch after its accepted changes are present on `dev`.
 - Platform differences belong behind `frontend/src/runtime/`. Shared business
   modules must not import Tauri APIs directly.
 - A release tag identifies one product source state. Web and Desktop artifacts