rpm-ostree/ostree only retain a couple of deployments, so there's no
durable record of what's been layered since the stock image. Add a
local history DB (lib/history/) keyed on the ostree deployment
checksum, with a parent pointer forming a tree, plus named "current"
and "last_known_safe" pointers.
Reconciling against live `rpm-ostree status --json` on every launch
means the history stays correct even across manual rpm-ostree/bootc
changes made outside this app: any booted checksum we don't recognize
gets recorded as a "detected" node rather than silently ignored.
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
A GUI installer wizard for permanent rpm-ostree package layers on
bootc/image-based systems. Walks through: welcome/current-version check,
package name entry with existence check, confirmation, then a streamed
rpm-ostree install via pkexec. On success, writes a pending-confirmation
marker and installs an autostart entry so the next login shows a
"did this update work?" screen with a one-click rollback (bootc rollback
--apply) if not.
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
