docs(agent): V2 the menu IA (#105/#111/#110) — content passes, file #131/#132
All checks were successful
Check / eval (push) Successful in 3m48s
All checks were successful
Check / eval (push) Successful in 3m48s
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.
This commit is contained in:
@@ -96,6 +96,31 @@ whether Nomarchy holds itself higher — darker label, or a darker accent mix
|
||||
for light palettes — and note `tools/check-theme-contrast.py` covers palette
|
||||
pairings only, never GTK widget surfaces. `[human]` for the aesthetic call.
|
||||
|
||||
### 131. Recovery cost labels truncate on 1366-wide panels
|
||||
|
||||
#111 gave Recovery scope-first labels that carry the cost inline — "Desktop
|
||||
generation — themes & home config (instant, reversible)" (462px in Inter 11)
|
||||
and "System boot generation — older NixOS (reboot, then pick in boot menu)"
|
||||
(509px). The picker is `width: 40%`, so text room is ~668px at 1920 (fits)
|
||||
but only ~446px at 1366 — **both long labels ellipsize, and the cost hint is
|
||||
exactly the part that gets cut**. The Acer Aspire M5-481T (1366×768) is an
|
||||
active QA machine, so this is live, not theoretical. Options: shorten to
|
||||
"Desktop generation (instant)" and put cost in a rofi `-mesg` line, widen the
|
||||
picker for narrow screens, or let rofi wrap. Measured, not observed — the VM
|
||||
renders menu geometry unfaithfully (see #132); confirm on the Acer.
|
||||
|
||||
### 132. VM cannot judge rofi menu geometry
|
||||
|
||||
The guest renders the picker with icons at roughly a quarter of `ui.iconSize`
|
||||
(44 → ~10px) and rows short enough that a 6-row root clips its last entry
|
||||
behind a scrollbar, though `lines = 8` and `dynamic = true` should fit it.
|
||||
Root is unchanged since before #105, so this is the guest's font/icon
|
||||
environment, not a regression — but it means `theme-shot.nix`/`menu-shot`
|
||||
screenshots are trustworthy for **menu content** and not for spacing, icon
|
||||
size, or truncation. Either fix the guest (fontconfig + icon cache in the
|
||||
test node) or document the gap in docs/TESTING.md §5 so the next agent does
|
||||
not chase it — right now nothing warns them.
|
||||
|
||||
### 120. A netinstall ISO, next to the fat offline one
|
||||
|
||||
Bernardo 2026-07-14, after seeing the measured size: **keep the current ISO
|
||||
|
||||
Reference in New Issue
Block a user