epic(packaging): portable + installable distribution channels

[ZhuchkaTriplesix]

Context

Today Release CI ships only relocatable Flutter-bundle zips (Querya-Desktop-{ver}-{linux,windows,macos}.zip). That is already a portable binary layout, but app data still lands in OS paths (getApplicationSupportDirectory, ~/.querya, libsecret/keyring).

The in-app updater already has forward-looking installers for AppImage / Windows setup EXE / macOS .app zip, but CI does not build those artifacts yet, and asset selection only matches *-{platform}.zip.

Users should choose on download:

Channel	Meaning
Portable	Zip (or portable-flagged build): run from folder/USB; optional data next to binary
Installable	OS-integrated packages: AppImage, Windows setup, macOS app/DMG, plus distro packages (deb/rpm/Flatpak/…)

Children

Core dual-channel

• packaging: portable data root (QUERYA_PORTABLE / QueryaData) #380 — Portable data root (QUERYA_PORTABLE / QueryaData/)
• packaging(ci): clarify portable zip channel on GitHub Releases #381 — CI + docs: portable zip channel (keep/clarify artifact names)
• packaging(ci): ship Linux AppImage as installable artifact #382 — CI: Linux AppImage installable artifact
• packaging(ci): ship Windows Inno Setup installer (setup.exe) #383 — CI: Windows Inno Setup (*-windows-setup.exe)
• packaging: updater selects asset by install context (zip vs AppImage vs setup) #384 — Updater: select release asset by install context
• packaging: replace com.example.querya_* bundle / application IDs #385 — Replace placeholder com.example.querya_* bundle IDs

Linux distro packages

• packaging(linux): distro packages (deb, rpm, Flatpak, optional AUR) #386 — Linux distro installers (deb / rpm / Flatpak / optional AUR)

Optional later

• macOS DMG / real Sparkle appcast (code already accepts .app zip)
• Snap (updater already defers to snap refresh when SNAP is set)

Acceptance (epic)

• Each GitHub Release offers clear Portable and Installable downloads per supported OS
• Updater updates with the same packaging family the running binary used
• Portable mode can keep profile data beside the binary when opted in
• At least one multi-distro Linux install path beyond raw zip (AppImage and/or Flatpak/deb/rpm)
• SHA256SUMS.txt covers all published artifacts
• Docs: download matrix + support paths for portable vs installed

Out of scope for this epic

• Shipping AppImage/Inno/deb inside the 0.4.11 tag unless explicitly pulled in after QA (qa(0.4.11): manual release checklist (extensions, export, parity, shell, updater) #344 / epic(release): ship 0.4.11 from dev (UI standard, shell UX, export, parity) #341)
• Changing secret storage away from OS keyring in v1 of portable mode (document limitation; optional later)

References

• .github/workflows/release.yml
• lib/core/updater/installers/ (linux_appimage_installer.dart, windows_exe_installer.dart, macos_sparkle_installer.dart)
• lib/core/updater/installers/update_install_context.dart (APPIMAGE / Snap / Flatpak detection)
• docs/tags-and-releases.md, docs/theme-import.md (support paths)

[ZhuchkaTriplesix]

Progress (implementation started)

Issue	PR	Status
#380 portable data	#387	merged
#381 portable zip docs	#388	merged
#382 AppImage	#389	open
#383 Windows setup	#392	open
#384 updater assets	#390	open
#385 bundle ids	#391	open
#386 deb (partial; rpm/Flatpak still todo)	#393	open

Merge order tip: #391 (ids) before packaging that freezes desktop files; then #389/#392/#393 (may need rebase of release.yml); #390 updater anytime after assets exist.

[ZhuchkaTriplesix]

Shipped in 0.4.11 (tag pushed 2026-07-27).