Make installation, upgrades, and platform recovery dependable #11

Outcome

Portable binaries are a starting point. Users need predictable setup, update behavior, credential storage, and recovery on each supported desktop.

Priority: P1 · Release readiness

Scope

• Build on existing native packages and document platform prerequisites and supported architectures.
• Add preflight diagnostics for keyring/credential storage, external tools, and writable data locations.
• Define a signed release and update strategy with integrity verification, recovery, and user-visible update state. Keep signing secrets in release infrastructure.
• Until an updater is delivered, provide a clear version check and verified manual update path.
• Validate behavior on macOS, Windows, and an actual Omarchy desktop, beyond headless packaged-worker checks.

Acceptance criteria

• Fresh installs can open the sample and complete the core local workflow on all three platforms.
• Upgrading preserves existing drafts and history; failed updates or migrations have a documented recovery path.
• Locked or unavailable credential stores produce actionable guidance without insecure storage fallback.
• Package integrity and signing status are accurately reported.
• Platform evidence covers startup, rendering, preview behavior, credentials, and applicable connection flows; unsupported cases are documented.

Validation

Maintain a clean-install and upgrade matrix with OS/runtime versions and reproducible evidence. Separate automated native smoke checks from actual GUI/OAuth/keyring verification.

Dependencies

• Build a unified connection center with actionable repair flows #6 — Build a unified connection center with actionable repair flows
• Add explicit storage migrations, backup, and recovery checks #10 — Add explicit storage migrations, backup, and recovery checks