Packaging: the Homebrew cask workflow is dormant, and there is no Flathub package

[EtienneLescot]

Context

Most of the distribution plumbing already exists. State checked on 2026-08-10:

Channel	Workflow	Status
winget	publish-winget.yml	Configured. WINGET_IDENTIFIER=OpenScreen.OpenScreen is set; microsoft/winget-pkgs still only carries manifests/s/SiddharthVaddem/OpenScreen, so the new identifier lands on the next release.
AUR	aur-publish.yml	Configured (AUR_PACKAGE_NAME, AUR_SSH_PRIVATE_KEY).
Nix	bump-nix-package.yml	Configured.
Microsoft Store	—	MSSTORE_PRODUCT_ID set.
Homebrew cask	update-homebrew-cask.yml	Dormant — see below.
Flathub	—	Absent.

Two gaps remain.

1. The Homebrew cask job is skipped on every release

update-homebrew-cask.yml is gated on:

if: ... && vars.HOMEBREW_TAP_OWNER != '' && vars.HOMEBREW_TAP_REPO != ''

Neither variable exists on the repo, so the job is skipped every time — and a skipped job is green. This is the exact failure mode that publish-winget.yml documents in the comment above its own if:, after eight releases "succeeded" without publishing anything (#148). The same guard shape is still in place here.

• Create the tap repo (getopenscreen/homebrew-openscreen)
• Set HOMEBREW_TAP_OWNER and HOMEBREW_TAP_REPO
• Move the config check out of if: into a step that reports its absence, mirroring what publish-winget.yml now does
• Verify brew install --cask getopenscreen/openscreen/openscreen

If the tap isn't wanted, delete the workflow instead — dormant-and-green is the worst of the three options.

2. No Flathub package

A Flathub search for "openscreen" returns zero results. It is the main Linux discovery surface (GNOME Software and KDE Discover both pull from it) and the only channel here with no automation at all. The AppImage/deb/rpm/pacman targets don't help — Flathub needs its own manifest submitted to flathub/flathub.

• Submit a manifest to flathub/flathub
• Wire release automation once the app ID is accepted

Deliberately not proposed

Chocolatey and Scoop. Windows is already covered by winget plus the Store; add them only if someone asks.

Why this is worth finishing

Beyond installation convenience, these are the highest-authority pages that link the project by name, and they intercept "install openscreen" before it reaches the stale third-party download mirrors currently outranking getopenscreen.com.