GovInfo adapter: wired but waiting on an upstream npm package
Gadoes adds the GovInfo adapter for federal publications (CFR, Federal Register, public laws), following the same template as CourtListener. The commit message flags it explicitly: the `govinfo-mcp` npm package hasn't been published yet, so the server config is scaffolding only.
backend/src/lib/mcp/servers/govinfo.ts exports buildGovInfoConfig, isValidGovInfoKey, GOVINFO_TOOLS, and GOVINFO_SYSTEM_PROMPT. The config calls npx govinfo-mcp - the package that doesn't exist yet.
Fixtures cover three document types: a CFR entry for Clean Air Act regulations, a Federal Register final rule for PFAS reporting (EPA, 2023), and the Infrastructure Investment and Jobs Act (Pub. L. 117-58). The 21 tests cover config construction, key validation (null, empty, whitespace-only all return false), citation parsing, and the empty/malformed-input edge cases.
Everything testable without a live govinfo-mcp process works: the parser, the key validator, and the config shape. The mock-MCP integration test is there but can only verify the fixture-response path.
Spotted something wrong? Or know the PR text has fresher detail than the writeup above?