c139. Updates

Mark, 2026-11-11. Verbatim.

Let's start a new cycle, updates. We need a seamless way to push out new updates of our app. this may already be solved elsewhere and we're just updating design to support it, but updates should be able to be launched from the settings, they should be invisible to the user (if their preference so desires). We should show current version, new version and link to release notes. Early users may have heightened access to our internal notes (build partners) and so initial access may look different to a more structured roll out that comes with a product maturity that is down the road from where we are right now.

The app is the native desktop app (qnative, GPUI; c130, c131), which also absorbs the tray. The low-level self-update already exists in qcontrol (qupdate); this cycle designs the user-facing half. Run in a cloud session the same day, from the session that opened it: Phases 0–3 to a first review stop.

Create a plan, ask any clarifying questions, suggest patterns I may not be considering.