Repin conformance harness to the published 0.2.0-alpha.10
Repins the conformance harness from the temporary pkg.pr.new build of main@da56f663 to the published @modelcontextprotocol/conformance@0.2.0-alpha.10, and drops the sha256 fetch-and-verify steps that only the tarball URL needed.
Motivation and Context
The pkg.pr.new pin was a stopgap until an npm release carrying conformance #403 (sep-2575 checks aligned with spec #3002) and #406 (per-check expected-failures granularity) shipped. 0.2.0-alpha.10 is now on npm (the alpha dist-tag) with both, so CONFORMANCE_PKG can go back to a plain registry spec — npm's own integrity check replaces the recorded digest.
The release adds two commits beyond the previous pin (conformance #409, #383); neither changes results against this SDK, so both expected-failures*.yml baselines are unchanged apart from comment wording.
How Has This Been Tested?
Ran all six CI legs locally against the 0.2.0-alpha.10 tarball (server active/draft/2026-07-28/all, client all/2026-07-28) — every leg passes with the existing baselines and no stale entries.
Breaking Changes
None; CI-only.
Types of changes
- Bug fix (non-breaking change which fixes an issue)
- New feature (non-breaking change which adds functionality)
- Breaking change (fix or feature that would cause existing functionality to change)
- Documentation update
- CI
Checklist
- I have read the MCP Documentation
- My code follows the repository's style guidelines
- New and existing tests pass locally
- I have added appropriate error handling
- I have added or updated documentation as needed