Record the scheduling baseline and implementation plan for review

Why: preserve the user's continuation from the delivered r1 specification into a concrete implementation and verification plan.

Evidence: precheck and plan source/link/example checks are preserved as SELF receipts in the task card; code, CI and platform trials remain NOT_RUN.

Impact: approval metadata, plan association and project entry only; the delivery mode remains unchanged and the plan awaits stage 5 review.

Refs: policy/merge-queue.md; .task/feature-merge-queue-policy-draft.md; Documents docs/proposals/2026-10-13-merge-queue-implementation-plan.md
This commit is contained in:
2026-10-13 06:40:57 +00:00
parent 913b214f28
commit 64dd48e92b
3 changed files with 97 additions and 17 deletions
+1 -1
View File
@@ -51,7 +51,7 @@ U2 起实施与部署分别评审。
## 验证
规范修订待审:[最终验证与合入调度 r1](policy/merge-queue.md)。方向已确认,通用候选与 Dev 配套条文待文本评审;当前 gitlink、脚本、CI 和平台模式未切换。
规范修订:[最终验证与合入调度 r1](policy/merge-queue.md) 已作为实施计划基线。Documents 的 U1–U6 计划待阶段 5 评审,独立候选位置见本任务卡;当前 gitlink、脚本、CI 和平台模式未切换。
`make test` 先核对子模块工作树与固定指针,再运行治理脚本、公开边界、跨仓指针、库及各模块
测试。实际目标以根 Makefile 为准。`make test-governance` 可独立检查开发门禁,使用临时