chore(backlog): remove completed menu parity item

agent/BACKLOG.md

@@ -226,22 +226,6 @@ job: the `checks.*` VM suite + real toplevel/HM builds on every push
 *Agents: append here with a one-paragraph pitch (what/why/cost). Do not
 implement. Bernardo moves accepted items into a tier.*
 
-- **Menu parity for downstream-flake options** (raised by Bernardo,
-  2026-07-04, from the hardware sweep): anything the docs or the
-  hardware queue ask a user to *hand-edit into the downstream flake*
-  (`keyboard.layout` multi-layout, `power.batteryChargeLimit`,
-  `updates.enable`, `services.printing`, …) should have a menu toggle
-  instead — the in-flake-state philosophy already gives the menu a
-  write-into-the-flake path, and night-light / auto-timezone /
-  auto-commit prove the pattern (incl. rebuild-on-first-enable).
-  Pitch: (a) an audit listing every user-facing `nomarchy.*` option vs
-  its menu surface; (b) menu writers for the gaps, respecting the
-  toggle-vs-package discipline (bare template packages stay hand-edits)
-  and menu-placement convention (right submenu, root stays short).
-  Values beyond booleans (layout lists, charge thresholds) need a small
-  input UI per option. Cost: audit is one iteration; the writers a few
-  more, sliceable per option.
-
 - **Portal/Flatpak camera picker still lists the internal IR sensor**
   (ROADMAP § Webcam follow-up). The shipped IR-hide is a *WirePlumber
   v4l2* rule, but Flatpak/portal apps consume cameras via the