@fitlab-ai/agent-infra 0.9.1 → 0.9.3

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

@@ -0,0 +1,158 @@
+---
+name: review-pr
+description: >
+  按证据分级审查 PR 并发布正式 Review。
+  当需要审查一个 PR（无论是否已有可信生命周期记录）时使用。
+  仅当对话包含可解析的 PR 编号或 PR URL 时才可自动调用本技能。
+---
+
+# 审查 PR
+
+根据目标 PR 的生命周期证据完整度与变更风险，选择 `verify`（轻量复核）、`audit`（证据审计）或 `reconstruct`（重建式审查），并把可执行的检视结论作为正式 PR Review 发布到目标 PR，同时保留可追溯的审查过程证据（`pr-review.md` / `pr-review-r{N}.md`）。
+
+## 行为边界 / 关键规则
+
+- 严格遵循方案中固化的证据分级主决策流：宿主解析 → 证据分类 → 新鲜度/对齐 → 风险分级 → 模式选择
+- `pr-review*` 是独立 artifact family：不接入 analysis/plan/code 阶段依赖链，不修改 `current_step`
+- PR 上只发布正式 PR Review（head SHA、结论、finding、receipt、Issue artifact 链接），不发第二份完整过程原文到 PR 普通评论
+- 完整过程原文与 `task.md` 的可逆镜像只在关联 Issue 上同步；`restore-task` 保持 Issue-only 契约
+- 不得为外部 PR 倒填或伪造已发生的 `analysis`/`plan`/`code` 生命周期历史
+- head SHA 唯一记录于 `pr-review*` 与正式 PR Review；head 漂移必须进入新轮次，不得沿用旧结论
+- 审查深度由证据完整度和变更风险决定，不由提交者身份决定
+- 执行本技能后，你**必须**立即更新 task.md（经 `task-activity` typed intent）
+- 绝不自动执行 `git add` 或 `git commit`
+- 一次性检视路径（无任务/Issue）走 `.agents/workspace/reviews/{pr-number}/`，标记 `recoverable: false`，不承担可恢复承诺
+
+## 常见违规借口与反驳
+
+| 借口 | 反驳 |
+|------|------|
+| 「代码 diff 直接看就行了，不需要重建上下文」 | 仅看 diff 会遗漏需求边界、架构选择与迁移策略；`reconstruct` 必须先产出最低充分重建记录。 |
+| 「PR 没有关联任务，直接写个报告发出去」 | 默认阻塞并要求先关联 Issue/task；只有显式「仅一次性检视」才走不可恢复降级路径。 |
+| 「把完整重建过程也发到 PR 普通评论，方便贡献者看」 | 过程原文只同步到 Issue artifact 评论；PR 只保留正式 Review，避免重复远端副本与恢复源混淆。 |
+| 「审查完了顺手提交一下」 | 本技能绝不执行 `git add`/`git commit`；提交是用户显式发起的独立步骤。 |
+
+## 第 0 步：状态核对（执行前硬约束）
+
+在加载本技能与相关规则后、做任何任务状态判断或用户可见结论之前，必须先执行状态核对：
+
+```bash
+agent-infra-internal task-snapshot {task-id} --format text
+```
+
+任务锚定路径在开始前记录当前任务目录与既有 `pr-review*` 轮次；一次性路径（无任务）记录 PR 编号与目标目录。状态核对输出粘贴到本轮产物 `pr-review-rN.md` 的 `## 状态核对` 段。
+
+## 执行步骤
+
+### 1. 解析入参与宿主解析
+
+解析目标 PR 编号 `{pr-number}`（`--pr <number>`，或 PR URL，或省略时按当前分支反查）。执行：
+
+```bash
+agent-infra-internal platform-pr-review inspect --pr {pr-number} [--cwd <path>]
+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）。
+- **多宿主歧义**：`resolve-host` 返回 `ambiguous`，`decide` 会拒绝分类（fail closed）。立即停止并提示人工指定唯一宿主；不进入证据分类。
+- **无宿主**：默认阻塞，要求先建立 Issue/task 关联（给出关联指引），不自动创建/导入 Issue。仅当用户显式选择「仅一次性检视」时，过程文件写入 `.agents/workspace/reviews/{pr-number}/`（`recoverable: false`）。
+
+### 2. 单次 decide：证据枚举 + 场景分类 + 风险分级 + 模式选择
+
+把宿主、artifact 存在性、head 状态与六个纯证据风险因素写入输入 JSON，调用一次：
+
+```bash
+agent-infra-internal pr-review-grade decide --input-file {decide-input.json} [--cwd <path>]
+```
+
+一次返回完整 `DecisionRecord`（`scenario` / `freshness` / `alignment` / `risk` / `mode` / `firstReview` / `reason`）。把决策输入与输出原样记录到 `pr-review-rN.md` 的「证据清单」段（AC3 可追溯）。`host.kind === 'ambiguous'` 时命令拒绝，回到步骤 1 的阻塞出口。
+
+### 3. 生成 `pr-review-rN.md`
+
+按 `reference/report-template.md` 生成本轮产物。`reconstruct`（或 `audit` 证据不足）时，在行级 finding 之前先写「重建上下文」段（需求边界 / 架构选择 / 影响面 / 验证覆盖，见 `reference/evidence-grading.md`）。frontmatter 或首部记录 `recoverable: true|false`（一次性路径为 `false`）。
+
+### 4. 同步 Issue artifact 评论（任务锚定路径）
+
+依次同步 task 评论与 artifact 评论，取得稳定 comment URL：
+
+```bash
+agent-infra-internal platform-comment sync {task-id} --kind task --agent {agent}
+agent-infra-internal platform-comment sync {task-id} --kind artifact --artifact {pr-review-artifact} --agent {agent}
+```
+
+一次性路径（无任务/Issue）跳过本步。
+
+### 5. 核对 head 并发布正式 Review
+
+再次读取远端 head，确认未被审查期间漂移：
+
+```bash
+agent-infra-internal platform-pr-review inspect --pr {pr-number} [--cwd <path>]
+```
+
+若 head 与步骤 1 记录一致，组装正文（head SHA / 结论 / finding / receipt / Issue artifact 链接，**不含 marker**），发布正式 Review：
+
+```bash
+agent-infra-internal platform-pr-review publish --pr {pr-number} --scope {taskId|pr{pr-number}} --round {round} \
+  --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`）。
+
+### 6. 回写发布结果与任务状态
+
+- **任务锚定路径**：把 Review ID/URL 写入 `pr-review-rN.md`「发布结果」段，并追加活动日志：
+
+  ```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}
+  ```
+
+  `task-activity` 经 `writeTask` 原子完成 Activity Log 追加、`## 审查反馈` 链接与版本戳刷新；不改 `current_step`。
+
+- **一次性路径（无任务）**：Review ID/URL 只写 `pr-review-rN.md`「发布结果」段，不调用 `task-activity`。
+
+### 7. 发布后回写再同步（任务锚定路径）
+
+步骤 6 已改写本地 `pr-review-rN.md`「发布结果」段与 task.md（活动日志），而步骤 4 同步的是旧快照。`verify_comment_content` / `verify_task_comment_content` 会全文比对，必须先再同步使本地与远端一致。依次调用：
+
+```bash
+agent-infra-internal platform-comment sync {task-id} --kind task --agent {agent}
+agent-infra-internal platform-comment sync {task-id} --kind artifact --artifact {pr-review-artifact} --agent {agent}
+```
+
+`platform-comment sync` 对既有 marker 评论是幂等原地更新，comment URL 不变。一次性路径无任务，跳过本步。
+
+### 8. 完成校验
+
+- **任务锚定路径**：
+
+  ```bash
+  agent-infra-internal task-verify {task-id} review-pr.completed --artifact {pr-review-artifact} --format text
+  ```
+
+- **一次性路径**：
+
+  ```bash
+  agent-infra-internal pr-review-grade verify-artifact --artifact-file {pr-review-artifact} [--cwd <path>]
+  ```
+
+退出码 0 通过；1 按输出修复后重跑；2 停止并告知用户需要人工介入。
+
+### 9. 告知用户
+
+按 `reference/output-guidance.md` 选择唯一出口（正常发布 / 阻塞要求关联 / 一次性检视），渲染下一步前读取 `.agents/rules/next-step-output.md`。
+
+## 完成检查清单
+
+- [ ] 已按证据分级完成 PR 审查并产出 `pr-review-rN.md`
+- [ ] 正式 Review 已发布到目标 PR，绑定被审 head SHA
+- [ ] 任务锚定路径的 Issue artifact/task 评论已同步并再同步
+- [ ] 已完成校验（`task-verify` 或 `verify-artifact`）
+- [ ] 已更新 task.md 并追加 Activity Log（任务锚定路径）
+
+## 停止
+
+完成检查清单后立即停止。不要自动提交。

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

@@ -0,0 +1,37 @@
+{
+  "skill": "review-pr",
+  "checks": {
+    "artifact": {
+      "file_pattern": "pr-review.md|pr-review-r{N}.md",
+      "required_sections": [
+        "Identity",
+        "Evidence List",
+        "Coverage Matrix",
+        "Findings",
+        "Publication Result",
+        "State Check",
+        "Evidence"
+      ],
+      "required_patterns": [
+        "^\\$ ",
+        "^- \\*\\*Reviewed Head SHA\\*\\*[:：]\\s*[0-9a-f]{40}\\s*$",
+        "^- \\*\\*Review Mode\\*\\*[:：]\\s*(?:verify|audit|reconstruct)\\s*$",
+        "^- \\*\\*Evidence Scenario\\*\\*[:：]\\s*S[123]\\s*$",
+        "^- \\*\\*receipt\\*\\*[:：]\\s*\\S"
+      ]
+    },
+    "activity-log": {
+      "expected_action_pattern": "Review PR \\(Round \\d+\\)"
+    },
+    "platform-sync": {
+      "when": "issue_number_exists",
+      "expected_comment_marker": "<!-- sync-issue:{task-id}:{artifact-stem} -->",
+      "verify_comment_content": true,
+      "verify_task_comment_content": true,
+      "verify_issue_type": false,
+      "verify_issue_fields": false,
+      "verify_milestone": false,
+      "expected_comment_marker_key": "artifact"
+    }
+  }
+}

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

@@ -0,0 +1,37 @@
+{
+  "skill": "review-pr",
+  "checks": {
+    "artifact": {
+      "file_pattern": "pr-review.md|pr-review-r{N}.md",
+      "required_sections": [
+        "身份信息",
+        "证据清单",
+        "覆盖矩阵",
+        "问题清单",
+        "发布结果",
+        "状态核对",
+        "证据原文"
+      ],
+      "required_patterns": [
+        "^\\$ ",
+        "^- \\*\\*被审 head SHA\\*\\*[:：]\\s*[0-9a-f]{40}\\s*$",
+        "^- \\*\\*审查模式\\*\\*[:：]\\s*(?:verify|audit|reconstruct)\\s*$",
+        "^- \\*\\*证据场景\\*\\*[:：]\\s*S[123]\\s*$",
+        "^- \\*\\*receipt\\*\\*[:：]\\s*\\S"
+      ]
+    },
+    "activity-log": {
+      "expected_action_pattern": "Review PR \\(Round \\d+\\)"
+    },
+    "platform-sync": {
+      "when": "issue_number_exists",
+      "expected_comment_marker": "<!-- sync-issue:{task-id}:{artifact-stem} -->",
+      "verify_comment_content": true,
+      "verify_task_comment_content": true,
+      "verify_issue_type": false,
+      "verify_issue_fields": false,
+      "verify_milestone": false,
+      "expected_comment_marker_key": "artifact"
+    }
+  }
+}

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

@@ -0,0 +1,65 @@
+# Evidence Grading Reference
+
+This file fixes the evidence-graded decision flow of `review-pr`. All determinations are executed mechanically by the typed-core pure functions (`lib/pr-review/evidence-grading.ts`); the skill's prompt layer only orchestrates. This file explains the criteria and rationale; it does not replace the core.
+
+## Main Decision Flow
+
+```text
+Resolve PR base/head and linked Issue/task (host resolution)
+   ├─ Unique host → bind the task, enumerate artifact presence → evidence classification
+   ├─ Ambiguous hosts → fail closed (decide refuses to classify; require a human-pinned host)
+   └─ No host → block by default and require linking; explicit one-shot → reviews/{pr-number}/
+        ↓
+Evidence scenario classification (S1/S2/S3) → freshness/alignment → risk grading → mode selection
+```
+
+## Host Resolution
+
+- 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` `pr_number` hit takes priority over the `issue_number` reverse lookup, 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 |
+| 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*` |
+
+- S3(b) symmetric criterion: `!hasAnalysis && !hasPlan && !hasCode && !hasReviewAnalysis && !hasReviewPlan && !hasReviewCode && !hasPriorPrReview`. A malformed task with only one review family (review-analysis / review-plan / review-code) falls to S2 → audit.
+- On first review (no prior `pr-review*`) S1(c) is unsatisfied, so a complete-lifecycle task falls to S2 → audit.
+
+## 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` / `pr_number` match the resolution result.
+- No prior `pr-review*` → `n/a` / `n/a` (first-review special case).
+
+## Risk Grading (pure evidence)
+
+| Factor | LOW | HIGH |
+|--------|-----|------|
+| Change size | few files, small net additions | many files, large net additions |
+| Change sensitivity | no protected paths touched | touches lifecycle / rule / skill / config / security / auth / idempotency / concurrency paths |
+| Structural change | no schema/frontmatter/migration/interface-contract changes | involves schema / frontmatter / migration / interface contract |
+| Test coverage | tests present and passing | no tests or tests missing/failing |
+| Source credibility | a reviewable trusted lifecycle exists and aligns with the current head | no trusted record, or the source is not reviewable |
+| Recovery/merge impact | recovery contract unaffected | may break the recovery contract or create a dual-write source |
+
+Aggregation: any priority factor (sensitivity / source credibility) HIGH → HIGH; otherwise any HIGH → MEDIUM; all LOW → LOW. Identity factors never participate in any factor determination.
+
+## Mode Selection Matrix
+
+| Evidence scenario | Freshness/alignment | Risk | Mode |
+|-------------------|---------------------|------|------|
+| S1 | fresh + aligned | LOW/MEDIUM | verify (lightweight recheck) |
+| S1 | fresh + aligned | HIGH | audit (evidence audit) |
+| S2 | stale / misaligned / partial-missing | any | audit |
+| S3 | n/a | any | reconstruct (reconstruction review) |
+
+Running `review-pr` on a complete-lifecycle task for the first time falls to S2 → audit because there is no prior head record; "trusted lifecycle records → verify" corresponds to the re-review case where a prior `pr-review*` exists and the head has not drifted.
+
+## Minimum-Sufficient Reconstruction
+
+When the mode is `reconstruct` (or `audit` with insufficient evidence), form a reconstruction record before the line-level review covering at least: requirement boundary, architecture choices, impact surface, validation coverage; the on-disk order is "Reconstruction Context → Coverage Matrix → line-level Findings".

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

@@ -0,0 +1,65 @@
+# 证据分级参考
+
+本文件固化 `review-pr` 的证据分级主决策流。判定全部由 typed core 纯函数（`lib/pr-review/evidence-grading.ts`）机械执行，skill 提示词层只做编排；本文件用于解释判据与理由，不替代 core。
+
+## 主决策流
+
+```text
+解析 PR base/head 与关联 Issue/task（宿主解析）
+   ├─ 唯一宿主 → 绑定任务，枚举 artifact 存在性 → 证据分类
+   ├─ 多宿主歧义 → fail closed（decide 拒绝分类，要求人工指定）
+   └─ 无宿主 → 默认阻塞要求关联；显式一次性检视 → reviews/{pr-number}/
+        ↓
+证据场景分类（S1/S2/S3）→ 新鲜度/对齐 → 风险分级 → 模式选择
+```
+
+## 宿主解析
+
+- 唯一命中 → `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` 的 `pr_number` 命中优先于 `issue_number` 反查，同一任务经两条路径命中按单候选去重。
+
+## 证据场景分类（S1 → S2 → S3）
+
+| 场景 | 判据 |
+|------|------|
+| S1 完整可信 | 唯一任务且 issue_number 与远端一致 + `analysis`/`plan`/`code` 及三族 review 齐全 + 最新 `pr-review*` 被审 head == 当前 head + 来源受信 |
+| S2 部分/可疑 | 任务存在但 artifact 缺失关键产物，或 head 漂移，或来源不可信 / 无法证明与当前 head 对齐 |
+| S3 仅 PR | 无宿主；或任务唯一但无任何生命周期 artifact 且无先前 `pr-review*` |
+
+- S3(b) 判据（对称口径）：`!hasAnalysis && !hasPlan && !hasCode && !hasReviewAnalysis && !hasReviewPlan && !hasReviewCode && !hasPriorPrReview`。仅含任一 review 产物（review-analysis / review-plan / review-code）的畸形任务落 S2 → audit。
+- 首次审查（无先前 `pr-review*`）时 S1(c) 不满足，完整生命周期任务落入 S2 → audit。
+
+## 新鲜度与对齐
+
+- 新鲜度基准 = 上一轮 `pr-review*` 记录的被审 head SHA，与当前 head 逐字符比对：一致 → `fresh`，否则 → `stale`。
+- 对齐 = freshness 为 fresh 且 `issue_number` / `pr_number` 与解析结果一致。
+- 无先前 `pr-review*` → `n/a` / `n/a`（首轮特例）。
+
+## 风险分级（纯证据口径）
+
+| 因素 | LOW | HIGH |
+|------|-----|------|
+| 变更规模 | 文件少、净增行少 | 文件多、净增行大 |
+| 变更敏感度 | 未触及受保护路径 | 触及 lifecycle / rule / skill / config / 安全 / 认证 / 幂等 / 并发路径 |
+| 结构性变更 | 无 schema/frontmatter/迁移/接口契约变化 | 涉及 schema / frontmatter / 迁移 / 接口契约 |
+| 测试覆盖 | 有配套测试且可通过 | 无测试或测试缺失/不可通过 |
+| 证据来源可信度 | 存在可复核的受信生命周期且与当前 head 对齐 | 无受信记录，或来源不可复核 |
+| 恢复/合并影响 | 不影响可恢复契约 | 可能破坏可恢复契约或形成双写真源 |
+
+聚合：任一优先因素（敏感度 / 证据来源可信度）HIGH → HIGH；否则任一 HIGH → MEDIUM；全 LOW → LOW。身份因素不参与任何因素判定。
+
+## 模式选择矩阵
+
+| 证据场景 | 新鲜度/对齐 | 风险 | 模式 |
+|----------|-------------|------|------|
+| S1 | fresh + aligned | LOW/MEDIUM | verify（轻量复核） |
+| S1 | fresh + aligned | HIGH | audit（证据审计） |
+| S2 | stale / misaligned / 部分缺失 | 任意 | audit |
+| S3 | n/a | 任意 | reconstruct（重建式审查） |
+
+首次对完整生命周期任务运行 `review-pr` 因无先前 head 记录落入 S2 → audit；「已有可信生命周期记录 → verify」对应「存在上轮 `pr-review*` 且 head 未漂移」的再审查场景。
+
+## 最低充分重建
+
+模式为 `reconstruct`（或 `audit` 证据不足）时，在行级审查前形成重建记录，至少覆盖：需求边界、架构选择、影响面、验证覆盖；顺序保证「重建上下文 → 覆盖矩阵 → 行级 finding」。

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

@@ -0,0 +1,18 @@
+# Output Guidance
+
+Read this file and `.agents/rules/next-step-output.md` before presenting the final result to the user. `review-pr` has exactly three exits; pick exactly one based on the run outcome.
+
+## Exit Selection
+
+| Exit | Trigger | Present |
+|------|---------|---------|
+| A Published | the formal Review was published (applied/no-op) and verification passed | conclusion, mode, reviewed head SHA, Review URL, receipt, next step |
+| B Blocked, requires linking | `resolve-host` returned none or ambiguous | linking guidance (create/link an Issue and task); do not auto-create an Issue; or explicitly choose the one-shot review |
+| C One-shot review | the user explicitly chose a "one-shot review" | non-recoverable notice, artifact directory `.agents/workspace/reviews/{pr-number}/`, Review URL |
+
+## Presentation Requirements
+
+- On publish (exit A) report: review mode (verify/audit/reconstruct), evidence scenario (S1/S2/S3), reviewed head SHA, finding count, formal Review URL, receipt.
+- On block (exit B) provide concrete commands/steps to establish the link; if `resolve-host` returned `ambiguous`, list the candidate tasks and ask a human to pin the host.
+- On one-shot (exit C) state clearly `recoverable: false` and make no recovery promise.
+- Read `.agents/rules/next-step-output.md` before rendering the next step, and generate the "next step" command per its convention.

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

@@ -0,0 +1,18 @@
+# 输出指引
+
+向用户呈现最终结果前先读取本文件与 `.agents/rules/next-step-output.md`。`review-pr` 有且仅有三个出口，按本次运行结果选一个，不要输出多个。
+
+## 出口选择
+
+| 出口 | 触发条件 | 呈现内容 |
+|------|----------|----------|
+| A 正常发布 | 正式 Review 已发布（applied/no-op）且校验通过 | 结论、模式、被审 head SHA、Review URL、receipt、下一步 |
+| B 阻塞要求关联 | `resolve-host` 返回 none 或 ambiguous | 关联指引（创建/关联 Issue 与 task），不自动创建 Issue；或显式选择一次性检视 |
+| C 一次性检视 | 用户显式选择「仅一次性检视」 | 不可恢复提示、产物目录 `.agents/workspace/reviews/{pr-number}/`、Review URL |
+
+## 呈现要求
+
+- 正常发布（出口 A）时报告：审查模式（verify/audit/reconstruct）、证据场景（S1/S2/S3）、被审 head SHA、finding 总数、正式 Review URL、receipt。
+- 阻塞（出口 B）时给出建立关联的具体命令或步骤；如果 `resolve-host` 返回 ambiguous，列出候选任务并要求人工指定。
+- 一次性检视（出口 C）明确 `recoverable: false`，不承诺可恢复。
+- 渲染下一步前读取 `.agents/rules/next-step-output.md`，并按其中的「下一步」命令约定生成。

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

@@ -0,0 +1,85 @@
+# PR Review Report Template
+
+Use the following structure when creating `pr-review.md` or `pr-review-r{N}.md`.
+
+```markdown
+# PR Review Report
+
+- **Review Round**: Round {round}
+- **Artifact File**: `pr-review.md` / `pr-review-r{N}.md`
+- **Recoverable**: true (task-anchored path) / false (one-shot path)
+
+## State Check
+
+> Paste the state-check command output verbatim; each command starts with `$ `.
+
+## Identity
+
+- **PR Number**: {pr-number}
+- **Base Branch**: {base-ref} (SHA `{base-sha}`)
+- **Head Branch**: {head-ref}
+- **Reviewed Head SHA**: {40 hex}
+- **Linked Issue**: {issue-number or N/A}
+- **Linked Task**: {task-id or N/A}
+- **Task Directory**: {task-dir or N/A}
+
+## Evidence List
+
+- **Host Resolution**: `unique` / `ambiguous` / `none`
+- **Evidence Scenario**: S{1|2|3}
+- **Freshness**: `fresh` / `stale` / `n/a`
+- **Alignment**: `aligned` / `misaligned` / `n/a`
+- **Review Mode**: `verify` / `audit` / `reconstruct`
+- **Risk Level**: `LOW` / `MEDIUM` / `HIGH`
+- **First Review**: true / false
+- **receipt**: {receipt}
+- **Decision Input and Output**: paste the full `pr-review-grade decide` input JSON and the output DecisionRecord (the decision input includes host, artifact presence, head state, and the six risk factors).
+
+### Reconstruction Context (reconstruct / audit with insufficient evidence)
+
+Land the following in order before the line-level findings, without impersonating a standard lifecycle artifact:
+
+1. **Requirement boundary**: what the PR does and does not do.
+2. **Architecture choices**: key technical paths and trade-offs.
+3. **Impact surface**: modules / rules / contracts touched.
+4. **Validation coverage**: what tests should exist and whether current tests cover them.
+
+## Coverage Matrix
+
+| Review Surface | Evidence | Conclusion | Uncovered / Gap |
+|----------------|----------|------------|-----------------|
+| Requirement boundary | {evidence} | {conclusion} | {gap} |
+| Architecture choices | {evidence} | {conclusion} | {gap} |
+| Impact surface | {evidence} | {conclusion} | {gap} |
+| Validation coverage | {evidence} | {conclusion} | {gap} |
+
+## Findings
+
+### Blockers (must fix)
+
+- **{title}**: {description} · `{file}:{line}` · Evidence: {evidence} · Impact: {impact} · Suggestion: {suggestion}
+
+### Major (should fix)
+
+- **{title}**: {description} · `{file}:{line}` · Evidence: {evidence} · Impact: {impact} · Suggestion: {suggestion}
+
+### Minor (low impact, close the loop)
+
+- **{title}**: {description} · `{file}:{line}` · Evidence: {evidence} · Impact: {impact} · Suggestion: {suggestion}
+
+## Publication Result
+
+- **Formal Review Status**: {applied / no-op / 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}
+
+## Evidence
+
+> Every "I verified X" assertion must pair with the corresponding tool output verbatim; the gate only checks this section exists and has at least one `$ ` line.
+
+- Assertion: {verified claim}
+```text
+$ {command}
+{raw output}
+```

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

@@ -0,0 +1,85 @@
+# PR 审查报告模板
+
+创建 `pr-review.md` 或 `pr-review-r{N}.md` 时使用以下结构。
+
+```markdown
+# PR 审查报告
+
+- **审查轮次**：Round {round}
+- **产物文件**：`pr-review.md` / `pr-review-r{N}.md`
+- **可恢复**：true（任务锚定路径）/ false（一次性检视路径）
+
+## 状态核对
+
+> 粘贴状态核对命令原文；每条命令以 `$ ` 开头。
+
+## 身份信息
+
+- **PR 编号**：{pr-number}
+- **Base 分支**：{base-ref}（SHA `{base-sha}`）
+- **Head 分支**：{head-ref}
+- **被审 head SHA**：{40 位 hex}
+- **关联 Issue**：{issue-number 或 N/A}
+- **关联任务**：{task-id 或 N/A}
+- **关联任务目录**：{task-dir 或 N/A}
+
+## 证据清单
+
+- **宿主解析结果**：`unique` / `ambiguous` / `none`
+- **证据场景**：S{1|2|3}
+- **新鲜度**：`fresh` / `stale` / `n/a`
+- **对齐**：`aligned` / `misaligned` / `n/a`
+- **审查模式**：`verify` / `audit` / `reconstruct`
+- **风险等级**：`LOW` / `MEDIUM` / `HIGH`
+- **是否首次审查**：true / false
+- **receipt**：{receipt}
+- **决策输入与输出**：粘贴 `pr-review-grade decide` 的完整输入 JSON 与输出 DecisionRecord（decision 输入含宿主、artifact 存在性、head 状态、六个风险因素）。
+
+### 重建上下文（reconstruct / audit 证据不足时）
+
+在行级 finding 之前按以下顺序落盘，不冒充标准生命周期产物：
+
+1. **需求边界**：PR 要实现什么、不做什么。
+2. **架构选择**：关键技术路径与取舍。
+3. **影响面**：改动波及的模块 / 规则 / 契约。
+4. **验证覆盖**：应有哪些测试、现有测试能否覆盖。
+
+## 覆盖矩阵
+
+| 检视面 | 证据 | 结论 | 未覆盖/缺口 |
+|--------|------|------|-------------|
+| 需求边界 | {证据} | {结论} | {缺口} |
+| 架构选择 | {证据} | {结论} | {缺口} |
+| 影响面 | {证据} | {结论} | {缺口} |
+| 验证覆盖 | {证据} | {结论} | {缺口} |
+
+## 问题清单
+
+### 阻塞项（必须修复）
+
+- **{标题}**：{描述} · `{file}:{line}` · 证据：{evidence} · 影响：{impact} · 建议：{suggestion}
+
+### 主要问题（建议修复）
+
+- **{标题}**：{描述} · `{file}:{line}` · 证据：{evidence} · 影响：{impact} · 建议：{suggestion}
+
+### 次要问题（低影响但需闭环）
+
+- **{标题}**：{描述} · `{file}:{line}` · 证据：{evidence} · 影响：{impact} · 建议：{suggestion}
+
+## 发布结果
+
+- **正式 Review 状态**：{applied / no-op / blocked / failed}
+- **Review ID**：{review-id 或 N/A}
+- **Review URL**：{review-url 或 N/A}
+- **Issue artifact 评论 URL**：{comment-url 或 N/A}
+
+## 证据原文
+
+> 每条「我验证了 X」断言都要配对对应 tool output 原文；gate 仅校验本段存在和至少一行 `$ `。
+
+- 断言：{verified claim}
+```text
+$ {command}
+{raw output}
+```

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

@@ -0,0 +1,22 @@
+---
+name: run-task
+description: >
+  Orchestrate lifecycle stages from the task's current state with fresh executors/reviewers and one-use provenance receipts.
+  Use when one entry should advance an existing task until a safe commit or stable pause.
+---
+
+# Run Task Lifecycle
+
+The orchestrator delegates only and never executes a stage skill itself. First read `.agents/rules/no-mid-flow-questions.md`, `.agents/rules/lifecycle-orchestration.md`, and `reference/host-validation.md`.
+
+1. Resolve the task, current Agent Client, and optional atomic policy flags `--executor-model`, `--executor-reasoning-effort`, `--reviewer-model`, and `--reviewer-reasoning-effort`, then run `task-snapshot`. If any explicit policy flag is present, all four role fields are required and must not be merged with configuration; both roles may use the same model.
+2. Run `task-orchestration {task-id} begin-or-resume --client {client}` with the complete explicit policy. With no explicit policy, core reads only that client's `agentClients[].orchestration`; an existing v2 run uses its persisted policy. Only on `ORCHESTRATION_MODEL_POLICY_REQUIRED`, show the complete/partial/interactive-only `agent-client model-selection` context and collect one complete policy; no answer means no run is created. Stop on paused/completed results.
+3. Run `route` and read its structured result. On `completed`, immediately run `agent-infra-internal task-verify {task-id} run-task.completed --format text` and stop. Only when the result is `running` with a non-null `next`, use its single action, role, round, artifact, `requestedModel`, and `requestedReasoningEffort`; never infer them from review prose, session defaults, or a partial tool schema.
+4. Only for the `running` result from step 3, run `prepare --client {client} --requested-model {requestedModel} --requested-reasoning-effort {requestedReasoningEffort}` so core validates both fields and host evidence before snapshotting. Claude Code's native start event currently cannot provide stable actual model/effort evidence, so it returns `ORCHESTRATION_CLIENT_UNSUPPORTED` and stops like any other client without that evidence. Only after validation succeeds, start a fresh native child with the same model/effort overrides and only the short task ref, skill name, literal `--orchestrated` execution marker, and minimal handoff. The child must forward that marker to every provenance-sensitive command in the stage.
+5. Native start/stop hooks correlate the unique pending delegation and let core compute workspace changes and seal the receipt. After the child returns, run `advance`. Repeat step 3 only for `running`; stop immediately for `paused` or `completed`.
+6. Create a new child every round and never follow up with an old reviewer. Native start must report actual model and actual reasoning effort; each requested/actual mismatch needs its own host fallback reason, and requested values must never be fabricated as actual evidence. Capability, hook, identity, evidence, ledger, or fingerprint failures must call `pause` and fail closed.
+7. On pause or completion, run the matching typed verification and report the structured run summary, pause reason, commit endpoint, or clean completion evidence.
+
+## Stop
+
+Stop after a safe `commit` or reviewed-head-clean endpoint; do not create a PR, monitor checks, or archive the task.

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

@@ -0,0 +1,22 @@
+---
+name: run-task
+description: >
+  从任务当前状态持续编排生命周期阶段，并用 fresh executor/reviewer 与一次性 receipt 验证隔离来源。
+  当用户希望通过单一入口推进已有任务直到安全提交或稳定暂停时使用。
+---
+
+# 运行任务生命周期
+
+总控只编排，不直接执行任何阶段技能。执行前先读取 `.agents/rules/no-mid-flow-questions.md`、`.agents/rules/lifecycle-orchestration.md` 与 `reference/host-validation.md`。
+
+1. 解析任务引用、当前 Agent Client，以及可选的原子策略 `--executor-model`、`--executor-reasoning-effort`、`--reviewer-model`、`--reviewer-reasoning-effort`，并执行 `agent-infra-internal task-snapshot {task-id} --format text`。任一显式策略字段出现时四个 role 字段必须完整，不得与配置拼接；两个角色可以使用同一模型。
+2. 调用 `agent-infra-internal task-orchestration {task-id} begin-or-resume --client {client}` 并转发完整显式策略。完全没有显式策略时由核心读取当前 client 的 `agentClients[].orchestration`；已有 v2 run 使用持久化策略。仅当核心返回 `ORCHESTRATION_MODEL_POLICY_REQUIRED` 时，先用 `agent-client model-selection` 展示 complete/partial/interactive-only 来源，再一次收集完整策略；未回答则不创建 run。若为 paused/completed，按结构化结果停止。
+3. 调用 `route` 并读取结构化结果。若返回 `completed`，立即运行 `agent-infra-internal task-verify {task-id} run-task.completed --format text` 并停止；仅当返回 `running` 且 `next` 非空时读取唯一 action、role、round、artifact、`requestedModel` 和 `requestedReasoningEffort`，不得从审查文案、会话默认或局部 tool schema 自行推断。
+4. 仅对步骤 3 的 `running` 结果调用 `prepare --client {client} --requested-model {requestedModel} --requested-reasoning-effort {requestedReasoningEffort}`；核心在记录工作区基线前校验两字段与宿主证据能力。当前 Claude Code 的原生 start 事件无法稳定提供 actual model/effort，因此与其他缺少该证据的客户端一样返回 `ORCHESTRATION_CLIENT_UNSUPPORTED` 并停止。只有校验成功时才用当前客户端的 fresh 原生子 Agent 启动指定角色，并显式覆盖同一 model/effort；只传短任务引用、skill 名、字面执行标记 `--orchestrated` 和最小交接摘要，不传 receipt identity，不继承总控历史。子 Agent 必须把该标记转发给本阶段所有 provenance 敏感命令。
+5. 原生 start/stop hook 通过唯一 pending delegation 自动关联任务，并由核心计算工作区变化、封存 receipt；子 Agent 返回后调用 `advance`。只有 `running` 才重复步骤 3；`paused` 或 `completed` 立即停止。
+6. 每轮创建新 child；禁止 follow-up 复用 reviewer。原生 start 必须回传 actual model 与 actual reasoning effort；任一 actual 与 requested 不同时必须有各自的宿主降级理由，缺失时不得用 requested 值补造。任何 capability、hook、身份、证据、账本或 fingerprint 异常都调用 `pause` 并失败关闭。
+7. 完成或暂停后运行对应 typed verification，并把结构化 run 摘要、暂停原因、commit 终点或 clean completion evidence 告知用户。
+
+## 停止
+
+在安全 `commit` 或 reviewed-head-clean 终点后结束；不要继续创建 PR、监控 checks 或归档任务。

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

@@ -0,0 +1,10 @@
+{
+  "skill": "run-task",
+  "checks": {
+    "task-meta": {
+      "required_fields": ["id", "status", "updated_at", "agent_infra_version", "current_step", "assigned_to"]
+    },
+    "orchestration-state": {},
+    "orchestration-evidence": {}
+  }
+}

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

@@ -0,0 +1,10 @@
+{
+  "skill": "run-task",
+  "checks": {
+    "task-meta": {
+      "required_fields": ["id", "status", "updated_at", "agent_infra_version", "current_step", "assigned_to"]
+    },
+    "orchestration-state": {},
+    "orchestration-evidence": {}
+  }
+}