@fitlab-ai/agent-infra 0.10.0 → 0.11.1

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

@@ -30,18 +30,7 @@
       ]
     },
     "platform-sync": {
-      "when": "platform_issue_identity_exists",
-      "expected_status_label": "status: in-progress",
-      "expected_comment_marker": "<!-- sync-issue:{task-id}:{artifact-stem} -->",
-      "verify_comment_content": true,
-      "verify_task_comment_content": true,
-      "verify_issue_type": true,
-      "verify_issue_fields": false,
-      "verify_in_labels_computed": true,
-      "verify_milestone": true,
-      "verify_milestone_specific": true,
-      "expected_status_label_key": "inProgress",
-      "expected_comment_marker_key": "artifact"
+      "when": "platform_issue_identity_exists"
     }
   }
 }

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

@@ -30,18 +30,7 @@
       ]
     },
     "platform-sync": {
-      "when": "platform_issue_identity_exists",
-      "expected_status_label": "status: in-progress",
-      "expected_comment_marker": "<!-- sync-issue:{task-id}:{artifact-stem} -->",
-      "verify_comment_content": true,
-      "verify_task_comment_content": true,
-      "verify_issue_type": true,
-      "verify_issue_fields": false,
-      "verify_in_labels_computed": true,
-      "verify_milestone": true,
-      "verify_milestone_specific": true,
-      "expected_status_label_key": "inProgress",
-      "expected_comment_marker_key": "artifact"
+      "when": "platform_issue_identity_exists"
     }
   }
 }

package/templates/.agents/skills/code-task/reference/dual-mode.en.md

@@ -10,7 +10,7 @@ agent-infra-internal task-artifact {task-id} inspect --family code
 
 The core scans `plan.md` / `plan-r{N}.md`, `review-plan.md` / `review-plan-r{N}.md`, `code.md` / `code-r{N}.md`, and `review-code.md` / `review-code-r{N}.md` in the task directory.
 
-`code.started` persists the plan identity and SHA-256 for the round in task.md frontmatter. `code.completed` must read the canonical plan from the implementation report's `Plan Input` field and match both that start context and the current latest plan; missing, mismatched, or changed input fails closed.
+`code.started` persists the plan identity and SHA-256 for the round in task.md frontmatter. `code.completed` uses that start context and verifies the current latest plan; changed input fails closed. The implementation report's `Plan Input` field is reader-facing traceability, not lifecycle identity validation.
 
 ## Eight Branches
 

package/templates/.agents/skills/code-task/reference/dual-mode.zh-CN.md

@@ -10,7 +10,7 @@ agent-infra-internal task-artifact {task-id} inspect --family code
 
 核心扫描任务目录中的 `plan.md` / `plan-r{N}.md`、`review-plan.md` / `review-plan-r{N}.md`、`code.md` / `code-r{N}.md` 和 `review-code.md` / `review-code-r{N}.md`。
 
-`code.started` 会在 task.md frontmatter 中绑定本轮方案文件及其 SHA-256。`code.completed` 必须从实现报告的“方案输入”/“Plan Input”字段读取 canonical plan，并同时匹配该开始上下文和当前最新 plan；缺失、身份不一致或内容变化均失败关闭。
+`code.started` 会在 task.md frontmatter 中绑定本轮方案文件及其 SHA-256。`code.completed` 使用该开始上下文并校验当前最新 plan；内容变化失败关闭。实现报告的“方案输入”/“Plan Input”仅供读者追溯，不参与生命周期身份校验。
 
 ## 8 个分支
 

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

@@ -4,6 +4,8 @@
 
 Use this structure when creating `code.md` or `code-r{N}.md`.
 
+> Implementation-input fields provide reader-facing traceability. Lifecycle identity uses the input frozen by `code.started` and the completion receipt; it is not parsed from this report body.
+
 ## Output Template
 
 ```markdown
@@ -103,6 +105,15 @@ Use this structure when creating `code.md` or `code-r{N}.md`.
 > Record the state-check command, task/artifact scope, key result, and uncovered parts; each command starts with `$ `.
 > Follow `.agents/rules/evidence-reporting.md`: record task/artifact scope, key result, and uncovered parts; do not paste complete successful stdout.
 
+Record at least one actually executed `$ ` command and its result summary; prose-only status is insufficient. An implementation-stage report normally includes:
+
+```text
+$ agent-infra-internal task-snapshot {task-id} --format text
+{task state, implementation-artifact scope, and uncovered-area summary}
+$ agent-infra-internal task-artifact {task-id} inspect --family code
+{code artifact, upstream input, and next-step summary}
+```
+
 ## Raw Evidence
 
 > Follow `.agents/rules/evidence-reporting.md`: pair each claim with a `$ ` command and proportionate result summary; include a decisive raw excerpt only for failures, blocking conditions, or disputes.

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

@@ -4,6 +4,8 @@
 
 创建 `code.md` 或 `code-r{N}.md` 时，使用以下结构。
 
+> “实现输入”字段用于读者追溯。生命周期身份以 `code.started` 冻结的输入和完成 receipt 为准，不从本报告正文解析。
+
 ## 输出模板
 
 ```markdown
@@ -103,6 +105,15 @@
 > 记录状态核对命令、任务/产物范围、关键结果和未覆盖部分；每条命令以 `$ ` 开头。
 > 按 `.agents/rules/evidence-reporting.md` 同时记录任务/产物范围、关键结果和未覆盖部分；正常成功不粘贴完整 stdout。
 
+必须记录至少一条实际执行的 `$ ` 命令及其结果摘要，不能只写自然语言状态。实现阶段通常包括：
+
+```text
+$ agent-infra-internal task-snapshot {task-id} --format text
+{任务状态、实现产物范围和未覆盖项摘要}
+$ agent-infra-internal task-artifact {task-id} inspect --family code
+{code artifact、上游输入和下一步摘要}
+```
+
 ## 证据原文
 
 > 遵循 `.agents/rules/evidence-reporting.md`：每条断言配对 `$ ` 命令和相称结果摘要；仅为失败、阻塞或争议附决定性原文摘录。

package/templates/.agents/skills/commit/config/verify.json

@@ -18,11 +18,7 @@
       "expected_action_pattern": "Commit"
     },
     "platform-sync": {
-      "when": "pr_fact_bound",
-      "expected_pr_comment_marker": "<!-- sync-pr:{task-id}:summary -->",
-      "verify_in_labels_computed": true,
-      "verify_pr_comment_last_commit_matches_head": true,
-      "expected_pr_comment_marker_key": "prSummary"
+      "when": "pr_fact_bound"
     }
   }
 }

package/templates/.agents/skills/complete-manual-validation/config/verify.en.json

@@ -31,17 +31,17 @@
       "expected_action_pattern": "Complete Manual Validation"
     },
     "review-ledger": {
-      "stage_scope": ["analysis", "plan", "code"]
+      "stage_scope": [
+        "analysis",
+        "plan",
+        "code"
+      ]
     },
     "platform-sync": {
       "when": "pr_fact_bound",
-      "expected_pr_comment_marker_key": "prSummary",
       "expected_pr_comment_required_patterns": [
         "^### ✅ (?:人工验证已通过|Manual Validation Passed)$"
-      ],
-      "verify_task_comment_content": true,
-      "verify_issue_type": true,
-      "verify_issue_fields": false
+      ]
     }
   }
 }

package/templates/.agents/skills/complete-manual-validation/config/verify.zh-CN.json

@@ -31,17 +31,17 @@
       "expected_action_pattern": "Complete Manual Validation"
     },
     "review-ledger": {
-      "stage_scope": ["analysis", "plan", "code"]
+      "stage_scope": [
+        "analysis",
+        "plan",
+        "code"
+      ]
     },
     "platform-sync": {
       "when": "pr_fact_bound",
-      "expected_pr_comment_marker_key": "prSummary",
       "expected_pr_comment_required_patterns": [
         "^### ✅ (?:人工验证已通过|Manual Validation Passed)$"
-      ],
-      "verify_task_comment_content": true,
-      "verify_issue_type": true,
-      "verify_issue_fields": false
+      ]
     }
   }
 }

package/templates/.agents/skills/complete-task/config/verify.en.json

@@ -15,8 +15,7 @@
         "completed_at"
       ],
       "expected_status": "completed",
-      "require_completed_at": true,
-      "require_target_date": true
+      "require_completed_at": true
     },
     "activity-log": {
       "expected_action_pattern": "(Complete Task|Completed)"
@@ -28,21 +27,11 @@
     "manual-validation": {},
     "post-review-commit": {},
     "platform-sync-preflight": {
-      "when": "platform_issue_identity_exists",
-      "expected_comment_marker": "<!-- sync-issue:{task-id}:summary -->",
-      "verify_task_comment_content": false,
-      "sync_checked_requirements": true,
-      "verify_issue_type": true,
-      "verify_issue_fields": false,
-      "verify_milestone": true,
-      "verify_closed_issue_has_no_status_labels": false,
-      "expected_comment_marker_key": "summary"
+      "when": "platform_issue_identity_exists"
     },
     "required-pr-delivery": {},
     "platform-sync": {
-      "when": "platform_issue_identity_exists",
-      "verify_task_comment_content": true,
-      "verify_closed_issue_has_no_status_labels": true
+      "when": "platform_issue_identity_exists"
     },
     "artifact": {
       "file_pattern": "task.md",

package/templates/.agents/skills/complete-task/config/verify.zh-CN.json

@@ -15,8 +15,7 @@
         "completed_at"
       ],
       "expected_status": "completed",
-      "require_completed_at": true,
-      "require_target_date": true
+      "require_completed_at": true
     },
     "activity-log": {
       "expected_action_pattern": "(Complete Task|Completed)"
@@ -28,21 +27,11 @@
     "manual-validation": {},
     "post-review-commit": {},
     "platform-sync-preflight": {
-      "when": "platform_issue_identity_exists",
-      "expected_comment_marker": "<!-- sync-issue:{task-id}:summary -->",
-      "verify_task_comment_content": false,
-      "sync_checked_requirements": true,
-      "verify_issue_type": true,
-      "verify_issue_fields": false,
-      "verify_milestone": true,
-      "verify_closed_issue_has_no_status_labels": false,
-      "expected_comment_marker_key": "summary"
+      "when": "platform_issue_identity_exists"
     },
     "required-pr-delivery": {},
     "platform-sync": {
-      "when": "platform_issue_identity_exists",
-      "verify_task_comment_content": true,
-      "verify_closed_issue_has_no_status_labels": true
+      "when": "platform_issue_identity_exists"
     },
     "artifact": {
       "file_pattern": "task.md",

package/templates/.agents/skills/create-pr/config/verify.json

@@ -18,16 +18,7 @@
       "expected_action_pattern": "(Create PR|PR Created)"
     },
     "platform-sync": {
-      "when": "platform_issue_identity_exists",
-      "expected_pr_comment_marker": "<!-- sync-pr:{task-id}:summary -->",
-      "verify_in_labels_match_pr": true,
-      "verify_in_labels_computed": true,
-      "verify_pr_type_label": true,
-      "verify_pr_assignee": true,
-      "verify_issue_fields": true,
-      "verify_milestone": true,
-      "verify_milestone_specific": true,
-      "expected_pr_comment_marker_key": "prSummary"
+      "when": "platform_issue_identity_exists"
     }
   }
 }

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

@@ -22,10 +22,7 @@
     },
     "platform-sync": {
       "when": "platform_issue_identity_exists",
-      "issue_must_exist": true,
-      "verify_task_comment_content": true,
-      "verify_milestone": true,
-      "expected_status_label_key": "waitingForTriage"
+      "issue_must_exist": true
     }
   }
 }

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

@@ -22,8 +22,7 @@
     },
     "platform-sync": {
       "when": "platform_issue_identity_exists",
-      "issue_must_exist": true,
-      "verify_task_comment_content": true
+      "issue_must_exist": true
     }
   }
 }

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

@@ -135,8 +135,8 @@ agent-infra-internal task-artifact {task-id} finalize-local --family plan --arti
 ```
 
 - On `status=passed`, save that result's `artifactSha256` and `semanticDigest`; the finalizer has recorded the matching one-shot local provenance intent.
-- On `status=failed` with recovery context, edit only the returned `candidatePath` once after the completion gates pass, then rerun the finalizer completely with the same `recoveryId`; the formal artifact must remain unchanged until commit.
-- The recovery candidate must match the recorded task, round, artifact, baseline, and request identity. On baseline conflict, unknown state, no progress, or repeated failure, stop without publishing a completed event.
+- On `status=failed` with recovery context, after the completion gates pass, edit the returned `candidatePath` only once for this attempt, then rerun the finalizer completely with the same `recoveryId`; if it still fails with a new diagnostic and fingerprint while the gates continue to pass, continue to the next attempt; the formal artifact must remain unchanged until commit.
+- The recovery candidate must match the recorded task, round, artifact, baseline, and request identity. On baseline conflict, unknown state, an unsafe repair, repeated diagnostics or fingerprints, no progress, or the shared edit limit, stop without publishing a completed event.
 
 Use the digests from that same `status=passed` result in `agent-infra-internal task-event {task-id} plan.completed --agent {standard-agent-token} --initiator {trigger-initiator} --request-id {request-id} --reason-code {reason-code} --artifact {plan-artifact} --artifact-sha256 {artifact-sha256} --semantic-digest {semantic-digest} {execution-flag}` so the core records the link, stage, agent, metadata, and Activity Log atomically.
   - {YYYY-MM-DD HH:mm:ss±HH:MM} — **Plan Task (Round {N})** by {agent} — Plan completed, awaiting human review → {artifact-filename}

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

@@ -134,8 +134,8 @@ agent-infra-internal task-artifact {task-id} init --family plan --artifact {plan
   agent-infra-internal task-artifact {task-id} finalize-local --family plan --artifact {plan-artifact}
   ```
   - `status=passed`：保存本次返回的 `artifactSha256` 和 `semanticDigest`；finalizer 已记录对应的一次性本地 provenance intent。
-  - `status=failed` 且返回 recovery context：完成门禁通过后，只编辑返回的 `candidatePath` 一次，然后使用同一个 `recoveryId` 完整重跑 finalizer；formal artifact 在 commit 前必须保持不变。
-  - recovery candidate 必须与记录的任务、轮次、产物、baseline 和 request identity 匹配；基线冲突、未知状态、无进展或重复失败：停止，不发布 completed 事件。
+  - `status=failed` 且返回 recovery context：完成门禁通过后，本次只编辑返回的 `candidatePath` 一次，然后使用同一个 `recoveryId` 完整重跑 finalizer；若仍失败但诊断和指纹均未重复且安全门继续通过，继续下一轮；formal artifact 在 commit 前必须保持不变。
+  - recovery candidate 必须与记录的任务、轮次、产物、baseline 和 request identity 匹配；基线冲突、未知状态、无法安全修复、诊断或指纹重复、无进展，或达到共享规则的编辑上限时停止，不发布 completed 事件。
 - 使用同一次 `status=passed` 返回的摘要执行 `agent-infra-internal task-event {task-id} plan.completed --agent {standard-agent-token} --initiator {trigger-initiator} --request-id {request-id} --reason-code {reason-code} --artifact {plan-artifact} --artifact-sha256 {artifact-sha256} --semantic-digest {semantic-digest} {execution-flag}`，由核心登记链接、阶段、代理、时间、版本和 Activity Log。
 
 如果 task.md 中存在有效的 `platform_issue_identity`，执行以下同步操作（任一失败则跳过并继续）：

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

@@ -28,16 +28,7 @@
       ]
     },
     "platform-sync": {
-      "when": "platform_issue_identity_exists",
-      "expected_status_label": "status: pending-design-work",
-      "expected_comment_marker": "<!-- sync-issue:{task-id}:{artifact-stem} -->",
-      "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"
+      "when": "platform_issue_identity_exists"
     }
   }
 }

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

@@ -28,16 +28,7 @@
       ]
     },
     "platform-sync": {
-      "when": "platform_issue_identity_exists",
-      "expected_status_label": "status: pending-design-work",
-      "expected_comment_marker": "<!-- sync-issue:{task-id}:{artifact-stem} -->",
-      "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"
+      "when": "platform_issue_identity_exists"
     }
   }
 }

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

@@ -45,13 +45,14 @@ Run `agent-infra-internal platform-comment list --issue {issue-token}` to read a
 
 ### 3. Determine the task-id and Files to Restore
 
-Filter comments by the task, artifact, and chunked artifact markers defined in `.agents/rules/issue-sync.md`.
+Filter comments by the task, artifact, chunked artifact, and recovery markers defined in `.agents/rules/issue-sync.md`.
 
 Rules:
 - when `{task-id}` was provided, match only that task
 - when `{task-id}` was omitted, infer it from the task comment marker first
 - if you cannot determine a unique task-id, stop and tell the user
 - ignore `summary` marker comments because they are complete-task aggregate output rather than restorable local task files
+- use the `task` comment only for the current projection and snapshot identity; the controlled recovery core validates `recovery-action`, `recovery-prepare`, and `recovery-commit` comments and reconstructs the complete `task.md`
 - map `{file-stem}` back to filenames:
   - `task` -> `task.md`
   - `analysis` / `analysis-r{N}` -> matching `.md`
@@ -68,7 +69,7 @@ Read `.agents/rules/issue-sync.md` before executing this step.
 
 For each file:
 - collect its single comment or chunked comments
-- for `task.md` comments, reverse the `<details>` frontmatter wrapper described in issue-sync.md before reassembling the file body
+- do not reverse the projected task comment directly into `task.md`; the complete task content must come from a recovery commit matching the current projection
 - when a chunk marker includes part and total indexes, sort by part and verify the set is complete
 - extract the file body by removing the hidden marker, heading, and footer
 - concatenate chunk bodies into the final file content
@@ -83,10 +84,14 @@ If the directory already exists, stop immediately and tell the user to handle it
 
 Create the controlled staging directory and write files back in this order:
 
-1. `task.md`
+1. call the recovery core to write `task.md`:
+   ```bash
+   agent-infra-internal platform-comment recover --issue {issue-token} --task-id {task-id} \
+     --output "{staging-dir}/task.md"
+   ```
 2. every other restored artifact file in filename order
 
-Write only files that were actually recovered from Issue comments. Do not invent missing files.
+Write only files that were actually recovered from Issue comments. Do not invent missing files. Stop without calling the lifecycle intent if the recovery core fails.
 
 ### 6. Apply the Restore Lifecycle Intent
 

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

@@ -44,13 +44,14 @@ description: >
 
 ### 3. 确定 task-id 与待恢复文件
 
-按 `.agents/rules/issue-sync.md` 中定义的 task、artifact 和分片 artifact 标记筛选评论。
+按 `.agents/rules/issue-sync.md` 中定义的 task、artifact 与分片 artifact 标记筛选评论。
 
 处理规则：
 - 用户提供了 `{task-id}` 时，仅匹配该任务
 - 未提供时，优先从 task 评论标记推断
 - 若找不到唯一 task-id，立即停止并告知用户
 - 忽略 `summary` 标记评论；它是 complete-task 的聚合产物，不对应本地任务文件
+- `task`、artifact 和交付摘要评论顶部的折叠恢复元数据由受控 recovery core 验证并重建活动日志。
 - 将 `{file-stem}` 映射回文件名：
   - `task` -> `task.md`
   - `analysis` / `analysis-r{N}` -> 对应 `.md`
@@ -67,9 +68,9 @@ description: >
 
 对每个文件执行：
 - 收集单条评论或分片评论
-- 对 `task.md` 评论按 issue-sync.md 中的 `<details>` frontmatter 格式反向拆解，提取 frontmatter 后再与正文拼合
+- 从 task 评论恢复当前任务投影，再只从通过校验的 artifact 恢复元数据重建活动日志；不得根据缺失记录推测过程状态
 - 如分片标记中存在 part 和 total 序号，按 part 升序排序并校验分片完整
-- 从评论正文中提取文件内容，去掉隐藏标记、标题和页脚
+- 从评论正文中提取文件内容，去掉隐藏标记、标题、恢复元数据和页脚
 - 拼接得到最终文件内容
 
 在写文件前检查：
@@ -82,10 +83,14 @@ description: >
 
 创建受控 staging 目录，按以下顺序写回：
 
-1. `task.md`
+1. 调用 recovery core 写入 `task.md`：
+   ```bash
+   agent-infra-internal platform-comment recover --issue {issue-token} --task-id {task-id} \
+     --output "{staging-dir}/task.md"
+   ```
 2. 其余产物文件（按文件名排序）
 
-仅写回从 Issue 评论中实际恢复出的文件，不补造缺失文件。
+仅写回从 Issue 评论中实际恢复出的文件，不补造缺失文件。recovery core 返回失败时停止，不调用 lifecycle intent。
 
 ### 6. 执行 restore 生命周期意图
 

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

@@ -83,7 +83,7 @@ Create `.agents/workspace/active/{task-id}/{review-artifact}`.
 
 ### 6. Update Task Status
 
-After the report, submit each new finding with `agent-infra-internal task-ledger {task-id} finding-upsert --stage analysis --review-artifact {review-artifact} --ordinal {n} --severity {blocker|major|minor} --evidence {review-artifact}#{anchor}`; submit prior-response dispositions with `finding-review --id {ledger-id} --status {confirmed|closed|open|needs-human-decision} --evidence {evidence}`. Do not scan ids or edit ledger rows. After all ledger writes, make the initial call to `agent-infra-internal task-review {task-id} finalize-summary --stage analysis --artifact {review-artifact} {execution-flag}`; after a failure, follow `.agents/rules/local-artifact-repair.md` to decide whether to edit and rerun, and never treat an error type or `changed=false` as automatic authorization.
+After the report, call `agent-infra-internal task-review {task-id} preflight --stage analysis --artifact {review-artifact} {execution-flag}` before any ledger write. On failure, follow `.agents/rules/local-artifact-repair.md`; on success, bind `{recovery-id}` from the response. Only after preflight passes, submit each new finding with `agent-infra-internal task-ledger {task-id} finding-upsert --stage analysis --review-artifact {review-artifact} --ordinal {n} --severity {blocker|major|minor} --evidence {review-artifact}#{anchor}` or prior-response dispositions with `finding-review --id {ledger-id} --status {confirmed|closed|open|needs-human-decision} --evidence {evidence}`. Do not scan ids or edit ledger rows. After all ledger writes, call `agent-infra-internal task-review {task-id} finalize-summary --stage analysis --artifact {review-artifact} --recovery-id {recovery-id} {execution-flag}`; never treat an error type or `changed=false` as automatic authorization.
 
 Bind and reuse this structured mapping from that one response:
 

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

@@ -86,7 +86,7 @@ agent-infra-internal task-artifact {task-id} init --family review-analysis --art
 
 ### 6. 更新任务状态
 
-报告完成后，新 finding 逐条调用 `agent-infra-internal task-ledger {task-id} finding-upsert --stage analysis --review-artifact {review-artifact} --ordinal {n} --severity {blocker|major|minor} --evidence {review-artifact}#{anchor}`；复核上一轮响应时调用 `finding-review --id {ledger-id} --status {confirmed|closed|open|needs-human-decision} --evidence {相称证据}`。不得扫描编号或手写账本行。全部账本写入完成后首次调用 `agent-infra-internal task-review {task-id} finalize-summary --stage analysis --artifact {review-artifact} {execution-flag}`；失败后是否继续编辑并重跑，必须遵循 `.agents/rules/local-artifact-repair.md`，不能把失败类型或 `changed=false` 当作自动授权。
+报告完成后，先调用 `agent-infra-internal task-review {task-id} preflight --stage analysis --artifact {review-artifact} {execution-flag}`，不得先写入账本。失败后是否继续编辑并重跑，必须遵循 `.agents/rules/local-artifact-repair.md`；通过时从返回值绑定 `{recovery-id}`。只有 preflight 通过后，才逐条调用 `agent-infra-internal task-ledger {task-id} finding-upsert --stage analysis --review-artifact {review-artifact} --ordinal {n} --severity {blocker|major|minor} --evidence {review-artifact}#{anchor}`，或复核上一轮响应时调用 `finding-review --id {ledger-id} --status {confirmed|closed|open|needs-human-decision} --evidence {相称证据}`。不得扫描编号或手写账本行。全部账本写入完成后调用 `agent-infra-internal task-review {task-id} finalize-summary --stage analysis --artifact {review-artifact} --recovery-id {recovery-id} {execution-flag}`；不能把失败类型或 `changed=false` 当作自动授权。
 
 从该次返回值绑定并复用以下结构化映射：
 

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

@@ -27,16 +27,7 @@
       "expected_action_pattern": "(Review Analysis|Analysis Review) \\(Round \\d+\\)"
     },
     "platform-sync": {
-      "when": "platform_issue_identity_exists",
-      "expected_status_label": "status: pending-design-work",
-      "expected_comment_marker": "<!-- sync-issue:{task-id}:{artifact-stem} -->",
-      "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"
+      "when": "platform_issue_identity_exists"
     }
   }
 }

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

@@ -27,16 +27,7 @@
       "expected_action_pattern": "(Review Analysis|Analysis Review) \\(Round \\d+\\)"
     },
     "platform-sync": {
-      "when": "platform_issue_identity_exists",
-      "expected_status_label": "status: pending-design-work",
-      "expected_comment_marker": "<!-- sync-issue:{task-id}:{artifact-stem} -->",
-      "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"
+      "when": "platform_issue_identity_exists"
     }
   }
 }

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

@@ -4,6 +4,8 @@
 
 Use this template when writing `review-analysis.md` or `review-analysis-r{N}.md`.
 
+> The `Review Input` field provides reader-facing traceability. Lifecycle identity uses the input frozen by `review-analysis.started` and the completion receipt; it is not parsed from this report body.
+
 ## Output Template
 
 ```markdown

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

@@ -4,6 +4,8 @@
 
 编写 `review-analysis.md` 或 `review-analysis-r{N}.md` 时使用本模板。
 
+> “审查输入”字段用于读者追溯。生命周期身份以 `review-analysis.started` 冻结的输入和完成 receipt 为准，不从本报告正文解析。
+
 ## 输出模板
 
 ```markdown

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

@@ -111,8 +111,9 @@ Create `.agents/workspace/active/{task-id}/{review-artifact}`.
 ### 6. Update Task Status
 
 Update task.md:
-- After the report, submit each new finding with `agent-infra-internal task-ledger {task-id} finding-upsert --stage code --review-artifact {review-artifact} --ordinal {n} --severity {blocker|major|minor} --evidence {review-artifact}#{anchor}`; submit prior-response dispositions with `finding-review --id {ledger-id} --status {confirmed|closed|open|needs-human-decision} --evidence {evidence}`. When escalating to `needs-human-decision`, append `--needs-implementation true|false` using the judgment recorded in the detail block. Do not scan ids or edit ledger rows
-- After all ledger writes, make the initial call to `agent-infra-internal task-review {task-id} finalize-summary --stage code --artifact {review-artifact} {execution-flag}`; after a failure, follow `.agents/rules/local-artifact-repair.md` to decide whether to edit and rerun, and never treat an error type or `changed=false` as automatic authorization
+- After the report, call `agent-infra-internal task-review {task-id} preflight --stage code --artifact {review-artifact} {execution-flag}` before any ledger write. On failure, follow `.agents/rules/local-artifact-repair.md`; on success, bind `{recovery-id}` from the response.
+- Only after preflight passes, submit each new finding with `agent-infra-internal task-ledger {task-id} finding-upsert --stage code --review-artifact {review-artifact} --ordinal {n} --severity {blocker|major|minor} --evidence {review-artifact}#{anchor}`; submit prior-response dispositions with `finding-review --id {ledger-id} --status {confirmed|closed|open|needs-human-decision} --evidence {evidence}`. When escalating to `needs-human-decision`, append `--needs-implementation true|false` using the judgment recorded in the detail block. Do not scan ids or edit ledger rows
+- After all ledger writes, call `agent-infra-internal task-review {task-id} finalize-summary --stage code --artifact {review-artifact} --recovery-id {recovery-id} {execution-flag}`; never treat an error type or `changed=false` as automatic authorization
 
   Bind and reuse this structured mapping from that one response:
 

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

@@ -109,8 +109,9 @@ agent-infra-internal task-artifact {task-id} init --family review-code --artifac
 
 ### 6. 更新任务状态
 
-- 报告完成后，新 finding 逐条调用 `agent-infra-internal task-ledger {task-id} finding-upsert --stage code --review-artifact {review-artifact} --ordinal {n} --severity {blocker|major|minor} --evidence {review-artifact}#{anchor}`；复核上一轮响应时调用 `finding-review --id {ledger-id} --status {confirmed|closed|open|needs-human-decision} --evidence {相称证据}`。升级为 `needs-human-decision` 时，按详情块中的判断追加 `--needs-implementation true|false`。不得扫描编号或手写账本行
-- 全部账本写入完成后首次调用 `agent-infra-internal task-review {task-id} finalize-summary --stage code --artifact {review-artifact} {execution-flag}`；失败后是否继续编辑并重跑，必须遵循 `.agents/rules/local-artifact-repair.md`，不能把失败类型或 `changed=false` 当作自动授权
+- 报告完成后，先调用 `agent-infra-internal task-review {task-id} preflight --stage code --artifact {review-artifact} {execution-flag}`，不得先写入账本。失败后是否继续编辑并重跑，必须遵循 `.agents/rules/local-artifact-repair.md`；通过时从返回值绑定 `{recovery-id}`。
+- 只有 preflight 通过后，新 finding 才逐条调用 `agent-infra-internal task-ledger {task-id} finding-upsert --stage code --review-artifact {review-artifact} --ordinal {n} --severity {blocker|major|minor} --evidence {review-artifact}#{anchor}`；复核上一轮响应时调用 `finding-review --id {ledger-id} --status {confirmed|closed|open|needs-human-decision} --evidence {相称证据}`。升级为 `needs-human-decision` 时，按详情块中的判断追加 `--needs-implementation true|false`。不得扫描编号或手写账本行
+- 全部账本写入完成后调用 `agent-infra-internal task-review {task-id} finalize-summary --stage code --artifact {review-artifact} --recovery-id {recovery-id} {execution-flag}`；不能把失败类型或 `changed=false` 当作自动授权
 
   从该次返回值绑定并复用以下结构化映射：
 

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

@@ -28,16 +28,7 @@
       "expected_action_pattern": "(Review Code|Code Review) \\(Round \\d+\\)"
     },
     "platform-sync": {
-      "when": "platform_issue_identity_exists",
-      "expected_status_label": "status: in-progress",
-      "expected_comment_marker": "<!-- sync-issue:{task-id}:{artifact-stem} -->",
-      "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"
+      "when": "platform_issue_identity_exists"
     }
   }
 }

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

@@ -28,16 +28,7 @@
       "expected_action_pattern": "(Review Code|Code Review) \\(Round \\d+\\)"
     },
     "platform-sync": {
-      "when": "platform_issue_identity_exists",
-      "expected_status_label": "status: in-progress",
-      "expected_comment_marker": "<!-- sync-issue:{task-id}:{artifact-stem} -->",
-      "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"
+      "when": "platform_issue_identity_exists"
     }
   }
 }

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

@@ -4,6 +4,8 @@
 
 Use this template when writing `review-code.md` or `review-code-r{N}.md`.
 
+> The `Review Input` field provides reader-facing traceability. Lifecycle identity uses the input frozen by `review-code.started` and the completion receipt; it is not parsed from this report body.
+
 ## Output Template
 
 ```markdown

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

@@ -4,6 +4,8 @@
 
 编写 `review-code.md` 或 `review-code-r{N}.md` 时使用本模板。
 
+> “审查输入”字段用于读者追溯。生命周期身份以 `review-code.started` 冻结的输入和完成 receipt 为准，不从本报告正文解析。
+
 ## 输出模板
 
 ```markdown