Document how Col answers on the MCP page#63

Adds a "How Col answers" section to the /mcp setup page, right after "Connect your client", so readers and agents can see the same transparency contract the tools actually return.

How Col answers

• States the behavior plainly: read-only tools, never touches the project, no account or API key — and names the four tools (search_libraries, search_components, get_library, get_component).
• Documents what every result carries: a canonical source link on every record, verification stated per part (page / install / compatibility / snapshot), explicit gaps ("not yet verified" never means "doesn't exist"), matchedOn explaining why a result matched, indexStatus hints on empty results, and documentation snapshots with fetch dates and source revisions.
• Shows a real result exactly as an agent receives it — the live mantine/Spotlight hit from a probe of the deployed endpoint — and closes on the point: the same evidence the agent cites is what the reader can click and check.

Tests

tests/docs-pages.test.mjs now recognizes connection configs by their mcpServers key, so JSON result examples can appear on the page without breaking the config assertion. Full suite green (npm test).