Bump the basecamp/mcp toolkit, and title every MCP tool
Moves github.com/basecamp/mcp from the 2026-08-28 pin (2d6f44b) to 663b2e5. go-sdk moves with it to the toolkit's own pin.
What broke
The code still compiled, but basecamp mcp could no longer start. The toolkit now derives each gateway tool's annotations (title, idempotent, destructive, and open-world false), and both its catalog loader and gateway.New refuse a domain without a title. None of our domains had one, so every server test failed with domain "projects" has no title.
Fix
- Each
DomainSpecgets aBasecamp …title, the form the HEY and Fizzy MCP servers use (HEY Boxes,Fizzy Cards). - The hand-built
recordingscomposite domain getsBasecamp Recordings. nix/package.nixhas a refreshedvendorHashfor the new go.sum. It came frommake update-nix-hash, and the rebuild with it succeeded.
The catalog snapshot changes only by the toolkit's new (destructive) notes. These cover the 23 delete_*, destroy_*, remove_*, trash_* and unsubscribe* actions that its action-name classifier marks. Clients now also see these actions as destructiveHint: true.
Checks
bin/ci passes except for 13 PTY/terminal tests in appctx, cli, commands, connector/runner, stdinarg and tui/resolve. All 13 fail the same way on unmodified main in the local sandbox. CI is the judge for those.
Summary by cubic
Bumps github.com/basecamp/mcp to a pin that starts deriving gateway tool annotations and refuses domains without a title, which broke basecamp mcp startup. Every domain now carries a Basecamp … title in the HEY/Fizzy style, including the composite recordings domain.
- The catalog snapshot changes only by the toolkit's new
(destructive)notes on the 23 delete/destroy/remove/trash/unsubscribe actions, which now also reach clients asdestructiveHint. go-sdkmoves with the toolkit pin, andnix/package.nixgets a refreshedvendorHashfrommake update-nix-hash.