Rebuild the validation record after the authoritative combination advances

Why: Main advanced after the first fixed candidate passed CI, changing four component pins and invalidating final admission against the new target. Stage progress must also be referenced outside fixed source to avoid status-driven commits.

Evidence: Source-external original receipts preserve the previous clean local test/build, three successful CI jobs on 80f5e9a, detection of target advance, the refused transient lock and successful serial synchronization to 10d54d5. New combination verification and exact-head CI are pending.

Impact: Preserve the merged authoritative component versions; record the expired candidate honestly and replace a temporary stage-status sentence with its authoritative record pointers. No platform protection change or queue activation.

Refs: PR #519; main PR #513; implementation plan U1/U3/U4; Issue #518

policy/merge-queue.md

@@ -1,7 +1,7 @@
 # 最终验证与合入调度（候选条文 r1）
 
 状态：approved（r1 条文作为实施计划基线）；执行模式：未切换；日期：2026-10-13（Asia/Shanghai）；规范采纳负责人：weichen。
-r1 条文来源提交为 913b214f2826a50b3dab65f79d9ebf83e84f2519；Documents 实施与测试计划 r1@ba4044d57e38d0887dd425d052abf26b20a28bf4 已于 2026-10-13 获用户「批准」。阶段 6 的本地实现产物仍待人工确认，规范及计划批准不等于模式已启用。
+r1 条文来源提交为 913b214f2826a50b3dab65f79d9ebf83e84f2519；Documents 实施与测试计划 r1@ba4044d57e38d0887dd425d052abf26b20a28bf4 已于 2026-10-13 获用户「批准」。阶段结论与执行进展按 [迭代交付](delivery.md) 记录在任务主记录，候选固定后的结论保存在关联 PR 与源码外收据中；规范及计划批准不等于模式已启用。
 现行规则仍以根 AGENTS.md、[迭代交付](delivery.md)、[开发门禁](governance.md) 和已采纳 gitlink 为准。
 本分支已实施 CLI 同步/恢复及源码外证据基础，自检依据见本任务卡；线上队列、CI 分流、平台保护和当前 gitlink 尚未切换，不承诺自动调度能力已就位。