Move plugin source .mcp.json out of repo root

Symptom: starting Claude Code in this repo loaded the *template* shape
of the Roboflow MCP config -- the one with the literal placeholder
"x-api-key:${ROBOFLOW_API_KEY}" -- because Claude Code treats any
.mcp.json at the project root as a project-scope MCP config and
auto-loads it. The plugin marketplace install path patches a *separate*
cached copy under ~/.claude/plugins/cache/, so the patched copy never
gets loaded in this dir. Net effect: developers working on this repo
hit a 401 from mcp.roboflow.com with the literal "${ROBOFLOW_API_KEY}"
string as the key value.

The file isn't legacy -- .claude-plugin/plugin.json's `mcpServers`
field points at it and `claude plugin install` bundles its contents
into the cache. So we keep the file but move it under .claude-plugin/
where Claude Code's project-level auto-loader won't see it. The
plugin.json reference becomes "./.mcp.json" relative to the plugin
manifest dir; cache layout is unchanged because Claude Code's plugin
install logic preserves the source filename, and the installer's
patcher still finds .mcp.json in the cache as before.

Also fix .codex-plugin/plugin.json's mcpServers pointer, which was
"./.mcp.json" relative to .codex-plugin/ but no such file ever
existed there -- repoint at ../.claude-plugin/.mcp.json so both plugin
manifests share one source of truth.

No installer changes needed. No test changes needed (the Pester / bats
tests cover the CACHE file, not the source). Pre-existing 2 failing
claude-desktop tests still fail unchanged.

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

Author: yeldarby

.mcp.json .claude-plugin/.mcp.json.mcp.json renamed to .claude-plugin/.mcp.json

@@ -20,7 +20,7 @@
     "mcp"
   ],
   "skills": "./skills/",
-  "mcpServers": "./.mcp.json",
+  "mcpServers": "../.claude-plugin/.mcp.json",
   "interface": {
     "displayName": "Roboflow",
     "shortDescription": "Build computer vision projects with Roboflow",