Sync server.json version to package.json and fail the build on drift

[stonematt]

What to build

server.json and package.json report the same version, and the test suite fails when they drift.

Today server.json declares 2.0.2 (both the top-level version and packages[0].version) while package.json is at 2.0.4. server.json is what the MCP Registry reads, so a drifted manifest advertises a version that was never published.

The release ritual already bumps package.json; the gap is that nothing forces server.json to follow, and nothing catches it if it doesn't.

Acceptance criteria

• server.json version fields match package.json version
• A test under test/ fails when the two disagree
• The test covers both server.json top-level version and packages[0].version
• npm test passes

Blocked by

None — can start immediately.