@fitlab-ai/agent-infra 0.9.15 → 0.10.0

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

@@ -114,7 +114,7 @@ Before writing this round's `{plan-artifact}`, create the controlled report skel
 agent-infra-internal task-artifact {task-id} init --family plan --artifact {plan-artifact} --locale en
 ```
 
-The skeleton contains identity metadata, stable section markers, and required headings only; real plan content is required before the completion gate can pass. If the finalizer returns one provably safe structural error, call `task-artifact {task-id} repair --family plan --artifact {plan-artifact} --expected-sha256 {artifact-sha256} --expected-semantic-digest {semantic-digest}`, then rerun the same finalizer.
+The skeleton contains identity metadata, stable section markers, and required headings only; real plan content is required before the completion gate can pass. If the finalizer returns one provably safe structural error, it returns a controlled recovery candidate; edit only its `candidatePath`, then rerun `task-artifact {task-id} finalize-local --family plan --artifact {plan-artifact} --recovery-id {recovery-id}` with the same `recoveryId`. Candidate-only is a protocol authorization boundary, not OS isolation; arbitrary same-UID host writers are outside the protocol's protection claim, and fingerprint/state checks fail closed on anomalies.
 
 Create `.agents/workspace/active/{task-id}/{plan-artifact}`.
 
@@ -135,14 +135,14 @@ 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 `repairable=true`, apply only the diagnostic's `replace-line` operation once, then rerun the same command completely; count an attempt only after bytes change, up to 8 attempts.
-- The first repairable failure's `semanticDigest` is retained as the baseline; a retried `status=passed` result must match it. On baseline mismatch, any other failure, no progress, or a repeated diagnostic, stop without publishing a completed event.
+- 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.
 
 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}
   ```
 
-If task.md contains a valid `issue_number`, perform these sync actions (skip and continue on any failure):
+If task.md contains a valid `platform_issue_identity`, perform these sync actions (skip and continue on any failure):
 - Run `agent-infra-internal platform-issue sync {task-id} --agent {standard-agent-token} --status pending-design-work --fields`
 - Run `agent-infra-internal platform-comment sync {task-id} --kind task --agent {standard-agent-token}`
 - Run `agent-infra-internal platform-comment sync {task-id} --kind artifact --artifact {plan-artifact} --agent {standard-agent-token}`

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

@@ -117,7 +117,7 @@ agent-infra-internal task-event {task-id} plan.started --agent {standard-agent-t
 agent-infra-internal task-artifact {task-id} init --family plan --artifact {plan-artifact}
 ```
 
-骨架只包含身份元数据、稳定 section marker 和必需标题；必须填入真实方案内容后才能通过完成门禁。finalizer 返回可证明的单个结构错误时，使用其 SHA 和 semantic digest 调用 `task-artifact {task-id} repair --family plan --artifact {plan-artifact} --expected-sha256 {artifact-sha256} --expected-semantic-digest {semantic-digest}`，然后完整重跑 finalizer。
+骨架只包含身份元数据、稳定 section marker 和必需标题；必须填入真实方案内容后才能通过完成门禁。finalizer 返回可证明的单个结构错误时，会返回受控 recovery candidate；只能编辑返回的 `candidatePath`，然后使用同一个 `recoveryId` 重跑 `task-artifact {task-id} finalize-local --family plan --artifact {plan-artifact} --recovery-id {recovery-id}`。candidate-only 是协议授权边界，不是操作系统隔离；同 UID 的任意宿主写入者不在本协议的防护承诺内，异常由指纹/状态校验失败关闭。
 
 创建 `.agents/workspace/active/{task-id}/{plan-artifact}`。
 
@@ -134,11 +134,11 @@ 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` 且 `repairable=true`：仅按诊断中的 `replace-line` 操作做一次最小修改，然后完整重跑同一命令；实际字节发生变化才计一次 `repairAttempts`，最多 8 次。
-  - 首次可修复失败的 `semanticDigest` 由 finalizer 保留为基线；重试后的 `status=passed` 必须匹配该基线。基线不匹配、其他失败、无进展或重复诊断：停止，不发布 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 中存在有效的 `issue_number`，执行以下同步操作（任一失败则跳过并继续）：
+如果 task.md 中存在有效的 `platform_issue_identity`，执行以下同步操作（任一失败则跳过并继续）：
 - 调用 `agent-infra-internal platform-issue sync {task-id} --agent {standard-agent-token} --status pending-design-work --fields`
 - 调用 `agent-infra-internal platform-comment sync {task-id} --kind task --agent {standard-agent-token}`
 - 调用 `agent-infra-internal platform-comment sync {task-id} --kind artifact --artifact {plan-artifact} --agent {standard-agent-token}`

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

@@ -28,7 +28,7 @@
       ]
     },
     "platform-sync": {
-      "when": "issue_number_exists",
+      "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,

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

@@ -28,7 +28,7 @@
       ]
     },
     "platform-sync": {
-      "when": "issue_number_exists",
+      "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,

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

@@ -33,7 +33,7 @@ Comment parsing must not write the formal active directory. Step 6 declares one
 ### 1. Verify Input and Environment
 
 Check:
-- required `{issue-number}`
+- required `{issue-token}`
 - optional `{task-id}`
 - read `.agents/rules/issue-pr-commands.md` first and use its authentication commands to verify current platform access
 
@@ -41,7 +41,7 @@ If the user provided `{task-id}`, validate the `TASK-{yyyyMMdd-HHmmss}` format.
 
 ### 2. Fetch Issue Comments
 
-Run `agent-infra-internal platform-comment list --issue {issue-number}` to read all paginated comments while preserving order and comment IDs; the intent owns platform context, authentication, and upstream resolution.
+Run `agent-infra-internal platform-comment list --issue {issue-token}` to read all paginated comments while preserving order and comment IDs; the intent owns platform context, authentication, and upstream resolution.
 
 ### 3. Determine the task-id and Files to Restore
 

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

@@ -32,7 +32,7 @@ description: >
 ### 1. 验证输入与环境
 
 检查：
-- 必填参数 `{issue-number}`
+- 必填参数 `{issue-token}`
 - 可选参数 `{task-id}`
 - 执行前先读取 `.agents/rules/issue-pr-commands.md`，并按其中的认证命令验证当前平台访问能力
 
@@ -40,7 +40,7 @@ description: >
 
 ### 2. 获取 Issue 评论
 
-调用 `agent-infra-internal platform-comment list --issue {issue-number}` 读取全部分页评论，保留原始顺序和评论 ID；平台上下文、认证和 upstream 由 internal intent 处理。
+调用 `agent-infra-internal platform-comment list --issue {issue-token}` 读取全部分页评论，保留原始顺序和评论 ID；平台上下文、认证和 upstream 由 internal intent 处理。
 
 ### 3. 确定 task-id 与待恢复文件
 

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

@@ -14,7 +14,7 @@
         "assigned_to"
       ],
       "expected_status": "active",
-      "require_issue_number": true
+      "require_platform_issue_identity": true
     },
     "activity-log": {
       "expected_action_pattern": "Restore Task"

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

@@ -75,7 +75,7 @@ Before writing this round's `{review-artifact}`, create the controlled review sk
 agent-infra-internal task-artifact {task-id} init --family review-analysis --artifact {review-artifact} --locale en
 ```
 
-The skeleton contains identity metadata, stable section markers, and required headings only; complete review content is required before summary finalization. If structural finalization returns one provably safe error, call `task-artifact {task-id} repair --family review-analysis --artifact {review-artifact} --expected-sha256 {artifact-sha256} --expected-semantic-digest {semantic-digest}`, then rerun the original finalizer.
+The skeleton contains identity metadata, stable section markers, and required headings only; complete review content is required before summary finalization. If structural finalization returns one provably safe error, it returns a controlled recovery candidate; edit only its `candidatePath`, then rerun the original finalizer with the same `recoveryId`. Candidate-only is a protocol authorization boundary, not OS isolation; arbitrary same-UID host writers are outside the protocol's protection claim, and fingerprint/state checks fail closed on anomalies.
 
 Create `.agents/workspace/active/{task-id}/{review-artifact}`.
 
@@ -97,7 +97,7 @@ The intent atomically finalizes the report summary and returns the same ledger s
 
 `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`, run `agent-infra-internal platform-comment sync {task-id} --kind task --agent {standard-agent-token}`, then `agent-infra-internal platform-comment sync {task-id} --kind artifact --artifact {review-artifact} --agent {standard-agent-token}`.
+If task.md has a valid `platform_issue_identity`, run `agent-infra-internal platform-comment sync {task-id} --kind task --agent {standard-agent-token}`, then `agent-infra-internal platform-comment sync {task-id} --kind artifact --artifact {review-artifact} --agent {standard-agent-token}`.
 
 Before writing the summary, the finalization intent checks decision-detail ids; any visible duplicate returns a structured failure and preserves the artifact bytes, while the model decides whether a minimal edit is safe under the shared rule. If the safety gates fail, diagnostics repeat, no byte-level progress occurs, or the emergency cap is reached, stop before the completion event; the stop path must still show the existing review result instead of hiding the artifact.
 

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

@@ -78,7 +78,7 @@ agent-infra-internal task-snapshot {task-id} --format text
 agent-infra-internal task-artifact {task-id} init --family review-analysis --artifact {review-artifact}
 ```
 
-骨架不生成审查结论、发现或计数；完成审查内容后才能进入 summary finalizer。结构 finalizer 返回可证明的单个错误时，使用其 SHA 和 semantic digest 调用 `task-artifact {task-id} repair --family review-analysis --artifact {review-artifact} --expected-sha256 {artifact-sha256} --expected-semantic-digest {semantic-digest}`，再重跑原 finalizer。
+骨架不生成审查结论、发现或计数；完成审查内容后才能进入 summary finalizer。结构 finalizer 返回可证明的单个错误时，会返回受控 recovery candidate；只能编辑返回的 `candidatePath`，然后使用同一个 `recoveryId` 重跑原 finalizer。candidate-only 是协议授权边界，不是操作系统隔离；同 UID 的任意宿主写入者不在本协议的防护承诺内，异常由指纹/状态校验失败关闭。
 
 创建 `.agents/workspace/active/{task-id}/{review-artifact}`。
 
@@ -100,7 +100,7 @@ agent-infra-internal task-artifact {task-id} init --family review-analysis --art
 
 `manual-validation` 是 `ai task log` 中 review 行「人工校验点」（EN `Manual-validation`）计数的数据源；不要新增并行人工验证字段。
 
-如果 task.md 中存在有效的 `issue_number`，调用 `agent-infra-internal platform-comment sync {task-id} --kind task --agent {standard-agent-token}`，再调用 `agent-infra-internal platform-comment sync {task-id} --kind artifact --artifact {review-artifact} --agent {standard-agent-token}`；失败按 `.agents/rules/issue-sync.md` 记录 warning。
+如果 task.md 中存在有效的 `platform_issue_identity`，调用 `agent-infra-internal platform-comment sync {task-id} --kind task --agent {standard-agent-token}`，再调用 `agent-infra-internal platform-comment sync {task-id} --kind artifact --artifact {review-artifact} --agent {standard-agent-token}`；失败按 `.agents/rules/issue-sync.md` 记录 warning。
 
 最终化 intent 会在写入摘要前检查详情块 ID；任何可见重复都返回结构化失败并保持 artifact 字节不变，由模型按共享规则判断是否进行最小编辑。无法通过安全门、诊断重复、没有实际字节变化或达到紧急熔断时，停止在完成事件之前；停止路径仍必须展示已有审查结果，不得吞掉 artifact 内容。
 

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

@@ -27,7 +27,7 @@
       "expected_action_pattern": "(Review Analysis|Analysis Review) \\(Round \\d+\\)"
     },
     "platform-sync": {
-      "when": "issue_number_exists",
+      "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,

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

@@ -27,7 +27,7 @@
       "expected_action_pattern": "(Review Analysis|Analysis Review) \\(Round \\d+\\)"
     },
     "platform-sync": {
-      "when": "issue_number_exists",
+      "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,

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

@@ -7,7 +7,7 @@ Use this template when writing `review-analysis.md` or `review-analysis-r{N}.md`
 ## Output Template
 
 ```markdown
-# Requirement Analysis Review Report
+# Analysis Review Report
 
 - **Review Round**: Round {review-round}
 - **Artifact File**: `{review-artifact}`
@@ -16,6 +16,12 @@ Use this template when writing `review-analysis.md` or `review-analysis-r{N}.md`
 
 ## Review Summary
 
+- **Reviewer**: {reviewer-name}
+- **Review Time**: {timestamp}
+- **Scope**: {file-count and major modules}
+- **Overall Verdict**: {Approved / Changes Requested / Rejected}
+- **Findings (AI-actionable)**: {unresolved-blockers} blockers, {unresolved-major} majors, {unresolved-minor} minors / **Manual validation**: 0
+
 ## Qualification Audit Review
 
 > Use `.agents/rules/decision-qualification.md` to review the five tables: constraint dependencies, candidate qualification, classification results, upstream relations, and dependency snapshot.
@@ -40,12 +46,6 @@ Use this template when writing `review-analysis.md` or `review-analysis-r{N}.md`
 | task_input_digest | non_constraint_input_digest | upstream_artifact_digest |
 | --- | --- | --- |
 
-- **Reviewer**: {reviewer-name}
-- **Review Time**: {timestamp}
-- **Scope**: {file-count and major modules}
-- **Overall Verdict**: {Approved / Changes Requested / Rejected}
-- **Findings (AI-actionable)**: {unresolved-blockers} blockers, {unresolved-major} majors, {unresolved-minor} minors / **Manual validation**: 0
-
 ## Inspection Coverage
 
 | pass_id | scope | evidence | result | gaps_or_assumptions |

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

@@ -16,6 +16,12 @@
 
 ## 审查摘要
 
+- **审查者**：{reviewer-name}
+- **审查时间**：{timestamp}
+- **审查范围**：{file-count and major modules}
+- **总体结论**：{通过 / 需要修改 / 拒绝}
+- **发现（AI 可处理）**：{unresolved-blockers} 阻塞项，{unresolved-major} 主要，{unresolved-minor} 次要 / **人工校验**：0
+
 ## 资格审计复核
 
 > 按 `.agents/rules/decision-qualification.md` 复核：约束依赖、候选资格、分类结果、上游关系和依赖快照五张表。
@@ -40,12 +46,6 @@
 | task_input_digest | non_constraint_input_digest | upstream_artifact_digest |
 | --- | --- | --- |
 
-- **审查者**：{reviewer-name}
-- **审查时间**：{timestamp}
-- **审查范围**：{file-count and major modules}
-- **总体结论**：{通过 / 需要修改 / 拒绝}
-- **发现（AI 可处理）**：{unresolved-blockers} 阻塞项，{unresolved-major} 主要，{unresolved-minor} 次要 / **人工校验**：0
-
 ## 检视覆盖声明
 
 | pass_id | scope | evidence | result | gaps_or_assumptions |

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

@@ -102,7 +102,7 @@ Before writing this round's `{review-artifact}`, create the controlled review sk
 agent-infra-internal task-artifact {task-id} init --family review-code --artifact {review-artifact} --locale en
 ```
 
-The skeleton does not generate a verdict, findings, or counts; complete review content is required before summary finalization. If structural finalization returns one provably safe error, call `task-artifact {task-id} repair --family review-code --artifact {review-artifact} --expected-sha256 {artifact-sha256} --expected-semantic-digest {semantic-digest}`, then rerun the original finalizer.
+The skeleton does not generate a verdict, findings, or counts; complete review content is required before summary finalization. If structural finalization returns one provably safe error, it returns a controlled recovery candidate; edit only its `candidatePath`, then rerun the original finalizer with the same `recoveryId`. Candidate-only is a protocol authorization boundary, not OS isolation; arbitrary same-UID host writers are outside the protocol's protection claim, and fingerprint/state checks fail closed on anomalies.
 
 Create `.agents/workspace/active/{task-id}/{review-artifact}`.
 
@@ -130,7 +130,7 @@ Update task.md:
 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):
+If task.md contains a valid `platform_issue_identity`, perform these sync actions (skip and continue on any failure):
 - Run `agent-infra-internal platform-issue sync {task-id} --agent {standard-agent-token} --status in-progress`
 - Run `agent-infra-internal platform-comment sync {task-id} --kind task --agent {standard-agent-token}`
 - Run `agent-infra-internal platform-comment sync {task-id} --kind artifact --artifact {review-artifact} --agent {standard-agent-token}`

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

@@ -101,7 +101,7 @@ agent-infra-internal task-snapshot {task-id} --format text
 agent-infra-internal task-artifact {task-id} init --family review-code --artifact {review-artifact}
 ```
 
-骨架不生成审查结论、发现或计数；完成审查内容后才能进入 summary finalizer。结构 finalizer 返回可证明的单个错误时，使用其 SHA 和 semantic digest 调用 `task-artifact {task-id} repair --family review-code --artifact {review-artifact} --expected-sha256 {artifact-sha256} --expected-semantic-digest {semantic-digest}`，再重跑原 finalizer。
+骨架不生成审查结论、发现或计数；完成审查内容后才能进入 summary finalizer。结构 finalizer 返回可证明的单个错误时，会返回受控 recovery candidate；只能编辑返回的 `candidatePath`，然后使用同一个 `recoveryId` 重跑原 finalizer。candidate-only 是协议授权边界，不是操作系统隔离；同 UID 的任意宿主写入者不在本协议的防护承诺内，异常由指纹/状态校验失败关闭。
 
 创建 `.agents/workspace/active/{task-id}/{review-artifact}`。
 
@@ -128,7 +128,7 @@ agent-infra-internal task-artifact {task-id} init --family review-code --artifac
 完成日志必须始终写入 `Manual-validation: {n}` 字段，0 也保留。
 `manual-validation` 是 `ai task log` 中 review 行「人工校验点」（EN `Manual-validation`）计数的数据源；不要新增并行人工验证字段。
 
-如果 task.md 中存在有效的 `issue_number`，执行以下同步操作（任一失败则跳过并继续）：
+如果 task.md 中存在有效的 `platform_issue_identity`，执行以下同步操作（任一失败则跳过并继续）：
 - 调用 `agent-infra-internal platform-issue sync {task-id} --agent {standard-agent-token} --status in-progress`
 - 调用 `agent-infra-internal platform-comment sync {task-id} --kind task --agent {standard-agent-token}`
 - 调用 `agent-infra-internal platform-comment sync {task-id} --kind artifact --artifact {review-artifact} --agent {standard-agent-token}`

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

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

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

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

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

@@ -16,6 +16,18 @@ Use this template when writing `review-code.md` or `review-code-r{N}.md`.
 
 ## Review Summary
 
+- **Reviewer**: {reviewer-name}
+- **Review Time**: {timestamp}
+- **Scope**: {file-count and major modules}
+- **Review Target Commit**: {target branch SHA M read once from the task-bound remote/base at review start; never overwritten by a later live target}
+- **Reviewed Head**: {local HEAD R captured once for this round; must equal this round's HEAD}
+- **Review Baseline Commit**: {compatibility display of R; must equal Reviewed Head}
+- **Reviewed Diff Base**: {D used for the complete diff/fingerprint; must equal merge-base(R, saved M)}
+- **Reviewed Diff Fingerprint**: {fingerprint field from git-workflow snapshot}
+- **Reviewed Snapshot Tree**: {tree field from git-workflow snapshot}
+- **Overall Verdict**: {Approved / Changes Requested / Rejected}
+- **Findings (AI-actionable)**: {unresolved-blockers} blockers, {unresolved-major} majors, {unresolved-minor} minors / **Manual validation**: 0
+
 ## Qualification Audit Review
 
 > Use `.agents/rules/decision-qualification.md` to review the five tables: constraint dependencies, candidate qualification, classification results, upstream relations, and dependency snapshot.
@@ -40,18 +52,6 @@ Use this template when writing `review-code.md` or `review-code-r{N}.md`.
 | task_input_digest | non_constraint_input_digest | upstream_artifact_digest |
 | --- | --- | --- |
 
-- **Reviewer**: {reviewer-name}
-- **Review Time**: {timestamp}
-- **Scope**: {file-count and major modules}
-- **Review Target Commit**: {target branch SHA M read once from the task-bound remote/base at review start; never overwritten by a later live target}
-- **Reviewed Head**: {local HEAD R captured once for this round; must equal this round's HEAD}
-- **Review Baseline Commit**: {compatibility display of R; must equal Reviewed Head}
-- **Reviewed Diff Base**: {D used for the complete diff/fingerprint; must equal merge-base(R, saved M)}
-- **Reviewed Diff Fingerprint**: {fingerprint field from git-workflow snapshot}
-- **Reviewed Snapshot Tree**: {tree field from git-workflow snapshot}
-- **Overall Verdict**: {Approved / Changes Requested / Rejected} (pick exactly one; combined phrases will fail the verify gate)
-- **Findings (AI-actionable)**: {unresolved-blockers} blockers, {unresolved-major} majors, {unresolved-minor} minors / **Manual validation**: 0
-
 ## Inspection Coverage
 
 | pass_id | scope | evidence | result | gaps_or_assumptions |

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

@@ -16,6 +16,18 @@
 
 ## 审查摘要
 
+- **审查者**：{reviewer-name}
+- **审查时间**：{timestamp}
+- **审查范围**：{file-count and major modules}
+- **审查目标提交**：{本轮一次性从任务绑定 remote/base 读取的目标分支 SHA M；不可被后续实时目标覆盖}
+- **审查已检视提交**：{本轮一次性捕获的本地 HEAD R；必须等于本轮 HEAD}
+- **审查基线提交**：{R 的兼容显示字段；必须与审查已检视提交相同}
+- **审查差异基线**：{用于完整 diff/fingerprint 的 D；必须等于 merge-base(R, saved M)}
+- **审查差异指纹**：{git-workflow snapshot 输出的 fingerprint 字段}
+- **审查快照树**：{git-workflow snapshot 输出的 tree 字段}
+- **总体结论**：{通过 / 需要修改 / 拒绝}
+- **发现（AI 可处理）**：{unresolved-blockers} 阻塞项，{unresolved-major} 主要，{unresolved-minor} 次要 / **人工校验**：0
+
 ## 资格审计复核
 
 > 按 `.agents/rules/decision-qualification.md` 复核：约束依赖、候选资格、分类结果、上游关系和依赖快照五张表。
@@ -40,18 +52,6 @@
 | task_input_digest | non_constraint_input_digest | upstream_artifact_digest |
 | --- | --- | --- |
 
-- **审查者**：{reviewer-name}
-- **审查时间**：{timestamp}
-- **审查范围**：{file-count and major modules}
-- **审查目标提交**：{本轮一次性从任务绑定 remote/base 读取的目标分支 SHA M；不可被后续实时目标覆盖}
-- **审查已检视提交**：{本轮一次性捕获的本地 HEAD R；必须等于本轮 HEAD}
-- **审查基线提交**：{R 的兼容显示字段；必须与审查已检视提交相同}
-- **审查差异基线**：{用于完整 diff/fingerprint 的 D；必须等于 merge-base(R, saved M)}
-- **审查差异指纹**：{git-workflow snapshot 输出的 fingerprint 字段}
-- **审查快照树**：{git-workflow snapshot 输出的 tree 字段}
-- **总体结论**：{通过 / 需要修改 / 拒绝}（恰取一个；禁止写组合短语，否则 verify gate 失败）
-- **发现（AI 可处理）**：{unresolved-blockers} 阻塞项，{unresolved-major} 主要，{unresolved-minor} 次要 / **人工校验**：0
-
 ## 检视覆盖声明
 
 | pass_id | scope | evidence | result | gaps_or_assumptions |

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

@@ -75,7 +75,7 @@ Before writing this round's `{review-artifact}`, create the controlled review sk
 agent-infra-internal task-artifact {task-id} init --family review-plan --artifact {review-artifact} --locale en
 ```
 
-The skeleton contains identity metadata, stable section markers, and required headings only; complete review content is required before summary finalization. If structural finalization returns one provably safe error, call `task-artifact {task-id} repair --family review-plan --artifact {review-artifact} --expected-sha256 {artifact-sha256} --expected-semantic-digest {semantic-digest}`, then rerun the original finalizer.
+The skeleton contains identity metadata, stable section markers, and required headings only; complete review content is required before summary finalization. If structural finalization returns one provably safe error, it returns a controlled recovery candidate; edit only its `candidatePath`, then rerun the original finalizer with the same `recoveryId`. Candidate-only is a protocol authorization boundary, not OS isolation; arbitrary same-UID host writers are outside the protocol's protection claim, and fingerprint/state checks fail closed on anomalies.
 
 Create `.agents/workspace/active/{task-id}/{review-artifact}`.
 
@@ -97,7 +97,7 @@ The intent atomically finalizes the report summary and returns the same ledger s
 
 `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`, run `agent-infra-internal platform-comment sync {task-id} --kind task --agent {standard-agent-token}`, then `agent-infra-internal platform-comment sync {task-id} --kind artifact --artifact {review-artifact} --agent {standard-agent-token}`.
+If task.md has a valid `platform_issue_identity`, run `agent-infra-internal platform-comment sync {task-id} --kind task --agent {standard-agent-token}`, then `agent-infra-internal platform-comment sync {task-id} --kind artifact --artifact {review-artifact} --agent {standard-agent-token}`.
 
 Before writing the summary, the finalization intent checks decision-detail ids; any visible duplicate returns a structured failure and preserves the artifact bytes, while the model decides whether a minimal edit is safe under the shared rule. If the safety gates fail, diagnostics repeat, no byte-level progress occurs, or the emergency cap is reached, stop before the completion event; the stop path must still show the existing review result instead of hiding the artifact.
 

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

@@ -78,7 +78,7 @@ agent-infra-internal task-snapshot {task-id} --format text
 agent-infra-internal task-artifact {task-id} init --family review-plan --artifact {review-artifact}
 ```
 
-骨架不生成审查结论、发现或计数；完成审查内容后才能进入 summary finalizer。结构 finalizer 返回可证明的单个错误时，使用其 SHA 和 semantic digest 调用 `task-artifact {task-id} repair --family review-plan --artifact {review-artifact} --expected-sha256 {artifact-sha256} --expected-semantic-digest {semantic-digest}`，再重跑原 finalizer。
+骨架不生成审查结论、发现或计数；完成审查内容后才能进入 summary finalizer。结构 finalizer 返回可证明的单个错误时，会返回受控 recovery candidate；只能编辑返回的 `candidatePath`，然后使用同一个 `recoveryId` 重跑原 finalizer。candidate-only 是协议授权边界，不是操作系统隔离；同 UID 的任意宿主写入者不在本协议的防护承诺内，异常由指纹/状态校验失败关闭。
 
 创建 `.agents/workspace/active/{task-id}/{review-artifact}`。
 
@@ -100,7 +100,7 @@ agent-infra-internal task-artifact {task-id} init --family review-plan --artifac
 
 `manual-validation` 是 `ai task log` 中 review 行「人工校验点」（EN `Manual-validation`）计数的数据源；不要新增并行人工验证字段。
 
-如果 task.md 中存在有效的 `issue_number`，调用 `agent-infra-internal platform-comment sync {task-id} --kind task --agent {standard-agent-token}`，再调用 `agent-infra-internal platform-comment sync {task-id} --kind artifact --artifact {review-artifact} --agent {standard-agent-token}`；失败按 `.agents/rules/issue-sync.md` 记录 warning。
+如果 task.md 中存在有效的 `platform_issue_identity`，调用 `agent-infra-internal platform-comment sync {task-id} --kind task --agent {standard-agent-token}`，再调用 `agent-infra-internal platform-comment sync {task-id} --kind artifact --artifact {review-artifact} --agent {standard-agent-token}`；失败按 `.agents/rules/issue-sync.md` 记录 warning。
 
 最终化 intent 会在写入摘要前检查详情块 ID；任何可见重复都返回结构化失败并保持 artifact 字节不变，由模型按共享规则判断是否进行最小编辑。无法通过安全门、诊断重复、没有实际字节变化或达到紧急熔断时，停止在完成事件之前；停止路径仍必须展示已有审查结果，不得吞掉 artifact 内容。
 

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

@@ -27,7 +27,7 @@
       "expected_action_pattern": "(Review Plan|Plan Review) \\(Round \\d+\\)"
     },
     "platform-sync": {
-      "when": "issue_number_exists",
+      "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,

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

@@ -27,7 +27,7 @@
       "expected_action_pattern": "(Review Plan|Plan Review) \\(Round \\d+\\)"
     },
     "platform-sync": {
-      "when": "issue_number_exists",
+      "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,

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

@@ -7,7 +7,7 @@ Use this template when writing `review-plan.md` or `review-plan-r{N}.md`.
 ## Output Template
 
 ```markdown
-# Technical Plan Review Report
+# Plan Review Report
 
 - **Review Round**: Round {review-round}
 - **Artifact File**: `{review-artifact}`
@@ -16,6 +16,12 @@ Use this template when writing `review-plan.md` or `review-plan-r{N}.md`.
 
 ## Review Summary
 
+- **Reviewer**: {reviewer-name}
+- **Review Time**: {timestamp}
+- **Scope**: {file-count and major modules}
+- **Overall Verdict**: {Approved / Changes Requested / Rejected}
+- **Findings (AI-actionable)**: {unresolved-blockers} blockers, {unresolved-major} majors, {unresolved-minor} minors / **Manual validation**: 0
+
 ## Qualification Audit Review
 
 > Use `.agents/rules/decision-qualification.md` to review the five tables: constraint dependencies, candidate qualification, classification results, upstream relations, and dependency snapshot.
@@ -40,12 +46,6 @@ Use this template when writing `review-plan.md` or `review-plan-r{N}.md`.
 | task_input_digest | non_constraint_input_digest | upstream_artifact_digest |
 | --- | --- | --- |
 
-- **Reviewer**: {reviewer-name}
-- **Review Time**: {timestamp}
-- **Scope**: {file-count and major modules}
-- **Overall Verdict**: {Approved / Changes Requested / Rejected}
-- **Findings (AI-actionable)**: {unresolved-blockers} blockers, {unresolved-major} majors, {unresolved-minor} minors / **Manual validation**: 0
-
 ## Inspection Coverage
 
 | pass_id | scope | evidence | result | gaps_or_assumptions |

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

@@ -7,7 +7,7 @@
 ## 输出模板
 
 ```markdown
-# 代码审查报告
+# 技术方案审查报告
 
 - **审查轮次**：第 {review-round} 轮
 - **产物文件**：`{review-artifact}`
@@ -16,6 +16,12 @@
 
 ## 审查摘要
 
+- **审查者**：{reviewer-name}
+- **审查时间**：{timestamp}
+- **审查范围**：{file-count and major modules}
+- **总体结论**：{通过 / 需要修改 / 拒绝}
+- **发现（AI 可处理）**：{unresolved-blockers} 阻塞项，{unresolved-major} 主要，{unresolved-minor} 次要 / **人工校验**：0
+
 ## 资格审计复核
 
 > 按 `.agents/rules/decision-qualification.md` 复核：约束依赖、候选资格、分类结果、上游关系和依赖快照五张表。
@@ -40,12 +46,6 @@
 | task_input_digest | non_constraint_input_digest | upstream_artifact_digest |
 | --- | --- | --- |
 
-- **审查者**：{reviewer-name}
-- **审查时间**：{timestamp}
-- **审查范围**：{file-count and major modules}
-- **总体结论**：{通过 / 需要修改 / 拒绝}
-- **发现（AI 可处理）**：{unresolved-blockers} 阻塞项，{unresolved-major} 主要，{unresolved-minor} 次要 / **人工校验**：0
-
 ## 检视覆盖声明
 
 | pass_id | scope | evidence | result | gaps_or_assumptions |

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

@@ -24,7 +24,7 @@
       "expected_action_pattern": "Review PR \\(Round \\d+\\)"
     },
     "platform-sync": {
-      "when": "issue_number_exists",
+      "when": "platform_issue_identity_exists",
       "expected_comment_marker": "<!-- sync-issue:{task-id}:{artifact-stem} -->",
       "verify_comment_content": true,
       "verify_task_comment_content": true,

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

@@ -24,7 +24,7 @@
       "expected_action_pattern": "Review PR \\(Round \\d+\\)"
     },
     "platform-sync": {
-      "when": "issue_number_exists",
+      "when": "platform_issue_identity_exists",
       "expected_comment_marker": "<!-- sync-issue:{task-id}:{artifact-stem} -->",
       "verify_comment_content": true,
       "verify_task_comment_content": true,

package/templates/.agents/skills/review-pr/reference/evidence-grading.en.md

@@ -17,13 +17,13 @@ Evidence scenario classification (S1/S2/S3) → freshness/alignment → risk gra
 
 - Exactly one hit → `unique`; multiple without a unique winner → `ambiguous` (candidate list); zero hits → `none`.
 - Ambiguous hosts fail closed and never enter evidence classification. `pr-review-grade resolve-host --pr <N>` returns a typed `HostResolution`, and `decide` explicitly rejects `ambiguous`.
-- `Closes/Fixes #N` in the PR body (case-insensitive, comma/space separated, lists supported) is parsed by `extractClosingIssueNumbers`; a local `active/*/task.md` verified `pr_delivery_fact.identity.number` hit takes priority over the `issue_number` reverse lookup, and a task hit via both paths deduplicates to a single candidate.
+- `Closes/Fixes #N` in the PR body (case-insensitive, comma/space separated, lists supported) is parsed by `extractClosingIssueNumbers`; a local `active/*/task.md` canonical `platform_issue_identity` numeric projection and verified `pr_delivery_fact.identity.number` are used for matching, and a task hit via both paths deduplicates to a single candidate.
 
 ## Evidence Scenario Classification (S1 → S2 → S3)
 
 | Scenario | Criteria |
 |----------|----------|
-| S1 complete & trusted | unique task with matching issue_number + complete `analysis`/`plan`/`code` and all three review families + latest `pr-review*` reviewed head == current head + trusted source |
+| S1 complete & trusted | unique task with a canonical Issue identity whose numeric projection matches + complete `analysis`/`plan`/`code` and all three review families + latest `pr-review*` reviewed head == current head + trusted source |
 | S2 partial / suspect | task exists but key artifacts are missing, or the head drifted, or the source is untrusted / cannot prove alignment with the current head |
 | S3 PR-only | no host; or unique task with no lifecycle artifacts at all and no prior `pr-review*` |
 
@@ -33,7 +33,7 @@ Evidence scenario classification (S1/S2/S3) → freshness/alignment → risk gra
 ## Freshness and Alignment
 
 - Freshness benchmark = the reviewed head SHA recorded by the latest `pr-review*`, compared character-for-character with the current head: match → `fresh`, otherwise → `stale`.
-- Alignment = freshness is `fresh` and the `issue_number` / verified `pr_delivery_fact.identity.number` match the resolution result.
+- Alignment = freshness is `fresh` and the canonical Issue identity numeric projection / verified `pr_delivery_fact.identity.number` match the resolution result.
 - No prior `pr-review*` → `n/a` / `n/a` (first-review special case).
 
 ## Risk Grading (pure evidence)

package/templates/.agents/skills/review-pr/reference/evidence-grading.zh-CN.md

@@ -17,13 +17,13 @@
 
 - 唯一命中 → `unique`；多个且无法唯一 → `ambiguous`（候选列表）；零命中 → `none`。
 - 多宿主歧义即 fail closed：不进入证据分类；由 `pr-review-grade resolve-host --pr <N>` 返回 typed `HostResolution`，`decide` 对 `ambiguous` 显式拒绝。
-- PR body 的 `Closes/Fixes #N`（大小写不敏感、逗号/空格分隔、支持列表）经 `extractClosingIssueNumbers` 解析；本地 `active/*/task.md` 的 verified `pr_delivery_fact.identity.number` 命中优先于 `issue_number` 反查，同一任务经两条路径命中按单候选去重。
+- PR body 的 `Closes/Fixes #N`（大小写不敏感、逗号/空格分隔、支持列表）经 `extractClosingIssueNumbers` 解析；本地 `active/*/task.md` 的 canonical `platform_issue_identity` numeric projection 与 verified `pr_delivery_fact.identity.number` 用于匹配，同一任务按单候选去重。
 
 ## 证据场景分类（S1 → S2 → S3）
 
 | 场景 | 判据 |
 |------|------|
-| S1 完整可信 | 唯一任务且 issue_number 与远端一致 + `analysis`/`plan`/`code` 及三族 review 齐全 + 最新 `pr-review*` 被审 head == 当前 head + 来源受信 |
+| S1 完整可信 | 唯一任务且 canonical Issue identity 的 numeric projection 与远端一致 + `analysis`/`plan`/`code` 及三族 review 齐全 + 最新 `pr-review*` 被审 head == 当前 head + 来源受信 |
 | S2 部分/可疑 | 任务存在但 artifact 缺失关键产物，或 head 漂移，或来源不可信 / 无法证明与当前 head 对齐 |
 | S3 仅 PR | 无宿主；或任务唯一但无任何生命周期 artifact 且无先前 `pr-review*` |
 
@@ -33,7 +33,7 @@
 ## 新鲜度与对齐
 
 - 新鲜度基准 = 上一轮 `pr-review*` 记录的被审 head SHA，与当前 head 逐字符比对：一致 → `fresh`，否则 → `stale`。
-- 对齐 = freshness 为 fresh 且 `issue_number` / verified `pr_delivery_fact.identity.number` 与解析结果一致。
+- 对齐 = freshness 为 fresh 且 canonical Issue identity 的 numeric projection / verified `pr_delivery_fact.identity.number` 与解析结果一致。
 - 无先前 `pr-review*` → `n/a` / `n/a`（首轮特例）。
 
 ## 风险分级（纯证据口径）

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

@@ -12,7 +12,7 @@
     "activity-log": { "expected_action_pattern": "Run Manual Validation \\(Round \\d+\\)" },
     "review-ledger": { "stage_scope": ["analysis", "plan", "code"] },
     "platform-sync": {
-      "when": "issue_number_exists",
+      "when": "platform_issue_identity_exists",
       "expected_comment_marker": "<!-- sync-issue:{task-id}:{artifact-stem} -->",
       "verify_comment_content": true,
       "verify_task_comment_content": true,