fix(setup): decouple OpenClaw config patch from being mandatory

OCP markets itself as a standalone OpenAI-compatible proxy with six
supported IDE clients (Cline / Cursor / Continue.dev / OpenCode / Aider /
OpenClaw). The README §Server Setup says "node setup.mjs" is the
installer entrypoint. But on a truly fresh box without OpenClaw
installed, setup.mjs hard-fails at line 111:

    if (!existsSync(CONFIG_PATH)) fail(`OpenClaw config not found...`);

This contradicts the standalone-proxy stance and was caught during
PR #71 dogfood testing on Pi231.

Root cause: the OpenClaw config patch (lines 110-148) was baked in as
required because OCP started life as an OpenClaw-internal helper. The
project has since rebranded to standalone OCP without decoupling the
installer.

Fix: gate the OpenClaw config patch (Step 2) and auth-profiles patch
(Step 3) on existsSync(CONFIG_PATH). When OpenClaw is present, behavior
is byte-for-byte identical to current main (verified via dry-run hash
diff against ~/.openclaw/openclaw.json — UNCHANGED). When OpenClaw is
absent, the installer logs a graceful warning, skips both patch
sections, and continues to start.sh / launchd-plist / systemd-unit
creation as before. The summary banner is also conditional: when
OpenClaw is absent, it points the user at README § "Client Setup"
instead of giving openclaw.json edit instructions.

Also moves `import { readdirSync }` from mid-file (line 178, post-use)
to the top-level imports block; this was a latent ESM-hoisting quirk
that worked but is now syntactically required at the top because the
readdirSync call moved inside an `if` block.

Out of scope (Iron Rule 11, single-layer PR): server.mjs, models.json,
scripts/sync-openclaw.mjs, README.md, ALIGNMENT.md, package.json
version, the duplicate-spawn / health-verify logic at line 268+ (that's
a separate fix/setup-spawn-conflict PR).

Mac mini production unaffected: ~/.openclaw/openclaw.json already
exists there, so the OpenClaw-present path is preserved. `ocp update`
doesn't invoke setup.mjs, so running services are not touched.

Smoke-tested locally:
- Path 1 (OpenClaw present): dry-run output functionally identical to
  current main; config sha256 unchanged after run.
- Path 2 (OpenClaw absent, OPENCLAW_STATE_DIR=/tmp/no-such-dir-*):
  graceful warn, both patch sections skipped, banner shows
  standalone-mode message, dry-run completes successfully.
- npm test: 43/43 pass.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

README.md

@@ -6,8 +6,6 @@
 
 *Open source from day one, used daily by my family, maintained on nights and weekends. If OCP saves you money too, you can [☕ buy me a coffee](https://buymeacoffee.com/dtzp555) — [full story below](#support-ocp).*
 
-*If OCP saves you a setup, a ⭐ helps other folks discover it. Issue reports are even more useful — that's the highest-quality feedback this project gets.*
-
 OCP turns your Claude Pro/Max subscription into a standard OpenAI-compatible API on localhost. Any tool that speaks the OpenAI protocol can use it — no separate API key, no extra billing.
 
 ```
@@ -85,96 +83,13 @@ OCP has two roles: **Server** (runs the proxy, needs Claude CLI) and **Client**
 
 ---
 
-### Quick install with AI assistance
-
-If you've got Claude Code, Cursor, or any other AI coding assistant on this machine, you can copy-paste one of these prompts and let the AI walk through the install for you. Each prompt pins the AI to the right README section, names the verification step, and forbids silent retries — so you stay in the loop.
-
-**Single-machine use** — install OCP for IDEs on this same machine only:
-
-```text
-I want to install OCP on this machine to use my Claude Pro/Max subscription
-as an OpenAI-compatible API for local IDEs.
-
-Please follow https://github.com/dtzp555-max/ocp/blob/main/README.md
-"Server Setup" → "Single-machine use" path:
-
-1. Verify prerequisites: macOS or Linux, Node.js 22.5+, git, Claude CLI
-   installed and logged in (`claude auth status`). Install missing pieces
-   using my system's package manager.
-2. git clone the repo, cd in, and run `node setup.mjs`.
-3. Verify with `curl http://127.0.0.1:3456/v1/models` (should list 4 models).
-4. Add `export OPENAI_BASE_URL=http://127.0.0.1:3456/v1` to my shell rc.
-5. Tell me to reload my shell and try a tool like Cline / Continue / Cursor.
-
-Before each step, tell me what you'll run and wait for confirmation.
-On any error, diagnose first — don't auto-retry.
-```
-
-**LAN mode (server)** — install OCP as a server so your family or multiple devices can share it:
-
-```text
-I want to install OCP on this device as a LAN server so my family and other
-devices on the network can share my Claude Pro/Max subscription.
-
-Please follow https://github.com/dtzp555-max/ocp/blob/main/README.md
-"Server Setup" → "LAN mode" path:
-
-1. Verify prerequisites: macOS or Linux (Windows not supported), Node.js
-   22.5+, git, Claude CLI installed and authenticated.
-2. Generate a strong admin key with `openssl rand -base64 32`. Save it —
-   I'll need it to manage per-user keys later.
-3. git clone https://github.com/dtzp555-max/ocp.git && cd ocp
-4. Run `node setup.mjs --bind 0.0.0.0 --auth-mode multi`.
-5. Add OCP_ADMIN_KEY to my shell rc (~/.zshrc or ~/.bashrc).
-6. Run `ocp lan` to show me the LAN IP and connect command.
-7. Optionally create example keys: `ocp keys add laptop`, `ocp keys add tablet`.
-8. Verify: `curl http://127.0.0.1:3456/v1/models` returns 4 models.
-
-Tell me each step before running it. On error, diagnose before retrying.
-```
-
-**Client connect** — configure this device to use an existing OCP server on your LAN:
-
-```text
-There's an OCP server at <SERVER_IP> on my LAN. Configure this machine to
-use it for any local IDEs (Cursor, Cline, Continue.dev, OpenCode, Claude
-Code, OpenClaw).
-
-Server IP: <SERVER_IP>
-API key (leave blank if the server has anonymous mode enabled): <OPTIONAL_KEY>
-
-Please follow https://github.com/dtzp555-max/ocp/blob/main/README.md
-"Client Setup" path:
-
-1. Download ocp-connect:
-     curl -fsSL https://raw.githubusercontent.com/dtzp555-max/ocp/main/ocp-connect -o ocp-connect
-     chmod +x ocp-connect
-2. Run `./ocp-connect <SERVER_IP>` (add `--key <KEY>` if you have one).
-3. Follow any IDE-specific manual hints it prints.
-4. Verify: `curl http://<SERVER_IP>:3456/v1/models` returns 4 models.
-5. Tell me to reload my shell + restart any IDE that was already running.
-
-Don't auto-retry on error. Tell me the failure mode first.
-```
-
-> If you'd rather do everything manually, the **Server Setup** and **Client Setup** sections below have the same steps in handbook form.
-
----
-
 ### Server Setup
 
 > **Recommended:** Install OCP on a device that stays powered on — Mac mini, NAS, Raspberry Pi, or a desktop that doesn't sleep. This ensures all clients always have access.
 
 **Prerequisites:**
-- macOS or Linux (Windows is not supported — `setup.mjs` installs launchd / systemd auto-start)
 - Node.js 22.5+ (Node 23+ recommended — `node:sqlite` is fully stable without flags from 23.0; on 22.5–22.x it works behind `--experimental-sqlite`)
-- `git`
+- [Claude CLI](https://docs.anthropic.com/en/docs/claude-cli) installed and authenticated (`claude auth login`)
-- [Claude CLI](https://docs.anthropic.com/en/docs/claude-cli) — install and authenticate:
-  ```bash
-  npm install -g @anthropic-ai/claude-code
-  claude auth login   # prints a URL + code — open URL on any browser, sign in, paste code back
-  ```
-  Headless servers (Pi / NAS / VPS without a desktop browser): see [Headless install notes](#headless-install-notes) below.
 
 ```bash
 # 1. Clone and run setup
@@ -187,8 +102,7 @@ The setup script will:
 1. Verify Claude CLI is installed and authenticated
 2. Start the proxy on port 3456
 3. Install auto-start (launchd on macOS, systemd on Linux)
-
+4. Symlink `ocp` to `/usr/local/bin` for CLI access
-After install the `ocp` CLI lives at `~/ocp/ocp`. To put it on your PATH, either symlink it manually (`ln -sf ~/ocp/ocp ~/.local/bin/ocp` if `~/.local/bin` is on your PATH, or `sudo ln -sf ~/ocp/ocp /usr/local/bin/ocp` for a system-wide symlink) or add an alias (`alias ocp=~/ocp/ocp`). Otherwise invoke it as `~/ocp/ocp <subcommand>`. The rest of this README assumes `ocp` is on your PATH.
 
 **Single-machine use** — just set your IDE to use the proxy:
 ```bash
@@ -203,9 +117,7 @@ node setup.mjs --bind 0.0.0.0 --auth-mode multi
 
 Then create API keys for each person/device:
 ```bash
-# Generate a strong admin key (one-time — save it for later key management):
+export OCP_ADMIN_KEY=your-secret-admin-key
-export OCP_ADMIN_KEY=$(openssl rand -base64 32)
-# Add the same export line to ~/.zshrc or ~/.bashrc so it persists.
 
 ocp keys add wife-laptop
 #  ✓ Key created for "wife-laptop"
@@ -224,22 +136,6 @@ curl http://127.0.0.1:3456/v1/models
 # Returns: claude-opus-4-7, claude-opus-4-6, claude-sonnet-4-6, claude-haiku-4-5-20251001
 ```
 
-#### Headless install notes
-
-OCP is designed for always-on devices that often don't have a desktop browser — Mac mini, NAS, Raspberry Pi, cloud VPS. The Claude CLI auth flow still works headless:
-
-**Option 1 — interactive OAuth over SSH (one-shot).** `claude auth login` prints a URL + 8-digit code. Open the URL on **any** device with a browser (your laptop, phone), sign in to your Anthropic account, and paste the code back into the SSH session. No browser needed on the server itself.
-
-**Option 2 — long-lived token (auth once, no re-prompts).**
-
-```bash
-claude setup-token   # subscription-backed long-lived token
-```
-
-Same Claude subscription as Option 1; the token is stored in Claude CLI's normal config location. Useful when you'd rather not redo the OAuth flow when sessions expire.
-
-If `claude auth login` errors out with something like `cannot open browser`, you've hit the same case — fall back to either option above.
-
 ---
 
 ### Uninstall
@@ -256,8 +152,6 @@ Removes the launchd (macOS) or systemd (Linux) auto-start entry. Handles both le
 ### Client Setup
 
 > Clients do **not** need to install Node.js, Claude CLI, or the OCP repo. Only `curl` and `python3` are required (pre-installed on most Linux/Mac systems).
->
-> **Find the server's LAN IP** by running `ocp lan` on the server machine — it prints both the IP and a ready-to-share connect command.
 
 **One-command setup** — download the lightweight `ocp-connect` script:
 
@@ -398,15 +292,11 @@ In `multi` mode, the admin can designate a single well-known "anonymous" key tha
 
 **Enable**:
 
-The anonymous key is wired into the service unit (launchd plist on macOS, systemd unit on Linux) at install time. Export `PROXY_ANONYMOUS_KEY` in your shell before running `setup.mjs`, and `setup.mjs` will write it into the service unit env so the auto-started proxy picks it up:
-
 ```bash
 export PROXY_ANONYMOUS_KEY=ocp_public_anon   # or any string of your choice
-node setup.mjs --bind 0.0.0.0 --auth-mode multi
+ocp start                                    # or however you start the server
 ```
 
-If OCP is already installed without it, re-export the env var and re-run `node setup.mjs` (the installer is idempotent — it refreshes the service unit). Then `ocp restart` so the running proxy picks up the new env. Setting `PROXY_ANONYMOUS_KEY` only in your interactive shell **does not** affect the auto-started proxy — the service unit is the source of truth for its environment.
-
 **Client side**: the anonymous key value is exposed via `GET /health` as the field `anonymousKey` (null when not set). Clients like `ocp-connect` can auto-discover and use it, so the end user doesn't need to get a personal key from the admin.
 
 **Security note**: setting this env var is an **opt-in** to public access — anyone who can reach your OCP endpoint can use it, up to any rate limits you configure. Don't enable this on internet-exposed OCP instances without additional protection.
@@ -707,37 +597,6 @@ After installing the gateway plugin, use `/ocp` slash commands in your chat:
 
 ## Troubleshooting
 
-### Setup fails with "claude: command not found"
-
-`setup.mjs` requires the Claude CLI to be on `PATH`. Install it via the [official guide](https://docs.anthropic.com/en/docs/claude-cli), confirm with `which claude`, then run `claude auth login` before re-running `node setup.mjs`.
-
-### Setup fails with "EADDRINUSE: port 3456 already in use"
-
-Something else is already bound to port 3456 — usually an old OCP instance. Check what:
-
-```bash
-lsof -nP -iTCP:3456 -sTCP:LISTEN
-```
-
-If it's an old OCP process, stop it before re-running setup:
-
-```bash
-ocp stop                                                # if the CLI is on PATH
-launchctl bootout gui/$(id -u)/dev.ocp.proxy            # macOS launchd fallback
-sudo systemctl stop ocp-proxy                           # Linux systemd fallback
-```
-
-### Setup fails with "node: command not found" or version error
-
-OCP requires Node.js 22.5+. Install:
-
-```bash
-brew install node          # macOS
-# Linux: see https://nodejs.org/en/download for current install commands
-```
-
-Confirm with `node --version` (should be ≥ v22.5).
-
 ### Requests fail or agents stuck
 
 ```bash

setup.mjs

@@ -285,6 +285,13 @@ if (OPENCLAW_PRESENT) {
 banner.push(`╚══════════════════════════════════════════════════════════════╝`);
 console.log("\n" + banner.join("\n") + "\n");
 
+// ── Step 6: Optionally start ────────────────────────────────────────────
+if (!SKIP_START && !DRY_RUN) {
+  try {
+    execSync(`bash "${startPath}"`, { stdio: "inherit" });
+  } catch { /* ignore */ }
+}
+
 // ── Step 7: Install auto-start on boot ──────────────────────────────────
 if (!DRY_RUN) {
   console.log("\n🔄 Installing auto-start on login...\n");
@@ -419,52 +426,4 @@ WantedBy=default.target
   }
 
   console.log("\n✅ Auto-start installed — proxy will start automatically on login\n");
-
-  // ── Step 8: Post-install health verification ───────────────────────────
-  if (!SKIP_START) {
-    console.log("⏳ Waiting for server to bind...\n");
-    await new Promise(r => setTimeout(r, 3000));
-
-    const healthUrl = `http://127.0.0.1:${PORT}/health`;
-    let verified = false;
-    try {
-      const controller = new AbortController();
-      const timer = setTimeout(() => controller.abort(), 5000);
-      const res = await fetch(healthUrl, { signal: controller.signal });
-      clearTimeout(timer);
-
-      if (res.ok) {
-        const body = await res.json().catch(() => ({}));
-        console.log(`  ✓ Health check passed (${healthUrl})`);
-        console.log(`    version:  ${body.version ?? "unknown"}`);
-        console.log(`    authMode: ${body.authMode ?? "unknown"}`);
-
-        // Verify bind socket
-        try {
-          const bindCheck = process.platform === "linux"
-            ? execSync(`ss -tlnp 2>/dev/null | grep ':${PORT}'`, { encoding: "utf-8" }).trim()
-            : execSync(`lsof -nP -iTCP:${PORT} -sTCP:LISTEN 2>/dev/null`, { encoding: "utf-8" }).trim();
-          if (bindCheck) {
-            console.log(`    bind:     ${bindCheck.split("\n")[0]}`);
-          }
-        } catch { /* bind check is best-effort */ }
-
-        verified = true;
-      } else {
-        warn(`Health check returned HTTP ${res.status} — service may not have started cleanly`);
-      }
-    } catch (e) {
-      const isTimeout = e.name === "AbortError" || (e.cause && e.cause.code === "UND_ERR_CONNECT_TIMEOUT");
-      warn(`Health check failed: ${isTimeout ? "timeout (5s)" : e.message}`);
-    }
-
-    if (!verified) {
-      const logHint = process.platform === "linux"
-        ? "journalctl --user -u ocp-proxy -n 50"
-        : `tail -n 100 ~/.ocp/logs/proxy.log`;
-      console.error(`\n  ✗ Server did not respond on port ${PORT} within 5 seconds.`);
-      console.error(`    Check service logs:\n      ${logHint}\n`);
-      process.exit(1);
-    }
-  }
 }