chore: rename npm package opencodex → opencx

opencodex can't be published (npm rejects it as too similar to the existing open-codex) and ocx is already taken, so publish as opencx. Renames only the npm-package identity: package.json name, all -g install commands (README x3, docs x3 langs), the ocx update self-update target (src/update.ts PKG), the release.yml npm-view smoke, and bun.lock root name. Product brand (opencodex GUI/prose, ~/.opencodex config dir, lidge-jun/opencodex repo) and the ocx/opencodex bin commands are unchanged. Also fixes a stale NPM_TOKEN note in scripts/release.ts (we publish via Trusted Publishing/OIDC now).

Verified: tsc clean, npm pack --dry-run -> opencx-0.1.0.tgz (55 files).

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

Author: lidge-jun

.github/workflows/release.yml

@@ -90,4 +90,4 @@ jobs:
         if: ${{ inputs.dry-run != true }}
         run: |
           sleep 10
-          npm view "opencodex@${{ inputs.version }}" version dist-tags
+          npm view "opencx@${{ inputs.version }}" version dist-tags

README.ko.md

@@ -34,7 +34,7 @@ Codex CLI / App / SDK ──/v1/responses──▶ opencodex ──▶ Any provi
 
 ```bash
 # Install
-bun install -g opencodex      # or: npm install -g opencodex
+bun install -g opencx      # or: npm install -g opencx
 
 # Interactive setup (writes config + injects into Codex)
 ocx init
@@ -59,7 +59,7 @@ curl -fsSL https://bun.sh/install | bash
 powershell -c "irm bun.sh/install.ps1 | iex"
 ```
 
-설치 후 `bun install -g opencodex`를 다시 실행하세요. (`ocx` 바이너리는 bun 기반이라 bun이 `PATH`에 있어야 합니다.)
+설치 후 `bun install -g opencx`를 다시 실행하세요. (`ocx` 바이너리는 bun 기반이라 bun이 `PATH`에 있어야 합니다.)
 
 </details>
 

README.md

@@ -34,7 +34,7 @@ Codex CLI / App / SDK ──/v1/responses──▶ opencodex ──▶ Any provi
 
 ```bash
 # Install
-bun install -g opencodex      # or: npm install -g opencodex
+bun install -g opencx      # or: npm install -g opencx
 
 # Interactive setup (writes config + injects into Codex)
 ocx init
@@ -59,7 +59,7 @@ curl -fsSL https://bun.sh/install | bash
 powershell -c "irm bun.sh/install.ps1 | iex"
 ```
 
-Then re-run `bun install -g opencodex`. (The `ocx` binary is bun-native, so bun must be on your `PATH`.)
+Then re-run `bun install -g opencx`. (The `ocx` binary is bun-native, so bun must be on your `PATH`.)
 
 </details>
 

README.zh-CN.md

@@ -34,7 +34,7 @@ Codex CLI / App / SDK ──/v1/responses──▶ opencodex ──▶ Any provi
 
 ```bash
 # Install
-bun install -g opencodex      # or: npm install -g opencodex
+bun install -g opencx      # or: npm install -g opencx
 
 # Interactive setup (writes config + injects into Codex)
 ocx init
@@ -59,7 +59,7 @@ curl -fsSL https://bun.sh/install | bash
 powershell -c "irm bun.sh/install.ps1 | iex"
 ```
 
-然后重新运行 `bun install -g opencodex`。（`ocx` 可执行文件是 bun 原生的，因此 bun 必须在你的 `PATH` 中。）
+然后重新运行 `bun install -g opencx`。（`ocx` 可执行文件是 bun 原生的，因此 bun 必须在你的 `PATH` 中。）
 
 </details>
 

bun.lock

@@ -18,10 +18,10 @@ sends your traffic anywhere except the provider you configure.
 
 ```bash
 # With Bun (recommended)
-bun install -g opencodex
+bun install -g opencx
 
 # With npm
-npm install -g opencodex
+npm install -g opencx
 ```
 
 Verify the binary is on your `PATH`:

docs-site/src/content/docs/getting-started/installation.md

@@ -57,7 +57,7 @@ Codex CLI / App / SDK ──/v1/responses──▶ opencodex ──▶ Any provi
 
 ```bash
 # Install
-bun install -g opencodex      # or: npm install -g opencodex
+bun install -g opencx      # or: npm install -g opencx
 
 # Interactive setup (writes config + injects into Codex)
 ocx init

docs-site/src/content/docs/index.mdx

@@ -18,10 +18,10 @@ opencodex는 단일 CLI인 `ocx`로 제공됩니다. 작은 로컬 HTTP 서버(B
 
 ```bash
 # With Bun (recommended)
-bun install -g opencodex
+bun install -g opencx
 
 # With npm
-npm install -g opencodex
+npm install -g opencx
 ```
 
 바이너리가 `PATH`에 있는지 확인합니다:

docs-site/src/content/docs/ko/getting-started/installation.md

@@ -55,7 +55,7 @@ Codex CLI / App / SDK ──/v1/responses──▶ opencodex ──▶ Any provi
 
 ```bash
 # Install
-bun install -g opencodex      # or: npm install -g opencodex
+bun install -g opencx      # or: npm install -g opencx
 
 # Interactive setup (writes config + injects into Codex)
 ocx init

docs-site/src/content/docs/ko/index.mdx

@@ -93,7 +93,7 @@ ocx service uninstall
 ### `ocx update`
 
 Self-update opencodex to the latest version published on npm, using the package manager it was
-installed with (`bun add -g opencodex@latest` or `npm install -g opencodex@latest`). It detects a
+installed with (`bun add -g opencx@latest` or `npm install -g opencx@latest`). It detects a
 source checkout and tells you to `git pull && bun install` instead, and is a no-op if you're already
 on the newest version. Restart the proxy afterward (`ocx stop && ocx start`) to run the new build.