docs(omo-codex): clarify sisyphuslabs marketplace install

docs/reference/cli.md

@@ -68,7 +68,9 @@ bunx oh-my-openagent install
 | `--vercel-ai-gateway <value>` | Vercel AI Gateway: `no`, `yes` (Ultimate only) |
 | `--skip-auth` | Skip authentication setup hints |
 
-When using the `lazycodex` bin alias, `install` defaults to `--platform=codex`. Subscription flags (`--claude`, `--openai`, etc.) only apply when `--platform` is `opencode` or `both` — they are rejected under `--platform=codex` because the Light edition does not write OpenCode model config.
+When using the `lazycodex` bin alias, `install` defaults to `--platform=codex`. `lazycodex` is only the npm/bin alias and marketplace repository name. The Codex config uses marketplace `sisyphuslabs` and plugin `omo`, enabled as `omo@sisyphuslabs`, with the marketplace source set to `https://github.com/code-yeongyu/lazycodex.git`.
+
+Subscription flags (`--claude`, `--openai`, etc.) only apply when `--platform` is `opencode` or `both`. They are rejected under `--platform=codex` because the Light edition does not write OpenCode model config.
 
 ### Telemetry and opt-out
 

docs/reference/lazycodex-npm-reservation.md

@@ -1,5 +1,7 @@
 # Reserving the lazycodex npm name (first-publish playbook)
 
+`lazycodex` is the npm/bin alias for the Codex CLI Light edition and the Git repository that hosts the native Codex marketplace bundle. It is not the marketplace identity. Codex installs marketplace `sisyphuslabs` and plugin `omo`, enabled as `omo@sisyphuslabs`.
+
 The `publish.yml` workflow includes `lazycodex` in trusted-publisher preflight, but that check is soft for first publish.
 If `lazycodex` is not yet claimed on npm, the workflow warns and continues so existing package releases are not blocked.
 To claim the name, run a one-time manual `npm publish` for `lazycodex` from a trusted environment (for example local shell with `NPM_AUTH_TOKEN`).
@@ -7,3 +9,5 @@ After the first manual publish, configure GitHub Actions trusted publishing at:
 https://www.npmjs.com/package/lazycodex/access
 Set Provider to GitHub Actions, Organization to `code-yeongyu`, Repository to `oh-my-openagent`, and Workflow filename to `publish.yml`.
 After this setup, subsequent releases from `publish.yml` can publish `lazycodex` automatically.
+
+The same release workflow also syncs `packages/omo-codex/marketplace.json` and `packages/omo-codex/plugin/` into `code-yeongyu/lazycodex` as `.agents/plugins/marketplace.json` and `plugins/omo/`. That cross-repo push requires the `LAZYCODEX_SYNC_TOKEN` repository secret.

docs/reference/rules-injection-cross-module-comparison.md

@@ -3,7 +3,7 @@
 Comparison and porting record for the three rule injection implementations
 maintained out of `/Users/yeongyu/local-workspaces`:
 
-- **codex-rules** — Codex hook plugin (`codex-plugins/plugins/codex-rules`, repo `code-yeongyu/codex-rules`, branch `main`).
+- **codex-rules** — Codex hook plugin now bundled under the OMO Codex marketplace plugin (`packages/omo-codex/plugin/components/rules`, marketplace `sisyphuslabs`, plugin `omo`). The original standalone repo was `code-yeongyu/codex-rules`, branch `main`.
 - **pi-rules** — pi-mono extension (`pi-extensions/pi-rules`, repo `code-yeongyu/pi-rules`, branch `main`).
 - **omo rules-injector** — opencode plugin path (`omo/src/hooks/rules-injector`, repo `code-yeongyu/oh-my-openagent`, branch `dev`).
 
@@ -18,7 +18,7 @@ maintained out of `/Users/yeongyu/local-workspaces`:
 Installation state after the porting round:
 
 - **omo** — `~/.bun/install/global/node_modules/oh-my-opencode` is a symlink to the local workspace, so `bun run build` immediately publishes the rebuilt `dist/`. Verified via `grep -c transcriptHydration dist/index.js` → 6.
-- **codex-rules** — `node scripts/install-local.mjs ...` was rerun and the cache at `~/.codex/plugins/cache/code-yeongyu-codex-plugins/codex-rules/0.1.0` was refreshed.
+- **codex-rules** — now installed through the aggregate OMO Codex plugin cache at `~/.codex/plugins/cache/sisyphuslabs/omo/<version>/components/rules`, enabled by `[plugins."omo@sisyphuslabs"]`.
 - **pi-rules** — pi-mono consumes the package source directly; no separate install step.
 
 ## 1. Performance baseline