@fitlab-ai/agent-infra 0.7.7 → 0.8.1

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

@@ -99,7 +99,7 @@ Follow the `technical-design` step in `.agents/workflows/feature-development.yam
 - [ ] Define the verification strategy (tests, manual checks)
 - [ ] Assess impact and risks
 
-When this round introduces a new key design decision, record it under `## Open Questions` according to `.agents/rules/no-mid-flow-questions.md` and write the matching `HD-` ledger row.
+When this round introduces a new key design decision, per `.agents/rules/no-mid-flow-questions.md` write its detail block (background/options/impact/recommendation) into the plan artifact's `## 人工裁决待办` (Pending Human Decisions) section as `### HD-N：<title> [needs-human-decision]` (`HD-N` is globally unique, see `.agents/rules/review-handshake.md`), and write the matching `HD-` ledger row (evidence pointing to `{plan-artifact}#HD-N`); ordinary open questions still go under `## Open Questions`.
 
 **Design principles**:
 1. **Architectural soundness**: choose the structurally correct approach; diff size is not the primary criterion. Do not pile changes onto an unsound structure just to keep the diff small
@@ -125,7 +125,6 @@ Update `.agents/workspace/active/{task-id}/task.md`:
 - `assigned_to`: {current AI agent}
 - `updated_at`: {current time}
 - `agent_infra_version`: value from `.agents/rules/version-stamp.md`
-- If `target_date` is empty, write an estimated completion date based on the effort estimate (`YYYY-MM-DD`); leave it empty without blocking when no reasonable estimate exists; keep any existing value
 - Record the plan artifact for this round: `{plan-artifact}` (Round `{plan-round}`)
 - If the task template contains a `## Design` section, update it to link to `{plan-artifact}`
 - Mark technical-design as complete in workflow progress and include the actual round when the task template supports it

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

@@ -98,7 +98,7 @@ tail .agents/workspace/active/{task-id}/task.md
 - [ ] 定义验证策略（测试、手动检查）
 - [ ] 评估方案的影响和风险
 
-遇到本轮新增的关键设计决策时，按 `.agents/rules/no-mid-flow-questions.md` 判据写入 `## 未决问题`，并回写 `HD-` 账本行。
+遇到本轮新增的关键设计决策时，按 `.agents/rules/no-mid-flow-questions.md` 判据，把详情块（背景/选项/影响/推荐）写入方案产物的 `## 人工裁决待办` 段 `### HD-N：<标题> [needs-human-decision]`（`HD-N` 全局唯一，规则见 `.agents/rules/review-handshake.md`），并回写 `HD-` 账本行（evidence 指向 `{plan-artifact}#HD-N`）；普通未决问题仍写 `## 未决问题`。
 
 **设计原则**：
 1. **架构合理性**：选择结构正确的方案，改动大小不是首要依据。不要为了减少 diff 而在不合理的结构上叠加
@@ -124,7 +124,6 @@ date "+%Y-%m-%d %H:%M:%S%:z"
 - `assigned_to`：{当前 AI 代理}
 - `updated_at`：{当前时间}
 - `agent_infra_version`：按 `.agents/rules/version-stamp.md` 取值
-- 若 `target_date` 为空，基于工作量评估写入预估完成日（`YYYY-MM-DD`）；无法合理预估时保持留空、不阻塞；已有值则保留
 - 记录本轮方案产物：`{plan-artifact}`（Round `{plan-round}`）
 - 如任务模板包含 `## 设计` 段落，更新为指向 `{plan-artifact}` 的链接
 - 在工作流进度中标记 technical-design 为已完成，并注明实际轮次（如果任务模板支持）

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

@@ -77,9 +77,9 @@ date "+%Y-%m-%d %H:%M:%S%:z"
 ```
 
 Set `current_step` to `requirement-analysis-review`, refresh task metadata, and append:
-`- {YYYY-MM-DD HH:mm:ss±HH:MM} — **Review Analysis (Round {N})** by {agent} — Verdict: {Approved/Changes Requested/Rejected}, blockers: {n}, major: {n}, minor: {n}[ (+ {n} env-blocked)] → {review-artifact}`
+`- {YYYY-MM-DD HH:mm:ss±HH:MM} — **Review Analysis (Round {N})** by {agent} — Verdict: {Approved/Changes Requested/Rejected}, blockers: {n}, major: {n}, minor: {n}, Manual-validation: {n} → {review-artifact}`
 
-`env-blocked` is the data source for the `Manual-verify` count folded into review rows in `ai task log`; do not add a parallel manual-verification field.
+`manual-validation` is the data source for the `Manual-validation` count folded into review rows in `ai task log`; do not add a parallel manual-verification field.
 
 If task.md has a valid `issue_number`, read `.agents/rules/issue-sync.md`, sync the task comment, and publish the `{review-artifact}` comment.
 

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

@@ -88,9 +88,9 @@ date "+%Y-%m-%d %H:%M:%S%:z"
 - `updated_at`：{当前时间}
 - `agent_infra_version`：按 `.agents/rules/version-stamp.md` 取值
 - 追加：
-  `- {YYYY-MM-DD HH:mm:ss±HH:MM} — **Review Analysis (Round {N})** by {agent} — Verdict: {Approved/Changes Requested/Rejected}, blockers: {n}, major: {n}, minor: {n}[ (+ {n} env-blocked)] → {review-artifact}`
+  `- {YYYY-MM-DD HH:mm:ss±HH:MM} — **Review Analysis (Round {N})** by {agent} — Verdict: {Approved/Changes Requested/Rejected}, blockers: {n}, major: {n}, minor: {n}, Manual-validation: {n} → {review-artifact}`
 
-`env-blocked` 是 `ai task log` 中 review 行「人工校验点」（EN `Manual-verify`）计数的数据源；不要新增并行人工验证字段。
+`manual-validation` 是 `ai task log` 中 review 行「人工校验点」（EN `Manual-validation`）计数的数据源；不要新增并行人工验证字段。
 
 如果 task.md 中存在有效的 `issue_number`，执行前先读取 `.agents/rules/issue-sync.md`，完成 upstream 仓库检测和权限检测，然后同步 task 评论并发布 `{review-artifact}` 评论。
 

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

@@ -20,7 +20,7 @@
       "required_sections": [
         "Review Summary",
         "Findings",
-        "Environment-Blocked Findings",
+        "Manual Validation Items",
         "Conclusion and Recommendations",
         "State Check",
         "Evidence",

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

@@ -20,7 +20,7 @@
       "required_sections": [
         "审查摘要",
         "问题清单",
-        "环境性遗留",
+        "人工校验项",
         "结论与建议",
         "状态核对",
         "证据原文",

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

@@ -4,8 +4,8 @@ Read this file before presenting the final review result to the user.
 
 ## Select exactly one output scenario
 
-Evaluate in this order (**env-blocked count does not participate in selection**):
-1. If `Blocker = 0`, `Major = 0`, and `Minor = 0`, use Scenario A, regardless of env-blocked count
+Evaluate in this order (**manual-validation count does not participate in selection**):
+1. If `Blocker = 0`, `Major = 0`, and `Minor = 0`, use Scenario A, regardless of manual-validation count
 2. If `Blocker = 0` and (`Major > 0` or `Minor > 0`), use Scenario B
 3. If `Blocker > 0` and the issues can be handled by one focused revision, use Scenario C
 4. If the requirement analysis needs broad rewriting or fresh clarification, use Scenario D
@@ -14,7 +14,7 @@ Rules:
 - Do not skip scenario selection
 - Do not mix text from multiple scenarios
 - 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
+- Never count manual-validation 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=analysis` and `status=needs-human-decision` — a "pending human ruling" item that need not be zero and does not participate in scenario selection. When `{h} > 0`, before the selected scenario's "Next steps" commands you must expand each pending ruling per the "Pending human-decision pre-block" in `.agents/rules/next-step-output.md` and prompt to resolve them first
 
@@ -30,8 +30,8 @@ Next step - write the technical plan:
   - Gemini CLI: /agent-infra:plan-task {task-ref}
   - Codex CLI: $plan-task {task-ref}
 
-[When env-blocked > 0, append:]
-Reminder: env-blocked items belong in the PR description manual verification checklist and should not trigger /analyze-task.
+[When manual-validation > 0, append:]
+Reminder: manual-validation items belong in the PR description manual verification checklist and should not trigger /analyze-task.
 ```
 
 ### Scenario B: Approved with findings
@@ -51,8 +51,8 @@ Or proceed directly to planning:
   - Gemini CLI: /agent-infra:plan-task {task-ref}
   - Codex CLI: $plan-task {task-ref}
 
-[When env-blocked > 0, append:]
-Reminder: env-blocked items belong in the PR description manual verification checklist and should not trigger /analyze-task.
+[When manual-validation > 0, append:]
+Reminder: manual-validation items belong in the PR description manual verification checklist and should not trigger /analyze-task.
 ```
 
 ### Scenario C: Changes requested
@@ -67,8 +67,8 @@ Next step - revise requirement analysis:
   - Gemini CLI: /agent-infra:analyze-task {task-ref}
   - Codex CLI: $analyze-task {task-ref}
 
-[When env-blocked > 0, append:]
-Reminder: env-blocked items belong in the PR description manual verification checklist and should not trigger /analyze-task.
+[When manual-validation > 0, append:]
+Reminder: manual-validation items belong in the PR description manual verification checklist and should not trigger /analyze-task.
 ```
 
 ### Scenario D: Rejected
@@ -83,6 +83,6 @@ Next step - re-analyze:
   - Gemini CLI: /agent-infra:analyze-task {task-ref}
   - Codex CLI: $analyze-task {task-ref}
 
-[When env-blocked > 0, append:]
-Reminder: env-blocked items belong in the PR description manual verification checklist and should not trigger /analyze-task.
+[When manual-validation > 0, append:]
+Reminder: manual-validation items belong in the PR description manual verification checklist and should not trigger /analyze-task.
 ```

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

@@ -4,8 +4,8 @@
 
 ## 选择唯一输出场景
 
-按以下顺序判断（**注意：env-blocked 数量不参与判断**）：
-1. 如果 `Blocker = 0` 且 `Major = 0` 且 `Minor = 0`，使用场景 A（不管 env-blocked 是否 > 0）
+按以下顺序判断（**注意：manual-validation 数量不参与判断**）：
+1. 如果 `Blocker = 0` 且 `Major = 0` 且 `Minor = 0`，使用场景 A（不管 manual-validation 是否 > 0）
 2. 如果 `Blocker = 0` 且（`Major > 0` 或 `Minor > 0`），使用场景 B
 3. 如果 `Blocker > 0`，且问题可以通过一次聚焦修复解决，使用场景 C
 4. 如果需求分析需要大范围重写或重新澄清，使用场景 D
@@ -14,7 +14,7 @@
 - 不要跳过场景判断步骤
 - 不要混用不同场景的文案
 - 只要 `Blocker > 0`，就绝对不能输出通过模板
-- env-blocked 项绝对不能被计入 blocker / major / minor 计数，也不能用作触发场景 B/C/D 的依据
+- manual-validation 项绝对不能被计入 blocker / major / minor 计数，也不能用作触发场景 B/C/D 的依据
 - 所选场景中必须包含所有 TUI 命令格式
 - 计数行固定显示 4 个数字：前三项（阻塞 / 主要 / 次要）必须为 0 才进下一步；第四项 `人工裁决`（`{h}`）= task.md `## 审查分歧账本` 中 `stage=analysis` 且 `status=needs-human-decision` 的行数，是「待人裁」项、不要求归零，也不参与场景判断。当 `{h} > 0` 时，必须在选定场景的「下一步」命令之前，按 `.agents/rules/next-step-output.md`「人工裁决待办前置块」逐项展开裁决项并提示先完成裁决
 
@@ -30,8 +30,8 @@
   - Gemini CLI：/agent-infra:plan-task {task-ref}
   - Codex CLI：$plan-task {task-ref}
 
-[当 env-blocked > 0 时，在最后附加一行：]
-提醒：env-blocked 项需在 PR description 的「待人工验证」清单中承接，不应触发 /analyze-task。
+[当 manual-validation > 0 时，在最后附加一行：]
+提醒：manual-validation 项需在 PR description 的「待人工验证」清单中承接，不应触发 /analyze-task。
 ```
 
 ### 场景 B：通过但有问题
@@ -51,8 +51,8 @@
   - Gemini CLI：/agent-infra:plan-task {task-ref}
   - Codex CLI：$plan-task {task-ref}
 
-[当 env-blocked > 0 时，在最后附加一行：]
-提醒：env-blocked 项需在 PR description 的「待人工验证」清单中承接，不应触发 /analyze-task。
+[当 manual-validation > 0 时，在最后附加一行：]
+提醒：manual-validation 项需在 PR description 的「待人工验证」清单中承接，不应触发 /analyze-task。
 ```
 
 ### 场景 C：需要修改
@@ -67,8 +67,8 @@
   - Gemini CLI：/agent-infra:analyze-task {task-ref}
   - Codex CLI：$analyze-task {task-ref}
 
-[当 env-blocked > 0 时，在最后附加一行：]
-提醒：env-blocked 项需在 PR description 的「待人工验证」清单中承接，不应触发 /analyze-task。
+[当 manual-validation > 0 时，在最后附加一行：]
+提醒：manual-validation 项需在 PR description 的「待人工验证」清单中承接，不应触发 /analyze-task。
 ```
 
 ### 场景 D：拒绝
@@ -83,6 +83,6 @@
   - Gemini CLI：/agent-infra:analyze-task {task-ref}
   - Codex CLI：$analyze-task {task-ref}
 
-[当 env-blocked > 0 时，在最后附加一行：]
-提醒：env-blocked 项需在 PR description 的「待人工验证」清单中承接，不应触发 /analyze-task。
+[当 manual-validation > 0 时，在最后附加一行：]
+提醒：manual-validation 项需在 PR description 的「待人工验证」清单中承接，不应触发 /analyze-task。
 ```

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

@@ -22,7 +22,7 @@ Use this template when writing `review-analysis.md` or `review-analysis-r{N}.md`
 - **Review Time**: {timestamp}
 - **Scope**: {file-count and major modules}
 - **Overall Verdict**: {Approved / Changes Requested / Rejected}
-- **Findings (AI-actionable)**: 0 blockers, 0 majors, 0 minors / **env-blocked**: 0
+- **Findings (AI-actionable)**: 0 blockers, 0 majors, 0 minors / **Manual validation**: 0
 
 ## Findings
 
@@ -46,17 +46,17 @@ Use this template when writing `review-analysis.md` or `review-analysis-r{N}.md`
 **File**: `{file-path}:{line-number}`
 **Suggestion**: {improvement suggestion}
 
-## Environment-Blocked Findings
+## Manual Validation Items
 
 > Items the AI agent cannot close in the current execution environment; they do not participate in the next analysis round. Maintainers carry them in the PR description as a "manual verification required" checklist.
 
-#### 1. {environment-blocked finding title}
+#### 1. {manual validation item title}
 **File**: `{file-path}:{line-number}` (if applicable)
 **Description**: {details}
 **Required Environment**: {e.g. Docker sandbox / macOS host / privileged root / third-party account}
 **Manual Verification Steps**: {steps for the human verifier}
 
-> If this round has no env-blocked findings, keep the section heading and write "None".
+> If this round has no Manual validation items, keep the section heading and write "None".
 
 
 ## Review Disagreement Ledger Writeback

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

@@ -22,7 +22,7 @@
 - **审查时间**：{timestamp}
 - **审查范围**：{file-count and major modules}
 - **总体结论**：{通过 / 需要修改 / 拒绝}
-- **发现（AI 可处理）**：0 阻塞项，0 主要，0 次要 / **env-blocked**：0
+- **发现（AI 可处理）**：0 阻塞项，0 主要，0 次要 / **人工校验**：0
 
 ## 问题清单
 
@@ -46,17 +46,17 @@
 **文件**：`{file-path}:{line-number}`
 **建议**：{improvement suggestion}
 
-## 环境性遗留
+## 人工校验项
 
 > AI agent 在本执行环境无法闭环的项；不参与下一轮 refine。维护者在 PR description 中以「待人工验证」清单承接。
 
-#### 1. {环境性项标题}
+#### 1. {人工校验项标题}
 **文件**：`{file-path}:{line-number}`（如适用）
 **说明**：{details}
 **所需环境**：{e.g. Docker 沙箱 / macOS host / 特权 root / 第三方账号}
 **待人工执行的验证步骤**：{steps for the human verifier}
 
-> 如本轮无 env-blocked 项，保留段落标题并写「（无）」。
+> 如本轮无人工校验项，保留段落标题并写「（无）」。
 
 
 ## 审查分歧账本回写

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

@@ -29,7 +29,7 @@ Follow the `analysis-review` step in `.agents/workflows/feature-development.yaml
 3. **Actionable**: suggest a concrete fix
 4. **Severity-based**: clearly distinguish blockers, major issues, and minor issues
 
-## Environment-Blocked Classification
+## Manual Validation Classification
 
 Some findings cannot be closed by an AI agent in the current execution environment, for example:
 
@@ -40,11 +40,11 @@ Some findings cannot be closed by an AI agent in the current execution environme
 
 **Decision tree**: "Can the AI agent close this item independently without changing the environment?"
 - Yes -> blocker / major / minor, based on risk
-- No -> **env-blocked** (a meta-category, not part of severity ordering)
+- No -> **manual-validation** (a manual-validation meta-category, not part of severity ordering)
 
-Where env-blocked items go:
-- Record them in an independent review report section named "Environment-Blocked Findings"
-- Include them at the end of the numeric summary, for example `(+ 1 env-blocked)`
+Where manual-validation items go:
+- Record them in an independent review report section named "Manual Validation Items"
+- Record the done-note source field as `Manual-validation: 1`; `ai task log` normalizes it into review rows
 - Do **not** include them in the code-task fix loop; maintainers carry them in the PR description under manual verification
 
 Also inspect the latest requirement analysis artifact and `task.md` Activity Log so the report reflects the full analysis context.

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

@@ -29,7 +29,7 @@
 3. **可执行**：给出明确可落地的修复建议
 4. **按严重程度分类**：明确区分 blocker、major 和 minor
 
-## 环境性遗留分类
+## 人工校验项分类
 
 某些发现项是 AI agent 在本执行环境**无法闭环**的，例如：
 
@@ -40,11 +40,11 @@
 
 **分类决策树**：「AI agent 能否在不改环境的前提下独立闭环这一项？」
 - 是 -> blocker / major / minor 之一（按风险定档）
-- 否 -> **env-blocked**（元类目，不参与严重程度排序）
+- 否 -> **manual-validation**（人工校验元类目，不参与严重程度排序）
 
-env-blocked 项的去向：
-- 写入 review 报告独立段落「环境性遗留」
-- 在数字摘要末尾附带显示（如 `(+ 1 env-blocked)`）
+manual-validation 项的去向：
+- 写入 review 报告独立段落「人工校验项」
+- 在 done note 中写入源字段 `Manual-validation: 1`；`ai task log` 归一化展示到 review 行
 - **不**进入 code-task 修复循环；维护者在 PR description 中以「待人工验证」清单形式承接
 
 同时检查最新需求分析产物和 `task.md` Activity Log，确保报告反映完整的分析上下文。

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

@@ -96,10 +96,10 @@ date "+%Y-%m-%d %H:%M:%S%:z"
 ```
 
 Update task.md and append:
-`- {YYYY-MM-DD HH:mm:ss±HH:MM} — **Review Code (Round {N})** by {agent} — Verdict: {Approved/Changes Requested/Rejected}, blockers: {n}, major: {n}, minor: {n}[ (+ {n} env-blocked)] → {artifact-filename}`
+`- {YYYY-MM-DD HH:mm:ss±HH:MM} — **Review Code (Round {N})** by {agent} — Verdict: {Approved/Changes Requested/Rejected}, blockers: {n}, major: {n}, minor: {n}, Manual-validation: {n} → {artifact-filename}`
 
-Omit the bracketed segment when env-blocked = 0; append ` (+ {n} env-blocked)` when env-blocked > 0.
-`env-blocked` is the data source for the `Manual-verify` count folded into review rows in `ai task log`; do not add a parallel manual-verification field.
+Always include the `Manual-validation: {n}` field in the done log, including when it is 0.
+`manual-validation` is the data source for the `Manual-validation` count folded into review rows in `ai task log`; do not add a parallel manual-verification field.
 
 If task.md contains a valid `issue_number`, perform these sync actions (skip and continue on any failure):
 - Read `.agents/rules/issue-sync.md` before syncing, and complete upstream repository detection plus permission detection
@@ -134,7 +134,7 @@ Choose exactly one branch based on the findings:
 - blockers that can be fixed in a focused pass -> changes requested
 - major redesign or re-implementation needed -> rejected
 
-env-blocked counts do not influence branch selection; they are appended to the summary line only.
+manual-validation counts do not influence branch selection; they are displayed only as manual validation counts.
 
 > The full four-branch output templates, selection rules, and prohibition clauses live in `reference/output-templates.md`. Read `reference/output-templates.md` before reporting the review result.
 

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

@@ -99,10 +99,10 @@ date "+%Y-%m-%d %H:%M:%S%:z"
 - `updated_at`：{当前时间}
 - `agent_infra_version`：按 `.agents/rules/version-stamp.md` 取值
 - 追加：
-`- {YYYY-MM-DD HH:mm:ss±HH:MM} — **Review Code (Round {N})** by {agent} — Verdict: {Approved/Changes Requested/Rejected}, blockers: {n}, major: {n}, minor: {n}[ (+ {n} env-blocked)] → {artifact-filename}`
+`- {YYYY-MM-DD HH:mm:ss±HH:MM} — **Review Code (Round {N})** by {agent} — Verdict: {Approved/Changes Requested/Rejected}, blockers: {n}, major: {n}, minor: {n}, Manual-validation: {n} → {artifact-filename}`
 
-env-blocked = 0 时省略括号部分；env-blocked > 0 时附加 ` (+ {n} env-blocked)`。
-`env-blocked` 是 `ai task log` 中 review 行「人工校验点」（EN `Manual-verify`）计数的数据源；不要新增并行人工验证字段。
+完成日志必须始终写入 `Manual-validation: {n}` 字段，0 也保留。
+`manual-validation` 是 `ai task log` 中 review 行「人工校验点」（EN `Manual-validation`）计数的数据源；不要新增并行人工验证字段。
 
 如果 task.md 中存在有效的 `issue_number`，执行以下同步操作（任一失败则跳过并继续）：
 - 执行前先读取 `.agents/rules/issue-sync.md`，完成 upstream 仓库检测和权限检测
@@ -137,7 +137,7 @@ node .agents/scripts/validate-artifact.js gate review-code .agents/workspace/act
 - 有 blocker，且可集中修复 -> 需要修改
 - 需要重大返工或重新实现 -> 拒绝
 
-env-blocked 的数量不参与分支选择，仅在数字摘要末尾附带显示。
+manual-validation 的数量不参与分支选择，只作为人工校验计数显示。
 
 > 完整的 4 分支输出模板、判断规则和禁止条款见 `reference/output-templates.md`。向用户汇报审查结论前先读取 `reference/output-templates.md`。
 

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

@@ -20,7 +20,7 @@
       "required_sections": [
         "Review Summary",
         "Findings",
-        "Environment-Blocked Findings",
+        "Manual Validation Items",
         "Conclusion and Recommendations",
         "State Check",
         "Evidence",

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

@@ -20,7 +20,7 @@
       "required_sections": [
         "审查摘要",
         "问题清单",
-        "环境性遗留",
+        "人工校验项",
         "结论与建议",
         "状态核对",
         "证据原文",

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

@@ -6,8 +6,8 @@ Read this file before presenting the final review result to the user.
 
 ## Choose Exactly One Output Branch
 
-Apply these rules in order (**note: env-blocked counts do not participate in selection**):
-1. if `Blocker = 0` and `Major = 0` and `Minor = 0`, use Branch A (regardless of whether env-blocked > 0)
+Apply these rules in order (**note: manual-validation counts do not participate in selection**):
+1. if `Blocker = 0` and `Major = 0` and `Minor = 0`, use Branch A (regardless of whether manual-validation > 0)
 2. if `Blocker = 0` and (`Major > 0` or `Minor > 0`), use Branch B
 3. if `Blocker > 0` and the work can be repaired in a focused refinement pass, use Branch C
 4. if the task requires major redesign, broad reimplementation, or a restart, use Branch D
@@ -16,15 +16,15 @@ Prohibitions:
 - never skip the branch-selection step
 - never mix text from different branches
 - 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
+- never count manual-validation 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. When `{h} > 0`, before the selected scenario's "Next steps" commands you must expand each pending ruling per the "Pending human-decision pre-block" in `.agents/rules/next-step-output.md` and prompt to resolve them first
+- 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-validation` (`{e}`) = this round's manual-validation count, `Human-decision` (`{h}`) = the number of rows in task.md `## 审查分歧账本` with `stage=code` and `status=needs-human-decision`; neither participates in branch selection. When `{h} > 0`, before the selected scenario's "Next steps" commands you must expand each pending ruling per the "Pending human-decision pre-block" in `.agents/rules/next-step-output.md` and prompt to resolve them first
 
 ### Branch A: Approved with No Findings
 
 ```text
 Task {task-id} review completed. Verdict: approved.
-- Blockers: 0 | Major: 0 | Minor: 0 | Manual-verify: {e} | Human-decision: {h}
+- Blockers: 0 | Major: 0 | Minor: 0 | Manual-validation: {e} | Human-decision: {h}
 [- Review report: .agents/workspace/active/{task-id}/{review-artifact}]
 
 Next step - commit the code:
@@ -32,15 +32,15 @@ Next step - commit the code:
   - Gemini CLI: /agent-infra:commit
   - Codex CLI: $commit
 
-[When env-blocked > 0, append this final line:]
-Reminder: env-blocked findings must be carried in the PR description as a "manual verification required" checklist and should not trigger /code-task.
+[When manual-validation > 0, append this final line:]
+Reminder: manual-validation findings must be carried in the PR description as a "manual verification required" checklist and should not trigger /code-task.
 ```
 
 ### Branch B: Approved with Findings
 
 ```text
 Task {task-id} review completed. Verdict: approved.
-- Blockers: 0 | Major: {n} | Minor: {n} | Manual-verify: {e} | Human-decision: {h}
+- Blockers: 0 | Major: {n} | Minor: {n} | Manual-validation: {e} | Human-decision: {h}
 - Review report: .agents/workspace/active/{task-id}/{review-artifact}
 
 Next step - fix before commit (recommended):
@@ -53,15 +53,15 @@ Or commit directly (skip fix):
   - Gemini CLI: /agent-infra:commit
   - Codex CLI: $commit
 
-[When env-blocked > 0, append this final line:]
-Reminder: env-blocked findings must be carried in the PR description as a "manual verification required" checklist and should not trigger /code-task.
+[When manual-validation > 0, append this final line:]
+Reminder: manual-validation findings must be carried in the PR description as a "manual verification required" checklist and should not trigger /code-task.
 ```
 
 ### Branch C: Changes Requested
 
 ```text
 Task {task-id} review completed. Verdict: changes requested.
-- Blockers: {n} | Major: {n} | Minor: {n} | Manual-verify: {e} | Human-decision: {h}
+- Blockers: {n} | Major: {n} | Minor: {n} | Manual-validation: {e} | Human-decision: {h}
 - Review report: .agents/workspace/active/{task-id}/{review-artifact}
 
 Next step - fix the findings:
@@ -69,15 +69,15 @@ Next step - fix the findings:
   - Gemini CLI: /agent-infra:code-task {task-ref}
   - Codex CLI: $code-task {task-ref}
 
-[When env-blocked > 0, append this final line:]
-Reminder: env-blocked findings must be carried in the PR description as a "manual verification required" checklist and should not trigger /code-task.
+[When manual-validation > 0, append this final line:]
+Reminder: manual-validation findings must be carried in the PR description as a "manual verification required" checklist and should not trigger /code-task.
 ```
 
 ### Branch D: Rejected
 
 ```text
 Task {task-id} review completed. Verdict: rejected, re-design the technical plan.
-- Blockers: {n} | Major: {n} | Minor: {n} | Manual-verify: {e} | Human-decision: {h}
+- Blockers: {n} | Major: {n} | Minor: {n} | Manual-validation: {e} | Human-decision: {h}
 - Review report: .agents/workspace/active/{task-id}/{review-artifact}
 
 Next step - re-design the technical plan:
@@ -87,6 +87,6 @@ Next step - re-design the technical plan:
 
 > Note: Rejected means the implementation direction needs to be reworked end-to-end, not patched locally. `code-task/scripts/detect-mode.js` branch #7 refuses a direct `/code-task` and requires a fresh plan first.
 
-[When env-blocked > 0, append this final line:]
-Reminder: env-blocked findings must be carried in the PR description as a "manual verification required" checklist and should not trigger /code-task.
+[When manual-validation > 0, append this final line:]
+Reminder: manual-validation findings must be carried in the PR description as a "manual verification required" checklist and should not trigger /code-task.
 ```

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

@@ -6,8 +6,8 @@
 
 ## 选择唯一输出场景
 
-按以下顺序判断（**注意：env-blocked 数量不参与判断**）：
-1. 如果 `Blocker = 0` 且 `Major = 0` 且 `Minor = 0`，使用场景 A（不管 env-blocked 是否 > 0）
+按以下顺序判断（**注意：manual-validation 数量不参与判断**）：
+1. 如果 `Blocker = 0` 且 `Major = 0` 且 `Minor = 0`，使用场景 A（不管 manual-validation 是否 > 0）
 2. 如果 `Blocker = 0` 且（`Major > 0` 或 `Minor > 0`），使用场景 B
 3. 如果 `Blocker > 0`，且问题可以通过一次聚焦修复解决，使用场景 C
 4. 如果任务需要重大重构、大范围重写或整体重来，使用场景 D
@@ -16,9 +16,9 @@
 - 不要跳过场景判断步骤
 - 不要混用不同场景的文案
 - 只要 `Blocker > 0`，就绝对不能输出通过模板
-- env-blocked 项绝对不能被计入 blocker / major / minor 计数，也不能用作触发场景 B/C/D 的依据
+- manual-validation 项绝对不能被计入 blocker / major / minor 计数，也不能用作触发场景 B/C/D 的依据
 - 所选场景中必须包含所有 TUI 命令格式
-- 计数行固定显示 5 个数字：前三项（阻塞 / 主要 / 次要）必须为 0 才进下一步；后两项是「待人处理」项、不要求归零——`人工校验点`（`{e}`）= 本轮 env-blocked 计数，`人工裁决`（`{h}`）= task.md `## 审查分歧账本` 中 `stage=code` 且 `status=needs-human-decision` 的行数；二者均不参与场景判断。当 `{h} > 0` 时，必须在选定场景的「下一步」命令之前，按 `.agents/rules/next-step-output.md`「人工裁决待办前置块」逐项展开裁决项并提示先完成裁决
+- 计数行固定显示 5 个数字：前三项（阻塞 / 主要 / 次要）必须为 0 才进下一步；后两项是「待人处理」项、不要求归零——`人工校验点`（`{e}`）= 本轮 manual-validation 计数，`人工裁决`（`{h}`）= task.md `## 审查分歧账本` 中 `stage=code` 且 `status=needs-human-decision` 的行数；二者均不参与场景判断。当 `{h} > 0` 时，必须在选定场景的「下一步」命令之前，按 `.agents/rules/next-step-output.md`「人工裁决待办前置块」逐项展开裁决项并提示先完成裁决
 
 ### 场景 A：通过且无问题
 
@@ -32,8 +32,8 @@
   - Gemini CLI：/agent-infra:commit
   - Codex CLI：$commit
 
-[当 env-blocked > 0 时，在最后附加一行：]
-提醒：env-blocked 项需在 PR description 的「待人工验证」清单中承接，不应触发 /code-task。
+[当 manual-validation > 0 时，在最后附加一行：]
+提醒：manual-validation 项需在 PR description 的「待人工验证」清单中承接，不应触发 /code-task。
 ```
 
 ### 场景 B：通过但有问题
@@ -53,8 +53,8 @@
   - Gemini CLI：/agent-infra:commit
   - Codex CLI：$commit
 
-[当 env-blocked > 0 时，在最后附加一行：]
-提醒：env-blocked 项需在 PR description 的「待人工验证」清单中承接，不应触发 /code-task。
+[当 manual-validation > 0 时，在最后附加一行：]
+提醒：manual-validation 项需在 PR description 的「待人工验证」清单中承接，不应触发 /code-task。
 ```
 
 ### 场景 C：需要修改
@@ -69,8 +69,8 @@
   - Gemini CLI：/agent-infra:code-task {task-ref}
   - Codex CLI：$code-task {task-ref}
 
-[当 env-blocked > 0 时，在最后附加一行：]
-提醒：env-blocked 项需在 PR description 的「待人工验证」清单中承接，不应触发 /code-task。
+[当 manual-validation > 0 时，在最后附加一行：]
+提醒：manual-validation 项需在 PR description 的「待人工验证」清单中承接，不应触发 /code-task。
 ```
 
 ### 场景 D：拒绝
@@ -87,6 +87,6 @@
 
 > 注意：Rejected 表示实现方向需要整体重做，不是局部修复。`code-task/scripts/detect-mode.js` 分支 #7 会拒绝直接 `/code-task`，要求先重新方案设计。
 
-[当 env-blocked > 0 时，在最后附加一行：]
-提醒：env-blocked 项需在 PR description 的「待人工验证」清单中承接，不应触发 /code-task。
+[当 manual-validation > 0 时，在最后附加一行：]
+提醒：manual-validation 项需在 PR description 的「待人工验证」清单中承接，不应触发 /code-task。
 ```

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

@@ -24,7 +24,7 @@ Use this template when writing `review-code.md` or `review-code-r{N}.md`.
 - **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
+- **Findings (AI-actionable)**: 0 blockers, 0 majors, 0 minors / **Manual validation**: 0
 
 ## Findings
 
@@ -48,17 +48,17 @@ Use this template when writing `review-code.md` or `review-code-r{N}.md`.
 **File**: `{file-path}:{line-number}`
 **Suggestion**: {improvement suggestion}
 
-## Environment-Blocked Findings
+## Manual Validation Items
 
 > Items the AI agent cannot close in the current execution environment; they do not participate in the next code round. Maintainers carry them in the PR description as a "manual verification required" checklist.
 
-#### 1. {environment-blocked finding title}
+#### 1. {manual validation item title}
 **File**: `{file-path}:{line-number}` (if applicable)
 **Description**: {details}
 **Required Environment**: {e.g. Docker sandbox / macOS host / privileged root / third-party account}
 **Manual Verification Steps**: {steps for the human verifier}
 
-> If this round has no env-blocked findings, keep the section heading and write "None".
+> If this round has no Manual validation items, keep the section heading and write "None".
 
 
 ## Review Disagreement Ledger Writeback

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

@@ -24,7 +24,7 @@
 - **审查基线提交**：{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
+- **发现（AI 可处理）**：0 阻塞项，0 主要，0 次要 / **人工校验**：0
 
 ## 问题清单
 
@@ -48,17 +48,17 @@
 **文件**：`{file-path}:{line-number}`
 **建议**：{improvement suggestion}
 
-## 环境性遗留
+## 人工校验项
 
 > AI agent 在本执行环境无法闭环的项；不参与下一轮 refine。维护者在 PR description 中以「待人工验证」清单承接。
 
-#### 1. {环境性项标题}
+#### 1. {人工校验项标题}
 **文件**：`{file-path}:{line-number}`（如适用）
 **说明**：{details}
 **所需环境**：{e.g. Docker 沙箱 / macOS host / 特权 root / 第三方账号}
 **待人工执行的验证步骤**：{steps for the human verifier}
 
-> 如本轮无 env-blocked 项，保留段落标题并写「（无）」。
+> 如本轮无人工校验项，保留段落标题并写「（无）」。
 
 
 ## 审查分歧账本回写