v0.0.14 — see installed system packages, and safer reboots

Highlights

A node’s installed system software is now visible, searchable and upgradable from its own screen — the new OS Packages tab. This release also fixes a long-standing mix-up: a Raspberry Pi’s firmware update now reads clearly as “Firmware update,” separate from ordinary system-package work labelled “OS update,” so a firmware notice is never mistaken for a pending package update.
A reboot an update needs no longer requires a second, separate maintenance step. If updating a node’s system software leaves a reboot pending, you can now fold that reboot straight into the same action instead of running a second one afterward.
A pending reboot is now a fleet-wide signal shown alongside firmware and package updates, and it clears itself automatically once the node actually reboots.
A reboot that never comes back no longer hangs the operation forever. If a node doesn’t return within a reasonable time, the panel now fails that step clearly instead of leaving it spinning.
A migrated Raspberry Pi’s boot order is now visible and changeable from the panel, with a two-option switch between memory-card-first and SSD-first (both remain able to boot from the memory card). This came directly from a real failure where a present-but-corrupted SSD stalled a node’s boot, and physically opening the machine was the only way to recover — the boot-order control gives you a way to fix that ahead of time, while the node is still reachable.

None specific to this release beyond what’s already listed on earlier releases’ pages.