docs(agent): record #43 V2 (Firmware menu render) + #44 close

#43: theme-shot render confirms the System submenu renders themed and
self-gates correctly; the Firmware row's presence on a real install is
verified via /sw/bin/fwupdmgr existing in the live toplevel (same
mechanism as the working Bluetooth row). A filter render didn't surface
the row in the minimal capture VM — render artifact, not a bug. V3 (real
LVFS flash) stays queued.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

agent/JOURNAL.md

@@ -17,6 +17,22 @@ Template:
 
 ---
 
+## 2026-07-09 — #43 V2: System ▸ Firmware menu render
+- **Task:** V2 the shipped Firmware menu (#43). theme-shot render of
+  `nomarchy-menu system`.
+- **Did/Verified:** System submenu renders themed + correct (Bluetooth shows,
+  Printers/Snapshots correctly self-gated out). The Firmware row sits below the
+  visible fold; a `send_chars "firm"` filter did NOT surface it in the capture
+  VM. Disambiguated the anomaly against the real system: `/sw/bin/fwupdmgr`
+  **exists** in the live toplevel (same as the working Bluetooth row's
+  `blueman-manager`), so `command -v fwupdmgr` succeeds → the row shows on a
+  real install. The theme-shot filter view is a minimal-VM render artifact,
+  not a bug. Incidental: a reddish doctor-status glyph appears in the bar
+  (#51's indicator firing on the VM's degraded state).
+- **Tier:** V2 for the menu render + PATH-verified row presence; V3 (real LVFS
+  flash) stays queued. Over-spent renders here chasing the anomaly — noted.
+- **Next:** wrap.
+
 ## 2026-07-09 — #44 V2: checks.doctor guards the hardware section
 - **Task:** close #44's V2 (was V1 + real-hw smoke). Extend `checks.doctor`.
 - **Did:** The bare test VM has none of the probe tools, so the existing