Version-consistency patch closing the public metadata drift found after v0.3.2.
What changed
- MCP
serverInfo.versionnow derives from the shippedpackage.json, so protocol metadata cannot silently remain on an older release. - The README was updated before tagging and publishing, keeping GitHub release source and npm package presentation aligned.
- Packed-artifact verification now exercises
setup-deliveryand rejects any mismatch between the installed package version and the live MCP initialize response. - Added a protocol-level regression test for package-derived server metadata.
Verification
- 148/148 tests
- TypeScript build passed
- Packed-artifact verification passed
npm audit --omit=dev: 0 vulnerabilities- npm registry shasum:
2cd6f88600478411c7daeb0bbaf523bc9426acb8
rekindle@0.3.3 is published under the npm latest dist-tag.