docs(agent): promote v1.0 slices 42–44 to NEXT

Boreal default theme, System › Firmware (fwupd), and doctor hardware
section — human triage from PROPOSED for agents to execute.

agent/BACKLOG.md

@@ -28,7 +28,33 @@ in [`docs/ROADMAP.md`](../docs/ROADMAP.md); map in
 
 ## NEXT
 
+### 42. Default theme → boreal (`VISION § B` / v1.0 bar)
+Ship Boreal as the distro default instead of Tokyo Night: root
+`theme-state.json`, `templates/downstream/theme-state.json` (and any
+greeter/plymouth fallbacks that hardcode Tokyo Night when state is
+missing). Preset already exists under `themes/boreal/`. Capture
+`preview.png` if still missing so the picker looks first-class.
+Cost: copy/apply palette into seed state files + grep for tokyo-night
+defaults; V0 contrast, V1/V2 theme apply, V3 visual on hardware.
 
+### 43. System › Firmware — fwupd product surface (`VISION § A`)
+`services.fwupd.enable` is already default-on and never auto-flashes,
+but users only learn about `fwupdmgr` from a README sentence. Add a
+self-gated menu entry (System submenu) and/or Control Center row that:
+refreshes metadata, lists updatable devices, confirms, runs
+`fwupdmgr update`, then prints a reboot note when needed. Never
+silent-flash (pillar 1). Optional: first-boot / MOTD one-liner when
+the daemon is active. Spec: docs/HARDWARE.md §4. Cost: menu script +
+optional MOTD; V2 menu, V3 on real LVFS hardware.
+
+### 44. Doctor hardware section — read-only (`VISION § A`)
+Extend `nomarchy-doctor` with the same pass/fail + one-fix-command
+contract for: NetworkManager connectivity, default PipeWire sink,
+optional GPU smoke (`vainfo`/`glxinfo` if present), fprintd unit when
+fingerprint was enabled, fwupd active (+ warn if `get-updates`
+non-empty), laptop charge-threshold sysfs when a limit is set. Spec:
+docs/HARDWARE.md §10. Cost: doctor.sh sections; V1 in existing
+`checks.doctor` where fakes exist, rest V2/V3.
 
 ### 14. Automated lock bumps — confirm the first real run
 Slices b+c shipped 2026-07-05 (`.gitea/workflows/bump.yml`): weekly
@@ -105,25 +131,13 @@ implement. Bernardo moves accepted items into a tier.*
 
 ### v1.0 track — see `docs/VISION.md`
 
-Product themes and the release bar live in **VISION**. Many slices
+Product themes and the release bar live in **VISION**. Promoted to
-already have pitches below (Hardware product, Installer bugs, Default
+**NEXT:** #42 boreal default · #43 System › Firmware · #44 doctor
-theme → boreal). When adding new product work, reference
+hardware. Remaining candidate promotions: fingerprint menu ·
-`VISION § <theme>` and prefer the north-star laptop user. Suggested
-next promotions (human picks order): install P0 contracts · boreal
-default · System › Firmware · doctor hardware · fingerprint menu ·
 first-boot tips · human rebuild errors · neon-glass quarantine.
 
 ### Pre-existing
 
-- **Default theme → boreal** (`VISION § B` / v1.0 bar)
-  Ship Boreal as the distro default instead of Tokyo Night: root
-  `theme-state.json`, `templates/downstream/theme-state.json` (and any
-  greeter/plymouth fallbacks that hardcode Tokyo Night when state is
-  missing). Preset already exists under `themes/boreal/`. Capture
-  `preview.png` if still missing so the picker looks first-class.
-  Cost: copy/apply palette into seed state files + grep for tokyo-night
-  defaults; V0 contrast, V1/V2 theme apply, V3 visual on hardware.
-
 - **Battery charge-limit — make the toggle instant** `[blocked:hw]`
   (follow-up to the preset toggle shipped 2026-07-07, iteration #55).
   The control-center now has a proper toggle (Off / 80% / 90% / 60% /
@@ -533,25 +547,6 @@ autodetect is strong; day-2 lifecycle (firmware, biometrics, re-detect,
 NVIDIA depth) is still mostly CLI. Items below are product work on top
 of that doc — design notes live there (§4–§10).*
 
-- **System › Firmware (fwupd product surface)**
-  `services.fwupd.enable` is already default-on and never auto-flashes,
-  but users only learn about `fwupdmgr` from a README sentence. Add a
-  self-gated menu entry (System submenu) and/or Control Center row that:
-  refreshes metadata, lists updatable devices, confirms, runs
-  `fwupdmgr update`, then prints a reboot note when needed. Never
-  silent-flash (pillar 1). Optional: first-boot / MOTD one-liner when
-  the daemon is active. Spec: docs/HARDWARE.md §4. Cost: menu script +
-  optional MOTD; V2 menu, V3 on real LVFS hardware.
-
-- **Doctor hardware section (read-only)**
-  Extend `nomarchy-doctor` with the same pass/fail + one-fix-command
-  contract for: NetworkManager connectivity, default PipeWire sink,
-  optional GPU smoke (`vainfo`/`glxinfo` if present), fprintd unit when
-  fingerprint was enabled, fwupd active (+ warn if `get-updates`
-  non-empty), laptop charge-threshold sysfs when a limit is set. Spec:
-  docs/HARDWARE.md §10. Cost: doctor.sh sections; V1 in existing
-  `checks.doctor` where fakes exist, rest V2/V3.
-
 - **`nomarchy-detect-hw` CLI (post-install re-probe)**
   The installer already has pure `nomarchy_detect_hw` stdout protocol
   (MODULE / NOMARCHY / DETAIL). Ship it as a package on PATH that