chore: scope package name to avoid npm registry collision

Unscoped name codex-app-server-bridge collides with an unrelated
public package (w-okada/codex-app-server-bridge on npm), causing
`npm outdated -g` to compare this local install against a stranger's
releases.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>

package-lock.json

@@ -1,11 +1,11 @@
 {
-  "name": "codex-app-server-bridge",
+  "name": "@bodicsek/codex-app-server-bridge",
   "version": "0.1.1",
   "lockfileVersion": 3,
   "requires": true,
   "packages": {
     "": {
-      "name": "codex-app-server-bridge",
+      "name": "@bodicsek/codex-app-server-bridge",
       "version": "0.1.1",
       "bin": {
         "codex-app-server-bridge": "bin/codex-app-server-bridge.js"

package.json

@@ -1,5 +1,5 @@
 {
-  "name": "codex-app-server-bridge",
+  "name": "@bodicsek/codex-app-server-bridge",
   "version": "0.1.1",
   "description": "Bridge codex-acp stdio JSONL to an existing loopback Codex App Server WebSocket.",
   "private": true,