fix: point Claude Code profile at ~/.claude.json, not settings.json

Claude Code stores user-scope MCP servers in ~/.claude.json (what
'claude mcp add' writes); ~/.claude/settings.json is for permissions
and hooks and rejects an mcpServers key with a schema error, so BCC
was reading (and writing) servers where Claude Code never looks.

If servers are found parked in settings.json, that file is still
listed as 'Claude Code (legacy settings.json)' so they can be copied
into the real config via Copy to. Docs updated; verified against
docs.claude.com/en/docs/claude-code/settings.

README.md

@@ -32,8 +32,9 @@ python bcc.py
 
 - **Auto-discovers installs** — scans the platform's app-support folder for any
   `Claude*` directory (so `Claude` and `Claude-Work` both show up) **and** finds
-  Claude Code at `~/.claude/settings.json`. Use **Add config…** to point at any
-  other file manually.
+  Claude Code's user-scope config at `~/.claude.json` (the file `claude mcp add`
+  writes). Use **Add config…** to point at any other file manually — e.g. a
+  project's `.mcp.json`.
 - **Form-based editing** — name, command, args (one per line), env vars, or for
   remote servers: URL, transport, and headers. No raw JSON.
 - **Paste JSON — even broken JSON** — drop in any snippet from an MCP doc (full
@@ -80,7 +81,9 @@ After saving, **restart that Claude install** for changes to take effect.
 | Windows | `%APPDATA%`                      |
 | Linux   | `~/.config`                      |
 
-**Claude Code** (all platforms): `~/.claude/settings.json`
+**Claude Code** (all platforms): `~/.claude.json` (user scope). If servers are
+found parked in `~/.claude/settings.json` — where Claude Code ignores them — that
+file is also listed, marked *legacy*, so you can copy them over.
 
 ## Files