Follow-up to v2.6.7. The release bumped both packages[*].version
entries in server.json but missed the top-level "version" field, so
mcp-publisher rejected the publish with "cannot publish duplicate
version" and the MCP Registry stayed pinned at 2.6.6 even though
npm shipped 2.6.7.

No code, schema, or wire changes. v2.6.7 stays on npm as-is; the
MCP Registry skips from 2.6.6 → 2.6.8.

476 tests pass; bun run devcheck clean.