@fitlab-ai/agent-infra 0.7.4 → 0.7.6

package/templates/.agents/skills/review-code/config/verify.zh-CN.json

@@ -24,12 +24,15 @@
         "结论与建议",
         "状态核对",
         "证据原文",
-        "自我质疑"
+        "自我质疑",
+        "审查分歧账本回写"
       ],
       "required_patterns": [
         "^### 审查决定$",
         "^\\$ ",
-        "^- \\*\\*总体结论\\*\\*[:：]\\s*(?:通过|需要修改|拒绝|Approved|Changes Requested|Rejected)\\s*$"
+        "^- \\*\\*总体结论\\*\\*[:：]\\s*(?:通过|需要修改|拒绝|Approved|Changes Requested|Rejected)\\s*$",
+        "^- \\*\\*审查基线提交\\*\\*[:：]\\s*\\S",
+        "^- \\*\\*审查差异指纹\\*\\*[:：]\\s*sha256:[0-9a-f]{64}\\s*$"
       ],
       "freshness_minutes": 30
     },

package/templates/.agents/skills/review-code/reference/output-templates.en.md

@@ -18,12 +18,13 @@ Prohibitions:
 - if `Blocker > 0`, never output an approval template
 - never count env-blocked findings as blockers / major issues / minor issues, and never use them to trigger Branch B/C/D
 - always include every TUI command format in the selected branch
+- the count line always shows 5 numbers: the first three (Blockers / Major / Minor) must be 0 to proceed; the last two are "pending human" items and need not be zero — `Manual-verify` (`{e}`) = this round's env-blocked count, `Human-decision` (`{h}`) = the number of rows in task.md `## 审查分歧账本` with `stage=code` and `status=needs-human-decision`; neither participates in branch selection
 
 ### Branch A: Approved with No Findings
 
 ```text
 Task {task-id} review completed. Verdict: approved.
-- Blockers: 0 | Major: 0 | Minor: 0[ | env-blocked: {n} (outside AI repair scope)]
+- Blockers: 0 | Major: 0 | Minor: 0 | Manual-verify: {e} | Human-decision: {h}
 [- Review report: .agents/workspace/active/{task-id}/{review-artifact}]
 
 Next step - commit the code:
@@ -39,7 +40,7 @@ Reminder: env-blocked findings must be carried in the PR description as a "manua
 
 ```text
 Task {task-id} review completed. Verdict: approved.
-- Blockers: 0 | Major: {n} | Minor: {n}[ | env-blocked: {n} (outside AI repair scope)]
+- Blockers: 0 | Major: {n} | Minor: {n} | Manual-verify: {e} | Human-decision: {h}
 - Review report: .agents/workspace/active/{task-id}/{review-artifact}
 
 Next step - fix before commit (recommended):
@@ -60,7 +61,7 @@ Reminder: env-blocked findings must be carried in the PR description as a "manua
 
 ```text
 Task {task-id} review completed. Verdict: changes requested.
-- Blockers: {n} | Major: {n} | Minor: {n}[ | env-blocked: {n} (outside AI repair scope)]
+- Blockers: {n} | Major: {n} | Minor: {n} | Manual-verify: {e} | Human-decision: {h}
 - Review report: .agents/workspace/active/{task-id}/{review-artifact}
 
 Next step - fix the findings:
@@ -76,7 +77,7 @@ Reminder: env-blocked findings must be carried in the PR description as a "manua
 
 ```text
 Task {task-id} review completed. Verdict: rejected, re-design the technical plan.
-- Blockers: {n} | Major: {n} | Minor: {n}[ | env-blocked: {n} (outside AI repair scope)]
+- Blockers: {n} | Major: {n} | Minor: {n} | Manual-verify: {e} | Human-decision: {h}
 - Review report: .agents/workspace/active/{task-id}/{review-artifact}
 
 Next step - re-design the technical plan:

package/templates/.agents/skills/review-code/reference/output-templates.zh-CN.md

@@ -18,12 +18,13 @@
 - 只要 `Blocker > 0`，就绝对不能输出通过模板
 - env-blocked 项绝对不能被计入 blocker / major / minor 计数，也不能用作触发场景 B/C/D 的依据
 - 所选场景中必须包含所有 TUI 命令格式
+- 计数行固定显示 5 个数字：前三项（阻塞 / 主要 / 次要）必须为 0 才进下一步；后两项是「待人处理」项、不要求归零——`人工校验点`（`{e}`）= 本轮 env-blocked 计数，`人工裁决`（`{h}`）= task.md `## 审查分歧账本` 中 `stage=code` 且 `status=needs-human-decision` 的行数；二者均不参与场景判断
 
 ### 场景 A：通过且无问题
 
 ```text
 任务 {task-id} 代码审查完成。结论：通过。
-- 阻塞项：0 | 主要问题：0 | 次要问题：0[ | 环境性遗留：{n}（不在 AI 修复范围）]
+- 阻塞项：0 | 主要问题：0 | 次要问题：0 | 人工校验点：{e} | 人工裁决：{h}
 [- 审查报告：.agents/workspace/active/{task-id}/{review-artifact}]
 
 下一步 - 提交代码：
@@ -39,7 +40,7 @@
 
 ```text
 任务 {task-id} 代码审查完成。结论：通过。
-- 阻塞项：0 | 主要问题：{n} | 次要问题：{n}[ | 环境性遗留：{n}（不在 AI 修复范围）]
+- 阻塞项：0 | 主要问题：{n} | 次要问题：{n} | 人工校验点：{e} | 人工裁决：{h}
 - 审查报告：.agents/workspace/active/{task-id}/{review-artifact}
 
 下一步 - 修复问题后提交（推荐）：
@@ -60,7 +61,7 @@
 
 ```text
 任务 {task-id} 代码审查完成。结论：需要修改。
-- 阻塞项：{n} | 主要问题：{n} | 次要问题：{n}[ | 环境性遗留：{n}（不在 AI 修复范围）]
+- 阻塞项：{n} | 主要问题：{n} | 次要问题：{n} | 人工校验点：{e} | 人工裁决：{h}
 - 审查报告：.agents/workspace/active/{task-id}/{review-artifact}
 
 下一步 - 修复问题：
@@ -76,7 +77,7 @@
 
 ```text
 任务 {task-id} 代码审查完成。结论：拒绝，需要重新设计方案。
-- 阻塞项：{n} | 主要问题：{n} | 次要问题：{n}[ | 环境性遗留：{n}（不在 AI 修复范围）]
+- 阻塞项：{n} | 主要问题：{n} | 次要问题：{n} | 人工校验点：{e} | 人工裁决：{h}
 - 审查报告：.agents/workspace/active/{task-id}/{review-artifact}
 
 下一步 - 重新设计技术方案：

package/templates/.agents/skills/review-code/reference/report-template.en.md

@@ -21,6 +21,8 @@ Use this template when writing `review-code.md` or `review-code-r{N}.md`.
 - **Reviewer**: {reviewer-name}
 - **Review Time**: {timestamp}
 - **Scope**: {file-count and major modules}
+- **Review Baseline Commit**: {raw git rev-parse HEAD} (baseline for the complete-task post-review commit gate; see `.agents/rules/review-handshake.md`)
+- **Reviewed Diff Fingerprint**: {raw node .agents/scripts/review-diff-fingerprint.js worktree HEAD}
 - **Overall Verdict**: {Approved / Changes Requested / Rejected} (pick exactly one; combined phrases will fail the verify gate)
 - **Findings (AI-actionable)**: 0 blockers, 0 majors, 0 minors / **env-blocked**: 0
 
@@ -59,6 +61,10 @@ Use this template when writing `review-code.md` or `review-code-r{N}.md`.
 > If this round has no env-blocked findings, keep the section heading and write "None".
 
 
+## Review Disagreement Ledger Writeback
+
+> Upsert each finding this round into the task.md disagreement ledger: append an `open` row for new findings (id prefix `CD-`, stage=code); per the hand-back duty set the executor's prior-round responses to `confirmed` / back to `open` / `needs-human-decision`. State machine and evidence rules: `.agents/rules/review-handshake.md`.
+
 ## Evidence
 
 > Pair each "I verified X" claim with the corresponding raw tool output; the gate only checks that this section exists and at least one `$ ` line is present. Every Blocker must be backed by a reproducible command (rg/grep/sed/nl) and its raw output; a judgment that cannot be reproduced must be downgraded or moved to Self-Doubt.

package/templates/.agents/skills/review-code/reference/report-template.zh-CN.md

@@ -22,6 +22,8 @@
 - **审查者**：{reviewer-name}
 - **审查时间**：{timestamp}
 - **审查范围**：{file-count and major modules}
+- **审查基线提交**：{git rev-parse HEAD 原文}（complete-task 的 post-review commit 门禁基线；详见 `.agents/rules/review-handshake.md`）
+- **审查差异指纹**：{node .agents/scripts/review-diff-fingerprint.js worktree HEAD 原文}
 - **总体结论**：{通过 / 需要修改 / 拒绝}（恰取一个；禁止写组合短语，否则 verify gate 失败）
 - **发现（AI 可处理）**：0 阻塞项，0 主要，0 次要 / **env-blocked**：0
 
@@ -60,6 +62,10 @@
 > 如本轮无 env-blocked 项，保留段落标题并写「（无）」。
 
 
+## 审查分歧账本回写
+
+> 把本轮每条 finding upsert 到 task.md `## 审查分歧账本`：新 finding 追加 `open` 行（id 前缀 `CD-`，stage=code），对执行方上一轮响应按回交义务改 `confirmed` / 置回 `open` / `needs-human-decision`。状态机与证据规则见 `.agents/rules/review-handshake.md`。
+
 ## 证据原文
 
 > 每条“我验证了 X”断言都要配对对应 tool output 原文；gate 仅校验本段存在和至少一行 `$ `。每条 Blocker 必须配可复现命令（rg/grep/sed/nl）及其原文；无法复现的判断须降级或移入「自我质疑」。

package/templates/.agents/skills/review-code/reference/review-criteria.en.md

@@ -14,6 +14,7 @@ Follow the `code-review` step in `.agents/workflows/feature-development.yaml`.
 - [ ] Performance and security risks
 - [ ] Comments and documentation
 - [ ] Consistency with the approved technical plan
+- [ ] The reviewer checked whether the executor missed any key design decision that should be upgraded to `[needs-human-decision]`
 - [ ] Every blocker is backed by reproducible grep/sed/nl evidence; conclusions not directly verified are declared under Self-Doubt
 
 **Common anti-examples**:

package/templates/.agents/skills/review-code/reference/review-criteria.zh-CN.md

@@ -14,6 +14,7 @@
 - [ ] 性能与安全风险
 - [ ] 代码注释和文档
 - [ ] 与已批准技术方案的一致性
+- [ ] 已复核执行方是否漏标应升级为 `[needs-human-decision]` 的关键设计决策
 - [ ] 每条 blocker 都配可复现的 grep/sed/nl 证据，未直接验证的结论已在「自我质疑」声明
 
 **常见反例**：

package/templates/.agents/skills/review-plan/SKILL.en.md

@@ -30,6 +30,16 @@ tail .agents/workspace/active/{task-id}/task.md
 
 > If `{task-id}` matches `^[#]?[0-9]+$` (bare numeric or `#`-prefixed), follow the "SKILL parameter resolver" section of `.agents/rules/task-short-id.md`; treat `{task-id}` as the resolved full `TASK-YYYYMMDD-HHMMSS` form for every downstream command.
 
+## Step Start: Write the started Marker
+
+After prerequisites pass and before this round's first artifact action, append a started marker to task.md `## Activity Log` (same base action as this round's done entry plus a ` [started]` suffix, note `started`):
+
+```
+- {YYYY-MM-DD HH:mm:ss±HH:MM} — **Review Plan (Round {N}) [started]** by {agent} — started
+```
+
+`ai task log` pairs it with the done entry written when the review completes onto one row (in progress → done). Format and pairing rules: see the "Activity Log started / done dual-marker convention" in `.agents/rules/task-management.md`.
+
 ## Steps
 
 ### 1. Verify Prerequisites

package/templates/.agents/skills/review-plan/SKILL.zh-CN.md

@@ -32,6 +32,16 @@ tail .agents/workspace/active/{task-id}/task.md
 
 > 如果 `{task-id}` 入参匹配 `^[#]?[0-9]+$`（裸数字或带 `#` 前缀），先读取 `.agents/rules/task-short-id.md` 的「SKILL 入参解析」段执行解析；后续命令视 `{task-id}` 为解析后的全长 `TASK-YYYYMMDD-HHMMSS` 形式。
 
+## 步骤开始：写入 started 标记
+
+确认前置条件后、本轮第一个产出动作之前，向 task.md `## 活动日志` 追加一条 started 标记（与本轮 done 条目同基名 + ` [started]` 后缀，note 用 `started`）：
+
+```
+- {YYYY-MM-DD HH:mm:ss±HH:MM} — **Review Plan (Round {N}) [started]** by {agent} — started
+```
+
+`ai task log` 会把它与审查完成时写入的 done 条目配对成一行（进行中 → 已完成）。格式与配对规则见 `.agents/rules/task-management.md` 的「Activity Log started / done 双标记约定」。
+
 ## 执行步骤
 ### 1. 验证前置条件
 

package/templates/.agents/skills/review-plan/config/verify.en.json

@@ -24,7 +24,8 @@
         "Conclusion and Recommendations",
         "State Check",
         "Evidence",
-        "Self-Doubt"
+        "Self-Doubt",
+        "Review Disagreement Ledger Writeback"
       ],
       "required_patterns": [
         "^### Approval Decision$",

package/templates/.agents/skills/review-plan/config/verify.zh-CN.json

@@ -24,7 +24,8 @@
         "结论与建议",
         "状态核对",
         "证据原文",
-        "自我质疑"
+        "自我质疑",
+        "审查分歧账本回写"
       ],
       "required_patterns": [
         "^### 审查决定$",

package/templates/.agents/skills/review-plan/reference/output-templates.en.md

@@ -16,12 +16,13 @@ Rules:
 - If `Blocker > 0`, never use an approved template
 - Never count env-blocked items as blocker / major / minor or use them to trigger Scenario B/C/D
 - The selected scenario must include all TUI command formats
+- The count line always shows 4 numbers: the first three (Blockers / Major / Minor) must be 0 to proceed; the fourth, `Human-decision` (`{h}`), is the number of rows in task.md `## 审查分歧账本` with `stage=plan` and `status=needs-human-decision` — a "pending human ruling" item that need not be zero and does not participate in scenario selection
 
 ### Scenario A: Approved with no findings
 
 ```text
 Task {task-id} technical plan review completed. Verdict: approved.
-- Blockers: 0 | Major issues: 0 | Minor issues: 0[ | Environment-blocked: {n} (outside AI fix scope)]
+- Blockers: 0 | Major issues: 0 | Minor issues: 0 | Human-decision: {h}
 [- Review report: .agents/workspace/active/{task-id}/{review-artifact}]
 
 Next step - write code:
@@ -37,7 +38,7 @@ Reminder: env-blocked items belong in the PR description manual verification che
 
 ```text
 Task {task-id} technical plan review completed. Verdict: approved.
-- Blockers: 0 | Major issues: {n} | Minor issues: {n}[ | Environment-blocked: {n} (outside AI fix scope)]
+- Blockers: 0 | Major issues: {n} | Minor issues: {n} | Human-decision: {h}
 - Review report: .agents/workspace/active/{task-id}/{review-artifact}
 
 Next step - revise plan before coding (recommended):
@@ -58,7 +59,7 @@ Reminder: env-blocked items belong in the PR description manual verification che
 
 ```text
 Task {task-id} technical plan review completed. Verdict: changes requested.
-- Blockers: {n} | Major issues: {n} | Minor issues: {n}[ | Environment-blocked: {n} (outside AI fix scope)]
+- Blockers: {n} | Major issues: {n} | Minor issues: {n} | Human-decision: {h}
 - Review report: .agents/workspace/active/{task-id}/{review-artifact}
 
 Next step - revise technical plan:
@@ -74,7 +75,7 @@ Reminder: env-blocked items belong in the PR description manual verification che
 
 ```text
 Task {task-id} technical plan review completed. Verdict: rejected, redesign required.
-- Blockers: {n} | Major issues: {n} | Minor issues: {n}[ | Environment-blocked: {n} (outside AI fix scope)]
+- Blockers: {n} | Major issues: {n} | Minor issues: {n} | Human-decision: {h}
 - Review report: .agents/workspace/active/{task-id}/{review-artifact}
 
 Next step - redesign:

package/templates/.agents/skills/review-plan/reference/output-templates.zh-CN.md

@@ -16,12 +16,13 @@
 - 只要 `Blocker > 0`，就绝对不能输出通过模板
 - env-blocked 项绝对不能被计入 blocker / major / minor 计数，也不能用作触发场景 B/C/D 的依据
 - 所选场景中必须包含所有 TUI 命令格式
+- 计数行固定显示 4 个数字：前三项（阻塞 / 主要 / 次要）必须为 0 才进下一步；第四项 `人工裁决`（`{h}`）= task.md `## 审查分歧账本` 中 `stage=plan` 且 `status=needs-human-decision` 的行数，是「待人裁」项、不要求归零，也不参与场景判断
 
 ### 场景 A：通过且无问题
 
 ```text
 任务 {task-id} 技术方案审查完成。结论：通过。
-- 阻塞项：0 | 主要问题：0 | 次要问题：0[ | 环境性遗留：{n}（不在 AI 修复范围）]
+- 阻塞项：0 | 主要问题：0 | 次要问题：0 | 人工裁决：{h}
 [- 审查报告：.agents/workspace/active/{task-id}/{review-artifact}]
 
 下一步 - 编写代码：
@@ -37,7 +38,7 @@
 
 ```text
 任务 {task-id} 技术方案审查完成。结论：通过。
-- 阻塞项：0 | 主要问题：{n} | 次要问题：{n}[ | 环境性遗留：{n}（不在 AI 修复范围）]
+- 阻塞项：0 | 主要问题：{n} | 次要问题：{n} | 人工裁决：{h}
 - 审查报告：.agents/workspace/active/{task-id}/{review-artifact}
 
 下一步 - 修订方案后编码（推荐）：
@@ -58,7 +59,7 @@
 
 ```text
 任务 {task-id} 技术方案审查完成。结论：需要修改。
-- 阻塞项：{n} | 主要问题：{n} | 次要问题：{n}[ | 环境性遗留：{n}（不在 AI 修复范围）]
+- 阻塞项：{n} | 主要问题：{n} | 次要问题：{n} | 人工裁决：{h}
 - 审查报告：.agents/workspace/active/{task-id}/{review-artifact}
 
 下一步 - 修订技术方案：
@@ -74,7 +75,7 @@
 
 ```text
 任务 {task-id} 技术方案审查完成。结论：拒绝，需要重新设计。
-- 阻塞项：{n} | 主要问题：{n} | 次要问题：{n}[ | 环境性遗留：{n}（不在 AI 修复范围）]
+- 阻塞项：{n} | 主要问题：{n} | 次要问题：{n} | 人工裁决：{h}
 - 审查报告：.agents/workspace/active/{task-id}/{review-artifact}
 
 下一步 - 重新设计：

package/templates/.agents/skills/review-plan/reference/report-template.en.md

@@ -59,6 +59,10 @@ Use this template when writing `review-plan.md` or `review-plan-r{N}.md`.
 > If this round has no env-blocked findings, keep the section heading and write "None".
 
 
+## Review Disagreement Ledger Writeback
+
+> Upsert each finding this round into the task.md disagreement ledger: append an `open` row for new findings (id prefix `PL-`, stage=plan); per the hand-back duty set the executor's prior-round responses to `confirmed` / back to `open` / `needs-human-decision`. State machine and evidence rules: `.agents/rules/review-handshake.md`.
+
 ## Evidence
 
 > Pair each "I verified X" claim with the corresponding raw tool output; the gate only checks that this section exists and at least one `$ ` line is present. Every Blocker must be backed by a reproducible command (rg/grep/sed/nl) and its raw output; a judgment that cannot be reproduced must be downgraded or moved to Self-Doubt.

package/templates/.agents/skills/review-plan/reference/report-template.zh-CN.md

@@ -60,6 +60,10 @@
 > 如本轮无 env-blocked 项，保留段落标题并写「（无）」。
 
 
+## 审查分歧账本回写
+
+> 把本轮每条 finding upsert 到 task.md `## 审查分歧账本`：新 finding 追加 `open` 行（id 前缀 `PL-`，stage=plan），对执行方上一轮响应按回交义务改 `confirmed` / 置回 `open` / `needs-human-decision`。状态机与证据规则见 `.agents/rules/review-handshake.md`。
+
 ## 证据原文
 
 > 每条“我验证了 X”断言都要配对对应 tool output 原文；gate 仅校验本段存在和至少一行 `$ `。每条 Blocker 必须配可复现命令（rg/grep/sed/nl）及其原文；无法复现的判断须降级或移入「自我质疑」。

package/templates/.agents/skills/review-plan/reference/review-criteria.en.md

@@ -13,6 +13,7 @@ Follow the `design-review` step in `.agents/workflows/feature-development.yaml`.
 - [ ] Test strategy covers critical paths, regression risks, and edge cases
 - [ ] Risks, migration, rollback, or compatibility handling are sufficient
 - [ ] The plan avoids over-design and unrelated scope expansion
+- [ ] The reviewer checked whether the executor missed any key design decision that should be upgraded to `[needs-human-decision]`
 - [ ] Every blocker is backed by reproducible grep/sed/nl evidence; conclusions not directly verified are declared under Self-Doubt
 
 **Common anti-examples**:

package/templates/.agents/skills/review-plan/reference/review-criteria.zh-CN.md

@@ -13,6 +13,7 @@
 - [ ] 测试策略是否覆盖关键路径、回归风险和边界情况
 - [ ] 风险、迁移、回滚或兼容性处理是否充分
 - [ ] 方案是否避免过度设计和无关扩张
+- [ ] 已复核执行方是否漏标应升级为 `[needs-human-decision]` 的关键设计决策
 - [ ] 每条 blocker 都配可复现的 grep/sed/nl 证据，未直接验证的结论已在「自我质疑」声明
 
 **常见反例**：

package/templates/.agents/skills/watch-pr/SKILL.en.md

@@ -21,6 +21,16 @@ Version stamp rule: before creating or updating `task.md` frontmatter, read `.ag
 
 > If the `{task-id}` argument matches `^[#]?[0-9]+$` (a bare number or `#`-prefixed), first read the "SKILL argument parsing" section of `.agents/rules/task-short-id.md` to resolve it; subsequent commands treat `{task-id}` as the resolved full `TASK-YYYYMMDD-HHMMSS` form.
 
+## Step Start: Write the started Marker
+
+After prerequisites pass and before this round's first artifact action, append a started marker to task.md `## Activity Log` (same base action as this round's done entry plus a ` [started]` suffix, note `started`):
+
+```
+- {YYYY-MM-DD HH:mm:ss±HH:MM} — **Watch PR (Round {N}) [started]** by {agent} — started
+```
+
+`ai task log` pairs it with the done entry written on completion onto one row (in progress → done). See the "Activity Log started / done dual-marker convention" in `.agents/rules/task-management.md`.
+
 ## Steps
 
 ### 1. Resolve Arguments

package/templates/.agents/skills/watch-pr/SKILL.zh-CN.md

@@ -21,6 +21,16 @@ description: "监控 PR 的 required checks 并在失败时自愈"
 
 > 如果 `{task-id}` 入参匹配 `^[#]?[0-9]+$`（裸数字或带 `#` 前缀），先读取 `.agents/rules/task-short-id.md` 的「SKILL 入参解析」段执行解析；后续命令视 `{task-id}` 为解析后的全长 `TASK-YYYYMMDD-HHMMSS` 形式。
 
+## 步骤开始：写入 started 标记
+
+确认前置条件后、本轮第一个产出动作之前，向 task.md `## 活动日志` 追加一条 started 标记（与本轮 done 条目同基名 + ` [started]` 后缀，note 用 `started`）：
+
+```
+- {YYYY-MM-DD HH:mm:ss±HH:MM} — **Watch PR (Round {N}) [started]** by {agent} — started
+```
+
+`ai task log` 会把它与完成时写入的 done 条目配对成一行（进行中 → 已完成）。约定见 `.agents/rules/task-management.md` 的「Activity Log started / done 双标记约定」。
+
 ## 执行步骤
 
 ### 1. 解析入参

package/templates/.agents/templates/task.en.md

@@ -53,10 +53,22 @@ pr_status: pending             # PR status: pending (default) | created (PR crea
 
 <!-- Populated by review-* -->
 
+## Review Disagreement Ledger
+
+<!-- One row per review finding; state machine / evidence rules in .agents/rules/review-handshake.md. The phase-advance and complete-task gates read this section. Keep the header when there are no disagreements. -->
+
+| id | stage | round | severity | status | evidence |
+|----|-------|-------|----------|--------|----------|
+
+## Human Rulings
+
+<!-- Humans record rulings for needs-human-decision decisions here and flip matching HD- rows in the Review Disagreement Ledger to human-decided. -->
+
 ## Activity Log
 
 <!-- Append a new entry for each workflow step. Do NOT overwrite previous entries. -->
 <!-- Format: - {YYYY-MM-DD HH:mm:ss±HH:MM} — **{step}** by {agent} — {brief summary} -->
+<!-- Some workflow skills also write a started marker when the step begins (action suffixed with ` [started]`) and a done entry on completion; ai task log pairs them onto one row by base action. Convention: see .agents/rules/task-management.md. -->
 
 ## Completion Checklist
 

package/templates/.agents/templates/task.zh-CN.md

@@ -53,10 +53,22 @@ pr_status: pending             # PR 状态：pending（默认）| created（已
 
 <!-- 由 review-* 填写 -->
 
+## 审查分歧账本
+
+<!-- 每条 review finding 一行；状态机/证据规则见 .agents/rules/review-handshake.md。阶段推进与 complete-task gate 读取本段。无分歧时保留表头即可。 -->
+
+| id | stage | round | severity | status | evidence |
+|----|-------|-------|----------|--------|----------|
+
+## 人工裁决
+
+<!-- 人类在此记录对 needs-human-decision 决策的裁定，并把 ## 审查分歧账本 对应 HD- 行翻为 human-decided。 -->
+
 ## 活动日志
 
 <!-- 每个工作流步骤追加一条新记录，不要覆盖之前的记录。 -->
 <!-- 格式：- {YYYY-MM-DD HH:mm:ss±HH:MM} — **{步骤}** by {执行者} — {简要说明} -->
+<!-- 部分工作流 SKILL 在步骤开始时额外写一条 started 标记（action 末尾加 ` [started]`），完成时再写 done；ai task log 会按基名把两者配对成一行。约定见 .agents/rules/task-management.md。 -->
 
 ## 完成检查清单
 

package/templates/.github/workflows/metadata-sync.yml

@@ -56,7 +56,7 @@ jobs:
 
       - name: Checkout shared scripts
         if: steps.metadata.outputs.is_task_comment == 'true' && steps.metadata.outputs.type != ''
-        uses: actions/checkout@v6
+        uses: actions/checkout@v7
         with:
           sparse-checkout: .github/scripts
           sparse-checkout-cone-mode: false

package/templates/.github/workflows/pr-label.yml

@@ -18,7 +18,7 @@ jobs:
     runs-on: ubuntu-latest
     steps:
       - name: Checkout base branch
-        uses: actions/checkout@v6
+        uses: actions/checkout@v7
 
       - name: Sync in-labels
         env:

package/templates/.github/workflows/status-label.yml

@@ -19,7 +19,7 @@ jobs:
           (github.event_name == 'issues' && github.event.action == 'closed' && github.event.issue.state_reason == 'completed') ||
           (github.event_name == 'issues' && github.event.action == 'reopened') ||
           (github.event_name == 'pull_request_target' && github.event.action == 'closed' && github.event.pull_request.merged == true)
-        uses: actions/checkout@v6
+        uses: actions/checkout@v7
         with:
           sparse-checkout: .github/scripts
           sparse-checkout-cone-mode: false