Make every control tell the truth

The audit's first tier, in one change: every case found where the interface
asserted something the system did not do.

Twenty-one compositor-owned preferences -- the whole Mouse & Touchpad page,
plus window layout, snapping, dim-inactive and the magnifier -- had the live
half (hyprctl eval) and not the config-time half, so they quietly reverted on
every hyprctl reload. All 70 hypr-backed keys now have a prefs.get() in the
Lua, and hypr-prefs-contract pins both the presence and that the Lua fallback
equals the schema default, which is how the touchpad page misreported natural
scrolling on first boot.

The idle generator fell back from unwritten battery keys to the AC values
while the Power page displayed the schema defaults: a fresh laptop showed
"suspend at 20 minutes" and generated no suspend listener, then discharged to
zero in a bag. Unwritten keys now use the defaults the page shows
(idle-defaults-contract pins generator to schema; idle-config-contract
re-pinned to the new rule with the tradeoff recorded), and change-settings
enables managed idle on any machine with a battery -- without starting
hypridle in whatever session the installer runs under.

The per-app lock-screen notification switches wrote fields nothing read:
hyprlock cannot render notifications. Removed, with the rule model shrunk to
{enabled}, stale stored fields dropped at normalization, and the contract now
forbidding the page from growing lock-screen switches it cannot honor.

The battery warning thresholds were searchable, documented as "Found on
Power & Lock", and rendered nowhere -- and crossing the low threshold changed
only a glyph's color. Both sliders now exist where search was already sending
people, and low battery publishes a real notification at important priority.

Three handoffs opened GNOME panels that are inert in a Hyprland session. The
keyboard handoff is gone (that panel writes gsettings nothing here reads, and
the working controls sat on the same page); Connectivity gains a Wi-Fi row
that opens GNOME's actual Wi-Fi panel -- hidden SSIDs and 802.1X finally have
a road -- beside the network row that legitimately drives NetworkManager; the
universal-access handoff is gone, its few working toggles being controls this
app already owns. And the accessibility page now gives the true reason sticky
keys are missing: each Wayland compositor implements its own and Hyprland
does not yet -- not "an X11 feature with no Wayland equivalent," which sent
people to the wrong conclusion about the platform.

Claude-Session: https://claude.ai/code/session_01Epx9ZC1gwm81K3jm9x9CKh

tests/hypr/idle-config-contract

@@ -134,13 +134,23 @@ grep -q 'timeout = 1800' "$generated" || fail 'on wall power, the AC blank timin
 grep -q 'timeout = 2700' "$generated" || fail 'on wall power, the AC lock timing was not used'
 grep -q 'systemctl suspend' "$generated" && fail 'on wall power, a battery-only suspend listener was written'
 
-# A battery key that was never written falls back to its AC counterpart.
+# A battery key that was never written falls back to ITS OWN schema default,
+# not to the AC value. This section once pinned the opposite -- protecting a
+# deliberate AC setting from being "overridden" by unplugging -- but the
+# Power page's battery card shows the schema defaults for unwritten battery
+# keys, so the AC fallback made the generator disagree with what the screen
+# said: a fresh laptop displayed "suspend at 20 minutes on battery" and
+# generated no suspend listener at all. Whatever the sliders show is what
+# must be generated; a person who wants battery to match AC sets it so, on
+# the card that has said the real values all along.
 stub_hw 0 1
 run_powered '{"screenBlankMinutes":30,"lockMinutes":45}'
-grep -q 'timeout = 1800' "$generated" \
-    || fail 'an unset battery blank did not fall back to the AC value, so unplugging would override a deliberate setting'
-grep -q 'timeout = 2700' "$generated" \
-    || fail 'an unset battery lock did not fall back to the AC value'
+grep -q 'timeout = 120' "$generated" \
+    || fail 'an unset battery blank did not use the schema default the Power page displays'
+grep -q 'timeout = 300' "$generated" \
+    || fail 'an unset battery lock did not use the schema default the Power page displays'
+grep -q 'systemctl suspend' "$generated" \
+    || fail 'an unset battery suspend generated no suspend listener -- the discharged-in-a-bag bug, back again'
 
 # No battery at all: the battery keys are never consulted, even when present.
 stub_hw 1 0