Keep Windows releases on their existing beta channel

README.md

@@ -192,8 +192,8 @@ Gitea **Build** validates every push to `main` on two shared account-scoped host
 `mac-mini` (label `claudechecker-macos-arm64`, Xcode) and `jamespc` (label `claudechecker-windows-x64`)
 (Windows host, .NET 8, Inno Setup). Each run uploads its app/installer artifact.
 
-Use **Release macOS** or **Release Windows**, select `main`, and supply a version
-and channel. Stable versions use `X.Y.Z`; beta versions use `X.Y.Z-beta.N`.
+Use **Release macOS** or **Release Windows Beta**, select `main`, and supply a version
+(and macOS channel). Stable versions use `X.Y.Z`; beta versions use `X.Y.Z-beta.N`.
 The workflow builds that main revision, creates the release and uploads the asset
 before advancing the corresponding `version*.json` feed on main. Releases are
 never overwritten. macOS builds retain the existing ad-hoc signing model; this
@@ -202,7 +202,9 @@ project does not currently perform Developer ID signing or notarization.
 Existing installs still check the old GitHub `version*.json` URLs. Those files
 are kept as a migration bridge advertising the first Gitea-hosted update. Keep
 the GitHub repository accessible for those clients; subsequent updates use Gitea.
-GitHub workflows are disabled after the Gitea builds are verified.
+GitHub workflows are disabled after the Gitea builds are verified. The Homebrew
+cask downloads the latest stable macOS release from Gitea and enables app-managed
+updates. Windows releases remain prereleases and do not replace that stable URL.
 
 Local build commands are `bash scripts/build-macos.sh` and, on Windows,
 `./scripts/build-windows.ps1` with `INNO_SETUP_COMPILER` pointing to `ISCC.exe`.