oh-my-customcodex 0.5.21 → 1.0.0

package/README.md

@@ -13,7 +13,7 @@
 
 **[한국어 문서 (Korean)](./README_ko.md)**
 
-50 agents. 121 skills. 23 rules. One command.
+50 agents. 122 skills. 23 rules. One command.
 
 ```bash
 npm install -g oh-my-customcodex && cd your-project && omcustomcodex init
@@ -135,13 +135,13 @@ Each agent declares its tools, model, memory scope, and limitations in YAML fron
 
 ---
 
-### Skills (121)
+### Skills (122)
 
 | Category | Count | Includes |
 |----------|-------|----------|
 | Best Practices | 24 | Go, Python, TypeScript, Kotlin, Rust, React, FastAPI, Spring Boot, Django, Flutter, Docker, AWS, Postgres, Redis, Kafka, dbt, Spark, Snowflake, Airflow, pipeline-architecture-patterns, alembic, and more |
 | Routing | 4 | secretary, dev-lead, de-lead, qa-lead |
-| Workflow | 13 | structured-dev-cycle, deep-plan, research, evaluator-optimizer, dag-orchestration, worker-reviewer-pipeline, reasoning-sandwich, pipeline, and more |
+| Workflow | 14 | structured-dev-cycle, deep-plan, research, evaluator-optimizer, dag-orchestration, worker-reviewer-pipeline, reasoning-sandwich, pipeline, fsd, and more |
 | Development | 10 | dev-review, dev-refactor, analysis, create-agent, intent-detection, web-design-guidelines, omcodex:takeover, skill-extractor, pre-generation-arch-check, idea |
 | Operations | 10 | update-docs, audit-agents, sauron-watch, monitoring-setup, token-efficiency-audit, fix-refs, release-notes, and more |
 | Memory | 3 | memory-save, memory-recall, memory-management |
@@ -172,6 +172,7 @@ All commands are invoked inside the oh-my-customcodex GPT Codex + OMX session.
 | `/pre-generation-arch-check` | Check architecture risks before implementation |
 | `/adversarial-review` | Attacker-mindset security code review |
 | `/omcustomcodex:goal` | Keep a concrete objective in view through planning, execution, and verification |
+| `/omcustomcodex:fsd` | Full Self Driving release loop: repeat `/pipeline auto-dev` + `/homework` until eligible issues are exhausted |
 | `/pipeline` | Execute YAML-defined pipelines |
 | `/pipeline resume` | Resume a halted pipeline from last failure point |
 
@@ -288,7 +289,7 @@ your-project/
 │   ├── contexts/               # 4 shared context files
 │   └── ontology/               # Knowledge graph for RAG
 ├── .agents/
-│   └── skills/                 # 121 installed skill modules
+│   └── skills/                 # 122 installed skill modules
 └── guides/                     # 52 reference documents
 ```
 

package/dist/cli/index.js

@@ -3091,7 +3091,7 @@ var init_package = __esm(() => {
     workspaces: [
       "packages/*"
     ],
-    version: "0.5.21",
+    version: "1.0.0",
     requiresCC: ">=2.1.121",
     claudeCode: {
       minimumVersion: "2.1.121",

package/dist/index.js

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

package/package.json

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

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

@@ -27,7 +27,7 @@ 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.
+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.
 -->
 
 ### Optional Frontmatter
@@ -87,6 +87,7 @@ This Codex port ships `.claude` compatibility templates. When updating those tem
 - 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.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.
+- v2.1.169: `--safe-mode` / `CLAUDE_CODE_SAFE_MODE` disables all customizations for Claude regression isolation; `disableBundledSkills` / `CLAUDE_CODE_DISABLE_BUNDLED_SKILLS` hides bundled skills/workflows/slash commands from the model. Keep distinct from advisory `skills:` frontmatter metadata.
 - v2.1.170: Claude compatibility sessions gain access to the `fable` alias (`claude-fable-5`) and fix a VS Code integrated-terminal transcript persistence bug. Skills that rely on transcript replay (for example `homework`) should prefer v2.1.170+ in Claude-template sessions. No Codex runtime model-routing change.
 -->
 

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

@@ -49,6 +49,10 @@ Do not confuse these mechanisms.
 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.
 -->
 
+<!-- DETAIL: Claude Agent Session Ground Truth (Claude Code v2.1.169+)
+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.
+-->
+
 ## 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

@@ -78,6 +78,18 @@ When diagnosing pipeline or data state, verify the canonical store — the autho
 
 A single path's failure does not prove the whole multi-path system is down.
 
+## Config-Schema-Before-Edit
+
+Before planning edits to configuration that participates in an override, precedence, inheritance, provider, endpoint, credential, or multi-key chain, read the full config schema and precedence chain first. Do not plan partial edits before understanding which fields override which.
+
+This applies when a change touches interdependent fields such as provider + `base_url`, endpoint overrides, multi-key fallback, or layered defaults. A single independent field edit does not require a full-schema read.
+
+| Anti-pattern | Required |
+|--------------|----------|
+| Plan a provider/endpoint switch as N commands without reading the override chain | Read schema and precedence → enumerate every touched field, including `base_url` → then plan |
+
+Sibling discipline to Read-Before-Characterize: diagnosis must read evidence before labeling; config edits must read precedence before planning.
+
 ## Degraded-Output Re-Verification Gate
 
 When tool output shows provider instability, buffering, truncation, duplicated chunks, `529`, timeout recovery, or `(no result)` while a permanent action is being considered, treat the current read as degraded. Do not characterize corruption, missing files, stale state, release failure, or data loss from that single degraded read.

package/templates/.claude/rules/MUST-intent-transparency.md

@@ -73,6 +73,19 @@ R001-listed catastrophic git operations (`git reset --hard`, `git clean -fd`, `g
 
 Boundary: this rule governs model behavior only. It cannot suppress Codex/Claude runtime auto-mode permission prompts. For genuine prompt suppression on a repeated destructive command, surface the scoped settings/permission-rule workaround for the specific command instead of re-asking the same high-level question.
 
+## User-Provided Input Precedence
+
+When the user explicitly provides new input (credentials, config values, IdP, API keys, endpoints), applying that new input takes precedence over idempotent "reuse existing" logic. After applying, verify the change took effect using only non-secret identifiers such as `client_id`, endpoint URL, key fingerprint/last-4, or a side-effect probe. Never echo secret values into the transcript.
+
+| Anti-pattern | Required |
+|--------------|----------|
+| "An existing X is present → reuse it" when the user just supplied a new X | Apply the user-supplied X; reuse only when the user supplied nothing |
+| User-supplied X equals the existing X | Treat as an idempotent no-op; do not re-provision |
+| User supplies only a subset of fields | Apply supplied fields; reuse existing values only for unsupplied fields |
+| Apply new credential, assume it took effect | Verify via non-secret identifier match or side-effect probe |
+
+Cross-reference: R001 credential guardrails and R020 actual-outcome verification.
+
 ## Structured Question Failure Discipline
 
 When a structured question surface (`AskUserQuestion`, `omx question`, or native structured input) is rejected, unavailable, or malformed, the orchestrator must not silently downgrade to a different workflow.

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

@@ -25,7 +25,7 @@ When the user has a standing "do not touch X" constraint and a safety classifier
 
 ### Infra-Diagnostic File Checks — Metadata, Not Contents
 
-When diagnosing infrastructure or health issues, file checks must stay metadata-only: `ls -la` for existence, size, permissions, and mtime. Do not `cat .env`, inspect credential JSON keys, or read secret contents into the transcript just to confirm configuration exists.
+When diagnosing infrastructure or health issues (502s, container state, env/config presence), file checks must stay metadata-only: `ls -la` for existence, size, permissions, and mtime. Do not `cat .env`, inspect credential JSON keys, parse secret-bearing files, or read secret contents into the transcript just to confirm configuration exists.
 
 | Anti-pattern | Required |
 |--------------|----------|

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

@@ -0,0 +1,137 @@
+---
+name: omcustomcodex:fsd
+description: Full Self Driving — autonomous release loop that processes all auto-dev-eligible GitHub issues until none remain, by repeatedly running /pipeline auto-dev then /homework.
+scope: harness
+user-invocable: true
+argument-hint: "[<max-releases>]"
+version: 0.1.0
+effort: high
+---
+
+# /omcustomcodex:fsd — Full Self Driving
+
+Autonomous release loop. Equivalent to running:
+
+```
+/omcustomcodex:goal "모든 이슈가 처리될 때까지" /omcustomcodex:loop "/pipeline auto-dev -> /homework"
+```
+
+This is a **thin alias / orchestrator skill**. It does not implement loop, issue-polling, release, or verification logic — it delegates entirely to existing skills.
+
+## Usage
+
+```
+/omcustomcodex:fsd               # Run until all auto-dev-eligible issues are exhausted
+/omcustomcodex:fsd 3             # Optional: cap at N releases (default: unlimited)
+```
+
+No arguments are required. The default behavior runs until the auto-dev-eligible issue set is empty.
+
+## What It Does
+
+FSD expands into:
+
+1. **`/omcustomcodex:goal` wrapper** — applies disciplined goal-to-execution workflow:
+   - Objective: "모든 이슈가 처리될 때까지"
+   - Delegates planning, gap detection, and R020 completion verification to the `goal` skill
+2. **`/omcustomcodex:loop` recurrence** — self-paced loop, each iteration runs:
+   1. `/pipeline auto-dev` — full release pipeline for the next eligible issue or release unit
+   2. `/homework` — retrospective 찐빠 audit gate
+
+### Loop Convergence
+
+The loop converges naturally when the auto-dev-eligible issue set reaches 0. Issue eligibility follows `/pipeline auto-dev` label selection exactly:
+
+- **Included**: `verify-ready` (preferred), unlabeled auto-dev candidates
+- **Excluded**: `verify-done`, `needs-review`, `decision-needed` labels
+
+Do NOT invent new label logic here — defer to the `pipeline` skill's auto-dev issue selection.
+
+### Iteration Flow (per iteration)
+
+```
+[FSD Iteration N]
+├── /pipeline auto-dev        → one release (PR create → merge → npm publish → milestone close)
+├── /homework                 → extract 찐빠, confirm gate (or --dry-run if requested)
+└── Check: any eligible issues remain?
+    ├── YES → next iteration
+    └── NO  → [FSD Done] converged naturally
+```
+
+## Safety and Discipline
+
+Each iteration operates under full project rules — no relaxation because FSD is autonomous:
+
+| Rule | Applies |
+|------|---------|
+| R001 (safety) | Destructive ops still require explicit approval. Credential guardrails always active. |
+| R009 (parallel) | Independent subtasks within each pipeline iteration run in parallel. |
+| R010 (orchestration) | File modifications follow repo delegation/ownership rules. |
+| R017 (sync verification) | Structural verification passes before any commit. |
+| R020 (completion verification) | Each release verified via `npm view`, `gh release view`, closed issues before `[Done]`. |
+
+`/homework` runs as a **retrospective gate** between iterations — findings go through `omcustomcodex:feedback`'s preview/confirmation gate. The loop does NOT skip homework because it is "automated". If homework requires user confirmation, the loop pauses and waits.
+
+If a release operation triggers the safety classifier, the current iteration stops and surfaces the block before continuing.
+
+## When to Use
+
+| Scenario | Use FSD? |
+|----------|----------|
+| Multiple eligible issues ready to process autonomously | YES |
+| Session where the user wants to "let it run" through the backlog | YES |
+| Verifying the autonomous release loop pattern from session memory | YES |
+| Single targeted issue fix | NO — use `/pipeline auto-dev` directly |
+| Exploratory research / planning only | NO — use `/research` or `/deep-plan` |
+| Only one issue and it needs human judgment | NO — use `/pipeline auto-dev` with manual oversight |
+
+## When NOT to Use
+
+- When issues require stakeholder approval or design decisions before implementation
+- When the issue set includes `decision-needed` or `needs-review` items only
+- When cost sensitivity is high and the issue backlog is large — inspect the eligible set first before running FSD
+
+## Optional Release Cap
+
+Pass a numeric argument to cap at N releases:
+
+```
+/omcustomcodex:fsd 3    # Process at most 3 releases this FSD run
+```
+
+The cap is advisory — the pipeline itself may stop earlier if the eligible set runs out before the cap is reached.
+
+## Session 114 Precedent
+
+This skill was extracted from the upstream manual pattern used in Session 114 (2026-06-09):
+
+```
+/goal "모든 이슈가 처리될 때까지" /loop "/pipeline auto-dev -> /homework"
+```
+
+The Codex port keeps the intent but uses `omcustomcodex:` namespaced goal/loop surfaces to avoid native runtime command collisions.
+
+## Cross-References
+
+| Skill / Rule | Role |
+|--------------|------|
+| `omcustomcodex:goal` | Disciplined goal-to-execution wrapper — objective parse, gap detection, R020 verification |
+| `omcustomcodex:loop` | Session auto-continuation during background work |
+| `pipeline` | `/pipeline auto-dev` — the core release pipeline per iteration |
+| `homework` | Retrospective 찐빠 audit gate per iteration |
+| R001 (safety) | Destructive ops require approval; credential guardrails |
+| R009 (parallel execution) | Parallel subtasks within each pipeline iteration |
+| R010 (orchestrator coordination) | File ownership and delegation discipline |
+| R017 (sync verification) | Structural verification before commit/push |
+| R020 (completion verification) | Actual outcome verified before declaring each release done |
+
+## Design Notes
+
+This skill is intentionally a **thin alias**. It does NOT duplicate issue polling, loop cadence, release steps, retrospective analysis, or completion verification. If the underlying skills evolve, FSD automatically benefits.
+
+## Artifact Output
+
+Artifacts from each iteration follow the constituent skills' conventions:
+
+- Pipeline artifacts: `.codex/outputs/sessions/{YYYY-MM-DD}/pipeline-auto-dev-{HHmmss}.md`
+- Homework artifacts: `.codex/outputs/sessions/{YYYY-MM-DD}/homework-{HHmmss}.md`

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

@@ -31,9 +31,11 @@ Quick Start:
   status             Show system status
   help <command>     Get help for a specific command
   /omcustomcodex:goal <objective>  Run a goal-to-execution workflow
+  /omcustomcodex:fsd [max]        Run the autonomous full-backlog release loop
 
 Common Commands:
   /omcustomcodex:goal  Keep an objective through planning, execution, and verification
+  /omcustomcodex:fsd   Repeat /pipeline auto-dev + /homework until eligible issues are exhausted
   /update-docs       Sync documentation with project
   /update-external   Update external agents
   /audit-agents      Check agent dependencies

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

@@ -28,6 +28,7 @@ System:
   status             Show system status
   help               Show help information
   /omcustomcodex:goal  Run a goal-to-execution workflow
+  /omcustomcodex:fsd   Run the autonomous full-backlog release loop
 
 Manager:
   /create-agent          Create a new agent
@@ -57,6 +58,7 @@ System Commands:
 │ status  │ Show system status and health checks         │
 │ help    │ Show help for commands and agents            │
 │ /omcustomcodex:goal │ Run a goal-to-execution workflow  │
+│ /omcustomcodex:fsd  │ Run full-backlog auto-dev loop    │
 └─────────┴──────────────────────────────────────────────┘
 
 Manager Commands:

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

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

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

@@ -13,6 +13,19 @@ Source: upstream oh-my-customcode #1352/#1354, Codex port #1504.
 | Claude Fable 5 is available through the `fable` alias (`claude-fable-5`) | Useful only for packaged Claude compatibility sessions needing mythos-class reasoning; Codex-native subagents continue to use the OMX model contract and `reasoning_effort`. | Document in R006 as Claude-compatibility metadata. Do not change Codex routing defaults. |
 | VS Code integrated-terminal sessions save transcripts correctly and show them in `--resume` | Improves Claude-template workflows that depend on transcript replay, including imported `homework`/retrospective flows. | Prefer Claude Code v2.1.170+ when testing Claude compatibility transcript-dependent skills. No Codex runtime change. |
 
+## v2.1.169
+
+Published: 2026-06-08.
+
+Source: upstream oh-my-customcode #1329, Codex port #1496.
+
+| Change | Impact on oh-my-customcodex | Action |
+|--------|------------------------------|--------|
+| `--safe-mode` and `CLAUDE_CODE_SAFE_MODE` start Claude Code with all customizations disabled | Useful for isolating whether a packaged `.claude` template, skill, hook, plugin, or MCP server causes a Claude-compatibility regression. | Document in R006; do not change Codex/OMX runtime loading. |
+| `disableBundledSkills` and `CLAUDE_CODE_DISABLE_BUNDLED_SKILLS` hide bundled skills, workflows, and built-in slash commands from the model | Helps when Claude bundled skills duplicate or conflict with project skills. Distinct from advisory `skills:` frontmatter metadata. | Record as Claude platform setting; keep Codex skill roots unchanged. |
+| `claude agents --json` includes blocked and just-dispatched sessions; `--all` includes completed sessions; output includes `id` and `state` | Strengthens Claude-template Agent Teams completion checks. | Prefer `--all` + `state` when diagnosing Claude Agent Teams; Codex/OMX uses native runtime state plus repo evidence. |
+| `/cd` command and reliability fixes for MCP policy/history behavior | Claude operator convenience only. | No Codex runtime change. |
+
 ## v2.1.168
 
 Published: 2026-06-07.

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

@@ -2,6 +2,19 @@
 
 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`.
 
+## rust-v0.139.0 / CLI 0.139.0
+
+Source: upstream OpenAI Codex release `rust-v0.139.0`, Codex-port issue #1498.
+
+| Change | Impact on oh-my-customcodex | Action |
+| --- | --- | --- |
+| Code mode can call standalone web search directly, including nested JavaScript tool calls, and receive plaintext results | Improves Codex runtime research ergonomics but does not change packaged skill/tool routing. | Keep repository research guidance source-backed; no package dependency change. |
+| Tool and connector schemas preserve `oneOf`/`allOf`; large schemas keep more shallow structure during compaction | Reduces MCP/app connector schema loss for richer tools. | No template migration; continue to prefer connector schemas as runtime ground truth. |
+| `codex doctor` includes editor and pager environment details while redacting raw values in JSON output | Aligns with metadata-only diagnostics and secret-redaction rules. | Document compatibility; keep `omcustomcodex doctor` separate. |
+| Plugin marketplace automation exposes marketplace source in `list --json` and returns cached catalogs before background refresh | Useful for future plugin inventory automation. | Prefer JSON when automating plugin inventory; no current CLI behavior change. |
+| `codex resume --last "..."` and `codex fork --last "..."` treat trailing text as the initial prompt | Reduces operator surprise for resume/fork workflows. | No package change. |
+| MCP startup warnings are scoped to the owning thread, image edits use exact referenced paths, URLs with `~` linkify correctly, thread resets preserve cloud requirements, and sandbox execution preserves approved escalation/proxy-only networking more consistently | Runtime stability and evidence quality improvements. | No package change beyond this compatibility record. |
+
 ## rust-v0.138.0 / CLI 0.138.0
 
 Source: upstream OpenAI Codex release `rust-v0.138.0`, Codex-port issue #1481.

package/templates/manifest.json

@@ -1,11 +1,11 @@
 {
-  "version": "0.5.21",
+  "version": "1.0.0",
   "requiresCC": ">=2.1.121",
   "claudeCode": {
     "minimumVersion": "2.1.121",
     "protectedPathBypassVersion": "2.1.126"
   },
-  "lastUpdated": "2026-06-11T00:00:00.000Z",
+  "lastUpdated": "2026-06-11",
   "components": [
     {
       "name": "rules",
@@ -23,7 +23,7 @@
       "name": "skills",
       "path": ".agents/skills",
       "description": "Reusable skill modules (project-scoped repo skills)",
-      "files": 121
+      "files": 122
     },
     {
       "name": "guides",