Make GitHub Releases the canonical download channel

[eimexdev]

Part of OpenBeat v0.1.0 public launch map.

Question

What concrete documentation and release-policy changes make GitHub Releases the only canonical installer download channel while keeping Ko-fi optional?

Goal

Make GitHub Releases the single canonical location for OpenBeat installer downloads. Ko-fi may remain an optional support or announcement channel, but it must not gate downloads or require duplicate binary uploads.

Work

• Replace Ko-fi download language in README.md, docs/install.md, and docs/release-checklist.md.
• Link users to the latest GitHub Release and name the macOS and Windows assets clearly.
• Rewrite the publishing checklist around GitHub Release assets.
• If Ko-fi remains, present it only as optional support and link back to GitHub.
• Remove or replace stale Ko-fi wording in any draft GitHub Release before publication.

Acceptance criteria

• A user can find the correct installer from the repository without visiting Ko-fi.
• GitHub Releases is described consistently as the source of binaries.
• No public text implies that checkout or Ko-fi access is required.

[eimexdev]

Resolved in 588db89.

GitHub Releases is now the sole canonical installer download channel. The README and install guide link directly to the latest release and identify the macOS .pkg and Windows .exe assets. The release checklist now publishes and verifies those assets on GitHub, while Ko-fi is explicitly optional support with no duplicated binaries, checkout, or account requirement. The stale Ko-fi distribution wording was also removed from the existing draft “OpenBeat v0.0.2” release.

Verification: git diff --check, byte-compilation, and all 8 unit tests passed using .venv/bin/python.