Connect delivery windows and recovery to the repository rules
Why: agents need consistent entrypoints and recording defaults to avoid retrying synchronization and CI outside the final delivery window. Evidence: SELF generated-task-card red-green regression and governance suite recorded through make evidence; pending shared record created as Issue #518. Impact: rules, task template and capability matrix stay explicit about pending activation, default strict startup, manual coordination and unchanged CI triggers. Refs: U4; policy/merge-queue.md; .task/feature-merge-queue-policy-draft.md
This commit is contained in:
+1
-1
@@ -51,7 +51,7 @@ U2 起实施与部署分别评审。
|
||||
|
||||
## 验证
|
||||
|
||||
规范修订:[最终验证与合入调度 r1](policy/merge-queue.md) 已作为实施计划基线。Documents 的 U1–U6 计划待阶段 5 评审,独立候选位置见本任务卡;当前 gitlink、脚本、CI 和平台模式未切换。
|
||||
规范修订:[最终验证与合入调度 r1](policy/merge-queue.md) 及 Documents 的 U1–U6 计划已批准,位置及固定提交见本任务卡。同步幂等化、显式局部恢复和源码外证据基础在本分支实施;当前规范 gitlink、CI 触发与平台调度模式尚未切换。
|
||||
|
||||
`make test` 先核对子模块工作树与固定指针,再运行治理脚本、公开边界、跨仓指针、库及各模块
|
||||
测试。实际目标以根 Makefile 为准。`make test-governance` 可独立检查开发门禁,使用临时
|
||||
|
||||
Reference in New Issue
Block a user