Production Readiness Checklist

This checklist tracks the minimum baseline Linuxy should satisfy before release.

Runtime Safety

• Restrict Tauri allowlist to the APIs actually used by the app
• Define a production CSP for remote catalog access and local asset loading
• Keep external URL opening in the backend and validate allowed URL schemes
• Gate optional update functionality when appimageupdatetool is
  unavailable

Install / Update / Remove Reliability

• Reject non-AppImage / non-ELF input before installation
• Validate AppImage extraction before copying into ~/.local/appimages
• Avoid leaving partially installed binaries behind on failed install
• Reject failed HTTP downloads before attempting installation
• Remove installed app binaries, desktop entries, and icons consistently

Background Behavior

• Avoid prompting on partially downloaded AppImages
• Bound watcher state so it does not grow forever during long sessions
• Handle missing home/downloads directories without panicking

Repository Quality Gates

• Make frontend CI run the declared project checks
• Make security audit jobs fail on real findings
• Restore valid clippy.toml configuration
• Use stable rustfmt configuration
• Add backend unit tests for critical helper behavior

Release Verification

• Run frontend checks in a clean dependency install
• Run cargo clippy -- -D warnings
• Run cargo fmt -- --check
• Run full Tauri bundle build on release target(s)
• Perform install/remove QA via CI on clean Linux VM
• Verify catalog fetch and image loading under the production CSP