@fitlab-ai/agent-infra 0.6.0 → 0.6.1

package/templates/.agents/skills/import-issue/SKILL.en.md

@@ -69,11 +69,18 @@ workflow: feature-development|bug-fix|refactoring
 status: active
 created_at: {YYYY-MM-DD HH:mm:ss±HH:MM}
 updated_at: {YYYY-MM-DD HH:mm:ss±HH:MM}
+agent_infra_version: {agent_infra_version}
 created_by: human
+priority:                  # optional; preserve source/frontmatter value when available
+effort:                    # optional; preserve source/frontmatter value when available
+start_date:                # optional; preserve explicit YYYY-MM-DD when available
+target_date:               # optional; preserve explicit YYYY-MM-DD when available
 current_step: requirement-analysis
 assigned_to: {current AI agent}
 ```
 
+Optional Issue field metadata should preserve recovered or explicit source values. If absent, leave it empty; do not invent dates.
+
 3.3 Append Activity Log entries.
 
 - Scenario B: append `Import Issue`
@@ -91,6 +98,7 @@ Update `.agents/workspace/active/{task-id}/task.md`:
 - `current_step`: requirement-analysis
 - `assigned_to`: {current AI agent}
 - `updated_at`: {current time}
+- `agent_infra_version`: value from `.agents/rules/version-stamp.md`
 - `## Context` -> `- **Branch**:`: update it to the generated branch name
 - **Append** to `## Activity Log` (do NOT overwrite previous entries):
   ```
@@ -162,6 +170,8 @@ Next step - run requirements analysis:
 
 After completing the checklist, **stop immediately**. Do not continue to later steps.
 
+Version stamp rule: when creating or updating `task.md` frontmatter, read `.agents/rules/version-stamp.md` first and write or refresh `agent_infra_version`.
+
 ## Notes
 
 1. **Issue validation**: verify that the Issue exists before continuing

package/templates/.agents/skills/import-issue/SKILL.zh-CN.md

@@ -69,11 +69,18 @@ workflow: feature-development|bug-fix|refactoring
 status: active
 created_at: {YYYY-MM-DD HH:mm:ss±HH:MM}
 updated_at: {YYYY-MM-DD HH:mm:ss±HH:MM}
+agent_infra_version: {agent_infra_version}
 created_by: human
+priority:                  # 可选；有来源/frontmatter 值时保留
+effort:                    # 可选；有来源/frontmatter 值时保留
+start_date:                # 可选；有明确 YYYY-MM-DD 时保留
+target_date:               # 可选；有明确 YYYY-MM-DD 时保留
 current_step: requirement-analysis
 assigned_to: {当前 AI 代理}
 ```
 
+可选 Issue 字段元数据应保留恢复得到或来源中明确给出的值。缺失时留空；不要臆测日期。
+
 3.3 追加 Activity Log。
 
 - 场景 B：追加 `Import Issue`
@@ -91,6 +98,7 @@ date "+%Y-%m-%d %H:%M:%S%:z"
 - `current_step`：requirement-analysis
 - `assigned_to`：{当前 AI 代理}
 - `updated_at`：{当前时间}
+- `agent_infra_version`：按 `.agents/rules/version-stamp.md` 取值
 - `## 上下文` 中的 `- **分支**：`：更新为生成的分支名
 - **追加**到 `## Activity Log`（不要覆盖之前的记录）：
   ```
@@ -162,6 +170,8 @@ Issue #{number} 已导入。
 
 完成检查清单后，**立即停止**。不要继续执行后续步骤。
 
+版本戳规则：创建或更新 `task.md` frontmatter 时，先读取 `.agents/rules/version-stamp.md`，并写入或刷新 `agent_infra_version`。
+
 ## 注意事项
 
 1. **Issue 验证**：在继续之前检查 Issue 是否存在

package/templates/.agents/skills/import-issue/config/verify.json

@@ -10,6 +10,7 @@
         "status",
         "created_at",
         "updated_at",
+        "agent_infra_version",
         "current_step",
         "assigned_to"
       ],

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

@@ -11,6 +11,8 @@ description: "Design a technical plan for a task"
 - This is a **mandatory human review checkpoint**; do not automatically proceed to implementation
 - After executing this skill, you **must** immediately update task status in task.md
 
+Version stamp rule: when creating or updating `task.md` frontmatter, read `.agents/rules/version-stamp.md` first and write or refresh `agent_infra_version`.
+
 ## Steps
 
 ### 1. Verify Prerequisites
@@ -88,6 +90,7 @@ Update `.agents/workspace/active/{task-id}/task.md`:
 - `current_step`: technical-design
 - `assigned_to`: {current AI agent}
 - `updated_at`: {current time}
+- `agent_infra_version`: value from `.agents/rules/version-stamp.md`
 - 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

@@ -11,6 +11,8 @@ description: "为任务设计技术方案和实施计划"
 - 这是一个**强制性的人工审查检查点** —— 不要自动进入实现阶段
 - 执行本技能后，你**必须**立即更新 task.md 中的任务状态
 
+版本戳规则：创建或更新 `task.md` frontmatter 时，先读取 `.agents/rules/version-stamp.md`，并写入或刷新 `agent_infra_version`。
+
 ## 执行步骤
 
 ### 1. 验证前置条件
@@ -88,6 +90,7 @@ date "+%Y-%m-%d %H:%M:%S%:z"
 - `current_step`：technical-design
 - `assigned_to`：{当前 AI 代理}
 - `updated_at`：{当前时间}
+- `agent_infra_version`：按 `.agents/rules/version-stamp.md` 取值
 - 记录本轮方案产物：`{plan-artifact}`（Round `{plan-round}`）
 - 如任务模板包含 `## 设计` 段落，更新为指向 `{plan-artifact}` 的链接
 - 在工作流进度中标记 technical-design 为已完成，并注明实际轮次（如果任务模板支持）

package/templates/.agents/skills/plan-task/config/verify.json

@@ -9,6 +9,7 @@
         "status",
         "created_at",
         "updated_at",
+        "agent_infra_version",
         "current_step",
         "assigned_to"
       ],
@@ -38,6 +39,7 @@
       "verify_comment_content": true,
       "verify_task_comment_content": true,
       "verify_issue_type": true,
+      "verify_issue_fields": false,
       "verify_milestone": true,
       "expected_status_label_key": "pendingDesignWork",
       "expected_comment_marker_key": "artifact"

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

@@ -10,9 +10,20 @@ Fix review findings and produce `refinement.md` or `refinement-r{N}.md`.
 ## Boundary / Critical Rules
 
 - Fix only the issues documented in review artifacts
+- env-blocked findings are outside the repair scope: the refinement report must preserve them and record "outside AI repair scope (environment-blocked)" instead of making no-op edits to clear the report
 - Never auto-run `git add` or `git commit`
 - After executing this skill, you **must** immediately update task.md
 
+Version stamp rule: when creating or updating `task.md` frontmatter, read `.agents/rules/version-stamp.md` first and write or refresh `agent_infra_version`.
+
+## Common Rationalizations and Rebuttals
+
+| Rationalization | Rebuttal |
+|------|------|
+| "This review comment is wrong, so I will ignore it." | If you disagree, record the reason under unresolved issues in the report; do not silently skip blocker or major findings. |
+| "I can clean up nearby code while I am here." | Scope is limited to review findings; changes outside that scope are out of bounds. |
+| "Clearing env-blocked items makes the report look better." | env-blocked findings are outside the repair scope; preserve and label them truthfully, and never use no-op edits to pad the fix count. |
+
 ## Steps
 
 ### 1. Verify Prerequisites
@@ -56,8 +67,11 @@ date "+%Y-%m-%d %H:%M:%S%:z"
 
 Update task.md:
 - review the `## Requirements` section and only change items from `- [ ]` to `- [x]` when they are newly satisfied by this round's fixes and passing tests
+- preserve explicit optional Issue field metadata (`priority`, `effort`, `start_date`, `target_date`); only infer `priority` or `effort` from clear review context, and do not invent dates
 - append:
-  `- {YYYY-MM-DD HH:mm:ss±HH:MM} — **Refinement (Round {N}, for {review-artifact})** by {agent} — Fixed {n} blockers, {n} major, {n} minor issues → {refinement-artifact}`
+  `- {YYYY-MM-DD HH:mm:ss±HH:MM} — **Refinement (Round {N}, for {review-artifact})** by {agent} — Fixed {n} blockers, {n} major, {n} minor issues[, skipped {n} env-blocked] → {refinement-artifact}`
+
+Append `, skipped {n} env-blocked` when env-blocked > 0; omit it when env-blocked = 0.
 
 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

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

@@ -10,9 +10,20 @@ description: "处理代码审查反馈并修复问题"
 ## 行为边界 / 关键规则
 
 - 只修复审查产物中记录的问题
+- env-blocked 项不在修复范围内：refinement 报告必须如实保留这些项并记录“不在 AI 修复范围（环境性遗留）”，不能为了清空报告做 no-op 改动
 - 绝不自动执行 `git add` 或 `git commit`
 - 执行本技能后，你**必须**立即更新 task.md
 
+版本戳规则：创建或更新 `task.md` frontmatter 时，先读取 `.agents/rules/version-stamp.md`，并写入或刷新 `agent_infra_version`。
+
+## 常见违规借口与反驳
+
+| 借口 | 反驳 |
+|------|------|
+| 「这条审查意见不合理，直接忽略」 | 不同意要在报告的未解决问题中写明理由，不能静默跳过 blocker/major。 |
+| 「顺手把旁边也优化了」 | 范围严格限定在审查项内，范围外改动属于越界。 |
+| 「env-blocked 项清掉报告好看」 | env-blocked 不在修复范围，必须如实保留并标注，禁止 no-op 改动充数。 |
+
 ## 执行步骤
 
 ### 1. 验证前置条件
@@ -56,8 +67,11 @@ date "+%Y-%m-%d %H:%M:%S%:z"
 
 更新 task.md：
 - 审查 `## 需求` 段落，仅把因本轮修复而新满足且有测试通过支撑的条目从 `- [ ]` 勾为 `- [x]`
+- 保留明确填写的可选 Issue 字段元数据（`priority`、`effort`、`start_date`、`target_date`）；仅在审查上下文非常明确时推断 `priority` 或 `effort`，不要臆测日期
 - 追加：
-  `- {YYYY-MM-DD HH:mm:ss±HH:MM} — **Refinement (Round {N}, for {review-artifact})** by {agent} — Fixed {n} blockers, {n} major, {n} minor issues → {refinement-artifact}`
+  `- {YYYY-MM-DD HH:mm:ss±HH:MM} — **Refinement (Round {N}, for {review-artifact})** by {agent} — Fixed {n} blockers, {n} major, {n} minor issues[, skipped {n} env-blocked] → {refinement-artifact}`
+
+env-blocked > 0 时附加 `, skipped {n} env-blocked`；env-blocked = 0 时省略。
 
 如果 task.md 中存在有效的 `issue_number`，执行以下同步操作（任一失败则跳过并继续）：
 - 执行前先读取 `.agents/rules/issue-sync.md`，完成 upstream 仓库检测和权限检测

package/templates/.agents/skills/refine-task/config/verify.json

@@ -9,6 +9,7 @@
         "status",
         "created_at",
         "updated_at",
+        "agent_infra_version",
         "current_step",
         "assigned_to"
       ]
@@ -32,6 +33,7 @@
       "verify_comment_content": true,
       "verify_task_comment_content": true,
       "verify_issue_type": true,
+      "verify_issue_fields": false,
       "verify_milestone": true,
       "expected_status_label_key": "inProgress",
       "expected_comment_marker_key": "artifact"

package/templates/.agents/skills/refine-task/reference/fix-workflow.en.md

@@ -20,6 +20,14 @@ Detailed priority rules:
 - Minor issues are optional only after Blockers and Majors are resolved
 - If you disagree with a finding, record that disagreement under unresolved issues instead of silently skipping it
 
+### Meta-category: env-blocked
+
+env-blocked findings are outside the repair scope. Handling rules:
+- do not write code changes for these findings
+- list them unchanged in the refinement report's "Environment-Blocked Handling" section and mark them "outside AI repair scope"
+- do not repeat them under unresolved issues, to avoid visually double-counting them
+- their destination is the PR description, where maintainers carry them as a "manual verification required" checklist
+
 ## Execute the Fixes
 
 For each fix:
@@ -51,6 +59,7 @@ Refinement status:
 - Blockers fixed: {fixed-blockers}/{total-blockers}
 - Major issues fixed: {fixed-majors}/{total-majors}
 - Minor issues fixed: {fixed-minors}/{total-minors}
+- [If env-blocked > 0] env-blocked skipped: {count}
 - All tests passing: {yes/no}
 - Review input: {review-artifact}
 - Refinement artifact: {refinement-artifact}

package/templates/.agents/skills/refine-task/reference/fix-workflow.zh-CN.md

@@ -20,6 +20,14 @@
 - 只有在 Blocker 和 Major 都解决后，Minor 才是可选项
 - 如果你不同意某条审查意见，不要静默跳过，而是把分歧记录到 unresolved issues
 
+### 元类目：env-blocked
+
+env-blocked 项不在修复范围。处理规则：
+- 不要为这些项编写代码改动
+- 在 refinement 报告的「环境性遗留处理」段落原样列出，标注「不在 AI 修复范围」
+- 不要在 unresolved 段落里重复列出（避免视觉计数翻倍）
+- 这些项的去向：维护者在 PR description 中以「待人工验证」清单承接
+
 ## 执行修复
 
 对每一项修复：
@@ -51,6 +59,7 @@
 - 阻塞项修复：{数量}/{总数}
 - 主要问题修复：{数量}/{总数}
 - 次要问题修复：{数量}/{总数}
+- [如 env-blocked > 0] 环境性遗留跳过：{数量}
 - 所有测试通过：{是/否}
 - 审查输入：{review-artifact}
 - 修复产物：{refinement-artifact}

package/templates/.agents/skills/refine-task/reference/report-template.en.md

@@ -29,6 +29,17 @@ Use this structure when writing `refinement.md` or `refinement-r{N}.md`.
 1. **{issue-title}**
    - **Fix**: {what changed}
 
+#### Environment-Blocked Handling
+
+> These findings are outside AI repair scope and do not count toward repair totals. Preserve them unchanged and identify the maintainer verification path.
+
+1. **{issue-title}**
+   - **Status**: skipped (outside AI repair scope)
+   - **Required Environment**: {e.g. Docker sandbox / macOS host / third-party account}
+   - **Maintainer Verification Steps**: {steps}
+
+> If this round has no env-blocked findings, keep the subsection heading and write "None".
+
 #### Unresolved Issues
 - {issue}: {reason}
 

package/templates/.agents/skills/refine-task/reference/report-template.zh-CN.md

@@ -29,6 +29,17 @@
 1. **{issue-title}**
    - **修复**: {what changed}
 
+#### 环境性遗留处理
+
+> 这些项不在 AI 修复范围；不计入修复总数。仅原样保留并指明维护者后续验证路径。
+
+1. **{issue-title}**
+   - **状态**：跳过（不在 AI 修复范围）
+   - **所需环境**：{e.g. Docker 沙箱 / macOS host / 第三方账号}
+   - **维护者验证步骤**：{steps}
+
+> 如本轮无 env-blocked 项，保留小节标题并写「（无）」。
+
 #### 未解决问题
 - {issue}: {reason}
 

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

@@ -14,6 +14,8 @@ Restore local task workspace files from platform Issue comments that contain syn
 - Stop immediately if the target directory already exists and ask the user to resolve the conflict first
 - After executing this skill, you **must** immediately update the restored `task.md`
 
+Version stamp rule: when creating or updating `task.md` frontmatter, read `.agents/rules/version-stamp.md` first and write or refresh `agent_infra_version`.
+
 ## Steps
 
 ### 1. Verify Input and Environment
@@ -83,6 +85,7 @@ Update the restored `task.md`:
 - `status`: `active`
 - `assigned_to`: {current AI agent}
 - `updated_at`: {current time}
+- `agent_infra_version`: value from `.agents/rules/version-stamp.md`
 
 Append an Activity Log entry indicating the task was restored from the platform Issue.
 

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

@@ -14,6 +14,8 @@ description: "从平台 Issue 评论还原本地任务文件"
 - 如果目标目录已存在，立即停止并提示用户先处理目录冲突
 - 执行本技能后，你**必须**立即更新恢复出的 `task.md`
 
+版本戳规则：创建或更新 `task.md` frontmatter 时，先读取 `.agents/rules/version-stamp.md`，并写入或刷新 `agent_infra_version`。
+
 ## 执行步骤
 
 ### 1. 验证输入与环境
@@ -83,6 +85,7 @@ date "+%Y-%m-%d %H:%M:%S%:z"
 - `status`：`active`
 - `assigned_to`：{当前 AI 代理}
 - `updated_at`：{当前时间}
+- `agent_infra_version`：按 `.agents/rules/version-stamp.md` 取值
 
 追加 Activity Log，说明任务已从平台 Issue 还原。
 

package/templates/.agents/skills/restore-task/config/verify.json

@@ -9,6 +9,7 @@
         "status",
         "created_at",
         "updated_at",
+        "agent_infra_version",
         "current_step",
         "assigned_to"
       ],

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

@@ -12,6 +12,16 @@ Review the latest implementation round and produce `review.md` or `review-r{N}.m
 - This skill reviews code and writes a report; it does not modify product code
 - After executing this skill, you **must** immediately update task.md
 
+Version stamp rule: when creating or updating `task.md` frontmatter, read `.agents/rules/version-stamp.md` first and write or refresh `agent_infra_version`.
+
+## Common Rationalizations and Rebuttals
+
+| Rationalization | Rebuttal |
+|------|------|
+| "It was only one line, so it cannot affect behavior." | Line count is not impact; read the full `git diff` and trace the downstream effect of each change. |
+| "It looks mostly fine, so approve it." | The verdict must be backed by blocker/major/minor counts, and every finding must cite file:line; do not approve from impression. |
+| "The test change looks reasonable, so I can skim it." | Before reviewing test changes, check `.agents/rules/testing-discipline.md` item by item (see the step 4 gate). |
+
 ## Steps
 
 ### 1. Verify Prerequisites
@@ -35,6 +45,7 @@ Read the highest-round implementation artifact and, if present, the highest-roun
 Follow `.agents/workflows/feature-development.yaml` and inspect `git diff` for the full change context.
 
 > Detailed review criteria, severity rules, and reviewer expectations live in `reference/review-criteria.md`. Read `reference/review-criteria.md` before reviewing.
+> Test review gate: when `git diff` touches test files, read `.agents/rules/testing-discipline.md` first and check it item by item, especially "do not add negative assertions when a positive assertion already covers the behavior".
 
 ### 5. Write the Review Report
 
@@ -51,7 +62,9 @@ date "+%Y-%m-%d %H:%M:%S%:z"
 ```
 
 Update task.md and append:
-`- {YYYY-MM-DD HH:mm:ss±HH:MM} — **Code Review (Round {N})** by {agent} — Verdict: {Approved/Changes Requested/Rejected}, blockers: {n}, major: {n}, minor: {n} → {artifact-filename}`
+`- {YYYY-MM-DD HH:mm:ss±HH:MM} — **Code Review (Round {N})** by {agent} — Verdict: {Approved/Changes Requested/Rejected}, blockers: {n}, major: {n}, minor: {n}[ (+ {n} env-blocked)] → {artifact-filename}`
+
+Omit the bracketed segment when env-blocked = 0; append ` (+ {n} env-blocked)` when env-blocked > 0.
 
 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
@@ -84,6 +97,8 @@ 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.
+
 > 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.
 
 Include all TUI command formats in the next-step output. If `.agents/.airc.json` configures custom TUIs (via `customTUIs`), read each tool's `name` and `invoke`, then add the matching command line in the same format (`${skillName}` becomes the skill name and `${projectName}` becomes the project name).

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

@@ -12,6 +12,16 @@ description: "审查任务实现并输出代码审查报告"
 - 本技能只审查代码并写报告，不修改业务代码
 - 执行本技能后，你**必须**立即更新 task.md
 
+版本戳规则：创建或更新 `task.md` frontmatter 时，先读取 `.agents/rules/version-stamp.md`，并写入或刷新 `agent_infra_version`。
+
+## 常见违规借口与反驳
+
+| 借口 | 反驳 |
+|------|------|
+| 「只改了一行，不影响功能」 | 行数不等于影响面；必须读完整 `git diff` 并定位每处改动的下游效果。 |
+| 「大体没问题，给个 Approved」 | 结论必须由 blocker/major/minor 计数支撑，每个问题引用文件:行号，不能凭印象放行。 |
+| 「测试改动看着合理，跳过细看」 | 审查测试变更前必须逐条核对 `.agents/rules/testing-discipline.md`（见步骤 4 门禁）。 |
+
 ## 执行步骤
 
 ### 1. 验证前置条件
@@ -35,6 +45,7 @@ description: "审查任务实现并输出代码审查报告"
 遵循 `.agents/workflows/feature-development.yaml`，并同时检查 `git diff` 获取完整变更上下文。
 
 > 详细审查标准、严重程度划分和 reviewer 关注点见 `reference/review-criteria.md`。执行此步骤前先读取 `reference/review-criteria.md`。
+> 测试审查硬门禁：当 `git diff` 触及测试文件时，必须先读取 `.agents/rules/testing-discipline.md` 并逐条核对（尤其"正向已覆盖时不应再加反向断言"）。
 
 ### 5. 编写审查报告
 
@@ -51,7 +62,9 @@ date "+%Y-%m-%d %H:%M:%S%:z"
 ```
 
 更新 task.md，并追加：
-`- {YYYY-MM-DD HH:mm:ss±HH:MM} — **Code Review (Round {N})** by {agent} — Verdict: {Approved/Changes Requested/Rejected}, blockers: {n}, major: {n}, minor: {n} → {artifact-filename}`
+`- {YYYY-MM-DD HH:mm:ss±HH:MM} — **Code Review (Round {N})** by {agent} — Verdict: {Approved/Changes Requested/Rejected}, blockers: {n}, major: {n}, minor: {n}[ (+ {n} env-blocked)] → {artifact-filename}`
+
+env-blocked = 0 时省略括号部分；env-blocked > 0 时附加 ` (+ {n} env-blocked)`。
 
 如果 task.md 中存在有效的 `issue_number`，执行以下同步操作（任一失败则跳过并继续）：
 - 执行前先读取 `.agents/rules/issue-sync.md`，完成 upstream 仓库检测和权限检测
@@ -84,6 +97,8 @@ node .agents/scripts/validate-artifact.js gate review-task .agents/workspace/act
 - 有 blocker，且可集中修复 -> 需要修改
 - 需要重大返工或重新实现 -> 拒绝
 
+env-blocked 的数量不参与分支选择，仅在数字摘要末尾附带显示。
+
 > 完整的 4 分支输出模板、判断规则和禁止条款见 `reference/output-templates.md`。向用户汇报审查结论前先读取 `reference/output-templates.md`。
 
 向用户展示下一步时，必须包含所有 TUI 命令格式。如果 `.agents/.airc.json` 中配置了自定义 TUI（`customTUIs`），读取每个工具的 `name` 和 `invoke`，按同样格式补充对应命令行（`${skillName}` 替换为技能名，`${projectName}` 替换为项目名）。

package/templates/.agents/skills/review-task/config/verify.json

@@ -9,6 +9,7 @@
         "status",
         "created_at",
         "updated_at",
+        "agent_infra_version",
         "current_step",
         "assigned_to"
       ]
@@ -18,6 +19,7 @@
       "required_sections": [
         "审查摘要",
         "问题清单",
+        "环境性遗留",
         "结论与建议"
       ],
       "required_patterns": [
@@ -36,6 +38,7 @@
       "verify_comment_content": true,
       "verify_task_comment_content": true,
       "verify_issue_type": true,
+      "verify_issue_fields": false,
       "verify_milestone": true,
       "expected_status_label_key": "inProgress",
       "expected_comment_marker_key": "artifact"

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

@@ -4,8 +4,8 @@ Read this file before presenting the final review result to the user.
 
 ## Choose Exactly One Output Branch
 
-Apply these rules in order:
-1. if `Blocker = 0` and `Major = 0` and `Minor = 0`, use Branch A
+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)
 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
@@ -14,25 +14,30 @@ 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
 - always include every TUI command format in the selected branch
 
 ### Branch A: Approved with No Findings
 
 ```text
 Task {task-id} review completed. Verdict: approved.
-- Blockers: 0 | Major: 0 | Minor: 0
+- Blockers: 0 | Major: 0 | Minor: 0[ | env-blocked: {n} (outside AI repair scope)]
+[- Review report: .agents/workspace/active/{task-id}/{review-artifact}]
 
 Next step - commit the code:
   - Claude Code / OpenCode: /commit
   - 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 /refine-task.
 ```
 
 ### Branch B: Approved with Findings
 
 ```text
 Task {task-id} review completed. Verdict: approved.
-- Blockers: 0 | Major: {n} | Minor: {n}
+- Blockers: 0 | Major: {n} | Minor: {n}[ | env-blocked: {n} (outside AI repair scope)]
 - Review report: .agents/workspace/active/{task-id}/{review-artifact}
 
 Next step - refine before commit (recommended):
@@ -44,29 +49,39 @@ Or commit directly (skip refinement):
   - Claude Code / OpenCode: /commit
   - 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 /refine-task.
 ```
 
 ### Branch C: Changes Requested
 
 ```text
 Task {task-id} review completed. Verdict: changes requested.
-- Blockers: {n} | Major: {n} | Minor: {n}
+- Blockers: {n} | Major: {n} | Minor: {n}[ | env-blocked: {n} (outside AI repair scope)]
 - Review report: .agents/workspace/active/{task-id}/{review-artifact}
 
 Next step - fix the findings:
   - Claude Code / OpenCode: /refine-task {task-id}
   - Gemini CLI: /agent-infra:refine-task {task-id}
   - Codex CLI: $refine-task {task-id}
+
+[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 /refine-task.
 ```
 
 ### Branch D: Rejected
 
 ```text
 Task {task-id} review completed. Verdict: rejected, major rework required.
+- Blockers: {n} | Major: {n} | Minor: {n}[ | env-blocked: {n} (outside AI repair scope)]
 - Review report: .agents/workspace/active/{task-id}/{review-artifact}
 
 Next step - re-implement:
   - Claude Code / OpenCode: /implement-task {task-id}
   - Gemini CLI: /agent-infra:implement-task {task-id}
   - Codex CLI: $implement-task {task-id}
+
+[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 /refine-task.
 ```

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

@@ -4,8 +4,8 @@
 
 ## 选择唯一输出场景
 
-按以下顺序判断：
-1. 如果 `Blocker = 0` 且 `Major = 0` 且 `Minor = 0`，使用场景 A
+按以下顺序判断（**注意：env-blocked 数量不参与判断**）：
+1. 如果 `Blocker = 0` 且 `Major = 0` 且 `Minor = 0`，使用场景 A（不管 env-blocked 是否 > 0）
 2. 如果 `Blocker = 0` 且（`Major > 0` 或 `Minor > 0`），使用场景 B
 3. 如果 `Blocker > 0`，且问题可以通过一次聚焦修复解决，使用场景 C
 4. 如果任务需要重大重构、大范围重写或整体重来，使用场景 D
@@ -14,25 +14,30 @@
 - 不要跳过场景判断步骤
 - 不要混用不同场景的文案
 - 只要 `Blocker > 0`，就绝对不能输出通过模板
+- env-blocked 项绝对不能被计入 blocker / major / minor 计数，也不能用作触发场景 B/C/D 的依据
 - 所选场景中必须包含所有 TUI 命令格式
 
 ### 场景 A：通过且无问题
 
 ```text
 任务 {task-id} 代码审查完成。结论：通过。
-- 阻塞项：0 | 主要问题：0 | 次要问题：0
+- 阻塞项：0 | 主要问题：0 | 次要问题：0[ | 环境性遗留：{n}（不在 AI 修复范围）]
+[- 审查报告：.agents/workspace/active/{task-id}/{review-artifact}]
 
 下一步 - 提交代码：
   - Claude Code / OpenCode：/commit
   - Gemini CLI：/agent-infra:commit
   - Codex CLI：$commit
+
+[当 env-blocked > 0 时，在最后附加一行：]
+提醒：env-blocked 项需在 PR description 的「待人工验证」清单中承接，不应触发 /refine-task。
 ```
 
 ### 场景 B：通过但有问题
 
 ```text
 任务 {task-id} 代码审查完成。结论：通过。
-- 阻塞项：0 | 主要问题：{n} | 次要问题：{n}
+- 阻塞项：0 | 主要问题：{n} | 次要问题：{n}[ | 环境性遗留：{n}（不在 AI 修复范围）]
 - 审查报告：.agents/workspace/active/{task-id}/{review-artifact}
 
 下一步 - 修复问题后提交（推荐）：
@@ -44,29 +49,39 @@
   - Claude Code / OpenCode：/commit
   - Gemini CLI：/agent-infra:commit
   - Codex CLI：$commit
+
+[当 env-blocked > 0 时，在最后附加一行：]
+提醒：env-blocked 项需在 PR description 的「待人工验证」清单中承接，不应触发 /refine-task。
 ```
 
 ### 场景 C：需要修改
 
 ```text
 任务 {task-id} 代码审查完成。结论：需要修改。
-- 阻塞项：{n} | 主要问题：{n} | 次要问题：{n}
+- 阻塞项：{n} | 主要问题：{n} | 次要问题：{n}[ | 环境性遗留：{n}（不在 AI 修复范围）]
 - 审查报告：.agents/workspace/active/{task-id}/{review-artifact}
 
 下一步 - 修复问题：
   - Claude Code / OpenCode：/refine-task {task-id}
   - Gemini CLI：/agent-infra:refine-task {task-id}
   - Codex CLI：$refine-task {task-id}
+
+[当 env-blocked > 0 时，在最后附加一行：]
+提醒：env-blocked 项需在 PR description 的「待人工验证」清单中承接，不应触发 /refine-task。
 ```
 
 ### 场景 D：拒绝
 
 ```text
 任务 {task-id} 代码审查完成。结论：拒绝，需要重大返工。
+- 阻塞项：{n} | 主要问题：{n} | 次要问题：{n}[ | 环境性遗留：{n}（不在 AI 修复范围）]
 - 审查报告：.agents/workspace/active/{task-id}/{review-artifact}
 
 下一步 - 重新实现：
   - Claude Code / OpenCode：/implement-task {task-id}
   - Gemini CLI：/agent-infra:implement-task {task-id}
   - Codex CLI：$implement-task {task-id}
+
+[当 env-blocked > 0 时，在最后附加一行：]
+提醒：env-blocked 项需在 PR description 的「待人工验证」清单中承接，不应触发 /refine-task。
 ```