oh-my-opencode 4.7.4 → 4.8.0

package/.agents/command/get-unpublished-changes.md

@@ -1,5 +1,5 @@
 ---
-description: Compare HEAD with the latest published npm version and list all unpublished changes
+description: Compare HEAD with the latest published npm versions and list all unpublished changes by release layer
 ---
 
 <command-instruction>
@@ -12,11 +12,23 @@ For each commit, you MUST:
 2. Describe the REAL change in plain language
 3. Explain WHY it matters (if not obvious)
 
+## Release Layers
+
+Analyze every change against these exact layers:
+
+| Layer | Includes | Version question |
+|---|---|---|
+| `omo pure components` | `packages/*-core`, MCP packages, `packages/shared-skills`, reusable scripts | Do shared components need a patch/minor/major release note even if adapters only consume them internally? |
+| `omo opencode` | Root `oh-my-opencode` / `oh-my-openagent`, `src/`, `.opencode/`, `.agents/`, CLI, config, hooks, tools, docs | What semver bump should the OpenCode/OpenAgent npm packages use? |
+| `omo codex` | `packages/omo-codex`, `lazycodex-ai`, Codex plugin metadata/hooks, bundled MCP runtimes, `code-yeongyu/lazycodex` marketplace payload | Does LazyCodex need the same bump, a Codex-only note, or a marketplace release? |
+
 ## Steps:
-1. Run `git diff v{published-version}..HEAD` to see actual changes
-2. Group by type (feat/fix/refactor/docs) with REAL descriptions
-3. Note breaking changes if any
-4. Recommend version bump (major/minor/patch)
+1. Detect latest published versions for `oh-my-opencode`, `oh-my-openagent`, and `lazycodex-ai`.
+2. Run `git diff v{published-version}..HEAD` to see actual changes.
+3. Classify every file into one or more release layers before grouping by feat/fix/refactor/docs.
+4. Describe the REAL changes and why each layer cares.
+5. Note breaking changes by affected layer.
+6. Recommend a layer-specific version bump and one overall workflow bump.
 
 ## Output Format:
 - feat: "Added X that does Y" (not just "add X feature")
@@ -31,6 +43,9 @@ For each commit, you MUST:
 <local-version>
 !`node -p "require('./package.json').version" 2>/dev/null || echo "unknown"`
 </local-version>
+<lazycodex-version>
+!`npm view lazycodex-ai version 2>/dev/null || echo "not published"`
+</lazycodex-version>
 <latest-tag>
 !`git tag --sort=-v:refname | head -1 2>/dev/null || echo "no tags"`
 </latest-tag>
@@ -77,7 +92,21 @@ None or list
 ### Files Changed
 {diff-stat}
 
-### Suggested Version Bump
+### Layered Impact Matrix
+| Layer | Impact | Breaking Risk |
+|-------|--------|---------------|
+| omo pure components | ... | ... |
+| omo opencode | ... | ... |
+| omo codex | ... | ... |
+
+### Layer-specific Version Recommendation
+| Layer | Recommendation | Reason |
+|-------|----------------|--------|
+| omo pure components | patch|minor|major | ... |
+| omo opencode | patch|minor|major | ... |
+| omo codex | patch|minor|major | ... |
+
+### Overall Suggested Version Bump
 - **Recommendation**: patch|minor|major
 - **Reason**: Reason for recommendation
 </output-format>

package/.agents/command/omomomo.md

@@ -17,7 +17,7 @@ Print the following message to the user EXACTLY as written (in a friendly, celeb
 
 **Oh My OpenCode** is a powerful OpenCode plugin that transforms your AI agent into a full development team:
 
-- 🤖 **Multi-Agent Orchestration**: Oracle (GPT-5.2), Librarian (Claude), Explore (Grok), Frontend Engineer (Gemini), and more
+- 🤖 **Multi-Agent Orchestration**: Oracle (GPT-5.5), Librarian (Claude), Explore (Grok), Frontend Engineer (Gemini), and more
 - 🔧 **LSP Tools**: Full IDE capabilities for your agents - hover, goto definition, find references, rename, code actions
 - 🔍 **AST-Grep**: Structural code search and replace across 25 languages
 - 📚 **Built-in MCPs**: Context7 for docs, Exa for web search, grep.app for GitHub code search

package/.agents/command/publish.md

@@ -6,6 +6,18 @@ argument-hint: <patch|minor|major>
 <command-instruction>
 You are the release manager for oh-my-opencode. Execute the FULL publish workflow from start to finish.
 
+## CRITICAL: FULL WORKFLOW MEANS THREE RELEASE SURFACES
+
+Publishing is complete only after all release surfaces are verified:
+
+| Release layer | Surface | Required proof |
+|---|---|---|
+| `omo pure components` | Core/MCP/shared-skill changes inside the published package payload | `/get-unpublished-changes` and pre-publish review include layer-specific version impact. |
+| `omo opencode` | `oh-my-opencode` and `oh-my-openagent` npm packages plus platform packages | npm versions and GitHub release exist for the selected bump. |
+| `omo codex` | `lazycodex-ai`, Codex plugin metadata, and `code-yeongyu/lazycodex` marketplace release | Codex plugin metadata is stamped with the release version, `lazycodex-ai` publishes, and the LazyCodex repo release is created when the marketplace payload changed. |
+
+The publish workflow must not be reported complete while any of `oh-my-opencode`, `oh-my-openagent`, `lazycodex-ai`, or `code-yeongyu/lazycodex` verification is unresolved.
+
 ## CRITICAL: ARGUMENT REQUIREMENT
 
 **You MUST receive a version bump type from the user.** Valid options:
@@ -35,6 +47,7 @@ You are the release manager for oh-my-opencode. Execute the FULL publish workflo
   { "id": "draft-summary", "content": "Draft enhanced release summary (mandatory for minor/major, optional for patch — ask user)", "status": "pending", "priority": "high" },
   { "id": "apply-summary", "content": "Prepend enhanced summary to release (if user opted in)", "status": "pending", "priority": "high" },
   { "id": "verify-npm", "content": "Verify npm package published successfully", "status": "pending", "priority": "high" },
+  { "id": "verify-lazycodex", "content": "Verify lazycodex-ai publish, Codex plugin metadata version stamp, and code-yeongyu/lazycodex release/sync", "status": "pending", "priority": "high" },
   { "id": "wait-platform-workflow", "content": "Wait for publish-platform workflow completion", "status": "pending", "priority": "high" },
   { "id": "verify-platform-binaries", "content": "Verify all 7 platform binary packages published", "status": "pending", "priority": "high" },
   { "id": "final-confirmation", "content": "Final confirmation to user with links", "status": "pending", "priority": "low" }

package/.agents/command/security-research.md

@@ -13,4 +13,3 @@ skill(name="security-research")
 <user-request>
 $ARGUMENTS
 </user-request>
-

package/.agents/skills/get-unpublished-changes/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: get-unpublished-changes
-description: "Compare HEAD with the latest published npm version and list all unpublished changes. Triggers: unpublished changes, changelog, what changed, whats new."
+description: "Compare HEAD with the latest published npm versions and list all unpublished changes by release layer. Triggers: unpublished changes, changelog, what changed, whats new."
 ---
 
 IMMEDIATELY output the analysis. NO questions. NO preamble.
@@ -12,13 +12,29 @@ For each commit, you MUST:
 2. Describe the REAL change in plain language
 3. Explain WHY it matters (if not obvious)
 
+## Release Layers
+
+Analyze every change against these exact layers:
+
+| Layer | Includes | Version question |
+|---|---|---|
+| `omo pure components` | `packages/*-core`, MCP packages, `packages/shared-skills`, reusable scripts | Do shared components need a patch/minor/major release note even if adapters only consume them internally? |
+| `omo opencode` | Root `oh-my-opencode` / `oh-my-openagent`, `src/`, `.opencode/`, `.agents/`, CLI, config, hooks, tools, docs | What semver bump should the OpenCode/OpenAgent npm packages use? |
+| `omo codex` | `packages/omo-codex`, `lazycodex-ai`, Codex plugin metadata/hooks, bundled MCP runtimes, `code-yeongyu/lazycodex` marketplace payload | Does LazyCodex need the same bump, a Codex-only note, or a marketplace release? |
+
 ## Steps:
-1. Run `git diff v{published-version}..HEAD` to see actual changes
-2. Group by type (feat/fix/refactor/docs) with REAL descriptions
-3. Note breaking changes if any
-4. Recommend version bump (major/minor/patch)
+1. Detect latest published versions for `oh-my-opencode`, `oh-my-openagent`, and `lazycodex-ai`.
+2. Run `git diff v{published-version}..HEAD` to see actual changes.
+3. Classify every file into one or more release layers before grouping by feat/fix/refactor/docs.
+4. Describe the REAL changes and why each layer cares.
+5. Note breaking changes by affected layer.
+6. Recommend a layer-specific version bump and one overall workflow bump.
 
 ## Output Format:
 - feat: "Added X that does Y" (not just "add X feature")
 - fix: "Fixed bug where X happened, now Y" (not just "fix X bug")
 - refactor: "Changed X from A to B, now supports C" (not just "rename X")
+
+Include:
+- `Layered Impact Matrix`: rows for `omo pure components`, `omo opencode`, `omo codex`
+- `Layer-specific Version Recommendation`: patch/minor/major per layer plus one overall release bump

package/.agents/skills/omomomo/SKILL.md

@@ -17,7 +17,7 @@ Print the following message to the user EXACTLY as written (in a friendly, celeb
 
 **Oh My OpenCode** is a powerful OpenCode plugin that transforms your AI agent into a full development team:
 
-- 🤖 **Multi-Agent Orchestration**: Oracle (GPT-5.2), Librarian (Claude), Explore (Grok), Frontend Engineer (Gemini), and more
+- 🤖 **Multi-Agent Orchestration**: Oracle (GPT-5.5), Librarian (Claude), Explore (Grok), Frontend Engineer (Gemini), and more
 - 🔧 **LSP Tools**: Full IDE capabilities for your agents - hover, goto definition, find references, rename, code actions
 - 🔍 **AST-Grep**: Structural code search and replace across 25 languages
 - 📚 **Built-in MCPs**: Context7 for docs, Exa for web search, grep.app for GitHub code search
@@ -33,4 +33,3 @@ Created with ❤️ by **[code-yeongyu](https://github.com/code-yeongyu)**
 ---
 
 *Enjoy coding on steroids!* 🚀
-

package/.agents/skills/opencode-qa/scripts/export-roundtrip.sh

@@ -16,34 +16,72 @@ SCRIPT_DIR="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"
 . "$SCRIPT_DIR/lib/common.sh"
 
 oqa_export() {
-  # stderr carries the "Exporting session:" banner; drop it for clean JSON.
-  opencode export "$1" 2>/dev/null
+  local id="$1" out
+  out="$(mktemp -t oqa-export.XXXXXX)" || return 1
+  OQA_TMPDIRS+=("$out")
+  oqa_export_to_file "$id" "$out" || return 1
+  oqa_validate_export_file "$id" "$out" || return 1
+  cat "$out"
 }
 
-oqa_self_test() {
-  oqa_require opencode jq || return 1
-  local id out got title msgtype
-  id="$(oqa_db_query "SELECT id FROM session ORDER BY time_created DESC LIMIT 1" | jq -r '.[0].id // empty')"
-  if [ -z "$id" ]; then oqa_log "FAIL: no sessions to export"; return 1; fi
+oqa_extract_json_stdout() {
+  local raw="$1" clean="$2"
+  awk '
+    BEGIN { started = 0 }
+    started { print; next }
+    {
+      pos = index($0, "{")
+      if (pos > 0) {
+        print substr($0, pos)
+        started = 1
+      }
+    }
+  ' "$raw" >"$clean"
+}
+
+oqa_export_to_file() {
+  local id="$1" out="$2" raw
+  if [ -z "$id" ]; then
+    oqa_log "FAIL: missing session id"
+    return 2
+  fi
+  raw="$(mktemp -t oqa-export-raw.XXXXXX)" || return 1
+  OQA_TMPDIRS+=("$raw")
+  opencode export "$id" >"$raw" 2>/dev/null || return 1
+  oqa_extract_json_stdout "$raw" "$out"
+}
 
-  out="$(oqa_export "$id")"
-  # 1) stdout must be valid JSON (stderr banner excluded).
-  if ! printf '%s' "$out" | jq -e . >/dev/null 2>&1; then
-    oqa_log "FAIL: export stdout is not valid JSON for $id"; return 1
+oqa_validate_export_file() {
+  local id="$1" file="$2" got title msgtype
+  if ! jq -e . "$file" >/dev/null 2>&1; then
+    oqa_log "FAIL: export stdout is not valid JSON for $id"
+    return 1
   fi
-  # 2) the info.id must round-trip.
-  got="$(printf '%s' "$out" | jq -r '.info.id // empty')"
+  got="$(jq -r '.info.id // empty' "$file")"
   if [ "$got" != "$id" ]; then
-    oqa_log "FAIL: export .info.id '$got' != '$id'"; return 1
+    oqa_log "FAIL: export .info.id '$got' != '$id'"
+    return 1
   fi
-  # 3) info.title is a string and messages is an array.
-  title="$(printf '%s' "$out" | jq -r '.info.title|type' 2>/dev/null)"
-  msgtype="$(printf '%s' "$out" | jq -r '.messages|type' 2>/dev/null)"
+  title="$(jq -r '.info.title|type' "$file" 2>/dev/null)"
+  msgtype="$(jq -r '.messages|type' "$file" 2>/dev/null)"
   if [ "$title" = "string" ] && { [ "$msgtype" = "array" ] || [ "$msgtype" = "null" ]; }; then
-    oqa_pass "export round-trips $id (info.id matches, valid JSON)"
     return 0
   fi
-  oqa_log "FAIL: unexpected shape (title=$title messages=$msgtype)"; return 1
+  oqa_log "FAIL: unexpected shape (title=$title messages=$msgtype)"
+  return 1
+}
+
+oqa_self_test() {
+  oqa_require opencode jq || return 1
+  local id out
+  id="$(oqa_db_query "SELECT id FROM session ORDER BY time_created DESC LIMIT 1" | jq -r '.[0].id // empty')"
+  if [ -z "$id" ]; then oqa_log "FAIL: no sessions to export"; return 1; fi
+
+  out="$(mktemp -t oqa-export.XXXXXX)" || return 1
+  OQA_TMPDIRS+=("$out")
+  oqa_export_to_file "$id" "$out" || return 1
+  oqa_validate_export_file "$id" "$out" || return 1
+  oqa_pass "export round-trips $id (info.id matches, valid JSON)"
 }
 
 case "${1:-}" in

package/.agents/skills/opencode-qa/scripts/lib/common.sh

@@ -45,8 +45,7 @@ oqa_db_path() {
 
 # Escape a value for safe embedding inside a single-quoted SQL literal.
 oqa_sql_escape() {
-  local s="${1//\'/\'\'}"
-  printf '%s' "$s"
+  printf '%s' "$1" | sed "s/'/''/g"
 }
 
 # Run a read-only SQL query against the active DB; emit JSON rows.
@@ -67,8 +66,10 @@ oqa_mk_isolated_xdg() {
   local root
   root="$(mktemp -d -t oqa-xdg.XXXXXX)" || return 1
   OQA_TMPDIRS+=("$root")
-  mkdir -p "$root/data" "$root/config" "$root/cache" "$root/state" "$root/proj"
+  mkdir -p "$root/data" "$root/config" "$root/cache" "$root/state" "$root/home" "$root/proj"
   export OQA_XDG_ROOT="$root"
+  export HOME="$root/home"
+  export OPENCODE_TEST_HOME="$root/home"
   export XDG_DATA_HOME="$root/data"
   export XDG_CONFIG_HOME="$root/config"
   export XDG_CACHE_HOME="$root/cache"
@@ -123,6 +124,7 @@ oqa_start_server() {
   OPENCODE_SERVER_PASSWORD="$pass" opencode serve --port "$port" --hostname 127.0.0.1 \
     >"$XDG_STATE_HOME/serve.log" 2>&1 &
   OQA_SERVER_PID=$!
+  disown "$OQA_SERVER_PID" 2>/dev/null || true
   export OQA_SERVER_PORT="$port"
   export OQA_SERVER_PASS="$pass"
   export OQA_SERVER_URL="http://127.0.0.1:$port"
@@ -138,7 +140,7 @@ oqa_cleanup() {
   if [ -n "${OQA_SERVER_PID:-}" ]; then
     kill "$OQA_SERVER_PID" 2>/dev/null || true
     sleep 0.3
-    kill -9 "$OQA_SERVER_PID" 2>/dev/null || true
+    kill -0 "$OQA_SERVER_PID" 2>/dev/null && kill -9 "$OQA_SERVER_PID" 2>/dev/null || true
     OQA_SERVER_PID=""
   fi
   local s p d
@@ -147,6 +149,8 @@ oqa_cleanup() {
   done
   for p in "${OQA_CURL_PIDS[@]:-}"; do
     [ -n "$p" ] && kill "$p" 2>/dev/null || true
+    [ -n "$p" ] && sleep 0.1
+    [ -n "$p" ] && kill -0 "$p" 2>/dev/null && kill -9 "$p" 2>/dev/null || true
   done
   for d in "${OQA_TMPDIRS[@]:-}"; do
     [ -n "$d" ] && rm -rf "$d" 2>/dev/null || true
@@ -192,15 +196,23 @@ oqa__self_check() {
   # isolation + trap teardown: an inner shell creates a sandbox (calling the
   # helper DIRECTLY so the cleanup registration survives) and exits; the EXIT
   # trap must remove it. We pass the sandbox path out via a marker file.
-  local marker isodir
+  local marker isodir home test_home
   marker="$(mktemp -t oqa-marker.XXXXXX)"
-  bash -c '. "'"${BASH_SOURCE[0]}"'"; oqa_mk_isolated_xdg; printf "%s" "$OQA_XDG_ROOT" > "'"$marker"'"'
-  isodir="$(cat "$marker" 2>/dev/null)"; rm -f "$marker"
+  bash -c '. "'"${BASH_SOURCE[0]}"'"; oqa_mk_isolated_xdg; printf "%s\n%s\n%s\n" "$OQA_XDG_ROOT" "$HOME" "$OPENCODE_TEST_HOME" > "'"$marker"'"'
+  isodir="$(sed -n '1p' "$marker" 2>/dev/null)"
+  home="$(sed -n '2p' "$marker" 2>/dev/null)"
+  test_home="$(sed -n '3p' "$marker" 2>/dev/null)"
+  rm -f "$marker"
   if [ -n "$isodir" ] && [ ! -d "$isodir" ]; then
     oqa_pass "isolated XDG sandbox auto-removed on exit ($isodir)"
   else
     oqa_log "FAIL: sandbox not cleaned: '$isodir' (exists=$([ -d "$isodir" ] && echo yes || echo no))"; fails=$((fails+1))
   fi
+  if [ -n "$isodir" ] && [ "$home" = "$isodir/home" ] && [ "$test_home" = "$isodir/home" ]; then
+    oqa_pass "isolated HOME points inside sandbox"
+  else
+    oqa_log "FAIL: sandbox HOME not isolated (HOME='$home' OPENCODE_TEST_HOME='$test_home' root='$isodir')"; fails=$((fails+1))
+  fi
 
   if [ "$fails" -eq 0 ]; then
     oqa_pass "common.sh self-check"

package/.agents/skills/opencode-qa/scripts/sse-hook-probe.sh

@@ -47,6 +47,7 @@ oqa_sse_watch() {
     curl -sN "$url/event?directory=$dir" >"$out" 2>/dev/null &
   fi
   cpid=$!; OQA_CURL_PIDS+=("$cpid")
+  disown "$cpid" 2>/dev/null || true
   deadline=$(( $(date +%s) + timeout ))
   while [ "$(date +%s)" -lt "$deadline" ]; do
     if grep -q "\"$want\"" "$out" 2>/dev/null; then found=1; break; fi
@@ -54,6 +55,8 @@ oqa_sse_watch() {
     sleep 0.2
   done
   kill "$cpid" 2>/dev/null || true
+  sleep 0.1
+  kill -0 "$cpid" 2>/dev/null && kill -9 "$cpid" 2>/dev/null || true
   if [ -n "$found" ]; then
     printf 'first matching event: '
     grep -m1 "\"$want\"" "$out" | sed 's/^data: //' | jq -c '{type: .type}' 2>/dev/null || true

package/.agents/skills/opencode-qa/scripts/tui-smoke.sh

@@ -34,7 +34,7 @@ oqa_tui_smoke() {
   tmux new-session -d -s "$sess" -x 200 -y 50
   # launch the TUI inside the pane, carrying the isolated sandbox env
   tmux send-keys -t "$sess" \
-    "XDG_DATA_HOME='$XDG_DATA_HOME' XDG_CONFIG_HOME='$XDG_CONFIG_HOME' XDG_CACHE_HOME='$XDG_CACHE_HOME' XDG_STATE_HOME='$XDG_STATE_HOME' OPENCODE_DISABLE_AUTOUPDATE=1 OPENCODE_DISABLE_MODELS_FETCH=1 opencode '$OQA_PROJ'" Enter
+    "HOME='$HOME' OPENCODE_TEST_HOME='$OPENCODE_TEST_HOME' XDG_DATA_HOME='$XDG_DATA_HOME' XDG_CONFIG_HOME='$XDG_CONFIG_HOME' XDG_CACHE_HOME='$XDG_CACHE_HOME' XDG_STATE_HOME='$XDG_STATE_HOME' OPENCODE_DISABLE_AUTOUPDATE=1 OPENCODE_DISABLE_MODELS_FETCH=1 opencode '$OQA_PROJ'" Enter
 
   # poll for a render marker (version string, composer placeholder, or footer)
   for ((i=0; i<50; i++)); do

package/.agents/skills/pre-publish-review/SKILL.md

@@ -5,7 +5,7 @@ description: "Nuclear-grade 16-agent pre-publish release gate. Runs /get-unpubli
 
 # Pre-Publish Review — 16-Agent Release Gate
 
-Three-layer review before publishing to npm. Every layer covers a different angle — together they catch what no single reviewer could.
+Three-agent-layer review before publishing to npm. Every layer covers a different angle, and every result is mapped onto the release layers below.
 
 | Layer | Agents | Type | What They Check |
 |-------|--------|------|-----------------|
@@ -13,11 +13,21 @@ Three-layer review before publishing to npm. Every layer covers a different angl
 | Holistic Review | 5 | review-work | Goal compliance, QA execution, code quality, security, context mining across full changeset |
 | Release Synthesis | 1 | oracle | Overall release readiness, version bump, breaking changes, deployment risk |
 
+## Release Layer Taxonomy
+
+Every phase classifies evidence and risk across:
+
+| Release Layer | Scope | Required version decision |
+|---|---|---|
+| `omo pure components` | Core packages, MCP packages, shared skills, reusable scripts, platform binary inputs | Patch/minor/major impact for shared logic consumed by adapters. |
+| `omo opencode` | Root `oh-my-opencode` / `oh-my-openagent`, `src/`, OpenCode plugin hooks/tools/CLI/config/docs, `.opencode/`, `.agents/` | Semver bump for the OpenCode/OpenAgent npm release. |
+| `omo codex` | `packages/omo-codex`, `lazycodex-ai`, Codex plugin metadata/hooks, bundled MCP runtimes, `code-yeongyu/lazycodex` marketplace payload | Codex adapter bump, LazyCodex npm publish risk, and marketplace/GitHub release need. |
+
 ---
 
 ## Phase 0: Detect Unpublished Changes
 
-Run `/get-unpublished-changes` FIRST. This is the single source of truth for what changed.
+Run `/get-unpublished-changes` FIRST. This is the single source of truth for what changed and must include `omo pure components`, `omo opencode`, and `omo codex` layer-specific version recommendations.
 
 ```
 skill(name="get-unpublished-changes")
@@ -29,7 +39,7 @@ This command automatically:
 - Reads actual diffs (not just commit messages) to describe REAL changes
 - Groups changes by type (feat/fix/refactor/docs) with scope
 - Identifies breaking changes
-- Recommends version bump (patch/minor/major)
+- Recommends a layer-specific version bump plus one overall workflow bump
 
 **Save the full output** — it feeds directly into Phase 1 grouping and all agent prompts.
 
@@ -61,6 +71,7 @@ Use the `/get-unpublished-changes` output as the starting point — it already g
 3. Target **up to 10 groups**. If fewer than 10 commits, each commit is its own group. If more than 10 logical areas, merge the smallest groups.
 4. For each group, extract:
    - **Group name**: Short descriptive label (e.g., "agent-model-resolution", "hook-system-refactor")
+   - **Release layer(s)**: `omo pure components`, `omo opencode`, `omo codex`
    - **Commits**: List of commit hashes and messages
    - **Files**: Changed files in this group
    - **Diff**: The relevant portion of the full diff (`git diff v${PUBLISHED}..HEAD -- {group files}`)
@@ -224,7 +235,7 @@ SYNTHESIS CHECKLIST:
    - PATCH: Bug fixes only, no behavior changes
    - MINOR: New features, backward-compatible changes
    - MAJOR: Breaking changes to public API, config format, or behavior
-   Recommend the correct bump with specific justification.
+   Recommend the correct bump for each release layer and the overall workflow with specific justification.
 
 3. **Breaking Changes Audit**: Exhaustively list every change that could break existing users. Check:
    - Config schema changes (new required fields, removed fields, renamed fields)
@@ -256,6 +267,7 @@ SYNTHESIS CHECKLIST:
 OUTPUT FORMAT:
 <verdict>SAFE / CAUTION / RISKY / BLOCK</verdict>
 <recommended_version_bump>PATCH / MINOR / MAJOR</recommended_version_bump>
+<layer_specific_version_bump>omo pure components: PATCH/MINOR/MAJOR; omo opencode: PATCH/MINOR/MAJOR; omo codex: PATCH/MINOR/MAJOR</layer_specific_version_bump>
 <version_bump_justification>Why this bump level</version_bump_justification>
 <release_coherence>Assessment of whether changes belong in one release</release_coherence>
 <breaking_changes>
@@ -337,6 +349,14 @@ Compile the final report:
 ## Recommended Version Bump: PATCH / MINOR / MAJOR
 {Justification from Oracle}
 
+## Layer-specific Version Recommendation
+
+| Layer | Recommendation | Reason |
+|---|---|---|
+| omo pure components | PATCH/MINOR/MAJOR | ... |
+| omo opencode | PATCH/MINOR/MAJOR | ... |
+| omo codex | PATCH/MINOR/MAJOR | ... |
+
 ---
 
 ## Per-Change Analysis (Ultrabrains)

package/.agents/skills/publish/SKILL.md

@@ -5,6 +5,18 @@ description: "Publish oh-my-opencode to npm via GitHub Actions workflow. Argumen
 
 You are the release manager for oh-my-opencode. Execute the FULL publish workflow from start to finish.
 
+## CRITICAL: FULL WORKFLOW MEANS THREE RELEASE SURFACES
+
+Publishing is complete only after all release surfaces are verified:
+
+| Release layer | Surface | Required proof |
+|---|---|---|
+| `omo pure components` | Core/MCP/shared-skill changes inside the published package payload | `/get-unpublished-changes` and pre-publish review include layer-specific version impact. |
+| `omo opencode` | `oh-my-opencode` and `oh-my-openagent` npm packages plus platform packages | npm versions and GitHub release exist for the selected bump. |
+| `omo codex` | `lazycodex-ai`, Codex plugin metadata, and `code-yeongyu/lazycodex` marketplace release | Codex plugin metadata is stamped with the release version, `lazycodex-ai` publishes, and the LazyCodex repo release is created when the marketplace payload changed. |
+
+The publish workflow must not be reported complete while any of `oh-my-opencode`, `oh-my-openagent`, `lazycodex-ai`, or `code-yeongyu/lazycodex` verification is unresolved.
+
 ## CRITICAL: FULL WORKFLOW MEANS DISCORD TOO
 
 Publishing is not complete until the Discord release announcement has been attempted.
@@ -45,6 +57,7 @@ Publishing is not complete until the Discord release announcement has been attem
   { "id": "apply-summary", "content": "Prepend enhanced summary to release", "status": "pending", "priority": "high" },
   { "id": "discord-announce", "content": "MANDATORY: post release announcement to Discord channel immediately after release notes are finalized", "status": "pending", "priority": "high" },
   { "id": "verify-npm", "content": "Verify npm package published successfully", "status": "pending", "priority": "high" },
+  { "id": "verify-lazycodex", "content": "Verify lazycodex-ai publish, Codex plugin metadata version stamp, and code-yeongyu/lazycodex release/sync", "status": "pending", "priority": "high" },
   { "id": "wait-platform-workflow", "content": "Wait for publish-platform workflow completion", "status": "pending", "priority": "high" },
   { "id": "verify-platform-binaries", "content": "Verify all 7 platform binary packages published", "status": "pending", "priority": "high" },
   { "id": "final-confirmation", "content": "Final confirmation to user with links", "status": "pending", "priority": "low" }

package/.agents/skills/remove-deadcode/SKILL.md

@@ -213,4 +213,3 @@ If `$ARGUMENTS` is provided, narrow the scan:
 STOP and report if:
 - More than 50 candidates found (ask user to narrow scope or confirm proceeding)
 - Build breaks and cannot be fixed by reverting
-

package/.agents/skills/security-research/SKILL.md

@@ -201,4 +201,3 @@ For each finding:
 - Do not claim CVSS precision unless you actually scored the metrics.
 - Include exact file paths and commands for every surviving finding.
 - If no findings survive PoC, say that plainly and list residual risk.
-

package/.agents/skills/work-with-pr-workspace/iteration-1/eval-3/with_skill/outputs/code-changes.md

@@ -8,7 +8,7 @@ import type { CategoryConfig } from "../../config/schema"
 export const DEFAULT_CATEGORIES: Record<string, CategoryConfig> = {
   "visual-engineering": { model: "google/gemini-3.1-pro", variant: "high" },
   ultrabrain: { model: "openai/gpt-5.4", variant: "xhigh" },
-  deep: { model: "openai/gpt-5.3-codex", variant: "medium" },
+  deep: { model: "openai/gpt-5.5-codex", variant: "medium" },
   artistry: { model: "google/gemini-3.1-pro", variant: "high" },
   quick: { model: "anthropic/claude-haiku-4-5" },
   "unspecified-low": { model: "anthropic/claude-sonnet-4-6" },

package/.agents/skills/work-with-pr-workspace/iteration-1/eval-3/without_skill/outputs/code-changes.md

@@ -8,7 +8,7 @@ import type { CategoryConfig } from "../../config/schema"
 export const DEFAULT_CATEGORIES: Record<string, CategoryConfig> = {
   "visual-engineering": { model: "google/gemini-3.1-pro", variant: "high" },
   ultrabrain: { model: "openai/gpt-5.4", variant: "xhigh" },
-  deep: { model: "openai/gpt-5.3-codex", variant: "medium" },
+  deep: { model: "openai/gpt-5.5-codex", variant: "medium" },
   artistry: { model: "google/gemini-3.1-pro", variant: "high" },
   quick: { model: "anthropic/claude-haiku-4-5" },
   "unspecified-low": { model: "anthropic/claude-sonnet-4-6" },
@@ -267,7 +267,7 @@ export const CATEGORY_MODEL_REQUIREMENTS: Record<string, ModelRequirement> = {
     fallbackChain: [
       // ... full content from original
     ],
-    requiresModel: "gpt-5.3-codex",
+    requiresModel: "gpt-5.5-codex",
   },
   artistry: {
     fallbackChain: [