[Feature] Optional Parallel Search MCP setup example

## Summary Would an opt-in [Parallel Search MCP](https://docs.parallel.ai/integrations/mcp/search-mcp) setup example fit CCGS? It would give users free web search and page fetching without a Parallel account or API key. ## Type - [x] Improvement to existing component - [x] Other: optional MCP setup documentation ## Problem / Motivation Engine setup and game-design research benefit from current web sources. An optional MCP setup example could give users another way to find engine documentation and fetch reference pages while keeping CCGS's existing WebSearch and WebFetch workflows. ## Proposed Solution Add a short opt-in section to `.claude/docs/setup-requirements.md` showing how to connect Claude Code to `https://search.parallel.ai/mcp` over HTTP, inspect its search and fetch tools, and remove the connection. Keep the default template configuration and agent permissions unchanged, and preserve user approval before writing research into project files. If this fits the project, I would validate the documented setup in a clean Claude Code session, run a search for official engine documentation, and fetch one of the resulting pages. ## Alternatives Considered Keep using the existing WebSearch and WebFetch tools without configuring an MCP server. Users can also configure their own MCP servers independently of CCGS. ## Additional Context Anonymous searches use Fast mode. The free endpoint has lower rate limits and is intended for exploration and light use. I work at Parallel.