Installing without Wi-Fi enabled meant the first boot found nothing to install and, worse, left the Store
broken for everything after it: the Store couldn't reach Flathub to refresh its catalog. First-boot setup
now runs through the dispatcher, so it records what happened and shows it in the Updates app. It retries a
failed install at most twice and then decides the remote is genuinely unavailable, and a remote with no
configured URL, or one that can't be resolved, is reported rather than retried. start-cosmic adds
flatpak's data directory to PATH and XDG_DATA_DIRS, so the Store can find what it installs and
flatpak works in a terminal, which it didn't for a session started by greetd.
The nightly batch in the same images was one routine bump, fzf 0.74.4 → 0.74.5. It's a fuzzy finder, not a crisis. What's worth saying is that the batch path now carries a routine bump end to end: prepare the edit, build, boot-check, sign, publish, and record what it closed, without a human in the loop.
Behind the scenes, the build-side boot check got real virtual machines rather than a hand-written QEMU command line per edition, and a recipe bug that had been costing full rebuilds was fixed: a recipe whose download hash is generated from upstream had that generated value anchored in the wrong place, so every nightly edit to it failed.