[dajiaohuang]

Summary

Graphicle's MCP setup documentation says VS Code stores servers in a root servers map in .vscode/mcp.json. The graph extractor recognizes mcp.json by filename but only accepted mcpServers and mcp.servers, so VS Code's documented configuration was rejected during extraction.

Accept the root servers map after the existing formats, preserving their precedence. Add a regression that follows .vscode/mcp.json through normal file dispatch and records the intentional product compatibility extension in the porting adaptations file.

Validation

• cargo +1.95.0 fmt --check passed.
• Focused regression mcp_ingest::tests::vscode_servers_map_is_extracted_through_the_file_dispatch passed.
• cargo +1.95.0 clippy --locked --all-targets --features postgres,bedrock -- -D warnings passed.
• cargo +1.95.0 test --locked --all-targets --features postgres,bedrock: 338 passed, 4 failed, 3 ignored. I reran all four failing tests individually on refreshed origin/main (ddf11b1dac674b4a854356bda8ab67c0d5ced239); each fails there with the same assertion. These baseline failures cover two Go module path separator expectations, record-edge cache/intermediate serialization equality, and a watch-sidecar path expectation.
• The crate's documented all-feature test command with transcription did not reach tests: CMake could not identify C/C++ compilers in the installed Visual Studio 18 toolchain.

No CI state was queried.