chore: establish npm beta prerelease channel

[github-actions]

Summary

• Enter Changesets prerelease mode with the beta tag.
• Roll all pending main changes into hevy-mcp@1.28.1-beta.0 and synchronize server.json.
• Make the server-manifest version lifecycle test work for stable and prerelease versions.
• Document installing and launching hevy-mcp@beta, plus switching back to @latest.
• Let authenticated, same-repository Mergify queue drafts skip only the changeset-presence guard; ordinary and fork PRs still enforce it.

Release behavior

All current changesets are recorded in .changeset/pre.json. After merge, the existing changesets/action@v1 workflow should find no pending changesets, run npm run release, and publish hevy-mcp@1.28.1-beta.0 with the npm beta dist-tag. The latest tag remains on 1.28.0.

Future Version Packages PRs will continue producing beta versions until prerelease mode is exited.

Validation

• npm run check:server-manifest
• npm run build
• npx vitest run --exclude tests/integration/**
• npm run check
• npm run check:types
• npm publish --dry-run --tag beta --ignore-scripts
• Changesets action-state simulation — no pending changesets; publish path selected
• Queue-exemption truth table — Mergify same-repo/author/ref is exempt; ordinary, fork, and non-Mergify lookalikes remain enforced
• Node 24.x and Node 26.x direct PR CI passed

The repository intentionally skips the ordinary PR changeset check for the canonical changeset-release/main branch and authenticated Mergify queue drafts; all prerelease changesets are already consumed into pre.json.

Post-merge verification

npm view hevy-mcp dist-tags --json
npm exec --yes --package=hevy-mcp@beta -- hevy-mcp --version
npm exec --yes --package=hevy-mcp@latest -- hevy-mcp --version

Resolves #584

Supersedes #591

[gitstream-cm]

✨ PR Review

LGTM

Generated by LinearB AI and added by gitStream.
_{AI-generated content may contain inaccuracies. Please verify before using.
💡 Tip: You can customize your AI Review using Guidelines Learn how}

Review dismissed

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 92.74%. Comparing base (e29d5b7) to head (0ae098f).

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #581   +/-   ##
=======================================
  Coverage   92.74%   92.74%           
=======================================
  Files          35       35           
  Lines        1530     1530           
  Branches      382      382           
=======================================
  Hits         1419     1419           
  Misses         48       48           
  Partials       63       63           

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[mergify]

Queued — the merge queue status continues in this comment ↓.

[github-actions]

Unit Test Results

  1 files   32 suites   2s ⏱️
489 tests 489 ✅ 0 💤 0 ❌
493 runs  493 ✅ 0 💤 0 ❌

Results for commit 0ae098f.

♻️ This comment has been updated with latest results.

[mergify]

Merge Queue Status

• ✅ Entered queue — 2026-07-10 19:39 UTC · Rule: default · triggered by rule Queue pull requests labeled 'queue'
• ❌ Checks failed · on draft merge queue: checking main (e29d5b7) and #581 together #596
• 🚫 Left the queue — 2026-07-10 19:46 UTC · at b842cceafd57b9a233e65cd421a61177e2886de0

This pull request spent 6 minutes 56 seconds in the queue, including 1 minute 15 seconds running CI.

Waiting for

• check-success = "Build and test (Node 24.x)"

All conditions

• check-success = "Build and test (Node 24.x)"
• check-success = "Build and test (Node 26.x)"

Reason

The merge conditions cannot be satisfied due to failing checks

• Build and test (Node 24.x)

Failing checks:

• ❌ Build and test (Node 24.x) (job log)

Hint

You may have to fix your CI before adding the pull request to the queue again.
If you update this pull request, to fix the CI, it will automatically be requeued once the queue conditions match again.
If you think this was a flaky issue instead, you can requeue the pull request, without updating it, by posting a @mergifyio queue comment.

Requeued — the merge queue status continues in this comment ↓.

[mergify]

Merge Queue Status

• ✅ Entered queue — 2026-07-10 20:04 UTC · Rule: default · triggered by rule Queue pull requests labeled 'queue'
• ✅ Checks passed · on draft merge queue: checking main (e29d5b7) and #581 together #597
• ✅ Merged — 2026-07-10 20:11 UTC · at 0ae098fad004fb5889a2d0a5b2a88b50598395ac · squash

This pull request spent 7 minutes 3 seconds in the queue, including 1 minute 15 seconds running CI.

Required conditions to merge

• check-success = "Build and test (Node 24.x)"
• check-success = "Build and test (Node 26.x)"