@fitlab-ai/agent-infra 0.9.3 → 0.9.5

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

@@ -17,7 +17,7 @@ description: >
 - 不要执行需求分析；分析由 `analyze-task` 独立完成
 - 不要直接实现所描述的功能
 - 不要跳过工作流直接进入计划/实现阶段
-- 仅执行：解析描述 -> 创建任务文件 -> 更新任务状态 -> 按 `.agents/rules/create-issue.md` 级联尝试创建 Issue -> 告知用户下一步
+- 仅执行：解析描述 -> 一次性生成结构化 candidate -> 调用宿主 `task-create` 入口 -> 校验结果 -> 告知用户下一步
 - Issue 创建由 `.agents/rules/create-issue.md` 规则决定；自定义或空平台（未提供平台变体规则文件）时，规则会自然降级为 no-op
 
 用户的描述是一个**待办事项**，而不是**立即执行的指令**。
@@ -71,7 +71,7 @@ description: >
 - `bugfix` -> `bug-fix`
 - `refactor` -> `refactoring`
 
-### 2. 创建任务目录和文件
+### 2. 生成不可变 candidate
 
 获取当前时间戳：
 
@@ -79,14 +79,17 @@ description: >
 date +%Y%m%d-%H%M%S
 ```
 
-- 创建任务目录：`.agents/workspace/active/TASK-{yyyyMMdd-HHmmss}/`
-- 使用 `.agents/templates/task.md` 模板创建任务文件：`task.md`
-- 将步骤 1 捕获的结构化上下文写入 `## 任务输入`，确保任务文件脱离原会话后仍可理解
+- 生成随机 UUID v4 作为 `idempotencyKey`，并把步骤 1 的结果写入单个 JSON 文件。
+- candidate 必须符合宿主 `TaskCreateCandidateV1`：`version`、`idempotencyKey`、标准 `agent`、`title`、`type`、不带项目前缀的 `branchSlug`、`priority`、`effort`、`description` 和 `taskInput` 七类列表。
+- 首次提交前只写一次 candidate；等待终态期间不得重新运行 AI 推导或改写文件。超时重试必须复用同一文件，由客户端生成新的 outer request ID。
 
-**重要**：
-- 目录命名：`TASK-{yyyyMMdd-HHmmss}`（**必须**包含 `TASK-` 前缀）
-- 示例：`TASK-20260306-143022`
-- 任务 ID = 目录名
+调用统一入口：
+
+```bash
+agent-infra-internal task-create --input "$candidate_file"
+```
+
+宿主负责 TASK-id/时间戳/版本戳、workflow/branch 派生、模板渲染、原子持久化、短号、Issue 与 warning。技能不得自行 `mkdir`、复制任务模板、分配短号或直接调用平台子命令。
 
 任务元数据（task.md YAML front matter）：
 ```yaml
@@ -108,7 +111,7 @@ assigned_to: {当前 AI 代理}
 
 priority / effort 必填：由 AI 从任务标题与描述推断后填入（候选值见 `.agents/rules/issue-fields.md`；中文输入按本地化映射规范化）。start_date / target_date 创建时保持留空：`start_date` 由 analyze 阶段写入、`target_date` 由 complete 阶段写入；不要臆测日期。
 
-### 3. 更新任务状态
+### 3. 处理结构化结果
 
 获取当前时间：
 
@@ -116,43 +119,25 @@ priority / effort 必填：由 AI 从任务标题与描述推断后填入（候
 date "+%Y-%m-%d %H:%M:%S%z" | sed 's/\([+-][0-9][0-9]\)\([0-9][0-9]\)$/\1:\2/'
 ```
 
-更新 `.agents/workspace/active/{task-id}/task.md`：
-- `current_step`：requirement-analysis
-- `assigned_to`：{当前 AI 代理}
-- `updated_at`：{当前时间}
-- `agent_infra_version`：按 `.agents/rules/version-stamp.md` 取值
-- `## 上下文` 中的 `- **分支**：`：更新为生成的分支名
-- **追加**到 `## Activity Log`（不要覆盖之前的记录）：
-  ```
-  - {YYYY-MM-DD HH:mm:ss±HH:MM} — **Create Task** by {agent} — Task created from description
-  ```
+- `applied` / `no-op`：从响应读取 task ID、短号与可选 Issue 身份；不得从目录扫描推断。
+- `degraded`：本地任务已经保留；展示响应中的 warning。
+- `blocked`：保留 candidate 文件，修复暂态问题后用同一文件重试。
+- `failed`：报告稳定错误码；幂等冲突时不得改写原 key 或原 candidate 后重试。
 
-### 4. 级联创建并同步 Issue
+### 4. 平台失败兼容说明
 
-在 task.md 落盘并记录 `Create Task` 后调用声明式 Issue intent；标题、正文、模板、身份校验、权限降级、幂等创建和 task.md 绑定均由 internal core 处理：
+平台级联由宿主服务完成。兼容的人工恢复命令仍由宿主 warning 指引，不在沙箱内执行：
 
 ```bash
-agent-infra-internal platform-issue create {task-id} --agent {standard-agent-token}
-agent-infra-internal platform-issue sync {task-id} --agent {standard-agent-token} --status waiting-for-triage --assignees current --milestone initial --issue-type --fields
+agent-infra-internal task-warning {task-id} add --step create-task --severity ACTION_REQUIRED --code ISSUE_CREATE_FAILED --target issue --message "{error_code}: {error_message}" --action "修复认证/网络/模板问题后手动重试 Issue 创建，或手动创建/找到 Issue 后写入 issue_number"
+agent-infra-internal platform-comment sync {task-id} --kind task --agent {standard-agent-token}
 ```
 
-处理结果：
-- intent 成功创建 Issue：`issue_number` 已由任务写入内核回写；调用 `agent-infra-internal platform-comment sync {task-id} --kind task --agent {standard-agent-token}`
-- 规则失败（认证 / 网络 / 模板解析等）：不回滚 task.md；不追加额外 Activity Log；先调用 `agent-infra-internal task-warning {task-id} add --step create-task --severity ACTION_REQUIRED --code ISSUE_CREATE_FAILED --target issue --message "{error_code}: {error_message}" --action "修复认证/网络/模板问题后手动重试 Issue 创建，或手动创建/找到 Issue 后写入 issue_number"` 提交结构化 warning 意图（调用方不分配编号或写表格）；再按"场景 C：Issue 创建失败"输出
-- intent 为 no-op/degraded：按结构化 operations 继续可执行部分；自定义或空平台不创建评论且不阻塞工作流
-- task.md 已存在有效 `issue_number`：create intent 校验绑定后返回 no-op，不重复创建
+技能只消费宿主返回的 Issue identity、operations 与 warnings；不得重复发起平台写入。
 
 ### 5. 完成校验
 
-**先调用短号分配**（保证注册表 entry 已分配；完成校验阶段会读取）：
-
-```bash
-node .agents/scripts/task-short-id.js alloc "$task_id"
-```
-
-如失败（退出码非 0），按提示「归档若干任务」或「调高 task.shortIdLength」处理；不要继续执行后续步骤。
-
-运行完成校验，确认任务产物和同步状态符合规范：
+宿主 `task-create` 服务在返回前运行同一 typed 完成校验；技能从响应的 `task:verify` operation 取得当次结果。branch-only 不得尝试读取不可见的新任务。宿主直接诊断时可运行：
 
 ```bash
 agent-infra-internal task-verify {task-id} create-task.completed --format text
@@ -243,12 +228,10 @@ Issue 创建失败：
 
 ## 完成检查清单
 
-- [ ] 创建了任务文件 `.agents/workspace/active/{task-id}/task.md`
+- [ ] 只生成一次结构化 candidate 并调用 `agent-infra-internal task-create`
+- [ ] 宿主创建了任务文件 `.agents/workspace/active/{task-id}/task.md`
 - [ ] 已按 `reference/context-capture.md` 写入并复核 `## 任务输入` 的来源与状态语义
-- [ ] 更新了 task.md 中的 `current_step` 为 requirement-analysis
-- [ ] 更新了 task.md 中的 `updated_at` 为当前时间
-- [ ] 更新了 task.md 中的 `assigned_to`
-- [ ] 追加了 Activity Log 条目到 task.md
+- [ ] 响应中的任务 ID 和短号已通过完成校验
 - [ ] 已按 `.agents/rules/create-issue.md` 尝试级联创建 Issue；失败时保留 task.md 并记录原因
 - [ ] 已通过统一 helper 渲染已选场景的下一步命令
 - [ ] **没有修改任何业务代码或配置文件**

package/templates/.agents/skills/create-task/reference/context-capture.en.md

@@ -18,6 +18,40 @@ Faithfully condense existing information into task.md under `## Task Input`:
 
 Leave missing categories empty rather than inferring content. Deduplicate repeated information without losing its source or state.
 
+## Observable Acceptance Extraction
+
+The following language-neutral contract is the stable boundary for capturing observable acceptance information:
+
+```text
+# observable-acceptance-contract
+sources: current-request,necessary-prior-discussion
+scan-entire-visible-context: true
+recognize-without-acceptance-label: true
+components: observable-input,action,expected-result
+combine-distributed-evidence: true
+preserve-source-state: true
+missing-components: preserve-as-gaps
+agent-inference-as-confirmed: false
+destination: task-input.acceptance-criteria
+scenario-explicit: capture-supported-components
+scenario-distributed: combine-supported-components
+scenario-insufficient: preserve-supported-components-and-gaps
+```
+
+Execution order:
+
+1. Scan the complete visible context of the current request and necessary prior discussion. Recognize observable information even when the user did not label it as acceptance criteria.
+2. Identify observable inputs, user or system actions, and expected results. These components may be distributed across turns.
+3. Combine supported components that describe the same behavior into a self-contained item, preserving the source and confirmation state of each piece of information.
+4. Preserve unexpressed components as gaps. Do not invent thresholds, scenarios, actions, or results, and do not mark agent inference as user-confirmed information.
+5. Write the items under `## Task Input / ### Acceptance Criteria`. If the context provides no observable criterion, leave that category empty and retain genuine unknowns in the existing categories.
+
+Boundary examples:
+
+- **Single-turn explicit information**: when the current request provides an input, action, and result, capture every supported component and identify the current request as its source.
+- **Distributed information**: when the current request describes an action and necessary prior discussion provides an input or result, combine only components for the same behavior and preserve their source states separately.
+- **Insufficient information**: when the user only says that something "should be faster" without an observable condition or threshold, do not invent a performance target; preserve the stated concern and gaps, leaving the acceptance category empty when no criterion can be formed.
+
 ## Safety and Compression
 
 - Exclude secrets, tokens, credentials, and unrelated personal information.

package/templates/.agents/skills/create-task/reference/context-capture.zh-CN.md

@@ -18,6 +18,40 @@
 
 缺失类别保持为空，不推导补齐。相同信息去重，但不得丢失来源或状态语义。
 
+## 可观察验收提取
+
+以下语言无关契约是可观察验收信息的稳定捕获边界：
+
+```text
+# observable-acceptance-contract
+sources: current-request,necessary-prior-discussion
+scan-entire-visible-context: true
+recognize-without-acceptance-label: true
+components: observable-input,action,expected-result
+combine-distributed-evidence: true
+preserve-source-state: true
+missing-components: preserve-as-gaps
+agent-inference-as-confirmed: false
+destination: task-input.acceptance-criteria
+scenario-explicit: capture-supported-components
+scenario-distributed: combine-supported-components
+scenario-insufficient: preserve-supported-components-and-gaps
+```
+
+执行顺序：
+
+1. 扫描当前请求及必要前序讨论的完整可见上下文；即使用户没有使用“验收标准”标签，也要识别其中的可观察信息。
+2. 找出可观察输入、用户或系统执行的动作以及预期结果。这些组成可以分散在不同轮次。
+3. 将描述同一行为且有上下文证据的组成合并为自足条目，并保留每项信息的来源和确认状态。
+4. 未表达的组成保持为缺口；不得补造阈值、场景、动作或结果，也不得把 Agent 推导标记为用户已确认。
+5. 将条目写入 `## 任务输入 / ### 验收标准`。如果上下文没有提供可观察标准，该分类保持为空，真实的待确认信息继续保留在既有分类中。
+
+边界样例：
+
+- **单轮显式信息**：当前请求同时给出输入、动作和结果时，捕获全部有证据的组成并注明来自当前请求。
+- **跨轮分散信息**：当前请求描述动作、必要前序讨论提供输入或结果时，只合并属于同一行为的组成，并分别保留来源状态。
+- **信息不足**：用户只说“应该更快”但没有可观察条件或阈值时，不得编造性能目标；保留已表达的关注点和缺口，无法形成标准则让验收分类为空。
+
 ## 安全与压缩
 
 - 排除密钥、Token、凭据和与任务无关的个人信息。

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

@@ -97,7 +97,7 @@ 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}`. Do not scan ids or edit ledger rows
+- 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, call `agent-infra-internal task-review {task-id} finalize-summary --stage code --artifact {review-artifact} {execution-flag}` exactly once
 
   Bind and reuse this structured mapping from that one response:
@@ -110,7 +110,7 @@ Update task.md:
 
   The intent atomically finalizes the report summary and returns the same ledger snapshot. Do not call `stage-status`, replace placeholders manually, or rescan the finding list. If finalization fails or a response field is missing, stop before the completion event. Derive the verdict and next-step branch from the same response's `stageStatus.canAdvance`; only `canAdvance=true` permits Approved
 - Only when `canAdvance=true`, the verdict is Approved, and `T == R^{tree}`, write `last_reviewed_commit: {R}`. Clear an old value for an Approved snapshot with uncommitted differences; otherwise preserve the existing value and do not advance it
-- For an Approved exit, collect PR and required-checks facts as defined in `reference/output-templates.md`: route uncommitted/unpushed code to `commit`, no PR to `create-pr` (except no-PR flow), non-terminal checks to `watch-pr`, and route to `complete-task` only when `HEAD == last_reviewed_commit == PR head` with checks `passed|no-required`; never route by review round alone
+- For an Approved exit, collect PR and all-check facts as defined in `reference/output-templates.md`: route uncommitted/unpushed code to `commit`, no PR to `create-pr` (except no-PR flow), non-terminal checks to `watch-pr`, and route to `complete-task` only when `HEAD == last_reviewed_commit == PR head` with checks `passed|no-required`; never route by review round alone
 - After handling `last_reviewed_commit`, run `agent-infra-internal task-event {task-id} review-code.completed --agent {standard-agent-token} --artifact {review-artifact} --verdict {approved|changes-requested|rejected} --blockers {unresolved-blockers} --major {unresolved-major} --minor {unresolved-minor} --manual-validation {n} {execution-flag}`
 
 Always include the `Manual-validation: {n}` field in the done log, including when it is 0.

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

@@ -95,7 +95,7 @@ agent-infra-internal task-snapshot {task-id} --format text
 
 ### 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 {相称证据}`。不得扫描编号或手写账本行
+- 报告完成后，新 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}`
 
   从该次返回值绑定并复用以下结构化映射：
@@ -108,7 +108,7 @@ agent-infra-internal task-snapshot {task-id} --format text
 
   该 intent 原子最终化报告摘要并返回同一次账本快照；不得再调用 `stage-status`、手工替换占位符或扫描问题清单。最终化失败或返回字段缺失时，停止在完成事件之前。以同一次返回的 `stageStatus.canAdvance` 决定 verdict 和下一步；仅 `canAdvance=true` 可用 Approved
 - 仅当 `canAdvance=true`、本轮结论为 Approved 且 `T == R^{tree}` 时写入 `last_reviewed_commit: {R}`；Approved 快照包含未提交差异时清除旧值。否则保留既有值，不得推进或清空
-- Approved 出口继续按 `reference/output-templates.md` 采集 PR 与 required-checks 事实：未提交/未推送走 `commit`，无 PR 走 `create-pr`（无 PR 流程除外），checks 未终态走 `watch-pr`，仅 `HEAD == last_reviewed_commit == PR head` 且 checks 为 `passed|no-required` 时走 `complete-task`；不得仅按审查轮次分流
+- Approved 出口继续按 `reference/output-templates.md` 采集 PR 与全部 checks 事实：未提交/未推送走 `commit`，无 PR 走 `create-pr`（无 PR 流程除外），checks 未终态走 `watch-pr`，仅 `HEAD == last_reviewed_commit == PR head` 且 checks 为 `passed|no-required` 时走 `complete-task`；不得仅按审查轮次分流
 - 完成 `last_reviewed_commit` 处理后执行 `agent-infra-internal task-event {task-id} review-code.completed --agent {standard-agent-token} --artifact {review-artifact} --verdict {approved|changes-requested|rejected} --blockers {unresolved-blockers} --major {unresolved-major} --minor {unresolved-minor} --manual-validation {n} {execution-flag}`
 
 完成日志必须始终写入 `Manual-validation: {n}` 字段，0 也保留。

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

@@ -59,7 +59,7 @@ Next step - create a Pull Request:
 {next-step-commands}
 ```
 
-#### Branch A3: Watch Required Checks
+#### Branch A3: Watch All Checks
 
 Populate `{next-step-commands}` for this scenario by running `agent-infra-internal agent-client next-steps --skill watch-pr --task-ref {task-ref}`.
 

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

@@ -59,7 +59,7 @@
 {next-step-commands}
 ```
 
-#### 场景 A3：监控 required checks
+#### 场景 A3：监控全部 checks
 
 使用 `agent-infra-internal agent-client next-steps --skill watch-pr --task-ref {task-ref}` 生成本场景的 `{next-step-commands}`。
 

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

@@ -55,13 +55,32 @@ agent-infra-internal pr-review-grade resolve-host --pr {pr-number} [--cwd <path>
 
 `resolve-host` returns a typed `HostResolution` (`unique` / `ambiguous` / `none`). Branch as follows:
 
-- **Unique host**: bind `{task-id}` and enumerate `analysis*`/`plan*`/`code*`/`review-*`/`pr-review*` presence (go to step 2).
+- **Unique host**: bind `{task-id}`, call `task-activity pr-review-inspect` to obtain the canonical round, prepared/open state, and latest successful review identity, then start this round using the recovery rules below (go to step 2).
 - **Ambiguous hosts**: `resolve-host` returns `ambiguous` and `decide` refuses to classify (fail closed). Stop and ask a human to pin the unique host; do not enter evidence classification.
 - **No host**: block by default and require linking an Issue/task first (show linking guidance); never auto-create/import an Issue. Only when the user explicitly chooses a "one-shot review" do process files land in `.agents/workspace/reviews/{pr-number}/` (`recoverable: false`).
 
+After the task-anchored path resolves the host and remote head, run:
+
+```bash
+agent-infra-internal task-activity {task-id} pr-review-inspect
+```
+
+- `prepared`: reuse that artifact; `open` with an unchanged head: replay start for the same artifact/head (a no-op) and resume the round.
+- `open` with a changed head: first set the old artifact Formal Review Status to `superseded`, then terminate it using the old artifact/head; continue with the next round returned by inspect.
+- No prepared/open round: create the next artifact skeleton from `reference/report-template.md`, initially recording the state check, identity, reviewed head, and `Formal Review Status: pending`.
+
+After this branch and before step 2 evidence grading, write started:
+
+```bash
+agent-infra-internal task-activity {task-id} pr-review-start --agent {agent} \
+  --artifact {pr-review-artifact} --head {head-sha}
+```
+
+The one-shot path never calls `task-activity`. For a controlled failure after started where the formal Review is known not to have been published, first set the artifact status to `aborted`, then call `pr-review-terminate --outcome aborted --reason <single-line>` with the same artifact/head. If publication outcome is uncertain, leave the round open rather than guessing aborted.
+
 ### 2. Single decide: evidence enumeration + classification + risk + mode
 
-Write the host, artifact presence, head state, and the six pure-evidence risk factors to an input JSON, then call once:
+Write the host, artifact presence, head state, and the six pure-evidence risk factors to an input JSON. Use only the highest `applied` / `no-op` artifact returned by inspect as the prior review; pending/aborted/superseded/failed artifacts count only toward round continuity. Then call once:
 
 ```bash
 agent-infra-internal pr-review-grade decide --input-file {decide-input.json} [--cwd <path>]
@@ -71,7 +90,7 @@ Returns the full `DecisionRecord` (`scenario` / `freshness` / `alignment` / `ris
 
 ### 3. Generate `pr-review-rN.md`
 
-Generate this round's artifact per `reference/report-template.md`. In `reconstruct` mode (or `audit` with insufficient evidence), write a "Reconstruction Context" section (requirement boundary / architecture choices / impact surface / validation coverage, see `reference/evidence-grading.md`) before the line-level findings. Record `recoverable: true|false` in the frontmatter or header (the one-shot path sets `false`).
+Complete this round's artifact per `reference/report-template.md`; the task-anchored path preserves the identity/head/pending status written in step 1 and does not reallocate the round. In `reconstruct` mode (or `audit` with insufficient evidence), write a "Reconstruction Context" section (requirement boundary / architecture choices / impact surface / validation coverage, see `reference/evidence-grading.md`) before the line-level findings. Record `recoverable: true|false` in the frontmatter or header (the one-shot path sets `false`). After finalizing the findings list, freeze `{verdict, blockers, major, minor}` once; the formal Review body and step 6 complete payload must consume that same object directly, never recounting report prose.
 
 ### 4. Sync the Issue artifact comments (task-anchored path)
 
@@ -99,18 +118,27 @@ agent-infra-internal platform-pr-review publish --pr {pr-number} --scope {taskId
   --commit {head-sha} --event {COMMENT|APPROVE|REQUEST_CHANGES} --body-file {review-body.md} [--dry-run] [--cwd <path>]
 ```
 
-`publish` generates and validates the marker (first line) in core and is idempotent per marker + commit (replay is a no-op; marker hit on a different commit fails stably). On head drift, stop and start a new round (re-run step 1 with round `{round}+1`).
+`publish` generates and validates the marker (first line) in core and is idempotent per marker + commit (replay is a no-op; marker hit on a different commit fails stably). On head drift, first set the old artifact status to `superseded`, then close the old round:
+
+```bash
+agent-infra-internal task-activity {task-id} pr-review-terminate --agent {agent} \
+  --artifact {pr-review-artifact} --head {head-sha} \
+  --outcome superseded --reason "head changed before publish"
+```
+
+After closure, re-run step 1 for the next canonical round; never start the new round first. If the remote outcome of `publish` is uncertain, keep the round open and recover through marker + commit idempotency on retry.
 
 ### 6. Write back the publication result and task state
 
-- **Task-anchored path**: write the Review ID/URL into the `pr-review-rN.md` "Publication Result" section and append the Activity Log entry:
+- **Task-anchored path**: after publish returns `applied` / `no-op`, write the Review ID/URL and matching Formal Review Status into the `pr-review-rN.md` "Publication Result" section, then close the Activity Log with the exact verdict/counts frozen in step 3:
 
   ```bash
-  agent-infra-internal task-activity {task-id} append --step "Review PR (Round {round})" --agent {agent} \
-    --note "receipt {receipt} · Review URL {review-url}" --artifact {pr-review-artifact}
+  agent-infra-internal task-activity {task-id} pr-review-complete --agent {agent} \
+    --artifact {pr-review-artifact} --head {head-sha} --verdict {approved|changes-requested|commented} \
+    --blockers {blockers} --major {major} --minor {minor}
   ```
 
-  `task-activity` atomically completes the Activity Log append, the `## Review Feedback` link, and the version-stamp refresh via `writeTask`; it never changes `current_step`.
+  `task-activity` generates `Verdict: <result>, blockers: N, major: N, minor: N → {pr-review-artifact}` from the typed payload and atomically writes the Activity Log, `## Review Feedback` link, and version stamp through `writeTask`. It never changes `current_step` or puts receipt/head/Review URL into the NOTE.
 
 - **One-shot path (no task)**: write the Review ID/URL only into the `pr-review-rN.md` "Publication Result" section; do not call `task-activity`.
 

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

@@ -55,13 +55,32 @@ agent-infra-internal pr-review-grade resolve-host --pr {pr-number} [--cwd <path>
 
 `resolve-host` 输出 `HostResolution`（`unique` / `ambiguous` / `none`），按以下策略分流：
 
-- **唯一宿主**：绑定 `{task-id}`，用 artifact 枚举确定 `analysis*`/`plan*`/`code*`/`review-*`/`pr-review*` 的存在性（进入步骤 2）。
+- **唯一宿主**：绑定 `{task-id}`，调用 `task-activity pr-review-inspect` 取得 canonical round、prepared/open 状态和最近成功审查身份，再按下述恢复规则开始本轮（进入步骤 2）。
 - **多宿主歧义**：`resolve-host` 返回 `ambiguous`，`decide` 会拒绝分类（fail closed）。立即停止并提示人工指定唯一宿主；不进入证据分类。
 - **无宿主**：默认阻塞，要求先建立 Issue/task 关联（给出关联指引），不自动创建/导入 Issue。仅当用户显式选择「仅一次性检视」时，过程文件写入 `.agents/workspace/reviews/{pr-number}/`（`recoverable: false`）。
 
+任务锚定路径在宿主与远端 head 确定后执行：
+
+```bash
+agent-infra-internal task-activity {task-id} pr-review-inspect
+```
+
+- `prepared`：复用该 artifact；`open` 且 head 未变：对同一 artifact/head 重放 start（no-op）并恢复该轮。
+- `open` 且 head 已变：先把旧 artifact 的正式 Review 状态写为 `superseded`，再用旧 artifact/head 执行 terminate；随后使用 inspect 返回的 next round。
+- 无 prepared/open：按 `reference/report-template.md` 创建 next artifact 骨架，先写状态核对、身份信息、被审 head 与 `正式 Review 状态: pending`。
+
+在上述分流完成后、步骤 2 证据分级开始前写 started：
+
+```bash
+agent-infra-internal task-activity {task-id} pr-review-start --agent {agent} \
+  --artifact {pr-review-artifact} --head {head-sha}
+```
+
+一次性路径不调用 `task-activity`。任意 started 后、正式 Review 明确尚未发布的受控失败，都先把 artifact 状态写为 `aborted`，再以同一 artifact/head 调用 `pr-review-terminate --outcome aborted --reason <single-line>`；发布结果不确定时保持 open，不臆断 aborted。
+
 ### 2. 单次 decide：证据枚举 + 场景分类 + 风险分级 + 模式选择
 
-把宿主、artifact 存在性、head 状态与六个纯证据风险因素写入输入 JSON，调用一次：
+把宿主、artifact 存在性、head 状态与六个纯证据风险因素写入输入 JSON。prior review 只使用 inspect 返回的最高 `applied` / `no-op` artifact；pending/aborted/superseded/failed 只参与 round 连续性，不作为既有结论。调用一次：
 
 ```bash
 agent-infra-internal pr-review-grade decide --input-file {decide-input.json} [--cwd <path>]
@@ -71,7 +90,7 @@ agent-infra-internal pr-review-grade decide --input-file {decide-input.json} [--
 
 ### 3. 生成 `pr-review-rN.md`
 
-按 `reference/report-template.md` 生成本轮产物。`reconstruct`（或 `audit` 证据不足）时，在行级 finding 之前先写「重建上下文」段（需求边界 / 架构选择 / 影响面 / 验证覆盖，见 `reference/evidence-grading.md`）。frontmatter 或首部记录 `recoverable: true|false`（一次性路径为 `false`）。
+按 `reference/report-template.md` 完成本轮产物；任务锚定路径保留步骤 1 已写入的身份/head/pending 状态，不重新分配 round。`reconstruct`（或 `audit` 证据不足）时，在行级 finding 之前先写「重建上下文」段（需求边界 / 架构选择 / 影响面 / 验证覆盖，见 `reference/evidence-grading.md`）。frontmatter 或首部记录 `recoverable: true|false`（一次性路径为 `false`）。完成最终问题清单后，一次性冻结 `{verdict, blockers, major, minor}`；正式 Review 正文与步骤 6 的 complete payload 必须直接复用该对象，不从报告文案反向统计。
 
 ### 4. 同步 Issue artifact 评论（任务锚定路径）
 
@@ -99,18 +118,27 @@ agent-infra-internal platform-pr-review publish --pr {pr-number} --scope {taskId
   --commit {head-sha} --event {COMMENT|APPROVE|REQUEST_CHANGES} --body-file {review-body.md} [--dry-run] [--cwd <path>]
 ```
 
-`publish` 由 core 生成并校验 marker（首行），按 marker + commit 幂等（重放 no-op；marker 命中但 commit 不一致稳定失败）。head 漂移则停止并转入新轮次（重新执行步骤 1，轮次 `{round}+1`）。
+`publish` 由 core 生成并校验 marker（首行），按 marker + commit 幂等（重放 no-op；marker 命中但 commit 不一致稳定失败）。head 漂移时，先把旧 artifact 状态写为 `superseded`，再闭合旧轮：
+
+```bash
+agent-infra-internal task-activity {task-id} pr-review-terminate --agent {agent} \
+  --artifact {pr-review-artifact} --head {head-sha} \
+  --outcome superseded --reason "head changed before publish"
+```
+
+闭合成功后重新执行步骤 1，进入下一 canonical round；不得先写新轮 started。若 publish 调用的远端结果不确定，保留 open 并在重试时依赖 marker + commit 恢复。
 
 ### 6. 回写发布结果与任务状态
 
-- **任务锚定路径**：把 Review ID/URL 写入 `pr-review-rN.md`「发布结果」段，并追加活动日志：
+- **任务锚定路径**：publish 返回 `applied` / `no-op` 后，把 Review ID/URL 与同名正式 Review 状态写入 `pr-review-rN.md`「发布结果」段，再以步骤 3 冻结的同一组 verdict/counts 闭合活动日志：
 
   ```bash
-  agent-infra-internal task-activity {task-id} append --step "Review PR (Round {round})" --agent {agent} \
-    --note "receipt {receipt} · Review URL {review-url}" --artifact {pr-review-artifact}
+  agent-infra-internal task-activity {task-id} pr-review-complete --agent {agent} \
+    --artifact {pr-review-artifact} --head {head-sha} --verdict {approved|changes-requested|commented} \
+    --blockers {blockers} --major {major} --minor {minor}
   ```
 
-  `task-activity` 经 `writeTask` 原子完成 Activity Log 追加、`## 审查反馈` 链接与版本戳刷新；不改 `current_step`。
+  `task-activity` 由 typed payload 生成 `Verdict: <结论>, blockers: N, major: N, minor: N → {pr-review-artifact}`，并经 `writeTask` 原子完成 Activity Log、`## 审查反馈` 链接与版本戳刷新；不改 `current_step`，也不把 receipt/head/Review URL 写入 NOTE。
 
 - **一次性路径（无任务）**：Review ID/URL 只写 `pr-review-rN.md`「发布结果」段，不调用 `task-activity`。
 

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

@@ -69,7 +69,7 @@ Land the following in order before the line-level findings, without impersonatin
 
 ## Publication Result
 
-- **Formal Review Status**: {applied / no-op / blocked / failed}
+- **Formal Review Status**: {pending / applied / no-op / aborted / superseded / blocked / failed}
 - **Review ID**: {review-id or N/A}
 - **Review URL**: {review-url or N/A}
 - **Issue Artifact Comment URL**: {comment-url or N/A}

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

@@ -69,7 +69,7 @@
 
 ## 发布结果
 
-- **正式 Review 状态**：{applied / no-op / blocked / failed}
+- **正式 Review 状态**：{pending / applied / no-op / aborted / superseded / blocked / failed}
 - **Review ID**：{review-id 或 N/A}
 - **Review URL**：{review-url 或 N/A}
 - **Issue artifact 评论 URL**：{comment-url 或 N/A}