Wave is installable as a Flatpak via FlatPark — happy to have it listed?

No repository file or test is named; start by reading this issue and the linked #1093 thread, then review the FlatPark app page and its installation details. Done means the team explicitly approves or rejects the listing, with any decision about closing #1093 or naming FlatPark in install documentation recorded.

Hi — #1093 has been open a while, with the stated blocker being that electron-builder can't produce a manifest Flathub's infrastructure will build from source, and the last word on the thread was that you'd be happy to hand the work off. So: Wave is now installable as a Flatpak from FlatPark, a small hub for desktop apps that aren't on Flathub, and I'd like to check that you're OK with the listing.

flatpak remote-add --if-not-exists flatpark https://dl.flatpark.org/flatpark.flatpakrepo
flatpak install flatpark dev.commandline.waveterm

App page: https://flatpark.org/apps/dev.commandline.waveterm/

This sidesteps the blocker entirely — it doesn't build from source. It pins your official amd64 .deb, unmodified, and re-pins automatically on each release. Chromium keeps its own internal sandbox (zypak), and wavesrv, the SQLite store, the SSH client and the staged wsh helpers all come from your payload; nothing is fetched or compiled at first run.

Details users may ask you about:

• No filesystem permission is granted. Wave writes only to XDG paths, which Flatpak redirects, so config, store and staged wsh binaries live under ~/.var/app/dev.commandline.waveterm/. Host SSH keys, home browsing and serial devices are opt-in flatpak overrides documented on the listing.
• The bundled updater (dl.waveterm.dev, install-on-quit) can't work for a Flatpak install, so the package seeds autoupdate:enabled=false on first run only — an existing config is left alone and the switch is still in Settings. Updates come from flatpak update.
• App id is your own electron-builder appId, so an official Flatpak from you later would land on the same id.

If the team is happy to have it listed, I'll mark the app page developer-approved; if you'd rather it not exist, say so and I'll take it down. And if you'd like to close #1093 out, I'd be glad for Wave's install docs to name FlatPark as the Flatpak path — packaging, signing, hosting and updates stay with me.