OpenRouter target: confirm intended consumer

[Astralchemist]

The openrouter install target landed in commit 8da5cdb as a best-guess scaffold:

• Writes ~/.config/openrouter/mcp.json with the standard mcpServers.rig shape
• Writes ~/.config/openrouter/AGENTS.md with the generated tool guidance
• Detection: dir exists OR OPENROUTER_API_KEY is set
• All 9 tool contracts now include openrouter: 'auto-allow'

OpenRouter itself is an API, not an MCP host. Real OpenRouter+MCP usage flows through a client (Cline, Continue.dev, LibreChat, Open WebUI, etc.) that handles MCP separately. The current paths are an invented convention.

Decision needed: keep the generic scaffold, or redirect to a specific OpenRouter-using client?

• Cline (VS Code) — config at `~/.config/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json`
• Continue.dev — config at `~/.continue/config.json`
• LibreChat — server-side, no per-user MCP config
• Keep generic — let the user copy the entry into whichever client they use

If we pick a specific client, the target's name should reflect that (e.g., rename to cline) and the contract paths updated. If generic, leave as-is and consider the doc note about manual copy-in.