feat: derive public release labels from published manifest

[YashasVM]

What changed

• Show a specific release version and version-specific download links only when the latest published release has a valid manifest, matching asset names and sizes, and matching SHA-256 sidecars.
• Keep the website on generic “Latest release” copy when the manifest is absent or invalid. The current published v1.0.1 release has no manifest, so the fallback stays active.
• Keep the website package and lockfile at 0.0.0, separate from release/version.properties.
• Replace the old release notes body with a per-release template and update release and README guidance. Preserve V1.0.1 details as historical facts and remove unverified scene, dock, reconnect, and latency claims.

Checks

• npm ci --ignore-scripts && npm run build
• Local Markdown links in README and release docs
• Live GitHub release metadata and download links
• Chromium render of the current no-manifest fallback
• git diff --check

The release workflow must accept per-release notes before publication; this depends on the V2 follow-up queued by the parent branch owner.

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Advanced

Run ID: e3a39107-4a37-4990-af7d-70219c6d963b

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}