Publish the public repository and v0.1.0 GitHub Release #26

Part of OpenBeat v0.1.0 public launch map.

Question

Are all launch gates satisfied, and can a signed-out user successfully inspect, download, verify, install, and get support for OpenBeat v0.1.0?

Final publish sequence

• Confirm the chosen license is present.
• Confirm the public-readiness audit is complete.
• Confirm signed or explicitly accepted release artifacts passed smoke testing.
• Make the repository public.
• Verify README, install, source, issue, and latest-release links in a signed-out/incognito session.
• Publish the v0.1.0 GitHub Release as the latest non-prerelease release.
• Confirm both installers and checksums are publicly downloadable.
• If using Ko-fi, publish an optional support/launch post that links to GitHub rather than hosting a second copy.
• Post the launch announcement only after the public path is verified.

Acceptance criteria

A signed-out user can inspect the licensed source, download and verify the correct installer directly from GitHub, follow the install guide, and report an issue.