A read-only audit of the v2.3.8 tree found several claims that do not match
the code, plus two packaging slips:
- `initialize` advertised `serverInfo.version` 3.4.5 — FastMCP's version, not
this package's — because the server was constructed without `version=`.
The low-level server now reports 2.3.8;
- `CHANGELOG` and `docs/FEATURES.md` both said *every* MCP tool response is
bounded and then listed the four that are not. Both now say "almost every"
and name `get_impact_radius`, `find_large_functions`, `traverse_graph` and
`semantic_search_nodes` as still open under #888;
- `docs/FEATURES.md` still called 2.3.6 the current release;
- the Voyage provider added in this release was missing from four provider
summaries (CLAUDE.md, FAQ, TROUBLESHOOTING, the README feature table) while
the detailed sections listed it correctly;
- the source distribution carried the issue tracker's `.beads/` hooks and the
VS Code extension's own README and LICENSE, because hatch adds readme- and
licence-named files from anywhere in the tree on top of `include`.
No behavior changes beyond the version string.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Tirth Kanani
d88ddf3a8f