oh-my-customcodex 0.5.14 → 0.5.16

package/dist/cli/index.js

@@ -3091,7 +3091,7 @@ var init_package = __esm(() => {
     workspaces: [
       "packages/*"
     ],
-    version: "0.5.14",
+    version: "0.5.16",
     requiresCC: ">=2.1.121",
     claudeCode: {
       minimumVersion: "2.1.121",
@@ -27574,6 +27574,34 @@ async function checkOmx() {
     fixable: false
   };
 }
+function checkOmxModelRouting() {
+  const frontierModel = process.env.OMX_DEFAULT_FRONTIER_MODEL?.trim() || null;
+  const sparkModel = process.env.OMX_DEFAULT_SPARK_MODEL?.trim() || process.env.OMX_SPARK_MODEL?.trim() || null;
+  const usingLegacySpark = !process.env.OMX_DEFAULT_SPARK_MODEL?.trim() && Boolean(sparkModel);
+  if (!frontierModel && !sparkModel) {
+    return {
+      name: "OMX model lanes",
+      status: "pass",
+      message: "OMX model lane routing uses runtime defaults (no explicit env override)",
+      fixable: false
+    };
+  }
+  const details = [
+    `frontier=${frontierModel ?? "runtime-default"}`,
+    `spark=${sparkModel ?? "runtime-default"}`
+  ];
+  if (usingLegacySpark) {
+    details.push("legacy OMX_SPARK_MODEL detected; prefer OMX_DEFAULT_SPARK_MODEL");
+  }
+  const sameExplicitLane = frontierModel !== null && sparkModel !== null && frontierModel === sparkModel;
+  return {
+    name: "OMX model lanes",
+    status: sameExplicitLane ? "warn" : "pass",
+    message: sameExplicitLane ? `OMX Spark/model lane routing uses the same explicit model for frontier and spark (${frontierModel})` : "OMX Spark/model lane routing overrides detected",
+    fixable: false,
+    details
+  };
+}
 async function checkContexts(targetDir, rootDir = ".codex") {
   const contextsDir = path.join(targetDir, rootDir, "contexts");
   const exists2 = await isDirectory(contextsDir);
@@ -27830,7 +27858,8 @@ async function runAllChecks(targetDir, layout, packageVersion, includeUpdates) {
     checkCustomComponents(targetDir, layout.rootDir),
     checkRtk(),
     checkCodex(),
-    checkOmx()
+    checkOmx(),
+    checkOmxModelRouting()
   ]);
   const frameworkCheck = await checkFrameworkDrift(targetDir, packageVersion);
   const checksWithFramework = frameworkCheck ? [...baseChecks, frameworkCheck] : baseChecks;

package/dist/index.js

@@ -2316,7 +2316,7 @@ var package_default = {
   workspaces: [
     "packages/*"
   ],
-  version: "0.5.14",
+  version: "0.5.16",
   requiresCC: ">=2.1.121",
   claudeCode: {
     minimumVersion: "2.1.121",

package/package.json

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

package/templates/.claude/rules/MAY-optimization.md

@@ -4,6 +4,8 @@
 
 ## Efficiency
 
+> **Tool availability note**: On first exploration, do not assume a specific tool surface is available without confirming the current session's tool set. Prefer the available native repository inspection tools; fall back to bounded shell `find`/`grep`/`rg` when higher-level glob/search tools are unavailable.
+
 | Strategy | When | Example |
 |----------|------|---------|
 | Parallel | 3+ independent I/O tasks | Read multiple files simultaneously |
@@ -43,6 +45,11 @@ Inspired by [ouroboros PR #353](https://github.com/Q00/ouroboros/pull/353) capab
 
 Readability > Optimization. No optimization without measurement.
 
+
+### Measure-Before-Adopt Gate
+
+For new workflow heuristics, TIDE-style discovery shortcuts, or routing optimizations, measure before adoption. A small proof-of-concept that fails its confidence gate should be recorded as deferred rather than promoted into default guidance. Future adoption needs a broader multi-session corpus or deterministic benchmark evidence, not a single-session impression.
+
 ## Context Optimization via HTML Comments (v2.1.72+)
 
 HTML comments in all auto-injected .md files (AGENTS.md and rules/*.md) are hidden from the model during auto-injection but visible via Read tool.

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

@@ -27,6 +27,10 @@ tools: [Read, Write, ...]  # Allowed tools
 
 Extended context suffix: `[1m]` (e.g., `claude-opus-4-6[1m]`) — enables 1M token context window.
 
+<!-- DETAIL: Fallback Models and Thinking Toggle (Claude Code v2.1.166+)
+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. Codex-native agents continue to use the OMX model contract and `reasoning_effort` routing.
+-->
+
 ### Optional Frontmatter
 
 Key optional fields: `memory`, `effort`, `skills`, `soul`, `isolation`, `background`, `maxTurns`, `maxTokens`, `mcpServers`, `hooks`, `permissionMode`, `disallowedTools`, `limitations`, `domain`, `disableSkillShellExecution`. Supported since CC v2.1.63+. See full optional frontmatter via Read tool.
@@ -83,7 +87,7 @@ This Codex port ships `.claude` compatibility templates. When updating those tem
 - v2.1.161: independent parallel tool calls no longer cancel siblings when one Bash call fails; this supports R009 same-message batching for independent work.
 - v2.1.162: `claude agents --json` includes waiting/blocker metadata and explicit `--tools Grep/Glob` behavior is fixed; compatibility prompts may use those fields when diagnosing stuck Claude sessions.
 - v2.1.163: managed `requiredMinimumVersion`/`requiredMaximumVersion`, `/plugin list`, Stop/SubagentStop `hookSpecificOutput.additionalContext`, and skill command literal `\$` escaping are available. Hook/skill template changes should preserve these affordances.
-- v2.1.165: bug-fix/reliability release; no local template change required beyond compatibility confirmation.
+- v2.1.165: bug-fix/reliability release; no local template change required beyond compatibility confirmation. v2.1.166: fallbackModel availability failover and thinking-disable controls are Claude compatibility settings, not Codex/OMX routing. v2.1.167/v2.1.168: bug-fix-only compatibility confirmation.
 -->
 
 ## Hook Event Types

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

@@ -33,6 +33,10 @@ When enabled and criteria match, Agent Teams is required.
 
 Do not confuse these mechanisms.
 
+<!-- DETAIL: Cross-Session Relay Authority Hardening (Claude Code v2.1.166+)
+Claude Code v2.1.166+ no longer propagates user authority through cross-session relays: permission requests relayed from another session are refused, and auto mode blocks them. A relayed message from session A cannot grant session B permissions the user did not authorize in session B. This hardens `send_message` / peer relay against privilege escalation. Intra-session Agent Teams `SendMessage` is unaffected, but privileged actions still require authority in the receiving session.
+-->
+
 ## 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-permissions.md

@@ -42,6 +42,19 @@ Current guidance:
 - For `.claude/**` or `templates/.claude/**`, direct writes are acceptable when the target Claude Code runtime is new enough and the session is running with `bypassPermissions`.
 - Treat the old `/tmp/{skill}-{timestamp}.md` wrapper flow as a historical fallback only for older Claude Code versions, non-bypass sessions, or interactive runs that still surface a protected-path prompt.
 
+
+## Deny Rule Glob Patterns (Claude Code v2.1.166+)
+
+Claude Code compatibility templates may rely on v2.1.166+ deny-rule glob behavior:
+
+| Position | Glob support |
+|----------|-------------|
+| Deny rule tool-name | Supported; `"*"` denies all tools |
+| Allow rule tool-name | MCP tool-name globs only; non-MCP globs are rejected |
+| Unknown tool in deny rule | Startup warning |
+
+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.
+
 ## Permission Request Format
 
 ```

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

@@ -37,6 +37,22 @@ Treat these commands as destructive even when they look like routine cleanup:
 
 Advisory hooks may warn on these patterns, but warnings do not replace the approval and preservation requirements.
 
+
+### Pre-Delegation Blast-Radius Enumeration
+
+Before delegating any destructive git command from the table above, enumerate the exact discard targets and present them for explicit approval. Do not delegate destructive operations from a paraphrase such as "discard local changes" without showing what will be lost.
+
+Required evidence before delegation:
+
+| Scope | Command |
+|-------|---------|
+| Modified/staged tracked files | `git status --short` |
+| Uncommitted diff size | `git diff --stat` and `git diff --stat --cached` |
+| Stash contents, when relevant | `git stash show --stat` |
+| Untracked files at risk, for clean | `git clean -nd` |
+
+Prefer non-destructive alternatives such as `git stash` when the user's goal can be met without permanent loss.
+
 ## On Violation
 
 1. Stop all operations

package/templates/.claude/rules/SHOULD-memory-integration.md

@@ -39,6 +39,10 @@ If both backend families are available, warn before writing. Dual-write is accep
 
 -->
 
+<!-- DETAIL: Safety Feedback Memory
+When a session exposes a safety-relevant correction (credential handling, destructive git blast radius, privileged-scope chaining, or permission-boundary mistakes), write the durable lesson with confidence metadata instead of leaving it only in chat. Record what was verified, what behavior should change, and the source issue/session when available. Do not store secrets or raw credential material in memory.
+-->
+
 ## Best Practices
 
 - Consult memory before starting work

package/templates/AGENTS.md.en

@@ -137,6 +137,12 @@ project/
 +-- guides/                      # Reference docs (51 topics)
 ```
 
+## OMX Command Routing
+
+- `omx explore` is deprecated and must not be recommended for new repository lookup work. Use normal Codex repository inspection tools/subagents for file, symbol, pattern, relationship, and implementation discovery.
+- `USE_OMX_EXPLORE_CMD` is compatibility-only for legacy callers; truthy values do not make `omx explore` preferred.
+- Use `omx sparkshell -- <command>` only when the operator explicitly wants shell-native read-only evidence, bounded verification, or a tmux-pane summary.
+
 ## Orchestration
 
 Orchestration is handled by routing skills in the main conversation:

package/templates/AGENTS.md.ko

@@ -137,6 +137,12 @@ project/
 +-- guides/                      # 레퍼런스 문서 (51 토픽)
 ```
 
+## OMX 명령 라우팅
+
+- `omx explore`는 deprecated 상태이며 새 저장소 조회 작업에 권장하지 않습니다. 파일, 심볼, 패턴, 관계, 구현 탐색에는 일반 Codex 저장소 검사 도구/서브에이전트를 사용합니다.
+- `USE_OMX_EXPLORE_CMD`는 레거시 호출자 호환용일 뿐이며 truthy 값이어도 `omx explore`가 선호 경로가 되지 않습니다.
+- `omx sparkshell -- <command>`는 사용자가 shell-native 읽기 전용 근거, 제한된 검증, tmux-pane 요약을 명시적으로 원할 때만 사용합니다.
+
 ## 오케스트레이션
 
 오케스트레이션은 메인 대화의 라우팅 스킬로 처리됩니다:

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

@@ -2,6 +2,39 @@
 
 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.168
+
+Published: 2026-06-07.
+
+Source: upstream oh-my-customcode #1315, Codex port #1479.
+
+| Change | Impact on oh-my-customcodex | Action |
+|--------|------------------------------|--------|
+| Bug-fix/reliability release after the v2.1.166 compatibility surface | No new repo-owned template, agent, skill, hook, or rule behavior was identified beyond the v2.1.166 notes. | Record as compatibility-confirmed; do not add speculative runtime behavior. |
+
+## v2.1.167
+
+Published: 2026-06-07.
+
+Source: upstream oh-my-customcode #1313, Codex port #1479.
+
+| Change | Impact on oh-my-customcodex | Action |
+|--------|------------------------------|--------|
+| Bug-fix/reliability release after the v2.1.166 compatibility surface | No new repo-owned template, agent, skill, hook, or rule behavior was identified beyond the v2.1.166 notes. | Record as compatibility-confirmed; do not add speculative runtime behavior. |
+
+## v2.1.166
+
+Published: 2026-06-07.
+
+Source: upstream oh-my-customcode #1314/#1316, Codex port #1479.
+
+| Change | Impact on oh-my-customcodex | Action |
+|--------|------------------------------|--------|
+| Deny rules support glob patterns in the tool-name position, including `"*"` to deny all tools; allow-rule globs remain limited to MCP tool-name globs | Relevant to Claude compatibility settings and permission debugging. Codex/OMX sandboxing remains the active runtime boundary for this package. | Port R002 compatibility note; do not treat Claude settings globs as Codex policy. |
+| `fallbackModel` supports up to three ordered fallback models and `--fallback-model` applies to interactive sessions | Useful Claude platform availability failover. It is distinct from per-agent `model:` metadata, the `model-escalation` skill, and Codex-native model routing. | Port R006 note; keep Codex child agents on the OMX model contract and `reasoning_effort`. |
+| `MAX_THINKING_TOKENS=0`, `--thinking disabled`, and per-model thinking toggles can disable default thinking | Claude compatibility sessions can reduce thinking overhead for low-effort work. | Document as Claude-only compatibility; do not infer Codex reasoning behavior. |
+| Cross-session relayed `SendMessage` no longer carries user authority; relayed permission requests are refused and auto mode blocks them | Hardens peer-relay workflows against privilege escalation between Claude sessions. Intra-session Agent Teams are unaffected. | Port R018 note and keep privileged actions scoped to the receiving session. |
+
 ## v2.1.158
 
 Published: 2026-05-30.

package/templates/manifest.json

@@ -1,5 +1,5 @@
 {
-  "version": "0.5.14",
+  "version": "0.5.16",
   "requiresCC": ">=2.1.121",
   "claudeCode": {
     "minimumVersion": "2.1.121",

package/templates/workflows/auto-dev.yaml

@@ -74,9 +74,20 @@ steps:
       Gate transparency:
       - Do not add or change labels solely to qualify for docs-only or lite mode.
       - If labels were changed during triage and affect compression eligibility, state that fact in the mode decision.
+      - Whenever a skill stage is replaced by integrated analysis, log a concrete justification:
+        `[compression-mode] lite — skill stage replaced by integrated analysis; scope={n}; low-risk evidence={issue_refs}`.
+      - If the justification cannot be stated concretely, do not compress that stage; run the full skill.
+
+      Cross-tier pre-existing converged artifact substitution:
+      - A triage, plan, deep-plan, or deep-verify step may be satisfied by an existing converged research/plan/verification artifact instead of a fresh skill spawn, even in standard mode.
+      - The artifact must explicitly cover the scoped issue domain, be current for the release scope, and provide output equivalent to the skipped step.
+      - This substitution never applies to implement, verify-build, release, publish, or CI/publish verification.
+      - Log the artifact path or URL and why it is equivalent before substituting.
 
       In docs-only mode, replace heavyweight triage/plan/deep-plan/deep-verify spawns with direct summaries plus local self-review.
       In lite mode, keep a concise implementation plan and local self-review, but still run verify-build.
+      In lite mode deep-verify, if the change set has no structural surface (for example workflow-YAML/docs-only with no agent/skill/guide/rule frontmatter changes), the R017/deep-verify spawn may be skipped and replaced by deterministic self-checks: template parity, multi-copy checksum, YAML parse, and the normal verify-build gate. Log:
+        `[compression-mode] lite deep-verify — R017 spawn skipped (no structural surface); deterministic self-check only`.
       Otherwise use standard mode.
       Output the selected compression_mode for downstream steps.
     description: Evaluate docs-only compression eligibility
@@ -130,7 +141,7 @@ steps:
   - name: verify
     depends_on: verify-build
     skill: deep-verify
-    description: Multi-angle release quality verification; self-review checklist only if compression_mode=docs-only
+    description: Multi-angle release quality verification; self-review checklist if compression_mode=docs-only, or deterministic self-check in lite mode when no structural surface changed
 
   - name: release
     depends_on: verify