docs: clarify release line service ownership

2026-05-25 11:52:28 +00:00
parent 4a03052747
commit 1d56c46546
2 changed files with 3 additions and 0 deletions
@@ -53,6 +53,7 @@ UniDesk 是一个以主 server 为统一入口的分布式工作平台；本文
 - 任何需要保留的代码、文档或配置变更，在完成必要自测/部署验证后必须立刻按 `git-spec` 提交并 push 到 remote；禁止让未推送的本地修改成为部署真相或后续任务依赖。
 - 提交前必须用 `git status` 和 `git diff` 区分并只提交当前任务相关文件，保留并避开并行任务产生的无关修改；所有 UniDesk agent 变更只允许在 `master` 上开发并 `git push origin master`，禁止新建、切换到或推送其他分支；长期规则见 `docs/reference/arch.md`。
 - `release/v1` 是规划中的稳定维护线，不是普通 feature/fix 分支；创建、更新或启用必须作为显式 release operation，先满足 `docs/reference/release-governance.md` 和 GitHub issue #6 的 CLI/CI/CD/文档条件。当前常规 agent 任务仍按 master-only 规则执行。
+- `frontend`、`scripts/cli.ts`、`tran` 和分布式 SSH 透传能力跟随 `master`；`release/v1` 仅用于明确批准的 backend-core / Code Queue 稳定维护，不作为 frontend 或 CLI/tran 修复的 backport 目标。

 ## Critical Master Server Build Ban

@@ -27,6 +27,8 @@ This document records the target policy. It does not by itself create a `release
 - security and compatibility fixes;
 - narrowly scoped deployment fixes that preserve the existing architecture.

+Frontend and CLI ownership are intentionally separate from this stable line. The production frontend service, `scripts/cli.ts`, the `tran` wrapper and distributed SSH passthrough behavior follow `master` unless an explicit release decision says otherwise. `release/v1` is only the stable maintenance target for backend-core / Code Queue runtime fixes; do not backport frontend or CLI/tran changes to `release/v1` merely because they are needed by the current production UI or runner control path.
+
 `release/v1` must not carry new product features, large architecture changes, the default Rust backend-core switch, or speculative Code Agent sandbox behavior. Any exception requires an explicit issue and a deployment rollback plan.

 Until the release-line implementation is completed in CLI, CI, CD and documentation, the current repository rule still applies: UniDesk agent changes are developed on `master` and pushed to `origin master`. Creating or updating `release/v1` is an explicit release operation, not a replacement for arbitrary feature or fix branches.