@fitlab-ai/agent-infra 0.9.12 → 0.9.13

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

@@ -46,6 +46,7 @@
       "verify_task_comment_content": true,
       "verify_issue_type": true,
       "verify_issue_fields": false,
+      "verify_in_labels_computed": true,
       "verify_milestone": true,
       "verify_milestone_specific": true,
       "expected_status_label_key": "inProgress",

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

@@ -46,6 +46,7 @@
       "verify_task_comment_content": true,
       "verify_issue_type": true,
       "verify_issue_fields": false,
+      "verify_in_labels_computed": true,
       "verify_milestone": true,
       "verify_milestone_specific": true,
       "expected_status_label_key": "inProgress",

package/templates/.agents/skills/commit/reference/issue-metadata-sync.en.md

@@ -14,6 +14,8 @@ Call one declarative intent. The internal core owns diff computation, repository
 agent-infra-internal platform-issue sync {task-id} --agent {standard-agent-token} --in-labels from-diff --base {base-branch} --requirements
 ```
 
+If `--base` is supplied, it must exactly match task.md's `delivery_base_ref`; the core uses that task-bound ref as the only diff evidence and never falls back to `main` or a repository default. The `in:` target is the intersection of the `labels.in` mapping and repository labels, and unrelated labels are preserved.
+
 ## Error Handling
 
 Treat sync failures as warnings only. Do not block an already completed `git commit`.

package/templates/.agents/skills/commit/reference/issue-metadata-sync.zh-CN.md

@@ -14,6 +14,8 @@
 agent-infra-internal platform-issue sync {task-id} --agent {standard-agent-token} --in-labels from-diff --base {base-branch} --requirements
 ```
 
+`--base`（如保留）必须与 task.md 的 `delivery_base_ref` 完全一致；core 以 task-bound base 作为唯一 diff evidence，不回退到 `main` 或仓库默认分支。`in:` target 只来自 `labels.in` 映射与仓库实际 labels 的交集，并保留其他 labels。
+
 ## 错误处理
 
 同步失败只记为警告，不阻塞已完成的 `git commit`。

package/templates/.agents/skills/commit/reference/pr-summary-sync.en.md

@@ -2,8 +2,8 @@
 
 Run only when `{task-id}` is valid and task.md has a `bound/verified` `pr_delivery_fact`.
 
-1. Run `agent-infra-internal platform-pr summary-context {task-id}`.
-2. Generate the plain summary body per `.agents/rules/pr-sync.md` and write it to a temporary file.
-3. Run `agent-infra-internal platform-pr summary-sync {task-id} --agent {standard-agent-token} --body-file {summary-body-file} --result no_op`. The commit path only synchronizes an existing PR summary and neither creates nor reuses a PR, so `no_op` explicitly represents the unchanged PR identity.
+1. Run `agent-infra-internal platform-pr summary-context {task-id}` to obtain canonical inputs and report status; rebuild a stale/missing sidecar through the `change-report` flow for the current head.
+2. Generate the plain summary body per `.agents/rules/pr-sync.md`, with exactly one `<!-- canonical-pr-change-report -->` placeholder, and write it to a temporary file.
+3. Run `agent-infra-internal platform-pr summary-sync {task-id} --agent {standard-agent-token} --body-file {summary-body-file} --change-report-file .agents/workspace/active/{task-id}/pr-change-report.json --result no_op`. The commit path only synchronizes an existing PR summary and neither creates nor reuses a PR, so `no_op` explicitly represents the unchanged PR identity.
 
 Failure records a warning but never blocks or rolls back the completed commit. `no-op` maps to `summary skipped (no diff)`.

package/templates/.agents/skills/commit/reference/pr-summary-sync.zh-CN.md

@@ -2,8 +2,8 @@
 
 仅当 `{task-id}` 有效且 `task.md` 存在 `bound/verified` 的 `pr_delivery_fact` 时执行；否则跳过。
 
-1. 调用 `agent-infra-internal platform-pr summary-context {task-id}` 获取 canonical 聚合输入。
-2. 按 `.agents/rules/pr-sync.md` 生成纯摘要正文并写入临时文件。
-3. 调用 `agent-infra-internal platform-pr summary-sync {task-id} --agent {standard-agent-token} --body-file {summary-body-file} --result no_op`。commit 路径只同步已有 PR 摘要，不创建或复用 PR，因此固定使用 `no_op` 表示 PR 身份未变化。
+1. 调用 `agent-infra-internal platform-pr summary-context {task-id}` 获取 canonical 聚合输入和报告状态；sidecar stale/missing 时先按 `change-report` 流程重建当前 head 报告。
+2. 按 `.agents/rules/pr-sync.md` 生成只含一次 `<!-- canonical-pr-change-report -->` 的纯摘要正文并写入临时文件。
+3. 调用 `agent-infra-internal platform-pr summary-sync {task-id} --agent {standard-agent-token} --body-file {summary-body-file} --change-report-file .agents/workspace/active/{task-id}/pr-change-report.json --result no_op`。commit 路径只同步已有 PR 摘要，不创建或复用 PR，因此固定使用 `no_op` 表示 PR 身份未变化。
 
 同步失败只记录 warning，不阻塞或回滚已经完成的 commit。`no-op` 回传 `summary skipped (no diff)`。

package/templates/.agents/skills/complete-manual-validation/SKILL.en.md

@@ -9,6 +9,8 @@ description: >
 # Complete Manual Validation
 > `--agent` values are defined in `.agents/rules/task-management.md` under “Collaborator Token Specification”.
 
+Lifecycle events require explicit trigger data: use `{trigger-initiator}=orchestrator` for orchestration and `model` otherwise; `{request-id}` is a stable single-line identifier for this task and artifact round, and `{reason-code}` is `user-request` or `validation-rerun`. Reuse the same values for started and completed.
+
 
 ## Boundary / Critical Rules
 
@@ -38,7 +40,7 @@ agent-infra-internal task-snapshot {task-id} --format text
 
 ## Step Start: Write the started Marker
 
-After resolving the artifact context and before this round's first artifact action, run `agent-infra-internal task-event {task-id} manual-validation.started --agent {standard-agent-token}` and record the returned `artifactContext`.
+After resolving the artifact context and before this round's first artifact action, run `agent-infra-internal task-event {task-id} manual-validation.started --agent {standard-agent-token} --initiator {trigger-initiator} --request-id {request-id} --reason-code {reason-code}` and record the returned `artifactContext`.
 
 ## Steps
 
@@ -86,7 +88,7 @@ Before this step, read `reference/report-template.md`. Create `{manual-validatio
 
 ### 6. Update task.md
 
-Run `agent-infra-internal task-event {task-id} manual-validation.completed --agent {standard-agent-token} --artifact {manual-validation-artifact} --summary-result "{summary-result}"`. The core keeps `current_step` unchanged while atomically recording the implementation-notes link, metadata, and done log.
+Run `agent-infra-internal task-event {task-id} manual-validation.completed --agent {standard-agent-token} --initiator {trigger-initiator} --request-id {request-id} --reason-code {reason-code} --artifact {manual-validation-artifact} --summary-result "{summary-result}"`. The core keeps `current_step` unchanged while atomically recording the implementation-notes link, metadata, and done log.
 
 If the task 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 {manual-validation-artifact} --agent {standard-agent-token}`.
 
@@ -109,7 +111,7 @@ Report:
 - Artifact path
 - PR summary sync result
 - Current verification output
-- Suggested next step: enter the final closing flow and run /complete-task {task-ref}
+- Suggested next step: enter the final closing flow and run /complete-task --task {task-ref}
 
 Before rendering the final output, read `.agents/rules/next-step-output.md` and append `Completed at: YYYY-MM-DD HH:mm:ss` as the absolute last line.
 

package/templates/.agents/skills/complete-manual-validation/SKILL.zh-CN.md

@@ -9,6 +9,8 @@ description: >
 # 完成人工验证
 > `--agent` 取值见 `.agents/rules/task-management.md`「合作者 token 规范」。
 
+生命周期事件必须携带显式触发信息：编排调用使用 `{trigger-initiator}=orchestrator`，否则使用 `model`；`{request-id}` 是本任务与本轮产物的稳定单行标识，`{reason-code}` 使用 `user-request` 或 `validation-rerun`；started 与 completed 使用同一组值。
+
 
 ## 行为边界 / 关键规则
 
@@ -38,7 +40,7 @@ agent-infra-internal task-snapshot {task-id} --format text
 
 ## 步骤开始：声明 started 事件
 
-确认前置条件和产物上下文后、本轮第一个产出动作之前执行 `agent-infra-internal task-event {task-id} manual-validation.started --agent {standard-agent-token}`，并以返回的 `artifactContext` 记录本轮身份。
+确认前置条件和产物上下文后、本轮第一个产出动作之前执行 `agent-infra-internal task-event {task-id} manual-validation.started --agent {standard-agent-token} --initiator {trigger-initiator} --request-id {request-id} --reason-code {reason-code}`，并以返回的 `artifactContext` 记录本轮身份。
 
 ## 执行步骤
 
@@ -86,7 +88,7 @@ complete-manual-validation [--task <ref> | -t <ref>] [{pr-ref}] {verification-su
 
 ### 6. 更新 task.md
 
-执行 `agent-infra-internal task-event {task-id} manual-validation.completed --agent {standard-agent-token} --artifact {manual-validation-artifact} --summary-result "{summary-result}"`，由核心在保持 `current_step` 不变的同时原子登记实现备注链接、时间/版本和完成日志。
+执行 `agent-infra-internal task-event {task-id} manual-validation.completed --agent {standard-agent-token} --initiator {trigger-initiator} --request-id {request-id} --reason-code {reason-code} --artifact {manual-validation-artifact} --summary-result "{summary-result}"`，由核心在保持 `current_step` 不变的同时原子登记实现备注链接、时间/版本和完成日志。
 
 如任务存在有效 `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 {manual-validation-artifact} --agent {standard-agent-token}`。
 
@@ -109,7 +111,7 @@ agent-infra-internal task-verify {task-id} manual-validation.completed --artifac
 - 产物路径
 - PR 摘要同步结果
 - 当次完成校验输出
-- 下一步建议：进入最终收尾流程，运行 /complete-task {task-ref}
+- 下一步建议：进入最终收尾流程，运行 /complete-task --task {task-ref}
 
 渲染最终输出前，先读取 `.agents/rules/next-step-output.md`，并在绝对最后一行追加 `Completed at: YYYY-MM-DD HH:mm:ss`。
 

package/templates/.agents/skills/complete-manual-validation/reference/summary-update.en.md

@@ -6,11 +6,12 @@ Follow `.agents/rules/pr-sync.md` for the shared summary structure and failure s
 
 1. After the canonical `manual-validation*` artifact is written, run `agent-infra-internal platform-pr summary-context {task-id}`.
 2. Rebuild the summary from canonical inputs and render `### ✅ Manual Validation Passed` with the validation time and explanation.
-3. Write the plain body to a temporary file and run:
+3. Write the plain body with exactly one `<!-- canonical-pr-change-report -->` placeholder to a temporary file and run:
 
 ```bash
 agent-infra-internal platform-pr summary-sync {task-id} \
-  --agent {standard-agent-token} --body-file {summary-body-file}
+  --agent {standard-agent-token} --body-file {summary-body-file} \
+  --change-report-file .agents/workspace/active/{task-id}/pr-change-report.json --result no_op
 ```
 
-The core owns marker/HEAD wrapping, pagination, and in-place reconciliation. If context says no manual validation is required, stop without marking it passed.
+The core owns the rendered report, marker/authoritative PR-head wrapping, pagination, and in-place reconciliation. If context says no manual validation is required, stop without marking it passed.

package/templates/.agents/skills/complete-manual-validation/reference/summary-update.zh-CN.md

@@ -6,13 +6,14 @@
 
 1. 在 canonical `manual-validation*` artifact 落盘后，调用 `agent-infra-internal platform-pr summary-context {task-id}`。
 2. 从返回的最新产物重新聚合摘要，将人工校验段渲染为 `### ✅ 人工验证已通过`，写明验证时间和说明。
-3. 把纯正文写入临时文件，调用：
+3. 把只含一次 `<!-- canonical-pr-change-report -->` 的纯正文写入临时文件，调用：
 
 ```bash
 agent-infra-internal platform-pr summary-sync {task-id} \
-  --agent {standard-agent-token} --body-file {summary-body-file}
+  --agent {standard-agent-token} --body-file {summary-body-file} \
+  --change-report-file .agents/workspace/active/{task-id}/pr-change-report.json --result no_op
 ```
 
-marker、当前 HEAD、分页查找和原地更新由 core 负责。若当前 context 表明无需人工校验，则停止并返回 `summary failed: no manual validation required`，不误标通过。
+marker、报告段、权威 PR head、分页查找和原地更新由 core 负责。若当前 context 表明无需人工校验，则停止并返回 `summary failed: no manual validation required`，不误标通过。
 
 结果回传：`summary updated`、`summary skipped (no diff)` 或 `summary failed: <reason>`。

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

@@ -87,14 +87,14 @@ agent-infra-internal platform-pr resolve-external {task-id} --agent {standard-ag
 Two-option guidance for absent + `pending`:
 ```
 Task {task-id} has no PR delivery decision yet (pr_delivery_fact: unbound). Choose one:
-  - Go through the PR flow: /create-pr {task-ref}
-  - Explicitly skip and complete: /complete-task {task-ref} --skip-pr
+  - Go through the PR flow: /create-pr --task {task-ref}
+  - Explicitly skip and complete: /complete-task --task {task-ref} --skip-pr
 ```
 
 Stop message for `required` + `pending`/`skipped`:
 ```
 This project enforces the PR flow (prFlow: "required") and the task has no PR yet.
-Run /create-pr {task-ref} first, then complete; --skip-pr is not accepted under a mandatory PR flow.
+Run /create-pr --task {task-ref} first, then complete; --skip-pr is not accepted under a mandatory PR flow.
 ```
 
 Before lifecycle, verify only the hard gates:
@@ -198,6 +198,24 @@ Handle the result as follows:
 
 Keep the gate output in your reply as fresh evidence. Do not claim completion without output from this run.
 
+### Accepted sandbox-control result recovery
+
+When this skill is invoked from a sandbox and the control client reports an
+accepted request without a terminal result, preserve the request identity. The
+client prints `SANDBOX_CONTROL_REQUEST_ID: <request-id>` on stderr for this
+case. After the broker is healthy again, recover the same terminal response:
+
+```bash
+agent-infra-internal sandbox-control recover <request-id>
+```
+
+Do not submit a new request for an accepted task finalization. The broker's
+`processing/<request-id>/result.json` is private transport evidence; it is not
+a task receipt and cannot by itself prove completion. The finalization receipt
+and the host completion gate remain authoritative. If the request was rejected
+before acceptance, a new request ID may be used according to the error's
+retryability.
+
 ### 8. Inform User
 
 > Execute this step only after the verification gate passes.

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

@@ -86,14 +86,14 @@ agent-infra-internal platform-pr resolve-external {task-id} --agent {standard-ag
 缺省 + `pending` 的二选一引导消息：
 ```
 任务 {task-id} 尚未决定 PR 交付（pr_delivery_fact: unbound）。请二选一：
-  - 走 PR 流程：/create-pr {task-ref}
-  - 显式跳过并完成：/complete-task {task-ref} --skip-pr
+  - 走 PR 流程：/create-pr --task {task-ref}
+  - 显式跳过并完成：/complete-task --task {task-ref} --skip-pr
 ```
 
 `required` + `pending`/`skipped` 的停止消息：
 ```
 当前项目强制 PR 流程（prFlow: "required"），任务尚未创建 PR。
-请先运行 /create-pr {task-ref} 创建 PR 后再完成；--skip-pr 在强制 PR 下不被接受。
+请先运行 /create-pr --task {task-ref} 创建 PR 后再完成；--skip-pr 在强制 PR 下不被接受。
 ```
 
 生命周期前只验证硬门禁：
@@ -197,6 +197,23 @@ agent-infra-internal task-verify {task-id} complete-task.completed --format text
 
 将校验输出保留在回复中作为当次验证输出。没有当次校验输出，不得声明完成。
 
+### accepted 后的 sandbox-control 结果恢复
+
+如果本技能在沙箱内执行，且 control client 报告请求已经 accepted 但没有
+terminal result，必须保留原 request identity。此时 client 会在 stderr 输出
+`SANDBOX_CONTROL_REQUEST_ID: <request-id>`。broker 恢复健康后，使用同一个
+request ID 读取 terminal response：
+
+```bash
+agent-infra-internal sandbox-control recover <request-id>
+```
+
+accepted 的 task finalization 不得提交新请求。broker 的
+`processing/<request-id>/result.json` 只是私有 transport evidence，不是 task
+receipt，单凭它不能证明任务完成；finalization receipt 和宿主完成校验仍是
+权威。如果请求在 accepted 之前已被拒绝，则可依据错误的 retryability 使用
+新的 request ID。
+
 ### 8. 告知用户
 
 > 仅在校验通过后执行本步骤。

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

@@ -74,19 +74,19 @@ If `{task-id}` is available and the related task provides `issue_number`, keep `
 
 ### 6. Sync PR Metadata
 
-Capture the `result` field from `platform-pr create` (`pr_created`, `pr_reused`, or `no_op`), then run `agent-infra-internal platform-pr sync {task-id} --agent {standard-agent-token} --metadata --closing-issue --result {primary-result}`. The core copies type / `in:` labels, assignee, and a specific milestone from the Issue and maintains the closing association. Permission-bound items degrade independently, and the Issue is never updated in reverse. After the PR identity is bound, metadata or summary sync failures produce `pr_created_with_warnings`, `pr_reused_with_warnings`, or `no_op_with_warnings` from that primary result, preserve the primary-action fact, and retry only unfinished sync steps.
+Capture the `result` field from `platform-pr create` (`pr_created`, `pr_reused`, or `no_op`), then run `agent-infra-internal platform-pr sync {task-id} --agent {standard-agent-token} --metadata --closing-issue --result {primary-result}`. The shared core computes one `in:` target from task-bound diff/PR evidence and the repository mapping, converges a unique closing Issue before the PR, and syncs other metadata from the Issue. It never copies `in:` labels back from the Issue or removes unrelated labels. Permission failures degrade independently; partial side effects return blocked/`IN_LABEL_SYNC_PARTIAL`.
 
 ### 7. Generate the PR Code Change Report
 
-After creating or uniquely reusing the PR, run `agent-infra-internal platform-pr inspect {task-id}` to obtain the authoritative base/head SHAs, then follow `reference/change-report.md` to classify the complete PR line counts, Git blob byte sizes, renames, and potentially unnecessary changes. Read that reference before this step.
+After creating or uniquely reusing the PR, run `agent-infra-internal platform-pr inspect {task-id}` to obtain the authoritative base/head SHAs, then follow `reference/change-report.md` for the mechanical complete-PR report. Combine the task goal with the complete three-dot diff to produce a six-check precheck candidate with file evidence, then run `platform-pr change-report` to write the task-bound `pr-change-report.json` sidecar. Read that reference before this step.
 
-The report is part of the reviewer summary below and must also appear in the final user response. Do not provide only total lines, omit byte changes, or inspect only the last commit.
+The core renderer owns the report section. It is part of the reviewer summary below and must also appear in the final user response. Do not provide only total lines, omit byte changes, inspect only the last commit, or let the caller assemble the report section.
 
 ### 8. Publish the Review Summary
 
 Read the latest context artifacts when they exist: `plan.md` / `plan-r{N}.md`, `review-plan.md` / `review-plan-r{N}.md`, `code.md` / `code-r{N}.md`, and `review-code.md` / `review-code-r{N}.md`.
 
-Aggregate a reviewer-facing summary from those artifacts, append the `### PR Code Changes` section generated in step 7, and maintain a single idempotent summary comment via the hidden marker. Pass the same `--result {primary-result}` to `summary-sync`; a sync substep must not infer whether the PR was created or reused.
+Aggregate a reviewer-facing summary from those artifacts with exactly one `<!-- canonical-pr-change-report -->` placeholder, and maintain a single idempotent summary comment via the hidden marker. Pass `--change-report-file .agents/workspace/active/{task-id}/pr-change-report.json` and the same `--result {primary-result}` to `summary-sync`; a sync substep must not infer whether the PR was created or reused.
 
 > Canonical context, aggregation, and the `summary-sync` call live in `reference/comment-publish.md`, which points to `.agents/rules/pr-sync.md`. Read that reference before publishing.
 
@@ -139,14 +139,15 @@ Next step (alternative) - Skip active monitoring and attempt completion:
 
 - Review every commit in the branch, not only the latest one
 - `create-pr` must not defer type-label mapping to another skill; inline the mapping here when `{task-id}` is available
-- The summary marker and current HEAD are wrapped by `platform-pr summary-sync`
+- The summary marker, authoritative PR head, and `### PR Code Changes` section are wrapped by `platform-pr summary-sync`
+- An existing PR still goes through binding, report generation, summary synchronization, and result verification; reuse must not end the flow early
 - When metadata inheritance from the Issue fails, continue with task.md and branch-based fallbacks
 
 ## Error Handling
 
 - No commits found between `{target}` and `HEAD`
 - Push rejected: suggest `git pull --rebase`
-- Existing PR found: show the current PR URL and stop
+- Existing PR found: continue through binding, report generation, summary synchronization, and result verification before showing the current PR URL
 - Inaccessible Issue metadata: skip inheritance and continue
 - PR creation failed with an associated `{task-id}`: run `agent-infra-internal task-warning {task-id} add --step create-pr --severity ACTION_REQUIRED --code PR_CREATE_FAILED --target pr --message "{reason}" --action "Fix push, permission, or platform issues and rerun create-pr"` to submit a structured warning intent, and do not write an incomplete `pr_delivery_fact`
 - PR summary comment failed with an associated `{task-id}`: record a `COMMENT_SYNC_FAILED` warning per `.agents/rules/pr-sync.md`, without rolling back an already-created PR

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

@@ -74,19 +74,19 @@ description: >
 
 ### 6. 同步 PR 元数据
 
-记录 `platform-pr create` 结构化结果中的 `result`（`pr_created`、`pr_reused` 或 `no_op`），并调用 `agent-infra-internal platform-pr sync {task-id} --agent {standard-agent-token} --metadata --closing-issue --result {primary-result}`。core 从 Issue 复制 type / `in:` labels、assignee 和具体 milestone，并维护 Development 关联；逐项权限不足返回 degraded，不反向更新 Issue。PR 已成功绑定后，metadata/summary 同步失败只产生与 primary result 对应的 `pr_created_with_warnings`、`pr_reused_with_warnings` 或 `no_op_with_warnings`，保留主动作事实，重试只执行未完成的同步步骤。
+记录 `platform-pr create` 结构化结果中的 `result`（`pr_created`、`pr_reused` 或 `no_op`），并调用 `agent-infra-internal platform-pr sync {task-id} --agent {standard-agent-token} --metadata --closing-issue --result {primary-result}`。`in:` target 由 shared core 根据 task-bound diff/PR evidence 和仓库映射计算，唯一 closing Issue 按 Issue→PR 顺序收敛，其他 metadata 仍从 Issue 同步；不从 Issue 反向复制 `in:`，也不清除非 `in:` labels。权限不足逐项返回 degraded，部分副作用返回 blocked/`IN_LABEL_SYNC_PARTIAL`。
 
 ### 7. 生成 PR 代码增减报告
 
-创建或唯一复用 PR 后，调用 `agent-infra-internal platform-pr inspect {task-id}` 取得权威 base/head SHA，并按 `reference/change-report.md` 统计完整 PR 的分类行数、Git blob 字节数、rename 与疑似不必要变化。执行本步骤前先读取该 reference。
+创建或唯一复用 PR 后，调用 `agent-infra-internal platform-pr inspect {task-id}` 取得权威 base/head SHA，并按 `reference/change-report.md` 生成完整 PR 的机械统计。结合任务目标与完整三点 diff 生成六项带文件证据的 precheck candidate，再调用 `platform-pr change-report` 写入任务绑定的 `pr-change-report.json` sidecar。执行本步骤前先读取该 reference。
 
-报告既是下方 reviewer 摘要的一部分，也必须出现在最终用户回复中；不得只给总行数、忽略字节变化或只统计最后一个 commit。
+报告由 core renderer 生成，既是下方 reviewer 摘要的一部分，也必须出现在最终用户回复中；不得只给总行数、忽略字节变化、只统计最后一个 commit，或由调用方自行拼接报告段。
 
 ### 8. 发布审查摘要
 
 读取最新的上下文产物：`plan.md` / `plan-r{N}.md`、`review-plan.md` / `review-plan-r{N}.md`、`code.md` / `code-r{N}.md`、`review-code.md` / `review-code-r{N}.md`（存在时）。
 
-基于这些产物聚合 reviewer 摘要，并追加第 7 步生成的 `### PR 代码增减` 段落，再使用隐藏标记维护唯一且幂等的摘要评论。调用 `summary-sync` 时继续传递同一个 `--result {primary-result}`，不得根据同步子步骤猜测 PR 是创建还是复用。
+基于这些产物聚合 reviewer 摘要，正文只放一次 `<!-- canonical-pr-change-report -->` 占位符，再使用隐藏标记维护唯一且幂等的摘要评论。调用 `summary-sync` 时传入 `--change-report-file .agents/workspace/active/{task-id}/pr-change-report.json`，并继续传递同一个 `--result {primary-result}`；不得根据同步子步骤猜测 PR 是创建还是复用。
 
 > canonical context、摘要聚合和 `summary-sync` 调用见 `reference/comment-publish.md`（其引用 `.agents/rules/pr-sync.md`）。发布摘要前先读取该 reference。
 
@@ -139,15 +139,15 @@ agent-infra-internal task-verify {task-id} create-pr.completed --format text
 
 - 必须检查分支中的全部提交，而不是只看最后一个
 - `create-pr` 不能把 type label 映射委托给其他技能，必须在获取到 `{task-id}` 时于本技能内内联处理
-- summary marker 与当前 HEAD 由 `platform-pr summary-sync` 统一包装
-- 如果当前分支已存在 PR，直接告知用户 PR URL 并结束，不做重复同步
+- summary marker、权威 PR head 和 `### PR 代码增减` 由 `platform-pr summary-sync` 统一包装
+- 如果当前分支已存在 PR，仍须完成绑定、报告生成、摘要同步和结果校验；不得因复用而直接结束
 - 如果从 Issue 继承元数据失败，继续使用 task.md 和分支推断兜底
 
 ## 错误处理
 
 - `{target}` 与 `HEAD` 之间没有可提交内容
 - 推送被拒绝：建议执行 `git pull --rebase`
-- 已存在 PR：直接输出当前 PR URL 并结束
+- 已存在 PR：继续完成绑定、报告生成、摘要同步和结果校验后输出当前 PR URL
 - 无法访问 Issue 元数据：跳过继承并继续
 - PR 创建失败且已关联 `{task-id}`：调用 `agent-infra-internal task-warning {task-id} add --step create-pr --severity ACTION_REQUIRED --code PR_CREATE_FAILED --target pr --message "{reason}" --action "修复推送、权限或平台问题后重跑 create-pr"` 提交结构化 warning 意图，不写不完整 `pr_delivery_fact`
 - PR 摘要评论失败且已关联 `{task-id}`：按 `.agents/rules/pr-sync.md` 记录 `COMMENT_SYNC_FAILED` 告警，不回滚已创建 PR

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

@@ -21,6 +21,7 @@
       "when": "issue_number_exists",
       "expected_pr_comment_marker": "<!-- sync-pr:{task-id}:summary -->",
       "verify_in_labels_match_pr": true,
+      "verify_in_labels_computed": true,
       "verify_pr_type_label": true,
       "verify_pr_assignee": true,
       "verify_issue_fields": true,

package/templates/.agents/skills/create-pr/reference/change-report.en.md

@@ -4,7 +4,7 @@
 {"source":"platform-pr-inspect","diff":"three-dot-find-renames","metrics":["numstat-lines","git-blob-bytes"],"publish":["pr-summary","user-response"]}
 -->
 
-After a PR is created or uniquely reused, use the authoritative `base.sha` and `head.sha` returned by `platform-pr inspect` to measure the complete PR diff. Do not substitute the last commit or current worktree state.
+After a PR is created or uniquely reused, use the authoritative `base.sha` and `head.sha` returned by `platform-pr inspect` to measure the complete PR diff. Do not substitute the last commit or current worktree state. The task-intent digest covers only the semantic section from `# Task`/`# 任务` through `## Context`/`## 上下文`, so lifecycle logs, receipts, and version metadata do not stale a sidecar for the same head.
 
 ## Evidence Commands
 
@@ -14,6 +14,18 @@ git diff --find-renames --name-status {base-sha}...{head-sha}
 git diff --find-renames --summary {base-sha}...{head-sha}
 ```
 
+Pass the script JSON and the model-generated six-check precheck candidate to the typed core:
+
+```bash
+agent-infra-internal platform-pr change-report {task-id} \
+  --agent {standard-agent-token} --mechanical-file {mechanical-report-file} \
+  --precheck-file {precheck-candidate-file}
+```
+
+The core validates the task-intent digest, PR identity, complete patch SHA, totals, and the ordered checks `target-alignment`, `change-composition`, `compatibility-policy`, `legacy-path-cleanup`, `redundancy`, and `scope-discipline`. A `needs-review` check routes to `review-code`; `formalReview` remains `false`.
+
+When generating the candidate, each check's `rationale` must state its actual finding: `target-alignment` explains the goal relationship, `change-composition` summarizes where new code concentrates responsibilities, `compatibility-policy` states the compatibility result, `legacy-path-cleanup` states how legacy paths were handled, `redundancy` states the redundancy result, and `scope-discipline` states the scope judgment. Do not reuse generic phrases such as "within scope" across checks; each check must provide at least one directly relevant path, line range, and concise `detail`, using the deployed skill's language. Chinese skill deployments must use Chinese. These high-level rationales and evidence are rendered in the canonical summary.
+
 The script calculates both `numstat` line counts and exact Git blob byte sizes between the merge base and head. Bytes provide a stable unit, cover binary files, and reveal same-line compaction; submodules are not blobs and contribute zero bytes. Added files have zero old bytes, deleted files have zero new bytes, pure renames have zero net bytes, and copies count only the new destination content.
 
 Count binary files in the file total but do not invent line counts for `-` numstat values. Explain renames and copies from the script's per-file records, `name-status`, and `summary` so moves are not reported as full rewrites.
@@ -31,7 +43,7 @@ Using the repository's actual structure, assign every file to exactly one closes
 
 The table must contain component, file count, added lines, deleted lines, net lines, old bytes, new bytes, and net bytes, followed by a total row. Byte columns describe the blob content size of files involved in this change, not disk usage for the entire repository or worktree. Use exact integers; optional KiB/MiB values may aid readability but must not replace byte counts.
 
-Category line and byte totals must each reconcile exactly with the script's `totals`. Then list the largest files by line change and absolute net-byte change, distinguishing source, tests, template mirrors, and pure renames.
+Category line and byte totals must each reconcile exactly with the script's `totals`. Then, for text files only, list the largest files by line change and absolute net-byte change, distinguishing source, tests, and template mirrors. Keep binary files in the category totals only; do not rank or interpret their content. Show renames as path changes without inferring a "pure rename" label.
 
 ## Required Analysis
 
@@ -40,7 +52,7 @@ Briefly explain:
 - where growth is concentrated and how runtime code compares with tests, docs, and templates;
 - whether net line and net byte changes tell different stories, especially for substantial same-line compaction or expansion;
 - which line changes are path moves, bilingual mirrors, or mechanical synchronization;
-- whether any change cannot be traced directly to the PR goal and may be unnecessary; if none, state the evidence;
+- whether any change cannot be traced directly to the PR goal and may be unnecessary; if none, state the evidence; every check must cite file and line evidence;
 - when a test fixture is much larger than production changes, what risk it covers instead of judging it only by size.
 
-Add the complete report as a `### PR Code Changes` section in the reviewer summary body. Preserve the same table and conclusion in the user-visible create-pr completion response. Do not create a second PR comment for this report.
+Do not write the `### PR Code Changes` section in the caller. Put exactly one `<!-- canonical-pr-change-report -->` placeholder in the plain body and let `summary-sync --change-report-file .agents/workspace/active/{task-id}/pr-change-report.json --result {primary-result}` replace it through the core renderer. Do not create a second PR comment for this report.

package/templates/.agents/skills/create-pr/reference/change-report.zh-CN.md

@@ -4,7 +4,7 @@
 {"source":"platform-pr-inspect","diff":"three-dot-find-renames","metrics":["numstat-lines","git-blob-bytes"],"publish":["pr-summary","user-response"]}
 -->
 
-PR 创建或复用成功后，使用 `platform-pr inspect` 返回的权威 `base.sha` 与 `head.sha` 统计完整 PR 差异，不以最后一个 commit 或工作树状态代替。
+PR 创建或复用成功后，使用 `platform-pr inspect` 返回的权威 `base.sha` 与 `head.sha` 统计完整 PR 差异，不以最后一个 commit 或工作树状态代替。任务意图 digest 只覆盖 `# 任务`/`# Task` 到 `## 上下文`/`## Context` 的语义区间，因此生命周期日志、收据和版本元数据不会使同一 head 的 sidecar 失效。
 
 ## 证据命令
 
@@ -14,6 +14,18 @@ git diff --find-renames --name-status {base-sha}...{head-sha}
 git diff --find-renames --summary {base-sha}...{head-sha}
 ```
 
+将脚本 JSON 和模型生成的六项 precheck candidate 交给 typed core：
+
+```bash
+agent-infra-internal platform-pr change-report {task-id} \
+  --agent {standard-agent-token} --mechanical-file {mechanical-report-file} \
+  --precheck-file {precheck-candidate-file}
+```
+
+core 校验任务意图 digest、PR identity、完整 patch SHA、统计合计和固定顺序的 `target-alignment`、`change-composition`、`compatibility-policy`、`legacy-path-cleanup`、`redundancy`、`scope-discipline`。任一项为 `needs-review` 时路由到 `review-code`，`formalReview` 仍为 `false`。
+
+生成 candidate 时，六项 `rationale` 必须分别写出实际检查结论：`target-alignment` 说明目标对应关系，`change-composition` 概括新增代码集中承担的职责，`compatibility-policy` 说明兼容策略，`legacy-path-cleanup` 说明旧路径处理，`redundancy` 说明冗余检查结果，`scope-discipline` 说明范围判断。不得六项复用“符合范围”等泛化套话；每项至少提供一条直接支持结论的路径、行号和简短 `detail`，并遵循当前已部署技能的语言。中文技能必须使用中文。这些高层理由和证据会直接展示在 canonical 摘要中。
+
 脚本在 merge base 与 head 之间同时计算 `numstat` 行数和 Git blob 的精确字节数。字节比字符具有稳定口径，也能覆盖二进制文件和同行内缩减；子模块不是 blob，按 0 字节贡献核算。新增文件的旧字节数为 0，删除文件的新字节数为 0，纯 rename 的净字节数为 0，copy 只计新增目标内容。
 
 `numstat` 中的二进制文件计入文件数，但不虚构行数。rename/copy 依据脚本的逐文件记录、`name-status` 与 `summary` 单独说明，避免把移动误报为整文件重写。
@@ -31,7 +43,7 @@ git diff --find-renames --summary {base-sha}...{head-sha}
 
 输出表格必须包含“部分、文件数、新增行、删除行、净增行、旧字节、新字节、净字节”，并有合计行。字节列表示本次变更涉及文件的 blob 内容体积，不表示整个仓库或工作树的磁盘占用。使用精确整数；可附加 KiB/MiB 便于阅读，但不能替代字节数。
 
-各类别的行数和字节数之和必须分别与脚本的 `totals` 一致。随后分别列出行数变化和绝对净字节变化最大的文件，并区分源码、测试、模板镜像和纯 rename。
+各类别的行数和字节数之和必须分别与脚本的 `totals` 一致。随后仅针对文本文件，分别列出行数变化和绝对净字节变化最大的文件，并区分源码、测试和模板镜像；二进制文件只保留在分类合计中，不参与代表性文件排序或内容判断。rename 只按路径变化展示，不推断“纯 rename”。
 
 ## 分析要求
 
@@ -40,7 +52,7 @@ git diff --find-renames --summary {base-sha}...{head-sha}
 - 增长主要集中在哪里，运行时代码与测试/文档/模板各占多少；
 - 行数净变化与净字节变化是否给出不同结论，尤其指出同行内明显缩减或膨胀；
 - 哪些行数只是路径迁移、双语镜像或机械同步；
-- 是否存在与 PR 目标无法直接对应、疑似不必要的变化；若没有，明确说明判断依据；
+- 是否存在与 PR 目标无法直接对应、疑似不必要的变化；若没有，明确说明判断依据；每项结论必须给出文件和行号证据；
 - 若某个测试 fixture 明显大于生产改动，解释它覆盖的风险，而不是仅以行数评价。
 
-将完整报告以 `### PR 代码增减` 段落写入 reviewer 摘要正文，并在 create-pr 的用户可见完成回复中原样保留同一张统计表与结论。不要把报告另建成第二条 PR 评论。
+调用方不要自行写入 `### PR 代码增减`。把恰好包含一次 `<!-- canonical-pr-change-report -->` 的普通摘要正文交给 `summary-sync --change-report-file .agents/workspace/active/{task-id}/pr-change-report.json --result {primary-result}`，由 core renderer 替换并发布。报告不另建第二条 PR 评论。

package/templates/.agents/skills/create-pr/reference/comment-publish.en.md

@@ -2,11 +2,13 @@
 
 After PR creation, run `agent-infra-internal platform-pr summary-context {task-id}` and aggregate the reviewer summary only from its canonical artifacts according to `.agents/rules/pr-sync.md`.
 
-Write the plain summary body to a temporary file, then run:
+Write the plain summary body, containing exactly one `<!-- canonical-pr-change-report -->` placeholder and no report heading/JSON, marker, or HEAD metadata, to a temporary file, then run:
 
 ```bash
 agent-infra-internal platform-pr summary-sync {task-id} \
-  --agent {standard-agent-token} --body-file {summary-body-file} --result {primary-result}
+  --agent {standard-agent-token} --body-file {summary-body-file} \
+  --change-report-file .agents/workspace/active/{task-id}/pr-change-report.json \
+  --result {primary-result}
 ```
 
-The caller does not add markers, HEAD metadata, or comment API parameters. `--result` is required and must be passed unchanged from `platform-pr create`; `no_op` maps to `no_op_with_warnings` if summary synchronization degrades. Summary failures do not roll back a created or reused PR.
+The caller does not add markers, HEAD metadata, report sections, or comment API parameters. The typed core rechecks the task-bound sidecar against the authoritative PR snapshot and renders the report. `--result` is required and must be passed unchanged from `platform-pr create`; `no_op` maps to `no_op_with_warnings` if summary synchronization degrades. Missing/stale/invalid sidecars or body bypasses do not publish, and summary failures do not roll back a created or reused PR.

package/templates/.agents/skills/create-pr/reference/comment-publish.zh-CN.md

@@ -2,11 +2,13 @@
 
 创建 PR 后先调用 `agent-infra-internal platform-pr summary-context {task-id}`，只根据返回的 canonical 产物按 `.agents/rules/pr-sync.md` 聚合 reviewer 摘要。
 
-把纯摘要正文写入临时文件，再调用：
+把恰好包含一次 `<!-- canonical-pr-change-report -->` 且不含报告标题/JSON、marker 或 HEAD 元数据的纯摘要正文写入临时文件，再调用：
 
 ```bash
 agent-infra-internal platform-pr summary-sync {task-id} \
-  --agent {standard-agent-token} --body-file {summary-body-file} --result {primary-result}
+  --agent {standard-agent-token} --body-file {summary-body-file} \
+  --change-report-file .agents/workspace/active/{task-id}/pr-change-report.json \
+  --result {primary-result}
 ```
 
-调用方不添加 marker、HEAD 或评论 API 参数。`--result` 是必填的，必须把 `platform-pr create` 的 `result` 原样传入；摘要失败沿用该 primary result 映射 warning（`no_op` 对应 `no_op_with_warnings`），不回滚已创建或复用的 PR。结果映射沿用 `.agents/rules/pr-sync.md`。
+调用方不添加 marker、HEAD、报告段或评论 API 参数。typed core 会重新校验任务绑定 sidecar 与权威 PR snapshot 并渲染报告。`--result` 是必填的，必须把 `platform-pr create` 的 `result` 原样传入；sidecar 缺失/过期/非法或正文旁路时不发布，摘要失败沿用该 primary result 映射 warning（`no_op` 对应 `no_op_with_warnings`），不回滚已创建或复用的 PR。结果映射沿用 `.agents/rules/pr-sync.md`。

package/templates/.agents/skills/create-pr/reference/pr-body-template.en.md

@@ -42,7 +42,7 @@ Type label mapping:
 
 Metadata sync order:
 1. query Issue labels and milestone via the Issue read command in `.agents/rules/issue-pr-commands.md`
-2. build `{label-args}` from the mapped type label, non-`type:` / non-`status:` Issue labels, and the current Issue `in:` labels (commit already computed them, so do not recompute them here and do not write back to the Issue)
+2. build `{label-args}` from the mapped type label and non-`type:` / non-`status:` Issue labels; `in:` labels are computed once by the shared platform core from task-bound diff/PR evidence, so do not recompute them here or copy them back from the Issue
 3. build `{milestone-arg}` by following "Phase 3: `create-pr`" in `.agents/rules/milestone-inference.md` and reusing the Issue milestone directly
 4. pass `{label-args}` and `{milestone-arg}` atomically by using the create-PR command template and permission-degradation rules in `.agents/rules/issue-pr-commands.md`
 5. ensure the PR body contains `Closes #{issue-number}` or an equivalent closing keyword

package/templates/.agents/skills/create-pr/reference/pr-body-template.zh-CN.md

@@ -42,7 +42,7 @@ git diff <target-branch>...HEAD
 
 元数据同步顺序：
 1. 通过 `.agents/rules/issue-pr-commands.md` 的 Issue 读取命令查询 Issue labels 和 milestone
-2. 从映射出的 type label、非 `type:` / 非 `status:` 的 Issue labels，以及当前 Issue `in:` labels 构建 `{label-args}`（commit 已经计算过，不在此重算，也不写回 Issue）
+2. 从映射出的 type label 和非 `type:` / 非 `status:` 的 Issue labels 构建 `{label-args}`；`in:` labels 由 shared platform core 根据 task-bound diff/PR evidence 统一计算，不在正文生成步骤重算，也不从 Issue 反向复制
 3. 按 `.agents/rules/milestone-inference.md` 的 "阶段 3：`create-pr`" 复用 Issue milestone 构建 `{milestone-arg}`
 4. 按 `.agents/rules/issue-pr-commands.md` 的创建 PR 命令模板与权限降级规则，将 `{label-args}` 和 `{milestone-arg}` 原子化传入
 5. 确保 PR 正文包含 `Closes #{issue-number}` 或等价关闭关键字

package/templates/.agents/skills/create-pr/scripts/change-report.mjs

@@ -1,4 +1,5 @@
 import { execFileSync } from "node:child_process";
+import { createHash } from "node:crypto";
 
 function fail(message) {
   process.stderr.write(`${message}\n`);
@@ -128,6 +129,7 @@ function numericLineCount(value) {
 function main() {
   const options = parseArgs(process.argv.slice(2));
   const mergeBase = git(["merge-base", options.base, options.head], options).trim();
+  const patch = git(["diff", "--no-ext-diff", "--binary", "--find-renames", mergeBase, options.head], options, null);
   const diffArgs = ["diff", "--no-ext-diff", "--find-renames", "-z", mergeBase, options.head];
   const files = parseRawDiff(git([...diffArgs.slice(0, 2), "--raw", "--abbrev=64", ...diffArgs.slice(2)], options, null));
   const numstat = parseNumstat(git([...diffArgs.slice(0, 2), "--numstat", ...diffArgs.slice(2)], options, null));
@@ -191,6 +193,7 @@ function main() {
     base: options.base,
     head: options.head,
     mergeBase,
+    patchSha256: createHash("sha256").update(patch).digest("hex"),
     files: reportFiles,
     totals
   }, null, 2)}\n`);

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

@@ -9,7 +9,7 @@ description: >
 # Design Technical Plan
 > `--agent` values are defined in `.agents/rules/task-management.md` under “Collaborator Token Specification”.
 
-If the entry operands contain `--orchestrated`, bind `{execution-flag}` to `--orchestrated` and forward it unchanged to the completed event; otherwise bind it to an empty value. Never infer it from `orchestration.json`, environment variables, or prior artifacts.
+If the entry operands contain `--orchestrated`, bind `{execution-flag}` to `--orchestrated` and forward it unchanged to the completed event; otherwise bind it to an empty value. Never infer it from `orchestration.json`, environment variables, or prior artifacts. Lifecycle events also require explicit trigger data: use `{trigger-initiator}=orchestrator` for orchestration and `model` otherwise; `{request-id}` is a stable single-line identifier for this task and artifact round, and `{reason-code}` is `user-request`, `new-requirement`, or `upstream-fact-doubt`. Reuse the same values for started and completed.
 
 ## Boundary / Critical Rules
 
@@ -41,7 +41,7 @@ Before the state check is complete, do not make external-state assertions such a
 
 ## Step Start: Write the started Marker
 
-After resolving the artifact context and before this round's first artifact action, run `agent-infra-internal task-event {task-id} plan.started --agent {standard-agent-token}` and verify the returned `artifactContext`.
+After resolving the artifact context and before this round's first artifact action, run `agent-infra-internal task-event {task-id} plan.started --agent {standard-agent-token} --initiator {trigger-initiator} --request-id {request-id} --reason-code {reason-code}` and verify the returned `artifactContext`.
 
 ## Steps
 
@@ -115,7 +115,17 @@ Update `.agents/workspace/active/{task-id}/task.md`:
   - Overwrite the `effort` field in frontmatter with the new value
   - Append a `## Effort Re-estimate` section to this round's plan artifact `{plan-artifact}`, recording: `effort {old} → {new} (rationale: {short basis grounded in this plan})`
   If the re-estimated value matches the current value, skip it: do not write the `## Effort Re-estimate` section. The Flow A sync that follows reads the possibly updated frontmatter and propagates the new value to the Issue automatically.
-After the business fields are updated, run `agent-infra-internal task-event {task-id} plan.completed --agent {standard-agent-token} --artifact {plan-artifact} {execution-flag}` so the core atomically records the link, stage, agent, metadata, and Activity Log.
+After writing the local artifact, run the pre-completion gate:
+
+```bash
+agent-infra-internal task-artifact {task-id} finalize-local --family plan --artifact {plan-artifact}
+```
+
+- 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.
+
+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}
   ```