Correct governance-v2 status and add the cross-repo master record
ci / svc-realcombo (pull_request) Successful in 1m55s
ci / test (pull_request) Successful in 5m53s
ci / test-pg (pull_request) Successful in 8m26s

Why: the task card claimed all units complete while confirmed blocking defects remain in triage and the Guidelines contract.

Evidence: review of task.sh triage (count-based JOIN, local-only scan) and Guidelines PR #7 diff; CI runs 3417/3419 apply only to superseded objects.

Impact: initiative stops accepting requirements; status uses the PLANNED..CLOSED model; remaining phases tracked in one master record.

Refs: PR #585, Guidelines PR #7
Co-authored-by: Cursor <cursoragent@cursor.com>
This commit is contained in:
2026-10-16 12:16:21 +00:00
co-authored by Cursor
parent e7e8ee0dd0
commit d46dec31de
2 changed files with 135 additions and 29 deletions
File diff suppressed because one or more lines are too long
@@ -0,0 +1,72 @@
# development-governance-v2 统一治理主记录
本文件是治理大任务跨仓状态的唯一汇总。每行状态只取以下值之一,不用笼统的“完成”:
`PLANNED / IMPLEMENTED / LOCALLY_VERIFIED / PR_OPEN / REVIEWED / GATE_PASS / MERGED / ADOPTED_ACTIVE / RELEASED / CLOSED`。
通过类结论须带来源(GATE / REPLAY / SELF)与对象 SHA;历史对象证据不得充当当前 HEAD 证据。
全局任务只有在全部正式仓达到 `ADOPTED_ACTIVE`、新项目入口启用、主 PR 全部合入并完成清理后才能标记 `CLOSED`。
## 交付主线
| Phase | 内容 | 仓库 / 分支 | PR | 状态 | 依赖 |
|---|---|---|---|---|---|
| 0 | 纠正候选状态、建立本主记录 | Dev `feature/development-governance-v2` | [#585](https://git-home.u1680832.nyat.app:30319/weichen/Agent-System-Dev/pulls/585) | IMPLEMENTED | — |
| 1 | Guidelines 合同加固 | Guidelines `feature/development-governance-v2-contract-hardening` → `feature/development-governance-v2` | [#7](https://git-home.u1680832.nyat.app:30319/weichen/Development-Guidelines/pulls/7)(initiative→main) | PLANNED | — |
| 2 | Dev triage 与两级生命周期整改(U2.1 远端发现与强制 triage;U2.2 即时目标完整性;U2.3 PR base 门禁) | Dev `feature/development-governance-v2-triage-hardening` → initiative | — | PLANNED | 1(合同) |
| 3 | 真实两级 PR 演练 | Dev child PR → initiative → #585 → main | — | PLANNED | 2 |
| 4 | Guidelines 合入 → Dev gitlink → Review → 三项 CI → 合入 #585 → 收口 | Guidelines / Dev | #7 / #585 | PLANNED | 1–3 |
| 5 | Development-Manager 共享执行器 `agent-exec`;Dev Python 实现退役 | DM `feature/shared-agent-executor` | — | PLANNED | 4 |
| 6 | 存量仓逐仓采纳 | 各仓独立 initiative | — | PLANNED | 5 |
| 7 | 新项目治理初始化与 CI 准入 | DM | — | PLANNED | 5 |
## 当前候选对象与历史证据
| 仓库 | 分支 | 对象 | 证据 | 说明 |
|---|---|---|---|---|
| Development-Guidelines | `feature/development-governance-v2` | `ed4726c` | 无当前 Review/GATE | PR #7 open,未合入 |
| Agent-System-Dev | `feature/development-governance-v2` | `611f855`(整改前)→ `e7e8ee0`(同步 main 后) | CI run 3417(对象 `9bc61ef`)、3419(对象 `611f855`)为历史对象证据 | PR #585 open,未合入;`accepting_requirements=false` 直至整改完成后按需重开 |
## 已确认阻塞缺陷(整改前)
1. Dev `task-triage` 按接纳中 initiative 数量直接给出 `JOIN`,不做适配判断(违反 KTD1)。
2. Dev `task-triage` 只扫描当前检出的 `.task/`,看不到只存在于远端分支的 initiative(违反 KTD2)。
3. `task-start KIND=child` 依赖本机已有父分支,未校验父 initiative 仍开放、接纳需求(违反 KTD3)。
4. `task-start` 不要求 triage 收据;无 PR base 门禁;闭合记录与证据未贯穿 `immediate_target`。
5. Guidelines 缺 terminal receipt 机器 Schema;配置 Schema 未覆盖 transport/admission/豁免/清理;`all-unavailable` 未与新项目准入隔离;triage 合同仍为数量判定。
6. 原 U4 实施方式为 host 预写补丁交 CLI 应用,后续单元须由 CLI 自主实施。
## 正式仓库清单与采纳矩阵
来源:Gitea `/user/repos`(2026-10-16 实测)。排除:`Agent-System`(冻结参考仓,不再开发)、`SMDF-Agent-System`(空仓)、
`governance-drill-2026-09` 与 `merge-queue-admission-fixture-20261014`(演练夹具)。本机 `*-wt-*`、备份与组合目录不计入。
| 批次 | 仓库 | Guidelines 固定版本 | AGENT-EXECUTION.md | 共享执行器入口 | 正例 | 负例 | Review/CI | 状态 |
|---|---|---|---|---|---|---|---|---|
| A | Development-Guidelines | 自身 | — | — | — | — | — | PLANNED |
| A | Agent-System-Dev | 待更新 | 有(本地 Python 控制器) | 待切换 | — | — | — | PLANNED |
| A | Development-Manager | 待更新 | 无 | 实现方 | — | — | — | PLANNED |
| B | Agent-System-Core | — | 无 | 无 | — | — | — | PLANNED |
| B | Agent-System-Backend | — | 无 | 无 | — | — | — | PLANNED |
| B | Agent-System-RDM | — | 无 | 无 | — | — | — | PLANNED |
| C | Agent-System-Frontend | — | 无 | 无 | — | — | — | PLANNED |
| C | Agent-System-UI | — | 无 | 无 | — | — | — | PLANNED |
| C | Agent-System-Documents | — | 无 | 无 | — | — | — | PLANNED |
| C | Agent-System-Releases | — | 无 | 无 | — | — | — | PLANNED |
| D | Agent-Command | — | 无 | 无 | — | — | — | PLANNED |
| D | Agent-Intent | — | 无 | 无 | — | — | — | PLANNED |
| D | Agent-Native | — | 无 | 无 | — | — | — | PLANNED |
| D | Agent-Squad | — | 无 | 无 | — | — | — | PLANNED |
| E | Error-Code-System | — | 无 | 无 | — | — | — | PLANNED |
| E | Logging-System | — | 无 | 无 | — | — | — | PLANNED |
| E | Agent-Document-Renderer | — | 无 | 无 | — | — | — | PLANNED |
## 停止条件
无法获取权威远端 initiative;triage 收据与需求或候选 HEAD 不一致;child PR base 错误;Guidelines gitlink 未指向真实已合入版本;
CLI 终态无效或副作用未知;Review、CI 或平台准入缺失;主干在最终 CI 后继续前进;存量仓无共享执行器却启用强制规则;
需要发布规范 tag 而用户尚未执行双钥匙操作。出现任一项即停止对应交付窗口。
## 用户双钥匙事项
- Development-Guidelines 正式版本 tag:Agent 只准备命令,由用户执行。
- 分支保护变更(如新增必需检查):Agent 只准备方案,由用户执行。