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

config/dot/quickshell/scripts/panama-idle

@@ -71,16 +71,24 @@ load() {
         suffix="Battery"
     fi
 
-    # The battery variants fall back to their AC counterparts rather than to a
-    # constant, so a machine whose battery keys were never written still gets
-    # coherent behavior instead of the schema's shipped shorter timings
-    # overriding a deliberately long AC setting.
-    blank_min="$(clamp_int "$(read_setting "screenBlankMinutes$suffix" \
-        "$(read_setting screenBlankMinutes 5)")" 0 120 5)"
-    lock_min="$(clamp_int "$(read_setting "lockMinutes$suffix" \
-        "$(read_setting lockMinutes 10)")" 0 240 10)"
-    suspend_min="$(clamp_int "$(read_setting "suspendMinutes$suffix" \
-        "$(read_setting suspendMinutes 0)")" 0 480 0)"
+    # An unwritten key falls back to ITS OWN schema default, never to the
+    # other power source's value. The battery keys once fell back to their AC
+    # counterparts, which sounded protective and produced a lie instead: the
+    # Power page shows the schema default (suspend at 20) for an unwritten
+    # battery key, while this generator quietly used the AC value (never), so
+    # a fresh laptop displayed one behavior and shipped another -- and
+    # discharged to zero in a bag. Whatever the sliders show is what must be
+    # generated; these fallbacks are pinned to the schema by
+    # tests/hypr/idle-defaults-contract.
+    if [[ "$suffix" == "Battery" ]]; then
+        blank_min="$(clamp_int "$(read_setting screenBlankMinutesBattery 2)" 0 120 2)"
+        lock_min="$(clamp_int "$(read_setting lockMinutesBattery 5)" 0 240 5)"
+        suspend_min="$(clamp_int "$(read_setting suspendMinutesBattery 20)" 0 480 20)"
+    else
+        blank_min="$(clamp_int "$(read_setting screenBlankMinutes 5)" 0 120 5)"
+        lock_min="$(clamp_int "$(read_setting lockMinutes 10)" 0 240 10)"
+        suspend_min="$(clamp_int "$(read_setting suspendMinutes 0)" 0 480 0)"
+    fi
     lock_on_sleep="$(read_setting lockOnSleep true)"
     [[ "$lock_on_sleep" == "true" || "$lock_on_sleep" == "false" ]] || lock_on_sleep=true
 }
@@ -162,7 +170,15 @@ case "${1:-apply}" in
     install)
         generate
         install_dropin
-        systemctl --user restart hypridle.service
+        # Restart only a daemon that is already running. `restart` on an
+        # inactive unit STARTS it, and this verb now also runs from
+        # change-settings during ./install -- possibly inside a GNOME
+        # session, where starting hypridle would fight GNOME's own idle
+        # handling. A session that has not started hypridle yet picks the
+        # drop-in up at its next launch.
+        if systemctl --user is-active -q hypridle.service; then
+            systemctl --user restart hypridle.service
+        fi
         ;;
     remove)
         rm -f "$dropin"