Bump the basecamp/mcp toolkit, and sync the catalog that titles its tools
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
gateway.Domain gained ToolTitle, AllIdempotent and AnyDestructive. The gateway now derives each tool's annotations from them (title, idempotent, destructive, and open-world false), and it refuses a domain that has no title. The vendored catalog was older than that change, so *catalog.Domain no longer satisfied the interface and the build failed.
Fix
I re-synced the catalog with scripts/sync-mcp-catalog.sh from fizzy-mcp-server 724955b, the commit where the sibling adopted these annotations. The copy stays verbatim and PROVENANCE.json names that commit. The sync brings:
- a
Fizzy …title on every domain Idempotenton every read, on the PUT-style updates and onpublish_boardDestructiveon thedelete_*actions and onunpublish_board- the
destructivenote in descriptions and describe summaries
The snapshot changes only by those new notes and fields.
The sync stops at 724955b, not the sibling's head. Later catalog changes there (top-level body fields, read-only blurbs) need matching dispatch and server changes in this repo, so they belong in a port of their own.
catalog_test.go picks up the sibling's matching test changes:
- titled fixtures
- three new
validaterefusals: missing title, a read not marked idempotent, a read marked destructive - a drift test that pins destructive curation to the toolkit's bridge classifier
Checks
make check passes. Lint ran at CI's golangci-lint v2.10. A local v2.15 flags two gosec G124 findings in signup.go, which this PR doesn't touch; CI's version doesn't report them.
Summary by cubic
Bumps the basecamp/mcp toolkit and re-syncs the vendored catalog so it satisfies the toolkit's new gateway.Domain contract. go-sdk moves with it to the toolkit's own pin.
The newer toolkit requires every domain to provide a ToolTitle, an AllIdempotent check, and an AnyDestructive check, and refuses any domain without a title. The catalog predated that, so the build failed. Re-syncing via scripts/sync-mcp-catalog.sh brings it in line, and validation now rejects reads not marked idempotent and reads marked destructive.
Catalog passes
- Every domain gets a
Fizzy …title. - Reads, PUT-style updates, and
publish_boardare idempotent. delete_*actions andunpublish_boardare destructive, with matching description notes and snapshot updates.- A drift test pins destructive curation to the toolkit's bridge classifier.
The sync stops at the sibling's commit that introduced these annotations; later catalog changes there need matching dispatch and server changes and land separately.