docs(agent): V2 the menu IA (#105/#111/#110) — content passes, file #131/#132

856a9d1 restructured the picker and shipped at "V0 menu-back; HM gen builds",
which §2.1 does not allow for a user-visible change. Rendered all eight
screens under the real HM session and viewed them.

IA verified: six-entry root; System → Connectivity/Devices/Recovery/
Preferences; Recovery lists each scope once; Preferences carries the migrated
update-checks/Bluetooth/Printing toggles; Control Center gone from the
dispatch (asserted, not eyeballed); no stderr on any screen. No code change.

Two findings, both filed rather than fixed:

#131 — the VM showed the long Recovery labels ellipsized. That specific
symptom is a guest artifact (they measure 462px/509px in Inter 11 against
~668px of room at 1920), but the same measurement says they DO truncate at
1366, where the picker is only 546px wide — cutting exactly the cost hint
#111 added them to carry. The Acer Aspire M5-481T is 1366x768 and in the QA
fleet. Shortening vs -mesg vs widening is a design call.

#132 — the guest draws icons at ~1/4 of ui.iconSize and clips a 6-row root
behind a scrollbar despite lines=8. Root predates #105, so this is the test
environment, not a regression — but it means menu screenshots are evidence
for content and never for geometry. Documented in docs/TESTING.md §5 so the
next agent doesn't chase it.

docs/TESTING.md

@@ -132,6 +132,12 @@ Hyprland's headless backend otherwise aborts in a VM-only zero-output state.
   not an inverted apply. Trust hyprctl / the toast numbers.
 - **First theme switch is the slowest**: it evaluates the flake on a RAM
   disk. Subsequent switches reuse the eval cache.
+- **Menu geometry does not survive the guest**: the rofi picker draws with
+  icons at roughly a quarter of `ui.iconSize` and rows short enough that a
+  6-row root clips its last entry behind a scrollbar (`lines = 8` should
+  fit it). Menu screenshots are evidence for **which rows appear**, never
+  for spacing, icon size or label truncation — measure text against the
+  40% window width instead, or check on hardware (BACKLOG #132).
 
 ## 6. When something fails