·
85 commits
to main
since this release
Documentation fix. No behaviour change, no API change.
0.2.0 renamed nine MCP tools into a single ratchet_<verb>_<object> scheme, but the bridge package's own README was missed — so the published tarball documented ratchet_check_effect and ratchet_usage, two names the server rejects. Anyone reading the npm package page and following its tool table would have called a name that does not exist.
Fixed, and the naming tests now read every surface a user takes a tool name from rather than only src/mcp/tools.ts, so a rename cannot be complete in the source and wrong in the shipped artifact again.
The 15 tools themselves are unchanged from 0.2.0.