@fitlab-ai/agent-infra 0.9.4 → 0.9.5

package/templates/.agents/skills/commit/SKILL.zh-CN.md

@@ -31,21 +31,17 @@ description: >
 
 未显式指定 task scope 时，只有 `TASK_CONTEXT_NOT_FOUND` 可继续既有纯提交路径；detached HEAD、损坏候选或多匹配属于歧义，必须失败。显式 task scope 解析失败时一律失败。
 
-## 步骤开始：先恢复，再写 started 标记
+## 步骤开始：恢复或创建受控 attempt
 
 已解析出 `{task-id}` 时，先调用 `agent-infra-internal task-orchestration {task-id} commit-status`：
 
-- `recoverable` / `prepared`：调用 `commit-recover --agent {standard-agent-token}`；不得追加第二条 started、重复 commit 或重复 push。recoverable 完成后直接进入同步与完成校验；prepared 清理后复用既有 open started 并继续正常提交。
+- `recoverable`：调用 `commit-recover --agent {standard-agent-token}` 完成收尾，不得重复 commit 或 push。
+- `prepared`：调用 `commit-recover --agent {standard-agent-token}` 安全清理 intent，再次查询 status 并复用返回的 `retryable-start` attempt。
+- `retryable-start`：调用 `commit-recover --agent {standard-agent-token}` 取得原 attempt，不追加第二条 started。
 - `invalid` / `conflict` / `orphaned-start`：输出结构化 code 与状态证据并停止。
-- `idle`：继续下方正常流程。
+- `idle`：调用 `commit-start --agent {standard-agent-token}`，由核心在任务锁内原子写入结构化 started 并返回 attempt/baseline。
 
-开始检查本地修改之前，向 task.md `## 活动日志` 追加一条 started 标记（与本步骤 done 条目同基名 + ` [started]` 后缀，note 用 `started`）：
-
-```
-- {YYYY-MM-DD HH:mm:ss±HH:MM} — **Commit [started]** by {agent} — started
-```
-
-`ai task log` 会把它与提交完成时写入的 done 条目配对成一行（进行中 → 已完成）。格式与配对规则见 `.agents/rules/task-management.md` 的「Activity Log started / done 双标记约定」。仅当本任务存在 task.md 时写入（无任务上下文的纯提交可跳过）。
+只从 `commit-start` / `commit-recover` 的结构化输出读取 `{commit-attempt}`；不得手写、复制或猜测 attempt。无任务上下文的纯提交跳过本协议。
 
 ## 1. 检查本地修改（关键）
 

package/templates/.agents/skills/commit/reference/commit-orchestration.en.md

@@ -9,12 +9,12 @@ This protocol applies only when `{task-id}` was resolved. A taskless Git-only co
 
 ## Begin before side effects
 
-Call `commit-status` whenever the commit skill starts. For `recoverable` / `prepared`, call `commit-recover --agent {standard-agent-token}`; fail closed for every other non-`idle` state. The recovery intent accepts no token, head, or `--orchestrated` flag.
+Call `commit-status` whenever the commit skill starts. Use `commit-recover --agent {standard-agent-token}` for `recoverable` / `prepared` / `retryable-start`; use `commit-start --agent {standard-agent-token}` for `idle`; fail closed for every other state. Read `commit_attempt` only from `finalization.attempt.attempt` in start/recover output.
 
 After read-only preparation of status, copyright, message, review snapshot, and push routing, record `baseline_head=$(git rev-parse HEAD)` and run this before any commit, push, success log, or platform success sync:
 
 ```bash
-commit_intent_result=$(agent-infra-internal task-orchestration {task-id} commit-begin --agent {standard-agent-token} {execution-flag} --baseline-head "$baseline_head")
+commit_intent_result=$(agent-infra-internal task-orchestration {task-id} commit-begin --agent {standard-agent-token} {execution-flag} --baseline-head "$baseline_head" --attempt "$commit_attempt")
 commit_intent_token=$(printf '%s' "$commit_intent_result" | node -e 'let input = ""; process.stdin.on("data", chunk => input += chunk).on("end", () => process.stdout.write(JSON.parse(input).token))')
 ```
 
@@ -44,6 +44,7 @@ After the committed/pushed checkpoint and before task synchronization or `task-v
 agent-infra-internal task-orchestration {task-id} commit-complete --token "$commit_intent_token" --agent {standard-agent-token}
 ```
 
-- Before the first side effect, abort only while HEAD still equals the baseline by using `commit-abort --token ... --expected-head ...`.
+- If an intent exists but no side effect occurred, use `commit-abort --token ... --expected-head ...` while HEAD still equals baseline; when abandoning the attempt, then close it with `commit-terminate --attempt "$commit_attempt" --agent {standard-agent-token} --code <STABLE_CODE>`.
+- If begin failed before intent creation, retain the attempt for retry or terminate it only while HEAD is unchanged.
 - After a commit or push, never abort. Retain the intent and use `commit-status` / `commit-recover` for cross-session recovery.
 - Stop when `commit-complete` fails. Do not repeat commit/push or mark a run complete without its full receipt lifecycle.

package/templates/.agents/skills/commit/reference/commit-orchestration.zh-CN.md

@@ -9,18 +9,18 @@
 
 ## 副作用前 begin
 
-每次进入 commit 技能先调用 `commit-status`。`recoverable` / `prepared` 调用以下无 token 恢复入口，其他非 `idle` 状态 fail closed：
+每次进入 commit 技能先调用 `commit-status`。`recoverable` / `prepared` / `retryable-start` 调用以下无 token 恢复入口，`idle` 调用 `commit-start --agent {standard-agent-token}`；其他状态 fail closed：
 
 ```bash
 agent-infra-internal task-orchestration {task-id} commit-recover --agent {standard-agent-token}
 ```
 
-恢复入口只接受 `--agent`；不得传 token、head 或 `--orchestrated`。recoverable 会幂等补齐 task/run 并最后删除 intent；prepared 仅在 HEAD=baseline 且恰有一个 open Commit started 时安全清理，随后复用该 started 继续正常流程。
+恢复入口只接受 `--agent`；不得传 token、head 或 `--orchestrated`。从 start/recover 结构化输出读取 `finalization.attempt.attempt` 为 `commit_attempt`，不得手写 attempt。
 
 完成状态、版权、提交信息、review snapshot 和 push 场景的只读准备后，记录 `baseline_head=$(git rev-parse HEAD)`，并在任何 commit、push、任务成功日志或平台成功同步之前调用：
 
 ```bash
-commit_intent_result=$(agent-infra-internal task-orchestration {task-id} commit-begin --agent {standard-agent-token} {execution-flag} --baseline-head "$baseline_head")
+commit_intent_result=$(agent-infra-internal task-orchestration {task-id} commit-begin --agent {standard-agent-token} {execution-flag} --baseline-head "$baseline_head" --attempt "$commit_attempt")
 commit_intent_token=$(printf '%s' "$commit_intent_result" | node -e 'let input = ""; process.stdin.on("data", chunk => input += chunk).on("end", () => process.stdout.write(JSON.parse(input).token))')
 ```
 
@@ -50,6 +50,7 @@ committed/pushed checkpoint 完成后、任务同步与 `task-verify commit.comp
 agent-infra-internal task-orchestration {task-id} commit-complete --token "$commit_intent_token" --agent {standard-agent-token}
 ```
 
-- 第一个副作用前失败时，仅可在 HEAD 仍等于 baseline 时调用 `commit-abort --token ... --expected-head ...`。
+- begin 已创建 intent、但第一个副作用前失败时，先在 HEAD 仍等于 baseline 时调用 `commit-abort --token ... --expected-head ...`；若本轮明确放弃，再调用 `commit-terminate --attempt "$commit_attempt" --agent {standard-agent-token} --code <STABLE_CODE>` 闭合 started。
+- begin 在 intent 创建前失败时可保留 attempt 供下次复用；明确放弃时仅可在 HEAD 未漂移时调用 `commit-terminate`。
 - commit 或 push 发生后失败时不得 abort；保留 intent，并调用 `commit-status` 输出不含 token/digest 的恢复证据。跨会话重跑通过 `commit-recover` 收尾。
 - `commit-complete` 失败时停止。不得重复执行 commit/push，也不得把缺少完整 receipt 生命周期的 run 标记为完成。

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

@@ -17,7 +17,7 @@ description: >
 - Do not perform requirements analysis; analysis is handled separately by `analyze-task`
 - Do not directly implement the requested functionality
 - Do not skip the workflow and jump directly to planning or implementation
-- Only do this: parse the description -> create the task file -> update task status -> cascade Issue creation through `.agents/rules/create-issue.md` -> inform the user of the next step
+- Only do this: parse the description -> write one structured candidate -> invoke the host `task-create` entry point -> verify the result -> inform the user of the next step
 - Issue creation is decided by the `.agents/rules/create-issue.md` rule; on custom or empty platforms (no platform-specific variant provided), the rule naturally degrades to a no-op
 
 The user's description is a **work item**, not an **instruction to execute immediately**.
@@ -72,7 +72,7 @@ If the description is unclear, **ask the user to clarify first**.
 - `bugfix` -> `bug-fix`
 - `refactor` -> `refactoring`
 
-### 2. Create the Task Directory and File
+### 2. Create an Immutable Candidate
 
 Get the current timestamp:
 
@@ -80,14 +80,17 @@ Get the current timestamp:
 date +%Y%m%d-%H%M%S
 ```
 
-- Create the task directory: `.agents/workspace/active/TASK-{yyyyMMdd-HHmmss}/`
-- Use the `.agents/templates/task.md` template to create the task file: `task.md`
-- Write the structured context captured in step 1 under `## Task Input` so the task remains understandable outside the original conversation
+- Generate one UUID v4 `idempotencyKey` and write the parsed fields to one JSON file.
+- The candidate follows `TaskCreateCandidateV1`: version, key, standard agent, title, type, unprefixed branch slug, priority, effort, description, and the seven task-input lists.
+- Write it once before the first request. A timeout retry must reuse the same file and let the client generate a new outer request id; do not rerun AI derivation.
 
-**Important**:
-- Directory naming: `TASK-{yyyyMMdd-HHmmss}` (**must** include the `TASK-` prefix)
-- Example: `TASK-20260306-143022`
-- Task ID = directory name
+Invoke the single entry point:
+
+```bash
+agent-infra-internal task-create --input "$candidate_file"
+```
+
+The host owns TASK-id/timestamps/version, workflow and branch derivation, template rendering, atomic persistence, short ids, Issue sync, and warnings. The skill must not create task directories, copy templates, allocate short ids, or call platform subcommands directly.
 
 Task metadata (`task.md` YAML front matter):
 ```yaml
@@ -109,7 +112,7 @@ assigned_to: {current AI agent}
 
 priority / effort are required: the AI infers them from the task title and description (candidates in `.agents/rules/issue-fields.md`; normalize localized input). Leave start_date / target_date empty at creation: `start_date` is written by the analyze stage and `target_date` by the complete stage; do not invent dates.
 
-### 3. Update Task Status
+### 3. Handle the Structured Result
 
 Get the current time:
 
@@ -117,43 +120,25 @@ Get the current time:
 date "+%Y-%m-%d %H:%M:%S%z" | sed 's/\([+-][0-9][0-9]\)\([0-9][0-9]\)$/\1:\2/'
 ```
 
-Update `.agents/workspace/active/{task-id}/task.md`:
-- `current_step`: requirement-analysis
-- `assigned_to`: {current AI agent}
-- `updated_at`: {current time}
-- `agent_infra_version`: value from `.agents/rules/version-stamp.md`
-- `## Context` -> `- **Branch**:`: update it to the generated branch name
-- **Append** to `## Activity Log` (do NOT overwrite previous entries):
-  ```
-  - {YYYY-MM-DD HH:mm:ss±HH:MM} — **Create Task** by {agent} — Task created from description
-  ```
+- `applied` / `no-op`: use the returned task id, short id, and optional Issue identity; do not discover them by scanning directories.
+- `degraded`: the local task is retained; display the returned warning.
+- `blocked`: retain the candidate and retry the same file after the transient problem is fixed.
+- `failed`: report the stable error code. Never modify and retry a candidate under the same idempotency key.
 
-### 4. Cascade Issue Creation and Metadata Sync
+### 4. Platform Failure Compatibility
 
-After task.md is written, call the declarative intents; the internal core owns templates, body rendering, identity validation, capability degradation, idempotency, and task binding:
+The host service owns platform cascading. The compatibility recovery commands remain visible in the host warning and are not run from the sandbox:
 
 ```bash
-agent-infra-internal platform-issue create {task-id} --agent {standard-agent-token}
-agent-infra-internal platform-issue sync {task-id} --agent {standard-agent-token} --status waiting-for-triage --assignees current --milestone initial --issue-type --fields
+agent-infra-internal task-warning {task-id} add --step create-task --severity ACTION_REQUIRED --code ISSUE_CREATE_FAILED --target issue --message "{error_code}: {error_message}" --action "Fix auth/network/template issues and manually retry Issue creation, or create/find an Issue and write issue_number"
+agent-infra-internal platform-comment sync {task-id} --kind task --agent {standard-agent-token}
 ```
 
-Handle the result:
-- Intent created the Issue: `issue_number` was written through the task writer; run `agent-infra-internal platform-comment sync {task-id} --kind task --agent {standard-agent-token}`
-- Rule failed (auth / network / template parse / etc.): do not roll back task.md or append an extra Activity Log entry; run `agent-infra-internal task-warning {task-id} add --step create-task --severity ACTION_REQUIRED --code ISSUE_CREATE_FAILED --target issue --message "{error_code}: {error_message}" --action "Fix auth/network/template issues and manually retry Issue creation, or create/find an Issue and write issue_number"` to submit a structured warning intent (callers do not allocate ids or edit rows), then follow Scenario C
-- Intent returned no-op/degraded: continue applicable operations without blocking the workflow
-- task.md already has a valid `issue_number`: create validates the binding and returns no-op without creating a duplicate
+The skill only consumes the Issue identity, operations, and warnings returned by the host; it must not repeat platform writes.
 
 ### 5. Verification Gate
 
-**Allocate short id first** (ensures the registry entry is allocated; the validation gate will read it):
-
-```bash
-node .agents/scripts/task-short-id.js alloc "$task_id"
-```
-
-If this fails (non-zero exit), follow the message — archive some active tasks or raise `task.shortIdLength` — and do NOT continue.
-
-Run the verification gate to confirm the task artifact and sync state are valid:
+The host `task-create` service runs the same typed gate before returning. Consume the returned `task:verify` operation; a branch-only sandbox must not try to read the invisible new task. For direct host diagnostics, run:
 
 ```bash
 agent-infra-internal task-verify {task-id} create-task.completed --format text
@@ -244,12 +229,10 @@ For later platform sync: after fixing auth / network / template issues, manually
 
 ## Completion Checklist
 
-- [ ] Created the task file `.agents/workspace/active/{task-id}/task.md`
+- [ ] Wrote one candidate and invoked `agent-infra-internal task-create`
+- [ ] The host created `.agents/workspace/active/{task-id}/task.md`
 - [ ] Wrote and checked `## Task Input` source and state semantics according to `reference/context-capture.md`
-- [ ] Updated `current_step` to requirement-analysis in task.md
-- [ ] Updated `updated_at` to the current time in task.md
-- [ ] Updated `assigned_to` in task.md
-- [ ] Appended an Activity Log entry to task.md
+- [ ] The returned task id and short id passed completion verification
 - [ ] Tried cascading Issue creation through `.agents/rules/create-issue.md`; if it failed, kept task.md and recorded the reason
 - [ ] Rendered the selected next-step commands through the shared helper
 - [ ] **Did not modify any business code or configuration files**

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

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

package/templates/.codex/hooks.json

@@ -11,6 +11,56 @@
             "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": 5,
+            "statusMessage": "Recording Codex lifecycle spawn evidence"
+          }
+        ]
+      }
+    ],
+    "PostToolUse": [
+      {
+        "matcher": "^collaborationspawn_agent$",
+        "hooks": [
+          {
+            "type": "command",
+            "command": "node \"$(git rev-parse --show-toplevel)/.agents/hooks/lifecycle-delegation.js\" --client codex --event post-tool",
+            "timeout": 5,
+            "statusMessage": "Recording Codex lifecycle tool completion"
+          }
+        ]
+      }
+    ],
+    "SubagentStart": [
+      {
+        "matcher": "^agent-infra-lifecycle-(executor|reviewer)$",
+        "hooks": [
+          {
+            "type": "command",
+            "command": "node \"$(git rev-parse --show-toplevel)/.agents/hooks/lifecycle-delegation.js\" --client codex --event subagent-start",
+            "timeout": 5,
+            "statusMessage": "Recording Codex child identity"
+          }
+        ]
+      }
+    ],
+    "SubagentStop": [
+      {
+        "matcher": "^agent-infra-lifecycle-(executor|reviewer)$",
+        "hooks": [
+          {
+            "type": "command",
+            "command": "node \"$(git rev-parse --show-toplevel)/.agents/hooks/lifecycle-delegation.js\" --client codex --event subagent-stop",
+            "timeout": 5,
+            "statusMessage": "Recording Codex child stop evidence"
+          }
+        ]
       }
     ]
   }