oh-my-customcodex 1.0.5 → 1.0.7

package/dist/cli/index.js

@@ -3091,7 +3091,7 @@ var init_package = __esm(() => {
     workspaces: [
       "packages/*"
     ],
-    version: "1.0.5",
+    version: "1.0.7",
     requiresCC: ">=2.1.121",
     claudeCode: {
       minimumVersion: "2.1.121",
@@ -26982,7 +26982,7 @@ init_lockfile();
 init_logger();
 import { execSync as execSync4 } from "node:child_process";
 import { platform as platform2 } from "node:os";
-var MINIMUM_OMX_VERSION = "0.18.17";
+var MINIMUM_OMX_VERSION = "0.19.0";
 var defaultDeps2 = {
   exec: execSync4,
   getPlatform: platform2

package/dist/index.js

@@ -1569,7 +1569,7 @@ init_lockfile();
 init_logger();
 import { execSync as execSync2 } from "node:child_process";
 import { platform as platform2 } from "node:os";
-var MINIMUM_OMX_VERSION = "0.18.17";
+var MINIMUM_OMX_VERSION = "0.19.0";
 var defaultDeps2 = {
   exec: execSync2,
   getPlatform: platform2
@@ -2316,7 +2316,7 @@ var package_default = {
   workspaces: [
     "packages/*"
   ],
-  version: "1.0.5",
+  version: "1.0.7",
   requiresCC: ">=2.1.121",
   claudeCode: {
     minimumVersion: "2.1.121",

package/package.json

@@ -3,7 +3,7 @@
   "workspaces": [
     "packages/*"
   ],
-  "version": "1.0.5",
+  "version": "1.0.7",
   "requiresCC": ">=2.1.121",
   "claudeCode": {
     "minimumVersion": "2.1.121",

package/templates/.claude/rules/MUST-agent-design.md

@@ -24,12 +24,22 @@ tools: [Read, Write, ...]  # Allowed tools
 | `opus` | claude-opus-4-6 | Complex reasoning, architecture |
 | `opusplan` | claude-opus-4-6 + plan mode | Architecture planning with approval gates |
 | `opus47` | claude-opus-4-7 | Latest Opus model, supports xhigh effort |
+| `fable` | claude-fable-5 | Claude compatibility only; high default effort; omit `[1m]` |
 
 <!-- DETAIL: Fable and Extended Context Aliases (Claude Code v2.1.170+)
 `fable` resolves to `claude-fable-5` for Claude compatibility only: Mythos-class model, tier above Opus; do not change Codex/OMX routing defaults. Extended context suffix `[1m]` (for example, `claude-opus-4-6[1m]`) enables a 1M token context window. For Fable 5, do not append `[1m]`; Claude Code v2.1.173+ strips it because Fable includes 1M context by default.
+
+Fable 5 effort strategy: Fable 5 defaults to high effort; reserve `xhigh` for capability-sensitive architecture, reasoning, or verification work. Its `low`/`medium` effort can exceed earlier-model high-effort quality, so avoid reflexive `xhigh` in Claude-template agents. Mythos 5 (`claude-mythos-5`) is Project Glasswing limited availability, not GA; do not add an alias until it is generally available. See `guides/claude-code/16-fable5-prompting.md` for Fable/Mythos prompting patterns and over-prescription risks.
 -->
 
 <!-- DETAIL: Fallback Models and Thinking Toggle (Claude Code v2.1.166+)
+
+Claude Code v2.1.198+ makes the built-in Explore agent inherit the main session model (capped at Opus) instead of staying fixed to Haiku, and makes subagents plus compaction inherit the session's extended-thinking setting. This improves Claude-template delegation quality, but Codex-native subagents still follow the installed OMX role/model contract.
+
+Claude Code v2.1.199+ shows stderr for SessionStart/Setup/SubagentStart hooks that exit 2, improving hard-block/advisory hook debugging. It also loads up to five leading stacked slash-skill calls (for example `/skill-a /skill-b do X`), reducing context loss in chained compatibility skills such as `omcustomcodex:fsd`; keep using explicit `$skill`/namespaced surfaces in Codex sessions.
+
+Claude Code v2.1.201+ changes Claude Sonnet 5 harness-reminder delivery so rule reminders are no longer injected as mid-conversation `system` role messages. This is a Claude-template prompt-shape change only; PostCompact rule reinjection and Codex/OMX session continuity remain governed by this repository's normal hooks and state.
+
 Claude compatibility settings can declare up to three `fallbackModel` entries tried in order when the primary Claude model is overloaded or unavailable. `--fallback-model` also applies to interactive Claude sessions. Treat this as platform availability failover, not Codex-native model routing or outcome-based escalation. Claude Code v2.1.166+ also supports disabling default thinking with `MAX_THINKING_TOKENS=0`, `--thinking disabled`, or the per-model thinking toggle. Claude Code v2.1.169+ adds `--safe-mode` / `CLAUDE_CODE_SAFE_MODE` to disable customizations for regression isolation, plus `disableBundledSkills` / `CLAUDE_CODE_DISABLE_BUNDLED_SKILLS` to hide bundled skills/workflows/slash commands when they conflict with project skills. Codex-native agents continue to use the OMX model contract and `reasoning_effort` routing. Claude Code v2.1.172+ applies `availableModels` restrictions to subagent `model:` overrides, the agent dispatch model picker, and the advisor model; compatibility allowlists should account for version-specific IDs and 1M suffix handling. Claude Code v2.1.173+ auto-normalizes Fable 5 IDs with redundant `[1m]` suffixes. Claude Code v2.1.175+ adds `enforceAvailableModels`, which constrains the resolved Default model as well as subagent overrides and prevents user/project settings from widening a managed allowlist.
 -->
 
@@ -196,6 +206,8 @@ When spawning agents via the Agent tool, CC applies a default `mode` of `acceptE
 1. **Agent frontmatter `permissionMode`**: Declares the agent's intended permission level. CC respects this when the agent is spawned via Agent tool.
 2. **Agent tool `mode` parameter**: Overrides frontmatter at spawn time. Routing skills should pass this explicitly.
 3. **Recommendation**: For agents that modify files, set `permissionMode: bypassPermissions` in frontmatter if the project uses `bypassPermissions` mode.
+
+Claude Code v2.1.200+ displays `default` permission mode as `Manual` in CLI help and IDE surfaces, and accepts `--permission-mode manual` / `"defaultMode": "manual"` alongside `default` with the same behavior. This is a Claude compatibility label change only; Codex/OMX approval policy and sandbox state remain controlled by the current Codex runtime.
 -->
 
 <!-- DETAIL: Isolation/Token/Limitations/Escalation details

package/templates/.claude/rules/MUST-agent-teams.md

@@ -53,6 +53,10 @@ Claude Code v2.1.166+ no longer propagates user authority through cross-session
 Claude Code v2.1.169+ makes `claude agents --json` include blocked and just-dispatched background sessions, adds `--all` for completed sessions, and includes `id` plus `state`. In Claude-template Agent Teams compatibility checks, prefer `--all` + `state` as ground truth for blocked/running/completed instead of inferring completion from a member disappearing from the active list. Codex/OMX sessions should use their native runtime state plus deterministic repository evidence.
 -->
 
+<!-- DETAIL: Claude Agent Teams Reliability Updates (Claude Code v2.1.198-v2.1.199)
+Claude Code v2.1.198+ reports teammate API errors to the lead as failed and wakes stuck teammates when messaged so they can retry. Claude Code v2.1.199+ returns partial work on rate-limit/server errors and reports API errors to the parent instead of misclassifying them as success. These fixes reduce false-success risk in Claude-template Agent Teams, but SendMessage reports remain low-reliability until backed by deterministic evidence such as `git status`, validation scripts, or native OMX state.
+-->
+
 ## Self-Check Before Agent Tool
 
 Quick rule: explicit user preference for plain subagents wins. Otherwise use Teams for 3+ agents, review cycles, shared state, complex debugging, dynamic creation, or multi-issue batches; use Agent Tool for 1-2 simple tasks, sequential scaffolding, or mechanical disjoint-file batches with explicit scopes.

package/templates/.claude/rules/MUST-completion-verification.md

@@ -162,6 +162,20 @@ Subagents often report failures as "pre-existing", "baseline", or "unchanged". T
 Never accept "pre-existing" without direct base-branch evidence. A false "pre-existing" claim can mask a regression introduced by the current change.
 -->
 
+### Verification-Delegation Non-Termination
+
+When delegating structural verification, release-quality judgment, or a quality gate, the prompt must state: **do not end the turn without a final PASS/FAIL verdict**. A mid-step verifier report is not completion evidence. If a verifier stops while still comparing hashes, reading logs, or drafting findings, resume it and obtain the final verdict before proceeding.
+
+| Anti-pattern | Required |
+|--------------|----------|
+| Verification delegate stops after partial analysis with no verdict | Prompt for a final PASS/FAIL and resume on mid-step termination |
+
+Origin: upstream #1443; prevents incomplete R017/deep-verify handoffs from being treated as release evidence.
+
+> **Claude Code v2.1.199+ compatibility**: subagent API errors are reported to the parent instead of being self-reported as success. This lowers false-success frequency, but R020 still requires canonical ground-truth verification (`git status`, grep, tests, validation scripts, registry/API checks) before accepting a subagent report.
+
+> **Claude Code v2.1.200+ compatibility**: subagents that hit a rate limit before emitting any output now return a clean failure instead of an empty result. This removes one silent-empty failure mode, but the R020 rule is unchanged: do not accept delegated completion without deterministic repository, test, validation, registry, or API evidence.
+
 ## Common False Completion Patterns — 7 anti-patterns including "Command executed" without exit code check, "Waiting for manual publish" when CI auto-publishes. See full table via Read tool.
 
 <!-- DETAIL: Common False Completion Patterns

package/templates/.claude/rules/MUST-enforcement-policy.md

@@ -42,6 +42,10 @@ Promotion requires: (1) measured violation rate data, (2) user approval, (3) rol
 | `rule-deletion-guard.sh` | 2026-04-08 | User-requested: rule files must require individual confirmation before deletion. Prevents accidental bulk deletion of project rules. |
 -->
 
+## Claude Compatibility Hook Visibility
+
+Claude Code v2.1.199+ displays stderr from SessionStart/Setup/SubagentStart hooks when they exit 2. This strengthens observability for hard-block and advisory hooks in packaged Claude templates, complementing structured `hookSpecificOutput.additionalContext` without changing the Codex/OMX enforcement model.
+
 ## Integration
 
 | Rule | Interaction |

package/templates/.claude/rules/MUST-orchestrator-coordination.md

@@ -256,6 +256,10 @@ Claude Code v2.1.172+ fixes background agents potentially reading another projec
 
 Claude Code v2.1.174+ fixes background sessions inheriting another session's `ANTHROPIC_*` provider environment (gateway URL, custom headers, `/model` aliases) from the shell that started the background daemon. It also fixes pre-warmed background workers failing with `Could not resolve authentication method` after sitting idle. This is a Claude-template isolation improvement; Codex/OMX sessions still keep explicit agent routing and permission boundaries.
 
+Claude Code v2.1.198+ background agents can auto-commit, push, and open draft PRs after completing work in a worktree, and retry transient network aborts. Claude Code v2.1.199+ returns partial subagent work on rate-limit/server errors and fixes several background-daemon lifecycle races. These are Claude-template reliability improvements only; Codex/OMX workflows must still make write authority explicit, keep release branches auditable, and verify the repository state before claiming completion.
+
+Claude Code v2.1.200+ further hardens background sessions and agents: sleep/wake or stalled-session resumes no longer silently stop mid-turn, cancelled respawned turns are not replayed after Esc, stale `daemon.lock` files from crashed workers are handled, older reinstalled builds cannot hijack newer daemons, roster corruption no longer disables orphan cleanup permanently, older binaries preserve newer record fields, and daemon restarts preserve socket auth tokens. Treat this as Claude-template reliability only; Codex/OMX still requires explicit branch, PR, and working-tree evidence.
+
 ## Agent Capability Pre-Check
 
 Before delegating work, compare the task requirements with the target agent frontmatter:
@@ -283,6 +287,16 @@ Required check:
 
 Do not rely on the delegate to repair stale path guesses in shared workflow, rule, guide, or release tasks.
 
+### New-File Count-Impact Pre-Check
+
+Before delegating a new-file addition that may affect a count in manifests, guide indexes, wiki summaries, or release notes, determine whether the file creates a new top-level topic/entity directory or only adds a document inside an existing directory. Measure the relevant top-level directories first, for example `find <dir> -mindepth 1 -maxdepth 1 -type d | wc -l`, and tell the delegate to sync based on the measured value rather than guessing a count change.
+
+| Anti-pattern | Required |
+|--------------|----------|
+| Delegating `count N→N+1` for a file under an existing topic directory | Measure directory/topic count first; pass the measured value and allow count to remain unchanged |
+
+Origin: upstream #1443; `guides/claude-code/16-fable5-prompting.md` is a new document inside an existing guide topic, so top-level guide count remains unchanged.
+
 <!-- DETAIL: Autonomous Execution Mode
 
 ## Autonomous Execution Mode

package/templates/.claude/rules/MUST-parallel-execution.md

@@ -90,6 +90,10 @@ Claude Code parallel tool calls in a single batch are independent — one failed
 | Instance independence | Isolated context, no shared state |
 | Large tasks (>3 min) | MUST split into parallel sub-tasks |
 
+<!-- DETAIL: Fable 5 long-lived subagent reuse
+Fable 5 is strong at long-horizon, long-lived subagent reuse. That does not weaken R009: independent work should still run in parallel, but Claude-template Fable 5 agents may carry a coherent multi-step lane longer instead of splitting every step into short-lived agents. See `guides/claude-code/16-fable5-prompting.md`.
+-->
+
 ## Capability-Aware Parallel Planning
 
 When capability metadata is available (for example via `action-validator` policy cache hints), use it to refine R009 parallelization decisions:

package/templates/.claude/rules/MUST-permissions.md

@@ -55,6 +55,12 @@ Claude Code compatibility templates may rely on v2.1.166+ deny-rule glob behavio
 
 Use `"*"` deny rules only for Claude compatibility settings that intentionally enforce deny-by-default, then add explicit allow rules. This is separate from Codex/OMX sandbox policy and the advisory tool-tier table above.
 
+## Claude Permission Mode Manual Label and AskUserQuestion (v2.1.200+)
+
+Claude Code v2.1.200+ displays the existing `default` permission mode as `Manual` across CLI help and IDE surfaces. `--permission-mode manual` and `"defaultMode": "manual"` are accepted alongside `default` with identical behavior. Document both names in Claude compatibility guidance, but do not translate the UI label into Codex sandbox policy.
+
+The same Claude release changed `AskUserQuestion` so dialogs no longer auto-continue by default; idle-timeout continuation is now explicit `/config` opt-in. Autonomous flows such as `omcustomcodex:fsd` should avoid question tools unless truly blocked and should proceed on best judgment for low-risk reversible work. Non-array `disabledMcpServers` / `enabledMcpServers` values in `.claude.json` no longer crash Claude startup.
+
 ## Permission Request Format
 
 ```

package/templates/.claude/rules/SHOULD-hud-statusline.md

@@ -23,6 +23,8 @@ Format: `─── [Spawn] {subagent_type}:{model} | {description} ───`
 
 > **v2.1.172+ Claude compatibility**: The `claude_code.lines_of_code.count` OTEL metric includes a `model` attribute, so lines-of-code telemetry can be sliced by model when monitoring is enabled. This extends the per-dimension slicing configured through the `monitoring-setup` skill.
 
+> **v2.1.198+ Claude compatibility**: background agent notifications fire the `Notification` hook when a session needs input or completes (`agent_needs_input` / `agent_completed`). Combine those notifications with HUD/statusline evidence so long-running Claude compatibility work does not appear silently idle. Codex/OMX status remains driven by native runtime state and `.codex/statusline.sh`.
+
 <!-- DETAIL: HUD Events full spec
 ### When to Display: Multi-step tasks, parallel execution, long-running operations. Skip for single brief operations.
 ### Parallel Display:

package/templates/.claude/rules/SHOULD-verification-ladder.md

@@ -59,6 +59,10 @@ R021 (MUST-enforcement-policy)과 R023은 **직교**한다. 두 규칙은 서로
 
 R021은 위반 시 어떻게 멈출지를, R023은 어떤 순서로 검증할지를 정의한다.
 
+## Fable 5 Over-Prescription Advisory
+
+Fable 5 follows instructions strongly enough that overly long, overly procedural prompts can reduce quality. When authoring Fable-targeted skills, agents, or delegation prompts, prefer concise goals, boundaries, and evidence requirements over repeating entire rulebooks. This advisory is orthogonal to R023: it concerns instruction compactness, while R023 concerns verification cost order. See `guides/claude-code/16-fable5-prompting.md`.
+
 ## Self-Check
 
 새 검증 도구 추가 시:
@@ -81,6 +85,18 @@ R021은 위반 시 어떻게 멈출지를, R023은 어떤 순서로 검증할지
 
 하나라도 불확실하면 **먼저 carve-out을 명시(Tier 1 우선 해결)**하고, 그래도 불확실하면 Tier 3 적대적 검증(`adversarial-review`, `multi-model-verification`)을 통과시킨 뒤 release한다 (ladder 순서 유지). 이는 R023 shift-left 원칙(저렴한 tier 우선)을 룰 작성 자체에 적용한 것이며, R016 룰 작성 워크플로우의 Tier-1 품질 게이트로 동작한다 (R016은 위반 후 룰 업데이트 소유, R023 carve-out은 안전-신호 룰 작성 시 사전 점검 — 직교). Closes #1353.
 
+## Detection Guard Delegation Standard
+
+When delegating Tier-1 detection guards such as deprecated-pattern grep checks, specify the difference between positive defects and negative/deprecated-context descriptions. Bare grep patterns can self-block on correct documentation that says a pattern is deprecated or no longer required.
+
+| Anti-pattern | Required |
+|--------------|----------|
+| Delegate a bare pattern scan that matches both mandates and deprecation notes | Require positive-match context (MUST/MANDATORY/use) and carve out negative context (deprecated/no longer/unnecessary) |
+
+Workflow prompt sanity checks must also catch unescaped shell variables in JavaScript template literals. Look for `$?`, `${PIPESTATUS[0]}`, command substitutions, and similar shell fragments inside prompt strings; escape them as `\${...}` when the string is evaluated by JavaScript before reaching Bash. `node --check` catches syntax, not this runtime interpolation failure.
+
+Origin: upstream #1438; a verify prompt containing `${PIPESTATUS[0]}` failed at runtime as `PIPESTATUS is not defined`.
+
 ## Integration
 
 | 규칙 | 상호작용 |
@@ -111,6 +127,7 @@ Before invoking a Workflow script, deterministically verify:
 | No unresolved placeholders (`{phase1_summary}`, `TODO`, `<...>`, `{{ }}`) remain in any agent prompt string | An unfilled placeholder reaches the agent verbatim → garbled task |
 | Template-literal / string concatenation produces the intended prompt (assemble-before-call, see above) | Post-call concatenation (`agent(prompt) + FACTS`) silently drops content |
 | Script parses — balanced braces/quotes, valid JS | A syntax error aborts the entire run after partial work |
+| Shell variables inside JS template prompt strings are escaped (`\${PIPESTATUS[0]}`, `$?`, `$(...)`) | Prevents JavaScript interpolation from turning shell variables into runtime `ReferenceError`s |
 
 #### Common Violation (#1271)
 Session 106 follow-up to #1266 ③: a Workflow authoring error recurred — the guardrail fact-sheet was concatenated onto the agent's RETURN VALUE instead of the prompt string, and a placeholder/assembly slip went uncaught because no pre-run sanity check existed. This check is the deterministic Tier-1 guard that catches such slips before the expensive run.

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

@@ -2,6 +2,63 @@
 
 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.201
+
+Reviewed: 2026-07-06.
+
+Source: upstream oh-my-customcode v1.1.7 / #1567.
+
+| Change | Impact on oh-my-customcodex | Action |
+|--------|------------------------------|--------|
+| Claude Sonnet 5 sessions no longer receive harness reminders as mid-conversation `system` role messages | Prompt-shape compatibility change for packaged Claude templates only. PostCompact rule reinjection and Codex/OMX continuity are unchanged. | Document in R006 and keep Codex-native routing/state on AGENTS.md plus OMX surfaces. |
+
+## v2.1.200
+
+Reviewed: 2026-07-06.
+
+Source: upstream oh-my-customcode v1.1.7 / #1567.
+
+| Change | Impact on oh-my-customcodex | Action |
+|--------|------------------------------|--------|
+| `default` permission mode is displayed as `Manual`; `manual` is accepted alongside `default` | Claude compatibility templates and operator docs should recognize both names as the same behavior. | Document in R002/R006; do not map the UI label onto Codex sandbox policy. |
+| `AskUserQuestion` no longer auto-continues by default | Unattended Claude compatibility flows can now block indefinitely if they ask questions without a real blocker. | Document in R002; FSD/auto-dev should continue using best judgment for low-risk reversible work. |
+| Subagents rate-limited before first output now return clean failure instead of an empty result | Reduces silent-empty delegated results, but does not remove the need for ground-truth verification. | Document in R020 and keep deterministic `git status`/validation/test/API checks. |
+| Background-session and daemon lifecycle fixes cover sleep/wake stalls, stale locks, daemon freshness, roster/orphan cleanup, record preservation, and socket auth token handling | Fewer Claude background-agent false blockers. | Document in R010; Codex/OMX release flow still verifies branch, PR, tag, registry, and working-tree state directly. |
+| `.claude.json` non-array MCP server lists no longer crash startup | Claude compatibility config is more forgiving. | Mention in R002 as Tier-6/MCP startup resilience; no Codex config schema change. |
+
+## v2.1.199
+
+Reviewed: 2026-07-05.
+
+Source: upstream oh-my-customcode v1.1.3 / #1561 and v1.1.6 / #1564.
+
+| Change | Impact on oh-my-customcodex | Action |
+|--------|------------------------------|--------|
+| SessionStart/Setup/SubagentStart hooks now surface stderr when exiting 2 | Improves Claude-template hard-block/advisory hook debugging. | Document in R006/R021; Codex/OMX enforcement remains advisory-first plus local hooks. |
+| Stacked slash-skill calls load up to five leading skills | Reduces context loss for chained Claude compatibility skill invocations. | Document in R006; keep `omcustomcodex:` namespaced skill surfaces for this package. |
+| Subagent rate-limit/server errors return partial work and API errors are no longer reported as success | Lowers false-success risk for Claude subagents and Agent Teams. | Document in R018/R020; still require deterministic repository/test/API evidence before accepting completion. |
+
+## v2.1.198
+
+Reviewed: 2026-07-05.
+
+Source: upstream oh-my-customcode v1.1.3 / #1561.
+
+| Change | Impact on oh-my-customcodex | Action |
+|--------|------------------------------|--------|
+| Built-in Explore agent inherits the main session model and subagents/compaction inherit extended-thinking settings | Improves Claude-template exploration/delegation quality. | Record as Claude compatibility only; Codex-native subagents still use installed OMX roles and model metadata. |
+| Background agents can auto-commit/push/open draft PRs after completing work, with better transient-network retry behavior | Reduces false blockers for Claude background-agent flows. | Document in R010; keep release branches and PR state explicitly verified by Git/GitHub evidence. |
+| Background agent notifications fire for needs-input and completed states | Better observability for long-running Claude compatibility sessions. | Document in R012; Codex/OMX status remains native runtime state plus `.codex/statusline.sh`. |
+| Agent Teams reports teammate API failures and wakes stuck teammates on message | Improves retry behavior but does not make SendMessage self-report authoritative. | Document in R018 and keep deterministic ground-truth checks. |
+
+## Claude Fable 5 prompting guide
+
+Reviewed: 2026-07-05.
+
+Source: upstream oh-my-customcode v1.1.4 / #1562.
+
+`guides/claude-code/16-fable5-prompting.md` records Fable 5 prompting guidance for packaged Claude compatibility sessions: high effort by default, `xhigh` only for capability-sensitive work, concise prompts over over-prescription, long-lived bounded lanes when appropriate, and Mythos 5 as limited availability / not GA. This does not change Codex-native OMX model routing.
+
 ## v2.1.178
 
 Published: 2026-06-15.

package/templates/guides/claude-code/16-fable5-prompting.md

@@ -0,0 +1,51 @@
+# Claude Fable 5 Prompting Guide
+
+> Source: upstream oh-my-customcode v1.1.4 / PR #1442, Codex-port issue #1562. This guide records the summarized compatibility impact for packaged Claude templates. It does not change Codex-native OMX model routing.
+
+## Overview
+
+Claude Fable 5 (`claude-fable-5`) is tracked here as a Claude compatibility model alias and prompting surface. In oh-my-customcodex, Fable guidance applies to packaged `.claude` templates and Claude compatibility sessions only; Codex-native subagents continue to use installed OMX roles, models, and `reasoning_effort` metadata.
+
+Fable 5 differs from prior Opus/Sonnet-tuned harness assumptions because it is stronger at long-horizon autonomy and instruction following. That can improve long-running delegated lanes, but it also means overly procedural prompts can over-constrain the model.
+
+## Behavior Differences to Account For
+
+| Area | Fable 5 guidance | oh-my-customcodex mapping |
+|------|------------------|---------------------------|
+| Long-horizon autonomy | Permit longer turns when a lane is coherent and bounded. | Keep R009 parallelism for independent work; avoid arbitrary turn chopping inside one lane. |
+| Effort strategy | High effort is the practical default; reserve `xhigh` for capability-sensitive architecture, reasoning, or verification. | R006 documents `fable` as Claude-template metadata only. |
+| Concise instructions | Prefer goals, boundaries, and evidence requirements over repeating entire rulebooks. | Aligns with R023 shift-left: cheap structure first, not prompt bloat. |
+| Ground-truth progress | Require actual artifacts, tests, registry/API checks, or diffs before accepting completion claims. | R020 already owns completion verification. |
+| Boundary clarity | State allowed and forbidden actions explicitly for privileged or external work. | R010 pre-delegation privileged-scope boundary already owns this. |
+| Parallel delegation | Independent lanes still benefit from parallel dispatch; a single Fable lane may also be reused across related steps. | R009 remains mandatory for independent tasks; long-lived reuse is a Fable-specific option, not a bypass. |
+| File memory | Persistent file-backed context can help long tasks. | Use project memory and repo artifacts deliberately; do not pollute AGENTS/rules for one-off facts. |
+| Context-budget phrasing | Avoid early stopping by naming the stop condition and required evidence. | R020/R013 cover completion and cost tradeoffs. |
+
+## Core Warning: Over-Prescription Can Lower Quality
+
+Fable 5 follows instructions strongly. If a Fable-targeted agent or skill is given a long sequence of procedural micro-rules, it may spend effort satisfying form over substance. For Fable-targeted compatibility prompts:
+
+1. State the desired outcome and stop condition.
+2. State safety/authority boundaries.
+3. Name required evidence.
+4. Let the model choose the smallest valid execution path.
+
+Do not remove the repository's rule corpus for other models; instead, avoid pasting large rule excerpts into a Fable delegation prompt when a concise boundary plus references is enough.
+
+## GA / Availability Notes
+
+| Item | Value |
+|------|-------|
+| Claude compatibility model ID | `claude-fable-5` |
+| Alias in this package | `fable` (Claude templates only) |
+| Context | 1M token context included; omit redundant `[1m]` suffix |
+| Effort | high by default; `xhigh` only for capability-sensitive tasks |
+| Mythos 5 | `claude-mythos-5` is limited availability / not GA; no package alias yet |
+
+## Cross-References
+
+- R006 (`MUST-agent-design.md`) — model aliases, effort guidance, Fable/Mythos availability distinction.
+- R009 (`MUST-parallel-execution.md`) — independent work still parallelizes; long-lived Fable lanes are optional within a bounded lane.
+- R010 (`MUST-orchestrator-coordination.md`) — privileged boundary and new-file count-impact pre-check.
+- R020 (`MUST-completion-verification.md`) — artifact/evidence-based completion.
+- R023 (`SHOULD-verification-ladder.md`) — over-prescription advisory and deterministic guard design.

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

@@ -69,3 +69,7 @@ documents:
     title: 버전 호환성
     description: Claude Code 릴리스별 oh-my-customcodex 호환성 판단 기록
     path: ./15-version-compatibility.md
+  - name: fable5-prompting
+    title: Claude Fable 5 Prompting Guide
+    description: Fable 5 prompting and harness-tuning patterns mapped to R006/R009/R010/R020/R023
+    path: ./16-fable5-prompting.md

package/templates/guides/openai-codex/01-version-compatibility.md

@@ -2,6 +2,15 @@
 
 This guide records OpenAI Codex release-note impact decisions for oh-my-customcodex. Use it for Codex/OMX runtime compatibility notes; keep Claude-only release notes in `guides/claude-code/15-version-compatibility.md`.
 
+## oh-my-codex v0.19.0 / OMX baseline
+
+Source: upstream oh-my-codex release `v0.19.0`, Codex-port issue #1565.
+
+| Change | Impact on oh-my-customcodex | Action |
+| --- | --- | --- |
+| Planning-gate and handoff transport lock-down, conductor contract, typed subagent provenance/lane fences, Ralplan consensus/terminal-state handling, Madmax fixes, Ultragoal HUD, and Rust flake fix | These are upstream OMX runtime reliability and safety fixes for workflows this package delegates to rather than reimplementing locally. | Raise the packaged `MINIMUM_OMX_VERSION` to `0.19.0` so `init`, `update`, and `doctor` require the fixed runtime. |
+| Release note states no intended breaking CLI/package/plugin-layout/config changes | No source migration, package dependency change, or template format change is required beyond the runtime baseline. | Record compatibility disposition and keep Codex/OMX runtime behavior external. |
+
 ## oh-my-codex v0.18.17 / OMX baseline
 
 Source: upstream oh-my-codex release `v0.18.17`, Codex-port issue #1556.

package/templates/manifest.json

@@ -1,11 +1,11 @@
 {
-  "version": "1.0.5",
+  "version": "1.0.7",
   "requiresCC": ">=2.1.121",
   "claudeCode": {
     "minimumVersion": "2.1.121",
     "protectedPathBypassVersion": "2.1.126"
   },
-  "lastUpdated": "2026-07-04",
+  "lastUpdated": "2026-07-06",
   "components": [
     {
       "name": "rules",