Give a laptop its first week: the keys, the lid, the battery's endgame

The audit's fourth tier -- what a Framework owner reaches for in the first
week and found missing.

The power button stops being an instant, unconfirmed poweroff: a shipped
logind drop-in tells the daemon to stand down and the compositor binds the
key to the power menu, the way GNOME turns it into a question. Holding it
still hard-cuts through firmware. change-settings restarts logind so the
change applies without waiting for a boot, and the Power page says what the
button does now.

The function row fills in: F10 (XF86RFKill) toggles airplane mode through a
new panama-osd verb that blocks or unblocks every radio and says which way it
went; F9 (XF86Display) opens the Displays page, the honest action until
mirroring exists. And the lid becomes a switch bind: closing a docked lid
turns the internal panel off so nothing renders inside a closed shell and no
workspace strands on an invisible output, and opening it restores the panel
with the mode and scale chosen in Settings. panama-lid owns both decisions;
undocked machines suspend via logind before any of it matters.

The battery gets an endgame. On battery the screen dims to 30% two-thirds of
the way to blanking -- GNOME's single largest idle battery saver -- and
restores exactly the level it saved. At the urgent threshold the machine
suspends after a fifteen-second grace, cancelled by plugging in, because a
suspend preserves the session for days and a hard cut at 0% preserves
nothing; "Only warn" remains a choice on the Power page. Hibernate joins the
power menu, but only where logind answers CanHibernate with yes -- an entry
that fails silently is worse than none.

And brightness stops being two code paths: the Displays page now embeds the
same control the quick-settings panel uses, so the built-in backlight and
DDC/CI monitors share one surface that withdraws itself where neither
exists. The lid contract narrows to what its principle protects -- a
HandleLidSwitch drop-in -- so deliberate policy for other keys can ship.

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

config/dot/quickshell/scripts/panama-osd

@@ -240,11 +240,34 @@ media_action() {
     show_message "$kind" "$label"
 }
 
+# Airplane mode: one rfkill state for every radio, with an OSD saying which
+# way it went. "Any radio unblocked" reads as radios-on, so toggle means
+# "block everything" from a mixed state -- the direction a person reaching
+# for airplane mode wants.
+airplane_action() {
+    case "${1:-toggle}" in
+        toggle)
+            if rfkill list 2>/dev/null | grep -q 'Soft blocked: no'; then
+                rfkill block all 2>/dev/null \
+                    && show_message "airplane-mode-symbolic" "Airplane mode on"
+            else
+                rfkill unblock all 2>/dev/null \
+                    && show_message "network-wireless-symbolic" "Airplane mode off"
+            fi
+            ;;
+        *)
+            printf 'Usage: panama-osd airplane toggle\n' >&2
+            return 2
+            ;;
+    esac
+}
+
 case "${1:-}" in
     volume) shift; adjust_volume "$@" ;;
     microphone) shift; adjust_microphone "$@" ;;
     brightness) shift; adjust_brightness "$@" ;;
     media) shift; media_action "$@" ;;
+    airplane) shift; airplane_action "$@" ;;
     message)
         shift
         kind="${1:-}"
@@ -256,7 +279,7 @@ case "${1:-}" in
         show_message "$kind" "$*"
         ;;
     *)
-        printf 'Usage: panama-osd volume|microphone|brightness|media|message ACTION [value]\n' >&2
+        printf 'Usage: panama-osd volume|microphone|brightness|media|airplane|message ACTION [value]\n' >&2
         exit 2
         ;;
 esac