Three fixes to the documentation MCP surfaced by review:
Query recall: the sanitizer required a CamelCase-style API anchor, which
rejected legitimate queries such as `expo-camera barcode scanner`,
`gradle configuration cache`, and `coroutine cancellation cooperative`
— exactly the guide, release-note, and Expo topics that have no symbol.
Accept hyphenated package tokens as anchors and accept short multi-word
lowercase concept phrases. The length, entropy, token-count, and secret
checks are unchanged, and a single generic word still fails closed.
Honest limits: the search tool advertised limit 1-10 (default 5) while
the server silently clipped results to resultsPerQuery (default 2), and
the same bound accidentally capped fetch_platform_doc's focused passage
count. Derive the advertised schema maximum and default from the
enforced cap, and give the focused passage count its own independent
bound.
Rejection visibility: sanitizer rejections, refused direct-fetch URLs,
and budget-exhausted attempts left no audit trace, so operators could
not see unmet research demand. Audit each refusal by reason class only
(query-rejected, url-rejected, budget-exhausted) — never the refused
input, which may be exactly the material the sanitizer refused to send —
and surface the counts in progress output and the step summary. Also
warn instead of returning silently empty when requested source kinds
exclude the Expo search, and record the platform on fetch audit inputs
so failed fetches stop mislabeling as react-native.
The evaluation scripts spawned the MCP as a subprocess and made live
Brave, Algolia, and page requests, so they could not run in CI and had
drifted: one fixture query no longer passes the current sanitizer, and
both scripts exceed the per-server call budget added in v0.12.2.
Run the documentation server in-process over an InMemoryTransport, one
server per case, and replay recorded fixtures through the existing
fetchImplementation seam. Each case carries its own fixture; the replay
synthesizes the exact wire formats (Brave hits, Algolia hits, the OkHttp
static index, DocC JSON, HTML, Markdown, YouTrack JSON) keyed by the
request URLs the production provider logic computes, so the sanitizer,
routing, allowlists, redirect and content-type checks, extraction, and
ranking all run unmodified. RESEARCH_EVAL_LIVE=1 keeps a live mode for
true retrieval-quality runs.
Thread fetchImplementation through the Expo Algolia search so the
recorded mode covers the expo provider, replace the sanitizer-broken
kotlin-coroutines query with a symbol-anchored one, and run both
evaluations in CI.
Brent Vatne