Doclea MCP

{ "queries": [ { "id": "q-live-e2e-choice-pipeline", "query": "How does the live measured E2E benchmark pipeline work from retrieval through CLI model request and timing aggregation?", "expectedFilePaths": [ "scripts/mcp-vs-grep-choice-benchmark.ts", "scripts/lib/llm-cli-runner.ts", "scripts/llm-cli-codex-adapter.ts" ] }, { "id": "q-doc-drift-guardrail-only", "query": "Where is the doc-drift workload generated and how is Doclea Guardrail enforced as the only Doclea comparison mode in reports?", "expectedFilePaths": [ "scripts/mcp-six-part-benchmark.ts", "scripts/mcp-six-part-presentation-html.ts", "documentation/live-e2e-benchmark-plan-2026-02-16.md" ] }, { "id": "q-config-context-vector-flow", "query": "Trace how project config is loaded and then used by context-building retrieval components and vector/storage backends.", "expectedFilePaths": [ "src/config.ts", "src/tools/context.ts", "src/storage/factory.ts", "src/vectors/factory.ts" ] }, { "id": "q-code-docs-drift-triage-path", "query": "For doc drift triage, map where stale-reference workload queries are generated, where Doclea Guardrail-only comparison is enforced, and where that appears in the presentation output.", "expectedFilePaths": [ "documentation/live-e2e-benchmark-plan-2026-02-16.md", "scripts/mcp-six-part-benchmark.ts", "scripts/mcp-six-part-presentation-html.ts" ] }, { "id": "q-retrieval-dependency-chain", "query": "Follow the dependency chain from benchmark entrypoint through config loading, embedding client creation, storage/vector backend factories, and context assembly calls.", "expectedFilePaths": [ "scripts/mcp-vs-grep-choice-benchmark.ts", "src/config.ts", "src/embeddings/provider.ts", "src/storage/factory.ts", "src/vectors/factory.ts", "src/tools/context.ts" ] } ] }