Notice the battery, and the machine it is or is not in

Panama had no idea whether it was running on a laptop. No upower, no battery, no lid, no AC: hypridle.conf says "This is a desktop" in its own header, and that was true of the code as well as the machine. panama-hw answers hardware questions one at a time, exits 0 or 1, and prints nothing, so scripts, services and contracts all ask the same way. The definition the rest of the laptop work hangs on is one line: clamshell is lid-closed AND an external monitor. A machine with no mains supply at all reports as being on wall power, because a desktop cannot run out of it. The battery service follows Vitals: sysfs through FileView, an availability flag, and no subprocess on the timer. Globbing is the one thing QML cannot do -- a battery is BAT0 or BAT1 or CMB0, mains is AC or ADP1 or ACAD -- so panama-battery resolves the names once and the shell reads the files directly after. Nothing falls back to a plausible zero: a desktop shows no indicator, no card, and no charge limit control where the firmware has no ceiling. Also repairs two contracts that were already failing and had not been noticed, because only the full suite runs them. The dependency scanner treated line-initial variable assignments, case labels, comments and heredoc bodies as commands, and `count`, `host`, `cancel` and `import` are all real binaries on Fedora, so `command -v` could not filter them out. It now drops comments and heredoc bodies and requires a command to be followed by whitespace. Verified it still catches a genuinely undeclared dependency rather than passing quietly. The launcher command contract had not been told about the fourteen commands added earlier today.
2026-08-21 21:43:14 -04:00
parent e446a1072c
commit 3c359f3f7e
17 changed files with 1032 additions and 9 deletions
@@ -116,4 +116,27 @@ Pill {
        glyph: "\u{F03F2}"                       // md-cellphone-link
        color: Theme.cyan
    }
+
+    // Battery. Absent entirely on a desktop: `available` is false until a
+    // battery has actually been read, so this is not a zero that looks like a
+    // flat cell. Same shape as the graphics field in VitalsWidget, which gates
+    // on both the preference and the hardware.
+    StatusGlyph {
+        visible: Settings.showBattery && Battery.available
+        glyph: {
+            if (Battery.charging)
+                return "\u{F0084}";              // md-battery_charging
+            const level = Math.round(Battery.percent / 10) * 10;
+            if (level >= 100) return "\u{F0079}";  // md-battery
+            if (level <= 0)   return "\u{F008E}";  // md-battery_outline
+            // md-battery_10 .. md-battery_90 are consecutive from F007A.
+            return String.fromCodePoint(0xF007A + (level / 10) - 1);
+        }
+        color: {
+            if (Battery.critical) return Theme.danger;
+            if (Battery.low) return Theme.warn;
+            if (Battery.charging) return Theme.ok;
+            return Theme.fg;
+        }
+    }
 }