@fitlab-ai/agent-infra 0.12.1 → 0.12.2

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

@@ -9,7 +9,7 @@ description: >
 # 代码审查
 > `--agent` 取值见 `.agents/rules/task-management.md`「合作者 token 规范」。
 
-若入口业务操作数包含 `--orchestrated`，绑定 `{execution-flag}` = `--orchestrated` 并原样转发给 summary finalizer 与 completed 事件；否则绑定为空。不得从 `orchestration.json`、环境变量或历史产物推断该标记。生命周期事件还必须携带显式触发信息：编排调用使用 `{trigger-initiator}=orchestrator`，否则使用 `model`；`{request-id}` 是本任务与本轮产物的稳定单行标识，普通调用的 `{reason-code}` 使用 `user-request` 或 `review-finding`；仅用户明确要求补充审查时，使用 `--initiator human --reason-code manual-review-supplement`。started 与 completed 使用同一组值。
+生命周期事件必须携带显式触发信息：普通调用使用 `model`；仅用户明确要求补充审查时，使用 `--initiator human --reason-code manual-review-supplement`。`{request-id}` 是本任务与本轮产物的稳定单行标识，`{reason-code}` 普通审查使用 `user-request` 或 `review-finding`；started 与 completed 使用同一组值。
 
 审查最新代码轮次，并产出 `review-code.md` 或 `review-code-r{N}.md`。
 
@@ -112,9 +112,9 @@ agent-infra-internal task-artifact {task-id} init --family review-code --artifac
 
 ### 6. 更新任务状态
 
-- 报告完成后，先调用 `agent-infra-internal task-review {task-id} preflight --stage code --artifact {review-artifact} {execution-flag}`，不得先写入账本。失败后直接修正正式产物并重跑。
+- 报告完成后，先调用 `agent-infra-internal task-review {task-id} preflight --stage code --artifact {review-artifact}`，不得先写入账本。失败后直接修正正式产物并重跑。
 - 只有 preflight 通过后，新 finding 才逐条调用 `agent-infra-internal task-ledger {task-id} finding-upsert --stage code --review-artifact {review-artifact} --ordinal {n} --severity {blocker|major|minor} --evidence {review-artifact}#{anchor}`；复核上一轮响应时调用 `finding-review --id {ledger-id} --status {confirmed|closed|open|needs-human-decision} --evidence {相称证据}`。升级为 `needs-human-decision` 时，按详情块中的判断追加 `--needs-implementation true|false`。不得扫描编号或手写账本行
-- 全部账本写入完成后调用 `agent-infra-internal task-review {task-id} finalize-summary --stage code --artifact {review-artifact} {execution-flag}`；不能把失败类型或 `changed=false` 当作自动授权
+- 全部账本写入完成后调用 `agent-infra-internal task-review {task-id} finalize-summary --stage code --artifact {review-artifact}`；不能把失败类型或 `changed=false` 当作自动授权
 
   从该次返回值绑定并复用以下结构化映射：
 
@@ -124,10 +124,10 @@ agent-infra-internal task-artifact {task-id} init --family review-code --artifac
   {unresolved-minor} = stageStatus.unresolvedFindingCounts.minor
   ```
 
-  该 intent 原子最终化报告摘要并返回同一次账本快照；不得再调用 `stage-status`、手工替换占位符或扫描问题清单。失败后，模型只能在共享规则的机械安全门通过时修改同一个受控 artifact，并完整重跑相同 intent；每次失败都重新判断是否收敛。最终一次完整成功返回决定同一快照的 verdict 和计数：`stageStatus.canAdvance=true` 且结论为 Approved 时允许跨阶段推进；`stageStatus.canAdvance=false` 时仍须执行 `agent-infra-internal task-event {task-id} review-code.completed --agent {standard-agent-token} --initiator {trigger-initiator} --request-id {request-id} --reason-code {reason-code} --artifact {review-artifact} --verdict {approved|changes-requested|rejected} --blockers {unresolved-blockers} --major {unresolved-major} --minor {unresolved-minor} --manual-validation {n} {execution-flag}`，使用 `changes-requested` 并路由到同阶段修订/复审（报告明确拒绝时使用 `rejected`）。失败、模型停止、无进展或紧急熔断时，不发布完成事件或跨阶段命令，但必须按 `reference/output-templates.md` 的 `repair-stop` 场景展示已有 summary/findings、artifact、实际修复次数、最后诊断和停止原因
+  该 intent 原子最终化报告摘要并返回同一次账本快照；不得再调用 `stage-status`、手工替换占位符或扫描问题清单。失败后，模型只能在共享规则的机械安全门通过时修改同一个受控 artifact，并完整重跑相同 intent；每次失败都重新判断是否收敛。最终一次完整成功返回决定同一快照的 verdict 和计数：`stageStatus.canAdvance=true` 且结论为 Approved 时允许跨阶段推进；`stageStatus.canAdvance=false` 时仍须执行 `agent-infra-internal task-event {task-id} review-code.completed --agent {standard-agent-token} --initiator {trigger-initiator} --request-id {request-id} --reason-code {reason-code} --artifact {review-artifact} --verdict {approved|changes-requested|rejected} --blockers {unresolved-blockers} --major {unresolved-major} --minor {unresolved-minor} --manual-validation {n}`，使用 `changes-requested` 并路由到同阶段修订/复审（报告明确拒绝时使用 `rejected`）。失败、模型停止、无进展或紧急熔断时，不发布完成事件或跨阶段命令，但必须按 `reference/output-templates.md` 的 `repair-stop` 场景展示已有 summary/findings、artifact、实际修复次数、最后诊断和停止原因
 - 仅当 `canAdvance=true`、本轮结论为 Approved 且 `T == R^{tree}` 时写入 `last_reviewed_commit: {R}`；Approved 快照包含未提交差异时清除旧值。否则保留既有值，不得推进或清空
 - Approved 出口按 `reference/output-templates.md` 选择唯一场景，并使用对应的 `agent-client next-steps` helper 生成下一步命令。
-- 完成 `last_reviewed_commit` 处理后执行 `agent-infra-internal task-event {task-id} review-code.completed --agent {standard-agent-token} --initiator {trigger-initiator} --request-id {request-id} --reason-code {reason-code} --artifact {review-artifact} --verdict {approved|changes-requested|rejected} --blockers {unresolved-blockers} --major {unresolved-major} --minor {unresolved-minor} --manual-validation {n} {execution-flag}`
+- 完成 `last_reviewed_commit` 处理后执行 `agent-infra-internal task-event {task-id} review-code.completed --agent {standard-agent-token} --initiator {trigger-initiator} --request-id {request-id} --reason-code {reason-code} --artifact {review-artifact} --verdict {approved|changes-requested|rejected} --blockers {unresolved-blockers} --major {unresolved-major} --minor {unresolved-minor} --manual-validation {n}`
 
 完成日志必须始终写入 `Manual-validation: {n}` 字段，0 也保留。
 `manual-validation` 是 `ai task log` 中 review 行「人工校验点」（EN `Manual-validation`）计数的数据源；不要新增并行人工验证字段。

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

@@ -9,7 +9,7 @@ description: >
 # Technical Plan Review
 > `--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 both the summary finalizer and 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` or `review-finding`. Reuse the same values for started and completed.
+Lifecycle events require explicit trigger data: ordinary skill invocation uses `model`; use `human` only when the user explicitly requests it. `{request-id}` is a stable single-line identifier for this task and artifact round, and `{reason-code}` use `user-request` or `review-finding`. Reuse the same values for started and completed.
 
 Review the latest plan artifact and produce `review-plan.md` or `review-plan-r{N}.md`.
 
@@ -87,7 +87,7 @@ Create `<task-workspace>/active/{task-id}/{review-artifact}`.
 
 ### 6. Update Task Status
 
-After the report, call `agent-infra-internal task-review {task-id} preflight --stage plan --artifact {review-artifact} {execution-flag}` before any ledger write. On failure, correct the formal artifact directly and rerun it. Only after preflight passes, submit each new finding with `agent-infra-internal task-ledger {task-id} finding-upsert --stage plan --review-artifact {review-artifact} --ordinal {n} --severity {blocker|major|minor} --evidence {review-artifact}#{anchor}` or prior-response dispositions with `finding-review --id {ledger-id} --status {confirmed|closed|open|needs-human-decision} --evidence {evidence}`. Do not scan ids or edit ledger rows. After all ledger writes, call `agent-infra-internal task-review {task-id} finalize-summary --stage plan --artifact {review-artifact} {execution-flag}`; never treat an error type or `changed=false` as automatic authorization.
+After the report, call `agent-infra-internal task-review {task-id} preflight --stage plan --artifact {review-artifact}` before any ledger write. On failure, correct the formal artifact directly and rerun it. Only after preflight passes, submit each new finding with `agent-infra-internal task-ledger {task-id} finding-upsert --stage plan --review-artifact {review-artifact} --ordinal {n} --severity {blocker|major|minor} --evidence {review-artifact}#{anchor}` or prior-response dispositions with `finding-review --id {ledger-id} --status {confirmed|closed|open|needs-human-decision} --evidence {evidence}`. Do not scan ids or edit ledger rows. After all ledger writes, call `agent-infra-internal task-review {task-id} finalize-summary --stage plan --artifact {review-artifact}`; never treat an error type or `changed=false` as automatic authorization.
 
 Bind and reuse this structured mapping from that one response:
 
@@ -97,7 +97,7 @@ Bind and reuse this structured mapping from that one response:
 {unresolved-minor} = stageStatus.unresolvedFindingCounts.minor
 ```
 
-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. After a failure, the model may edit the same controlled artifact and rerun the same intent only when the shared rule's mechanical gates pass; reassess convergence after every failure. The final complete result determines the verdict and counts from that same snapshot: `stageStatus.canAdvance=true` with an Approved conclusion permits cross-stage advancement; `stageStatus.canAdvance=false` still requires `agent-infra-internal task-event {task-id} review-plan.completed --agent {standard-agent-token} --initiator {trigger-initiator} --request-id {request-id} --reason-code {reason-code} --artifact {review-artifact} --verdict {approved|changes-requested|rejected} --blockers {unresolved-blockers} --major {unresolved-major} --minor {unresolved-minor} --manual-validation {n} {execution-flag}`, using `changes-requested` and routing to same-stage revision/review (use `rejected` when the report explicitly rejects). On failure, model stop, lack of progress, or the emergency cap, do not publish a completion event or cross-stage command; use the `repair-stop` scenario in `reference/output-templates.md` to show existing summary/findings, the artifact, actual repair attempts, the last diagnostic, and the stop reason.
+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. After a failure, the model may edit the same controlled artifact and rerun the same intent only when the shared rule's mechanical gates pass; reassess convergence after every failure. The final complete result determines the verdict and counts from that same snapshot: `stageStatus.canAdvance=true` with an Approved conclusion permits cross-stage advancement; `stageStatus.canAdvance=false` still requires `agent-infra-internal task-event {task-id} review-plan.completed --agent {standard-agent-token} --initiator {trigger-initiator} --request-id {request-id} --reason-code {reason-code} --artifact {review-artifact} --verdict {approved|changes-requested|rejected} --blockers {unresolved-blockers} --major {unresolved-major} --minor {unresolved-minor} --manual-validation {n}`, using `changes-requested` and routing to same-stage revision/review (use `rejected` when the report explicitly rejects). On failure, model stop, lack of progress, or the emergency cap, do not publish a completion event or cross-stage command; use the `repair-stop` scenario in `reference/output-templates.md` to show existing summary/findings, the artifact, actual repair attempts, the last diagnostic, and the stop reason.
 
 `manual-validation` is the data source for the `Manual-validation` count folded into review rows in `ai task log`; do not add a parallel manual-verification field.
 

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

@@ -9,7 +9,7 @@ description: >
 # 技术方案审查
 > `--agent` 取值见 `.agents/rules/task-management.md`「合作者 token 规范」。
 
-若入口业务操作数包含 `--orchestrated`，绑定 `{execution-flag}` = `--orchestrated` 并原样转发给 summary finalizer 与 completed 事件；否则绑定为空。不得从 `orchestration.json`、环境变量或历史产物推断该标记。生命周期事件还必须携带显式触发信息：编排调用使用 `{trigger-initiator}=orchestrator`，否则使用 `model`；`{request-id}` 是本任务与本轮产物的稳定单行标识，`{reason-code}` 使用 `user-request` 或 `review-finding`；started 与 completed 使用同一组值。
+生命周期事件必须携带显式触发信息：普通技能调用使用 `model`；仅用户明确要求时使用 `human`。`{request-id}` 是本任务与本轮产物的稳定单行标识，`{reason-code}` 使用 `user-request` 或 `review-finding`；started 与 completed 使用同一组值。
 
 审查最新技术方案产物，并产出 `review-plan.md` 或 `review-plan-r{N}.md`。
 
@@ -90,7 +90,7 @@ agent-infra-internal task-artifact {task-id} init --family review-plan --artifac
 
 ### 6. 更新任务状态
 
-报告完成后，先调用 `agent-infra-internal task-review {task-id} preflight --stage plan --artifact {review-artifact} {execution-flag}`，不得先写入账本。失败后直接修正正式产物并重跑；只有 preflight 通过后，才逐条调用 `agent-infra-internal task-ledger {task-id} finding-upsert --stage plan --review-artifact {review-artifact} --ordinal {n} --severity {blocker|major|minor} --evidence {review-artifact}#{anchor}`，或复核上一轮响应时调用 `finding-review --id {ledger-id} --status {confirmed|closed|open|needs-human-decision} --evidence {相称证据}`。不得扫描编号或手写账本行。全部账本写入完成后调用 `agent-infra-internal task-review {task-id} finalize-summary --stage plan --artifact {review-artifact} {execution-flag}`；不能把失败类型或 `changed=false` 当作自动授权。
+报告完成后，先调用 `agent-infra-internal task-review {task-id} preflight --stage plan --artifact {review-artifact}`，不得先写入账本。失败后直接修正正式产物并重跑；只有 preflight 通过后，才逐条调用 `agent-infra-internal task-ledger {task-id} finding-upsert --stage plan --review-artifact {review-artifact} --ordinal {n} --severity {blocker|major|minor} --evidence {review-artifact}#{anchor}`，或复核上一轮响应时调用 `finding-review --id {ledger-id} --status {confirmed|closed|open|needs-human-decision} --evidence {相称证据}`。不得扫描编号或手写账本行。全部账本写入完成后调用 `agent-infra-internal task-review {task-id} finalize-summary --stage plan --artifact {review-artifact}`；不能把失败类型或 `changed=false` 当作自动授权。
 
 从该次返回值绑定并复用以下结构化映射：
 
@@ -100,7 +100,7 @@ agent-infra-internal task-artifact {task-id} init --family review-plan --artifac
 {unresolved-minor} = stageStatus.unresolvedFindingCounts.minor
 ```
 
-该 intent 原子最终化报告摘要并返回同一次账本快照；不得再调用 `stage-status`、手工替换占位符或扫描问题清单。失败后，模型只能在共享规则的机械安全门通过时修改同一个受控 artifact，并完整重跑相同 intent；每次失败都重新判断是否收敛。最终一次完整成功返回决定同一快照的 verdict 和计数：`stageStatus.canAdvance=true` 且结论为 Approved 时允许跨阶段推进；`stageStatus.canAdvance=false` 时仍须执行 `agent-infra-internal task-event {task-id} review-plan.completed --agent {standard-agent-token} --initiator {trigger-initiator} --request-id {request-id} --reason-code {reason-code} --artifact {review-artifact} --verdict {approved|changes-requested|rejected} --blockers {unresolved-blockers} --major {unresolved-major} --minor {unresolved-minor} --manual-validation {n} {execution-flag}`，使用 `changes-requested` 并路由到同阶段修订/复审（报告明确拒绝时使用 `rejected`）。失败、模型停止、无进展或紧急熔断时，不发布完成事件或跨阶段命令，但必须按 `reference/output-templates.md` 的 `repair-stop` 场景展示已有 summary/findings、artifact、实际修复次数、最后诊断和停止原因。
+该 intent 原子最终化报告摘要并返回同一次账本快照；不得再调用 `stage-status`、手工替换占位符或扫描问题清单。失败后，模型只能在共享规则的机械安全门通过时修改同一个受控 artifact，并完整重跑相同 intent；每次失败都重新判断是否收敛。最终一次完整成功返回决定同一快照的 verdict 和计数：`stageStatus.canAdvance=true` 且结论为 Approved 时允许跨阶段推进；`stageStatus.canAdvance=false` 时仍须执行 `agent-infra-internal task-event {task-id} review-plan.completed --agent {standard-agent-token} --initiator {trigger-initiator} --request-id {request-id} --reason-code {reason-code} --artifact {review-artifact} --verdict {approved|changes-requested|rejected} --blockers {unresolved-blockers} --major {unresolved-major} --minor {unresolved-minor} --manual-validation {n}`，使用 `changes-requested` 并路由到同阶段修订/复审（报告明确拒绝时使用 `rejected`）。失败、模型停止、无进展或紧急熔断时，不发布完成事件或跨阶段命令，但必须按 `reference/output-templates.md` 的 `repair-stop` 场景展示已有 summary/findings、artifact、实际修复次数、最后诊断和停止原因。
 
 `manual-validation` 是 `ai task log` 中 review 行「人工校验点」（EN `Manual-validation`）计数的数据源；不要新增并行人工验证字段。
 

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

@@ -135,7 +135,7 @@ After closure, re-run step 1 for the next canonical round; never start the new r
 
 ### 6. Write back the publication result and task state
 
-- **Task-anchored path**: write the actual publication status in the `pr-review-rN.md` "Publication Result" section. Record the Review ID/URL for `applied` / `no-op`; for a failed write with a durable journal entry, record `blocked` / `failed`, the error code, and recovery action. Then close the local Activity Log with the verdict/counts frozen in step 3:
+- **Task-anchored path**: write the actual publication status in the `pr-review-rN.md` "Publication Result" section. Record the Review ID/URL for `applied` / `no-op`; for a failed write with a durable journal entry, record `blocked` / `failed`, the error code, and recovery action. Then close the local review state with the verdict/counts frozen in step 3:
 
   ```bash
   agent-infra-internal task-activity {task-id} pr-review-complete --agent {agent} \
@@ -143,13 +143,13 @@ After closure, re-run step 1 for the next canonical round; never start the new r
     --blockers {blockers} --major {major} --minor {minor}
   ```
 
-  `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.
+  `task-activity` generates `Verdict: <result>, blockers: N, major: N, minor: N → {pr-review-artifact}` from the typed payload and atomically writes the structured review state, `## Review Feedback` link, and version stamp through `writeTask`. It appends the log when safe and otherwise returns a diagnostic. It never changes `current_step` or puts receipt/head/Review URL into the NOTE.
 
 - **One-shot path (no task)**: record the actual publication status in the `pr-review-rN.md` "Publication Result" section. Record the Review ID/URL on success, or the error and lack of automatic recovery on failure. Do not call `task-activity`.
 
 ### 7. Re-sync after write-back (task-anchored path)
 
-Step 6 rewrote the local `pr-review-rN.md` "Publication Result" section and task.md (Activity Log), while step 4 synced the older snapshot. Attempt the syncs again in order; record failures as warnings for `complete-task` to restore before archiving:
+Step 6 rewrote the local `pr-review-rN.md` "Publication Result" section and task.md (review state and available log), while step 4 synced the older snapshot. Attempt the syncs again in order; record failures as warnings for `complete-task` to restore before archiving:
 
 ```bash
 agent-infra-internal platform-comment sync {task-id} --kind task --agent {agent}
@@ -186,7 +186,7 @@ Pick the single exit branch per `reference/output-guidance.md` (local review com
 - [ ] Published the formal Review, durably recorded its pending publication, or accurately recorded a one-shot publication failure
 - [ ] Synced the Issue artifact/task comments or recorded their pending recovery on the task-anchored path
 - [ ] Ran the completion verification (`task-verify` or `verify-artifact`)
-- [ ] Updated task.md and appended the Activity Log entry (task-anchored path)
+- [ ] Updated task.md review state and recorded log diagnostics when applicable
 
 ## Stop
 

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

@@ -135,7 +135,7 @@ agent-infra-internal task-activity {task-id} pr-review-terminate --agent {agent}
 
 ### 6. 回写发布结果与任务状态
 
-- **任务锚定路径**：把 publish 的实际状态写入 `pr-review-rN.md`「发布结果」段。`applied` / `no-op` 时记录 Review ID/URL；写入失败且已有任务账本记录时写 `blocked` / `failed`、错误码和恢复动作。随后以步骤 3 冻结的同一组 verdict/counts 闭合本地活动日志：
+- **任务锚定路径**：把 publish 的实际状态写入 `pr-review-rN.md`「发布结果」段。`applied` / `no-op` 时记录 Review ID/URL；写入失败且已有任务账本记录时写 `blocked` / `failed`、错误码和恢复动作。随后以步骤 3 冻结的同一组 verdict/counts 闭合本地审查状态：
 
   ```bash
   agent-infra-internal task-activity {task-id} pr-review-complete --agent {agent} \
@@ -143,13 +143,13 @@ agent-infra-internal task-activity {task-id} pr-review-terminate --agent {agent}
     --blockers {blockers} --major {major} --minor {minor}
   ```
 
-  `task-activity` 由 typed payload 生成 `Verdict: <结论>, blockers: N, major: N, minor: N → {pr-review-artifact}`，并经 `writeTask` 原子完成 Activity Log、`## 审查反馈` 链接与版本戳刷新；不改 `current_step`，也不把 receipt/head/Review URL 写入 NOTE。
+  `task-activity` 由 typed payload 生成 `Verdict: <结论>, blockers: N, major: N, minor: N → {pr-review-artifact}`，并经 `writeTask` 原子完成结构化审查状态、`## 审查反馈` 链接与版本戳刷新；日志可安全追加时一并写入，否则返回诊断；不改 `current_step`，也不把 receipt/head/Review URL 写入 NOTE。
 
 - **一次性路径（无任务）**：把实际发布状态写入 `pr-review-rN.md`「发布结果」段；成功时记录 Review ID/URL，失败时记录错误与不可自动恢复的限制。不调用 `task-activity`。
 
 ### 7. 发布后回写再同步（任务锚定路径）
 
-步骤 6 已改写本地 `pr-review-rN.md`「发布结果」段与 task.md（活动日志），而步骤 4 同步的是旧快照。依次尝试再同步；失败记录 warning，由 `complete-task` 在归档前补齐：
+步骤 6 已改写本地 `pr-review-rN.md`「发布结果」段与 task.md（审查状态及可用日志），而步骤 4 同步的是旧快照。依次尝试再同步；失败记录 warning，由 `complete-task` 在归档前补齐：
 
 ```bash
 agent-infra-internal platform-comment sync {task-id} --kind task --agent {agent}
@@ -186,7 +186,7 @@ agent-infra-internal platform-comment sync {task-id} --kind artifact --artifact
 - [ ] 正式 Review 已发布、任务账本已记录待恢复操作，或一次性路径已如实记录发布失败
 - [ ] 任务锚定路径的 Issue artifact/task 评论已同步，或失败已记录待恢复
 - [ ] 已完成校验（`task-verify` 或 `verify-artifact`）
-- [ ] 已更新 task.md 并追加 Activity Log（任务锚定路径）
+- [ ] 已更新 task.md 中的审查状态并记录日志诊断（如适用）
 
 ## 停止
 

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

@@ -8,7 +8,7 @@ description: >
 
 # Run Manual Validation
 
-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.
+Lifecycle events require explicit trigger data: ordinary skill invocation uses `model`; use `human` only when the user explicitly requests it. `{request-id}` is a stable single-line identifier for this task and artifact round, and `{reason-code}` use `user-request` or `validation-rerun`. Reuse the same values for started and completed.
 
 ## Task Context Resolution
 

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

@@ -8,7 +8,7 @@ description: >
 
 # 运行人工校验
 
-生命周期事件必须携带显式触发信息：编排调用使用 `{trigger-initiator}=orchestrator`，否则使用 `model`；`{request-id}` 是本任务与本轮产物的稳定单行标识，`{reason-code}` 使用 `user-request` 或 `validation-rerun`；started 与 completed 使用同一组值。
+生命周期事件必须携带显式触发信息：普通技能调用使用 `model`；仅用户明确要求时使用 `human`。`{request-id}` 是本任务与本轮产物的稳定单行标识，`{reason-code}` 使用 `user-request` 或 `validation-rerun`；started 与 completed 使用同一组值。
 
 ## 任务上下文解析
 

package/templates/.agents/skills/update-agent-infra/scripts/sync-templates.js

@@ -251,11 +251,10 @@ function normalizeAgentClientConfig(cfg) {
     }
     const keys = Object.keys(candidate);
     if (
-      (keys.length !== 3 && keys.length !== 4)
+      keys.length !== 3
       || !own(candidate, 'id')
       || !own(candidate, 'enabled')
       || !own(candidate, 'installInSandbox')
-      || (keys.length === 4 && !own(candidate, 'orchestration'))
     ) {
       return failure('INVALID_AGENT_CLIENTS', entryPath);
     }
@@ -266,52 +265,9 @@ function normalizeAgentClientConfig(cfg) {
     if (typeof candidate.enabled !== 'boolean' || typeof candidate.installInSandbox !== 'boolean') {
       return failure('INVALID_AGENT_CLIENTS', entryPath);
     }
-    let orchestration;
-    if (own(candidate, 'orchestration')) {
-      const policy = candidate.orchestration;
-      if (
-        !policy
-        || typeof policy !== 'object'
-        || Array.isArray(policy)
-        || Object.keys(policy).length !== 2
-        || !own(policy, 'executor')
-        || !own(policy, 'reviewer')
-      ) {
-        return failure('INVALID_AGENT_CLIENTS', `${entryPath}.orchestration`);
-      }
-      const parseExact = (value, path) => {
-        if (typeof value !== 'string' || value.length === 0 || value.trim() !== value) {
-          return failure('INVALID_AGENT_CLIENTS', path);
-        }
-        return value;
-      };
-      const parseRole = (role, rolePath) => {
-        if (
-          !role
-          || typeof role !== 'object'
-          || Array.isArray(role)
-          || Object.keys(role).length !== 2
-          || !own(role, 'model')
-          || !own(role, 'reasoningEffort')
-        ) {
-          return failure('INVALID_AGENT_CLIENTS', rolePath);
-        }
-        const model = parseExact(role.model, `${rolePath}.model`);
-        if (typeof model !== 'string') return model;
-        const reasoningEffort = parseExact(role.reasoningEffort, `${rolePath}.reasoningEffort`);
-        if (typeof reasoningEffort !== 'string') return reasoningEffort;
-        return { model, reasoningEffort };
-      };
-      const executor = parseRole(policy.executor, `${entryPath}.orchestration.executor`);
-      if (executor.errorCode) return executor;
-      const reviewer = parseRole(policy.reviewer, `${entryPath}.orchestration.reviewer`);
-      if (reviewer.errorCode) return reviewer;
-      orchestration = { executor, reviewer };
-    }
     entries.set(candidate.id, {
       enabled: candidate.enabled,
-      installInSandbox: candidate.installInSandbox,
-      ...(orchestration ? { orchestration } : {})
+      installInSandbox: candidate.installInSandbox
     });
   }
   if (AGENT_CLIENT_IDS.some((id) => !entries.has(id))) {
@@ -676,22 +632,6 @@ function mergeTemplateSources(baseRoot, sources, report) {
   };
 }
 
-function writeIfChanged(projectRoot, targetPath, content, reportBucket) {
-  const fullPath = path.join(projectRoot, targetPath);
-  const exists = fs.existsSync(fullPath);
-
-  if (exists && fs.readFileSync(fullPath, 'utf8') === content) {
-    reportBucket.unchanged.push(targetPath);
-    return;
-  }
-
-  const dir = path.dirname(fullPath);
-  if (!fs.existsSync(dir)) fs.mkdirSync(dir, { recursive: true });
-  fs.writeFileSync(fullPath, content, 'utf8');
-
-  (exists ? reportBucket.updated : reportBucket.generated).push(targetPath);
-}
-
 function syncCustomSkillSources(projectRoot, sources, report, templateSkillNames) {
   const skillsDir = path.join(projectRoot, '.agents/skills');
   const syncedSkills = new Map();
@@ -1102,7 +1042,7 @@ function syncTemplates(projectRoot, templateRootOverride) {
     && !Array.isArray(cfg.files.managedBaselines)
     ? { ...cfg.files.managedBaselines }
     : {};
-  let baselinesChanged = false;
+
 
   for (const target of Object.keys(managedBaselines)) {
     if (
@@ -1111,7 +1051,6 @@ function syncTemplates(projectRoot, templateRootOverride) {
       && !allClientManaged.some((entry) => assetMatches(entry, target))
     ) {
       delete managedBaselines[target];
-      baselinesChanged = true;
     }
   }
 
@@ -1206,7 +1145,6 @@ function syncTemplates(projectRoot, templateRootOverride) {
         if (!fs.existsSync(candidatePath)) {
           if (Object.prototype.hasOwnProperty.call(managedBaselines, candidate)) {
             delete managedBaselines[candidate];
-            baselinesChanged = true;
           }
           continue;
         }
@@ -1232,7 +1170,6 @@ function syncTemplates(projectRoot, templateRootOverride) {
         }
         if (Object.prototype.hasOwnProperty.call(managedBaselines, candidate)) {
           delete managedBaselines[candidate];
-          baselinesChanged = true;
         }
       }
       removeEmptyDirs(target);
@@ -1252,7 +1189,6 @@ function syncTemplates(projectRoot, templateRootOverride) {
       report.managed.removed.push(entry);
       if (Object.prototype.hasOwnProperty.call(managedBaselines, entry)) {
         delete managedBaselines[entry];
-        baselinesChanged = true;
       }
     } else {
       report.managed.protected.push({
@@ -1321,7 +1257,6 @@ function syncTemplates(projectRoot, templateRootOverride) {
 
     if (rawBaseline !== undefined && baseline === null) {
       delete managedBaselines[target];
-      baselinesChanged = true;
     }
     if (baseline === null && localHash !== null && localHash !== templateHash) {
       report.managed.conflicts.push({
@@ -1362,7 +1297,6 @@ function syncTemplates(projectRoot, templateRootOverride) {
       bucket.unchanged.push(target);
       if (managedBaselines[target] !== templateHash) {
         managedBaselines[target] = templateHash;
-        baselinesChanged = true;
       }
       return false;
     }
@@ -1371,7 +1305,6 @@ function syncTemplates(projectRoot, templateRootOverride) {
     if (!fs.existsSync(dir)) fs.mkdirSync(dir, { recursive: true });
     fs.writeFileSync(dstFull, content);
     managedBaselines[target] = templateHash;
-    baselinesChanged = true;
     if (Object.prototype.hasOwnProperty.call(bucket, 'written')) {
       (exists ? bucket.written : bucket.created).push(target);
     } else {
@@ -1417,7 +1350,6 @@ function syncTemplates(projectRoot, templateRootOverride) {
       report.managed.removed.push(renderedTarget);
       if (Object.prototype.hasOwnProperty.call(managedBaselines, renderedTarget)) {
         delete managedBaselines[renderedTarget];
-        baselinesChanged = true;
       }
       continue;
     }
@@ -1479,7 +1411,6 @@ function syncTemplates(projectRoot, templateRootOverride) {
       if (localHash === null) {
         if (Object.prototype.hasOwnProperty.call(managedBaselines, target)) {
           delete managedBaselines[target];
-          baselinesChanged = true;
         }
         continue;
       }
@@ -1492,7 +1423,6 @@ function syncTemplates(projectRoot, templateRootOverride) {
         report.managed.removed.push(target);
         if (Object.prototype.hasOwnProperty.call(managedBaselines, target)) {
           delete managedBaselines[target];
-          baselinesChanged = true;
         }
         removeEmptyDirs(path.dirname(dstFull));
         continue;
@@ -1608,7 +1538,6 @@ function syncTemplates(projectRoot, templateRootOverride) {
             if (baseline !== null && localHash === baseline) {
               fs.unlinkSync(path.join(projectRoot, projFile));
               delete managedBaselines[projFile];
-              baselinesChanged = true;
               report.managed.removed.push(projFile);
             } else {
               report.managed.protected.push({
@@ -1715,7 +1644,6 @@ function syncTemplates(projectRoot, templateRootOverride) {
   if (Object.keys(managedBaselines).length > 0) {
     cfg.files.managedBaselines = managedBaselines;
   } else {
-    if (Object.prototype.hasOwnProperty.call(cfg.files, 'managedBaselines')) baselinesChanged = true;
     delete cfg.files.managedBaselines;
   }
   cfg.templateVersion = version;

package/templates/.agents/templates/task.en.md

@@ -13,6 +13,7 @@ start_date:                     # Optional Issue field for Feature: YYYY-MM-DD
 target_date:                    # Optional Issue field for Feature: YYYY-MM-DD
 current_step: requirement-analysis # requirement-analysis | requirement-analysis-review | technical-design | technical-design-review | code | code-review | completed
 assigned_to:                   # claude | codex | antigravity | opencode | human
+lifecycle_execution: '{"version":1,"open":[],"prReview":{"open":null,"terminals":[]}}'
 pr_delivery_fact: '{"version":2,"state":"unbound","reason":"initial"}'
 delivery_remote: origin        # Git remote used to deliver the task branch
 delivery_base_ref: main        # Target branch for the task PR

package/templates/.agents/templates/task.zh-CN.md

@@ -13,6 +13,7 @@ start_date:                     # Feature 可选 Issue 字段：YYYY-MM-DD
 target_date:                    # Feature 可选 Issue 字段：YYYY-MM-DD
 current_step: requirement-analysis # requirement-analysis | requirement-analysis-review | technical-design | technical-design-review | code | code-review | completed
 assigned_to:                   # claude | codex | antigravity | opencode | human
+lifecycle_execution: '{"version":1,"open":[],"prReview":{"open":null,"terminals":[]}}'
 pr_delivery_fact: '{"version":2,"state":"unbound","reason":"initial"}'
 delivery_remote: origin        # 任务分支交付使用的 Git remote
 delivery_base_ref: main        # 任务 PR 的目标分支

package/templates/.claude/settings.json

@@ -30,30 +30,6 @@
         ]
       }
     ],
-    "SubagentStart": [
-      {
-        "matcher": "agent-infra-lifecycle-(executor|reviewer)",
-        "hooks": [
-          {
-            "type": "command",
-            "command": "node \"$(git rev-parse --show-toplevel)/.agents/hooks/lifecycle-delegation.js\" --client claude-code",
-            "timeout": 10
-          }
-        ]
-      }
-    ],
-    "SubagentStop": [
-      {
-        "matcher": "agent-infra-lifecycle-(executor|reviewer)",
-        "hooks": [
-          {
-            "type": "command",
-            "command": "node \"$(git rev-parse --show-toplevel)/.agents/hooks/lifecycle-delegation.js\" --client claude-code",
-            "timeout": 10
-          }
-        ]
-      }
-    ],
     "StopFailure": [
       {
         "matcher": "",

package/templates/.codex/hooks.json

@@ -11,56 +11,6 @@
             "statusMessage": "Checking template version before git commit"
           }
         ]
-      },
-      {
-      "matcher": "^collaborationspawn_agent$",
-        "hooks": [
-          {
-            "type": "command",
-            "command": "node \"$(git rev-parse --show-toplevel)/.agents/hooks/lifecycle-delegation.js\" --client codex --event pre-tool",
-            "timeout": 30,
-            "statusMessage": "Recording Codex lifecycle spawn evidence"
-          }
-        ]
-      }
-    ],
-    "PostToolUse": [
-      {
-      "matcher": "",
-        "hooks": [
-          {
-            "type": "command",
-            "command": "node \"$(git rev-parse --show-toplevel)/.agents/hooks/lifecycle-delegation.js\" --client codex --event post-tool",
-            "timeout": 30,
-            "statusMessage": "Recording Codex lifecycle tool completion"
-          }
-        ]
-      }
-    ],
-    "SubagentStart": [
-      {
-        "matcher": "",
-        "hooks": [
-          {
-            "type": "command",
-            "command": "node \"$(git rev-parse --show-toplevel)/.agents/hooks/lifecycle-delegation.js\" --client codex --event subagent-start",
-            "timeout": 30,
-            "statusMessage": "Recording Codex child identity"
-          }
-        ]
-      }
-    ],
-    "SubagentStop": [
-      {
-        "matcher": "",
-        "hooks": [
-          {
-            "type": "command",
-            "command": "node \"$(git rev-parse --show-toplevel)/.agents/hooks/lifecycle-delegation.js\" --client codex --event subagent-stop",
-            "timeout": 30,
-            "statusMessage": "Recording Codex child stop evidence"
-          }
-        ]
       }
     ]
   }