oh-my-customcodex 0.4.15 → 0.4.17

package/templates/.claude/skills/omcodex-release-notes/SKILL.md

@@ -46,8 +46,9 @@ Before creating a release, keep `CHANGELOG.md` as the durable source of release
 1. Confirm `CHANGELOG.md` has a `## [Unreleased]` section.
 2. Move non-empty `Unreleased` entries into `## [VERSION] - YYYY-MM-DD`.
 3. Insert a fresh empty `## [Unreleased]` section above the promoted version.
-4. Verify `.github/workflows/release.yml` can extract the promoted section with its existing `awk "/^## \\[${VERSION}\\]/{flag=1; next} /^## \\[/{flag=0} flag"` logic.
-5. If `Unreleased` is empty, add the release summary there first rather than relying only on GitHub auto-generated notes.
+4. Keep Keep a Changelog categories (`Added`, `Changed`, `Fixed`, `Removed`, `Deprecated`, `Security`) intact.
+5. Verify `.github/workflows/release.yml` can extract the promoted section with its existing `awk "/^## \\[${VERSION}\\]/{flag=1; next} /^## \\[/{flag=0} flag"` logic.
+6. If `Unreleased` is empty, add the release summary there first rather than relying only on GitHub auto-generated notes.
 
 ### Phase 2: Classify Changes
 
@@ -63,7 +64,7 @@ Categorize commits using Conventional Commits:
 | chore: | Chores | :wrench: |
 | security | Security | :lock: |
 
-### Phase 3: Generate Notes
+### Phase 4: Generate Notes
 
 Output format:
 
@@ -102,7 +103,7 @@ Output format:
 _Release notes generated with oh-my-customcodex_
 ```
 
-### Phase 4: Apply
+### Phase 5: Apply
 
 The generated notes can be:
 1. **Direct**: Passed to `gh release create --notes "{notes}"`

package/templates/.claude/skills/post-release-followup/SKILL.md

@@ -96,7 +96,7 @@ Use AskUserQuestion (or equivalent user prompt) to get the choice.
 
 **Option C (모두 이슈 등록)**:
 - All Immediate + Trackable items → `gh issue create` with appropriate labels
-- Label: `professor` for auto-triage in next workflow run
+- Label: `triage-needed` for the next workflow run; reserve `professor` for manual analysis requests
 
 **Option D (개별 선택)**:
 - For each item, ask: `[{n}] {description} — 실행(E) / 이슈(I) / 건너뛰기(S)?`

package/templates/.claude/skills/status/SKILL.md

@@ -122,7 +122,7 @@ Guides:
   ✓ docker, aws
 
 Commands:
-  system:    lists, status, help, goal
+  system:    lists, status, help, omcustomcodex:goal
   manager:   create-agent, update-docs, update-external, audit-agents, fix-refs
   dev:       dev-review, dev-refactor
 

package/templates/.claude/statusline.sh

@@ -246,7 +246,7 @@ if [[ -n "$git_branch" ]] && command -v gh >/dev/null 2>&1; then
         pr_number="$cached_pr"
     else
         # Cache miss — query gh and update cache
-        pr_number="$(gh pr view --json number -q .number 2>/dev/null || echo "")"
+        pr_number="$(timeout 2 gh pr view --json number -q .number 2>/dev/null || echo "")"
         printf '%s\t%s\n' "$git_branch" "$pr_number" > "$cache_file"
     fi
 
@@ -360,21 +360,42 @@ if [[ -n "$wl_display" ]]; then
     wl_segment=" | ${wl_color}${wl_display}${COLOR_RESET}"
 fi
 
+# Build the RTK segment from the session-env bridge if available.
+rtk_segment=""
+env_status_file="/tmp/.codex-env-status-${PPID}"
+if [[ -f "$env_status_file" ]]; then
+    rtk_status=""
+    while IFS='=' read -r key value; do
+        if [[ "$key" == "rtk" ]]; then
+            rtk_status="$value"
+            break
+        fi
+    done < "$env_status_file"
+
+    if [[ "$rtk_status" == "available" ]]; then
+        rtk_segment=" | ${COLOR_CTX_OK}RTK:on${COLOR_RESET}"
+    elif [[ "$rtk_status" == "unavailable" ]]; then
+        rtk_segment=" | ${COLOR_CTX_WARN}RTK:off${COLOR_RESET}"
+    fi
+fi
+
 if [[ -n "$git_branch" ]]; then
-    printf "${cost_color}%s${COLOR_RESET} | %s | %s%s%s%s | ${ctx_color}%s${COLOR_RESET}\n" \
+    printf "${cost_color}%s${COLOR_RESET} | %s | %s%s%s%s%s | ${ctx_color}%s${COLOR_RESET}\n" \
         "$cost_display" \
         "$project_name" \
         "$branch_display" \
         "$pr_segment" \
         "$rl_segment" \
         "$wl_segment" \
+        "$rtk_segment" \
         "$ctx_display"
 else
-    printf "${cost_color}%s${COLOR_RESET} | %s%s%s%s | ${ctx_color}%s${COLOR_RESET}\n" \
+    printf "${cost_color}%s${COLOR_RESET} | %s%s%s%s%s | ${ctx_color}%s${COLOR_RESET}\n" \
         "$cost_display" \
         "$project_name" \
         "$pr_segment" \
         "$rl_segment" \
         "$wl_segment" \
+        "$rtk_segment" \
         "$ctx_display"
 fi

package/templates/AGENTS.md.en

@@ -118,7 +118,7 @@ NO EXCEPTIONS. NO EXCUSES.
 | `/deep-plan` | Research-validated planning (research → plan → verify) |
 | `/omcustomcodex:sauron-watch` | Full R017 verification |
 | `/structured-dev-cycle` | 6-stage structured development cycle (Plan → Verify → Implement → Verify → Compound → Done) |
-| `/goal` | Keep a concrete objective through planning, execution, and verification |
+| `/omcustomcodex:goal` | Keep a concrete objective through planning, execution, and verification |
 | `/omcustomcodex:lists` | Show all available commands |
 | `/omcustomcodex:status` | Show system status |
 | `/omcustomcodex:help` | Show help information |
@@ -240,4 +240,6 @@ omx-memory setup
 
 Projects that run in the Claude Code plugin ecosystem may separately install plugins such as `superpowers`, `openai-docs`, `elements-of-style`, and `context7`. They are not required Codex init steps.
 
+On Claude Code v2.1.139+, use `claude agents` to inspect the unified agent list, `claude plugin details <name>` to inspect plugin components and projected token cost, and `/scroll-speed` for local scroll tuning. The native `/goal` command is reserved for Claude Code's completion tracker; use `/omcustomcodex:goal` for the oh-my-customcodex workflow.
+
 <!-- omcodex:git-workflow -->

package/templates/AGENTS.md.ko

@@ -118,7 +118,7 @@ oh-my-customcodex로 구동됩니다.
 | `/deep-plan` | 연구 검증 기반 계획 수립 (research → plan → verify) |
 | `/omcustomcodex:sauron-watch` | 전체 R017 검증 |
 | `/structured-dev-cycle` | 6단계 구조적 개발 사이클 (Plan → Verify → Implement → Verify → Compound → Done) |
-| `/goal` | 구체 목표를 계획, 실행, 검증까지 유지 |
+| `/omcustomcodex:goal` | 구체 목표를 계획, 실행, 검증까지 유지 |
 | `/omcustomcodex:lists` | 모든 사용 가능한 커맨드 표시 |
 | `/omcustomcodex:status` | 시스템 상태 표시 |
 | `/omcustomcodex:help` | 도움말 표시 |
@@ -240,4 +240,6 @@ omx-memory setup
 
 Claude Code 플러그인 생태계를 쓰는 프로젝트에서는 `superpowers`, `openai-docs`, `elements-of-style`, `context7` 같은 플러그인을 별도로 설치할 수 있습니다. Codex 초기화의 필수 단계는 아닙니다.
 
+Claude Code v2.1.139+에서는 `claude agents`로 통합 에이전트 목록을 확인하고, `claude plugin details <name>`으로 플러그인 구성 요소와 예상 토큰 비용을 점검하며, `/scroll-speed`로 로컬 스크롤 속도를 조정할 수 있습니다. 네이티브 `/goal`은 Claude Code 완료 추적기용으로 남기고, oh-my-customcodex 워크플로우는 `/omcustomcodex:goal`을 사용합니다.
+
 <!-- omcodex:git-workflow -->

package/templates/CLAUDE.md

@@ -99,7 +99,7 @@ oh-my-customcodex로 구동됩니다.
 |----------|------------|------|
 | 프로젝트 관리 | `/omcustomcodex:analysis`, `/omcustomcodex:create-agent`, `/omcustomcodex:audit-agents` | 분석, 에이전트/스킬 생성, 감사 |
 | 아이디어 | `/idea` | 자연어 아이디어를 구조화된 이슈 스펙으로 변환 |
-| 개발 | `/goal`, `/dev-review`, `/dev-refactor`, `/sdd-dev`, `/structured-dev-cycle` | 목표 실행, 코드 리뷰, 리팩토링, SDD |
+| 개발 | `/omcustomcodex:goal`, `/dev-review`, `/dev-refactor`, `/sdd-dev`, `/structured-dev-cycle` | 목표 실행, 코드 리뷰, 리팩토링, SDD |
 | 검증 | `/omcustomcodex:sauron-watch`, `/deep-verify`, `/adversarial-review` | R017 검증, 릴리즈 품질, 보안 리뷰 |
 | 릴리즈 | `/pipeline auto-dev`, `/omcustomcodex-release-notes`, `/release-plan` | 자동 개발, 릴리즈 노트 |
 | 리서치 | `/research`, `/scout`, `/deep-plan`, `/omcustomcodex:agora` | 병렬 분석, URL 평가, 연구 계획 |
@@ -256,6 +256,15 @@ Codex CLI의 Agent Teams 기능이 활성화되어 있으면 (`OMCODEX_AGENT_TEA
 /plugin install openai-docs
 /plugin install elements-of-style
 
+# 플러그인 인벤토리와 세션 토큰 비용 예측 확인 (Claude Code v2.1.139+)
+claude plugin details superpowers
+
+# 세션 전체 에이전트 목록 확인 (Claude Code v2.1.139+)
+claude agents
+
+# 인터랙티브 세션에서 마우스 휠 스크롤 속도 조정
+/scroll-speed
+
 # MCP 설정 (omx-memory)
 omx memory doctor
 ```

package/templates/CLAUDE.md.en

@@ -121,7 +121,7 @@ NO EXCEPTIONS. NO EXCUSES.
 | `/pre-generation-arch-check` | Check architecture risks before implementation |
 | `/omcustomcodex:sauron-watch` | Full R017 verification |
 | `/structured-dev-cycle` | 6-stage structured development cycle (Plan → Verify → Implement → Verify → Compound → Done) |
-| `/goal` | Keep a concrete objective through planning, execution, and verification |
+| `/omcustomcodex:goal` | Keep a concrete objective through planning, execution, and verification |
 | `/omcustomcodex:lists` | Show all available commands |
 | `/omcustomcodex:status` | Show system status |
 | `/omcustomcodex:help` | Show help information |
@@ -252,6 +252,15 @@ Install in Claude Code via `/plugin install <name>`:
 /plugin install openai-docs
 /plugin install elements-of-style
 
+# Inspect plugin inventory and projected session token cost (Claude Code v2.1.139+)
+claude plugin details superpowers
+
+# Inspect installed agents across sessions (Claude Code v2.1.139+)
+claude agents
+
+# Tune local mouse-wheel scrolling inside the interactive session
+/scroll-speed
+
 # MCP setup (omx-memory)
 omx memory doctor
 ```

package/templates/CLAUDE.md.ko

@@ -121,7 +121,7 @@ oh-my-customcodex로 구동됩니다.
 | `/pre-generation-arch-check` | 구현 전 아키텍처 위험 점검 |
 | `/omcustomcodex:sauron-watch` | 전체 R017 검증 |
 | `/structured-dev-cycle` | 6단계 구조적 개발 사이클 (Plan → Verify → Implement → Verify → Compound → Done) |
-| `/goal` | 구체 목표를 계획, 실행, 검증까지 유지 |
+| `/omcustomcodex:goal` | 구체 목표를 계획, 실행, 검증까지 유지 |
 | `/omcustomcodex:lists` | 모든 사용 가능한 커맨드 표시 |
 | `/omcustomcodex:status` | 시스템 상태 표시 |
 | `/omcustomcodex:help` | 도움말 표시 |
@@ -252,6 +252,15 @@ Claude Code 환경에서 `/plugin install <이름>`으로 설치:
 /plugin install openai-docs
 /plugin install elements-of-style
 
+# 플러그인 인벤토리와 세션 토큰 비용 예측 확인 (Claude Code v2.1.139+)
+claude plugin details superpowers
+
+# 세션 전체 에이전트 목록 확인 (Claude Code v2.1.139+)
+claude agents
+
+# 인터랙티브 세션에서 마우스 휠 스크롤 속도 조정
+/scroll-speed
+
 # MCP 설정 (omx-memory)
 omx memory doctor
 ```

package/templates/guides/claude-code/04-agent-skills.md

@@ -53,6 +53,22 @@ description: Brief description of what this Skill does and when to use it
 - 비어 있지 않아야 함
 - 최대 1024자
 
+### 네이티브 커맨드 충돌 피하기
+
+Claude Code v2.1.139+는 `/goal`을 세션 완료 조건 추적용 네이티브 커맨드로 예약합니다. oh-my-customcodex의 목표 실행 워크플로우는 `/omcustomcodex:goal`로 호출해야 하며, Skill 프론트매터도 `name: omcustomcodex:goal`을 사용합니다.
+
+디렉터리 이름은 호환성을 위해 `goal/`로 유지할 수 있지만, 사용자에게 노출되는 엔트리포인트는 프론트매터의 `name` 값입니다. 새 스킬이 Claude Code 네이티브 커맨드와 이름이 겹칠 가능성이 있으면 `omcustomcodex:` 네임스페이스를 우선 사용하세요.
+
+### 플러그인 인벤토리 검증
+
+Claude Code v2.1.139+에서는 다음 명령으로 설치된 플러그인의 구성 요소와 세션별 토큰 비용 예측을 확인할 수 있습니다:
+
+```bash
+claude plugin details <plugin-name>
+```
+
+oh-my-customcodex 호환 템플릿을 검증할 때는 플러그인 설치 후 이 명령으로 skill/agent 구성 요소 수와 예상 토큰 비용을 확인하고, Codex 쪽 패키지 인벤토리는 `omcustomcodex list`로 확인하세요.
+
 ## 사용 가능한 Skills
 
 ### 사전 구축된 Agent Skills

package/templates/guides/claude-code/06-mcp.md

@@ -55,6 +55,12 @@ response = client.beta.messages.create(
 | `name` | string | 예 | 이 MCP 서버의 고유 식별자 |
 | `authorization_token` | string | 아니오 | OAuth 인증 토큰 |
 
+## Claude Code 로컬 MCP 재연결
+
+Claude Code v2.1.139+에서는 `/mcp` reconnect가 `.mcp.json` 편집을 전체 재시작 없이 다시 읽습니다. Claude Code 호환 템플릿을 검증할 때 로컬 MCP 서버를 추가하거나 수정했다면 `/mcp`에서 reconnect를 실행해 즉시 반영 여부를 확인하세요.
+
+oh-my-customcodex의 Codex 런타임 MCP 설정은 여전히 `.codex/config.toml` 및 `omcustomcodex` 관리 경로를 기준으로 합니다. Claude Code 호환 테스트를 위해 `.mcp.json`을 쓰더라도 Codex 설치 경로의 MCP 설정과 혼동하지 마세요.
+
 ## MCP 도구 집합 구성
 
 ```json

package/templates/guides/claude-code/13-cli-flags.md

@@ -8,7 +8,7 @@
 | `--remote` | Connect to remote Claude Code instance | `claude --remote` |
 | `--bare` | Minimal UI, no statusline | `claude --bare` |
 | `--agent <name>` | Use specific agent as main thread | `claude --agent lang-golang-expert` |
-| `--agents` | List available agents | `claude --agents` |
+| `--agents` | List available agents (legacy flag; use `claude agents` for the unified view on v2.1.139+) | `claude --agents` |
 | `--from-pr <url>` | Start from a pull request | `claude --from-pr https://github.com/org/repo/pull/123` |
 | `--chrome` | Enable Chrome browser automation | `claude --chrome` |
 | `--json-schema` | Output JSON schema for structured output | `claude --json-schema schema.json` |
@@ -17,6 +17,18 @@
 | `--fork-session` | Fork an existing session | `claude --fork-session` |
 | `--teleport` | Transfer session context to another terminal | `claude --teleport` |
 
+## Interactive Commands
+
+Claude Code v2.1.139+ adds a few user-facing commands that are useful when running oh-my-customcodex compatibility templates inside Claude Code:
+
+| Command | Use |
+|---------|-----|
+| `claude agents` | Open the Research Preview agent view with a unified list across sessions. Use it to confirm installed `.claude/agents/` entries after template updates. |
+| `/scroll-speed` | Tune mouse-wheel scroll speed with live preview. This is a local UI preference and does not change harness behavior. |
+| `claude plugin details <name>` | Inspect a plugin's component inventory and projected per-session token cost. Use it after plugin installs to validate skill/agent counts. |
+
+`/goal` is also native in v2.1.139+. The oh-my-customcodex workflow entrypoint is `/omcustomcodex:goal` so the workflow does not shadow the native completion tracker.
+
 ## Headless Mode (`claude -p`)
 
 Headless mode runs Claude Code non-interactively, useful for CI/CD pipelines and automated workflows.

package/templates/guides/claude-code/15-version-compatibility.md

@@ -0,0 +1,59 @@
+# Claude Code Version Compatibility
+
+This guide records Claude Code release-note impact that affects the Claude compatibility template. The Codex-native runtime still uses `.codex/**` and OMX as the primary surface.
+
+## v2.1.141
+
+Published: 2026-05-13.
+
+Source: upstream oh-my-customcode #1137, Codex port #1310.
+
+| Change | Impact on oh-my-customcodex | Action |
+|--------|------------------------------|--------|
+| Hook JSON output can include `terminalSequence` for desktop notifications, window titles, and terminal bells | Optional complement to stderr HUD events and the command statusline; no Codex hook change is required for this release. | Record the option in R012 and defer any hook implementation until there is a concrete UX need. |
+| `CLAUDE_CODE_PLUGIN_PREFER_HTTPS` clones GitHub plugin sources over HTTPS instead of SSH | Helps Claude-template users install plugins in CI or locked-down networks without GitHub SSH keys. | No command change; document as opt-in environment behavior. |
+| `ANTHROPIC_WORKSPACE_ID` scopes workload identity federation tokens to one workspace | Useful only for multi-workspace enterprise Claude environments. | No Codex-side change required. |
+| `claude agents --cwd <path>` scopes the session list to a directory | Reduces noise when monitoring Claude compatibility sessions from a monorepo or multi-project workspace. | Track as a P3 CLI-flags guide follow-up; keep canonical project examples on `oh-my-customcodex`. |
+| `/feedback` can include recent sessions from the last 24 hours or 7 days | Improves upstream bug reports for multi-session agent behavior. | No harness change required. |
+| Rewind menu can summarize earlier context while preserving recent turns | Complements manual context management and memory handoff guidance. | No hook change required. |
+| Auto-mode permission dialogs explain which `permissions.ask` rule caused a prompt | Makes Claude-template permission debugging easier. | Keep permission guidance explicit; no template mutation needed. |
+| IDE file-edit prompts restored the "view diff in your IDE" option | UX restoration only. | No action. |
+| Background agents launched via `/bg` or `←←` preserve the current permission mode | Removes a historical source of unattended permission prompts in Claude compatibility sessions. | Add an R010 note; keep delegated tool policy explicit for workflows that rely on unattended writes. |
+| `claude agents` marks completed agents correctly even if a background shell remains | Improves R009/R018 monitoring for long-running compatibility sessions. | No Codex-side change required. |
+| Spinner, plugin menu, provider fallback, daemon, and Windows fixes are additive stability improvements | No direct package behavior change. | No action beyond this compatibility record. |
+
+## v2.1.140
+
+Published: 2026-05-12.
+
+| Change | Impact on oh-my-customcodex | Action |
+|--------|------------------------------|--------|
+| Agent `subagent_type` matching accepts case and separator variants | No runtime change. This repo still documents strict kebab-case agent names so Codex and Claude template references stay deterministic. | Keep examples such as `code-reviewer` and `lang-typescript-expert` in canonical form. |
+| Native `/goal` no longer silently hangs under managed-hook restrictions | Compatible with the v0.4.16 namespace split. | Keep the native `/goal` reserved and call the packaged workflow as `/omcustomcodex:goal`. |
+| Settings hot reload handles symlinked settings files more reliably | Reduces false `ConfigChange` noise for Claude template users. | No template change required. |
+| `claude --bg` and background service startup were hardened | Improves long-running Claude compatibility sessions. | No Codex-side change required. |
+| Remote managed settings retry once after a 401 | Reduces transient managed-settings failures. | No template change required. |
+| Managed `extraKnownMarketplaces` persistence was fixed | Relevant only when Claude plugin marketplaces are managed externally. | Audit managed settings if plugin marketplace state appears stale. |
+| `/loop` avoids redundant polling wakeups | Aligns with the repo's loop guidance to avoid unnecessary background wakeups. | No template change required. |
+| Windows missing-executable checks avoid repeated synchronous `where.exe` spawns | Helps Windows users when tools such as `gh` are missing. | Keep hook scripts graceful when optional tools are absent. |
+| `Read` offset validation accepts whitespace-padded or plus-prefixed strings | No template change. The repo examples already use numeric offsets plainly. | Keep generated examples simple. |
+| Plugin component-folder conflicts now warn in `/doctor`, `claude plugin list`, and `/plugin` | Useful for template compatibility checks. | Run `claude plugin details <name>` and `/doctor` after plugin manifest changes. |
+
+## v2.1.139
+
+Published: 2026-05-11.
+
+| Change | Port decision |
+|--------|---------------|
+| Hook `args: string[]` exec form | Reviewed. The current hook registry intentionally keeps shell `command` form because most hooks use `jq`, environment expansion, pipes, or inline shell snippets. Use `args` only for new hooks that are a single binary plus static arguments. |
+| PostToolUse `continueOnBlock` | Ported for high-signal advisory hooks. `context-budget-advisor.sh`, `stuck-detector.sh`, and `cost-cap-advisor.sh` set `continueOnBlock: true`; scripts use `exit 2` only when model-visible recovery guidance is needed. |
+| Native `/goal` | The packaged workflow uses `/omcustomcodex:goal`; native `/goal` stays available for Claude Code completion tracking. |
+| `claude agents`, `/scroll-speed`, `claude plugin details <name>`, `/mcp` reconnect | Documented in the CLI, MCP, AGENTS, and CLAUDE template guidance. |
+
+## Compatibility Rules
+
+1. Keep `.codex/**` as the source of truth for the Codex package.
+2. Mirror Claude compatibility guidance under `templates/.claude/**` and `templates/guides/**` when behavior affects installed templates.
+3. Prefer canonical kebab-case agent names even if Claude Code accepts looser variants.
+4. Do not migrate shell hook entries to `args` unless the hook has no shell expansion, no pipes, and no inline script body.
+5. Use `continueOnBlock` only for PostToolUse signals that the model can act on immediately.

package/templates/guides/claude-code/index.yaml

@@ -64,3 +64,8 @@ documents:
     title: 토큰 효율 레이어
     description: 플러그인, 런타임, 설정 레이어를 분리한 토큰 효율 최적화 가이드
     path: ./14-token-efficiency.md
+
+  - name: version-compatibility
+    title: 버전 호환성
+    description: Claude Code 릴리스별 oh-my-customcodex 호환성 판단 기록
+    path: ./15-version-compatibility.md

package/templates/guides/hook-data-flow/README.md

@@ -26,22 +26,22 @@ The pipeline spans two hook events and three scripts:
 SubagentStart event
   └─ agent-start-recorder.sh
        reads:  stdin JSON (agent_type, model, description)
-       writes: /tmp/.claude-agent-starts-$PPID  (appends 1 JSON line)
+       writes: /tmp/.codex-agent-starts-$PPID  (appends 1 JSON line)
 
 SubagentStop event  [hooks execute in array order — ordering is critical]
   │
   ├─ [1] task-outcome-recorder.sh
   │       reads:  stdin JSON (agent_type, model, outcome)
-  │       reads:  /tmp/.claude-agent-starts-$PPID  (duration calc — entry still present)
-  │       writes: /tmp/.claude-task-outcomes-$PPID  (appends 1 JSON line with duration_seconds)
+  │       reads:  /tmp/.codex-agent-starts-$PPID  (duration calc — entry still present)
+  │       writes: /tmp/.codex-task-outcomes-$PPID  (appends 1 JSON line with duration_seconds)
   │       writes: stderr  (on failure only)
   │
   └─ [2] stall-detection-advisor.sh
           reads:  stdin JSON (agent_type, model, description)
-          reads:  /tmp/.claude-agent-starts-$PPID  (finds matching start entry for duration)
-          reads:  /tmp/.claude-agent-durations-$PPID  (peer durations for average calculation)
-          writes: /tmp/.claude-agent-durations-$PPID  (appends completed agent's duration)
-          writes: /tmp/.claude-agent-starts-$PPID  (removes consumed start entry)
+          reads:  /tmp/.codex-agent-starts-$PPID  (finds matching start entry for duration)
+          reads:  /tmp/.codex-agent-durations-$PPID  (peer durations for average calculation)
+          writes: /tmp/.codex-agent-durations-$PPID  (appends completed agent's duration)
+          writes: /tmp/.codex-agent-starts-$PPID  (removes consumed start entry)
           writes: stderr  (advisory block if stall detected — R021 advisory-only)
 ```
 
@@ -49,9 +49,9 @@ SubagentStop event  [hooks execute in array order — ordering is critical]
 
 At SubagentStop, after at least one peer has already completed:
 
-1. Calculate `avg_duration` from all entries in `.claude-agent-durations-$PPID`
+1. Calculate `avg_duration` from all entries in `.codex-agent-durations-$PPID`
 2. Set `stall_threshold = avg_duration * 2`
-3. Scan `.claude-agent-starts-$PPID` for agents not yet in the duration file (still running)
+3. Scan `.codex-agent-starts-$PPID` for agents not yet in the duration file (still running)
 4. For each still-running agent where `elapsed > stall_threshold`, emit advisory to stderr
 
 The current agent's duration is recorded *after* stall detection so it does not inflate the average for its own check.
@@ -73,9 +73,9 @@ The current agent's duration is recorded *after* stall detection so it does not
 
 | File | Writer | Readers | Lifecycle |
 |------|--------|---------|-----------|
-| `/tmp/.claude-agent-starts-$PPID` | `agent-start-recorder.sh` (append) | `task-outcome-recorder.sh` (read), `stall-detection-advisor.sh` (read + remove entry) | Session-scoped via PPID; ring buffer 50 entries; entry removed after `stall-detection-advisor` consumes it |
-| `/tmp/.claude-task-outcomes-$PPID` | `task-outcome-recorder.sh` (append) | `feedback-collector.sh`, `eval-core-batch-save.sh` (at Stop) | Session-scoped via PPID; ring buffer 50 entries |
-| `/tmp/.claude-agent-durations-$PPID` | `stall-detection-advisor.sh` (append) | `stall-detection-advisor.sh` (read for average calculation) | Session-scoped via PPID; ring buffer 50 entries |
+| `/tmp/.codex-agent-starts-$PPID` | `agent-start-recorder.sh` (append) | `task-outcome-recorder.sh` (read), `stall-detection-advisor.sh` (read + remove entry) | Session-scoped via PPID; ring buffer 50 entries; entry removed after `stall-detection-advisor` consumes it |
+| `/tmp/.codex-task-outcomes-$PPID` | `task-outcome-recorder.sh` (append) | `feedback-collector.sh`, `eval-core-batch-save.sh` (at Stop) | Session-scoped via PPID; ring buffer 50 entries |
+| `/tmp/.codex-agent-durations-$PPID` | `stall-detection-advisor.sh` (append) | `stall-detection-advisor.sh` (read for average calculation) | Session-scoped via PPID; ring buffer 50 entries |
 
 ---
 
@@ -93,7 +93,7 @@ The SubagentStop hook array in `hooks.json` defines a strict ordering:
 
 **task-outcome-recorder MUST run before stall-detection-advisor.**
 
-Reason: `stall-detection-advisor.sh` removes the matching start entry from `.claude-agent-starts-$PPID` after reading it (to prevent re-matching on the next SubagentStop). If the order were reversed, `task-outcome-recorder.sh` would find no start entry for the agent and would always record `duration_seconds=0`.
+Reason: `stall-detection-advisor.sh` removes the matching start entry from `.codex-agent-starts-$PPID` after reading it (to prevent re-matching on the next SubagentStop). If the order were reversed, `task-outcome-recorder.sh` would find no start entry for the agent and would always record `duration_seconds=0`.
 
 If the order is swapped:
 - `task-outcome-recorder` records `duration_seconds=0` for all agents
@@ -107,10 +107,10 @@ If the order is swapped:
 ```
 Session start (PPID assigned)
   │
-  ├─ First SubagentStart  →  .claude-agent-starts-$PPID  created
+  ├─ First SubagentStart  →  .codex-agent-starts-$PPID  created
   │
-  ├─ First SubagentStop   →  .claude-task-outcomes-$PPID  created
-  │                          .claude-agent-durations-$PPID  created
+  ├─ First SubagentStop   →  .codex-task-outcomes-$PPID  created
+  │                          .codex-agent-durations-$PPID  created
   │
   ├─ Each SubagentStop    →  start entry consumed (removed by stall-detection-advisor)
   │                          duration entry appended