Prepare the stable 2.0.1 semantic release

[austin-smith]

What Changed

• Bump the app and widget marketing versions to 2.0.1.
• Make the validated release tag the single source for release versioning.
• Stamp CFBundleVersion from the semantic release version instead of the GitHub Actions run number.
• Verify the exported app bundle version matches the release tag.
• Generate the one-entry Sparkle appcast from the current release artifact without importing stale version metadata.
• Restrict releases to stable tags that exactly match the project marketing version.
• Remove prerelease tagging support from the release helper and documentation.

Why

Sparkle compares CFBundleVersion, but the 2.0.0 release workflow stamped it from a workflow-local run counter. That allowed the release to compare incorrectly against previously distributed builds. Version 2.0.1 establishes semantic bundle versioning using the same release model as ComputerSolitaire so future Sparkle comparisons remain consistent. Removing the obsolete prerelease path keeps the documented tag helper aligned with the stable-only workflow.

Validation

• Archived the macOS Release build with a semantic CURRENT_PROJECT_VERSION and code signing disabled.
• Confirmed the archived app and widget report matching semantic marketing and bundle versions.
• Confirmed Xcode resolves a single 2.0.1 MARKETING_VERSION across the app and widget targets.
• Validated workflow YAML and every embedded shell block.
• Validated scripts/tag-version.sh syntax and help output.
• Confirmed the removed --prerelease option is rejected with exit status 2.
• Confirmed no prerelease release-path references remain.
• Ran git diff --check.

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: c0bb4503f2

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".