publishlisted

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. - **DO NOT stop after creating the GitHub release.** - **DO NOT stop after drafting or applying release notes.** - **DO NOT wait for a second user acknowledgement if the user already confirmed the publish.** - After the release notes are finalized, immediately run Step 7.5 and post