Bernardo Magri
79528ff392
Some checks failed
Check / eval (push) Has been cancelled
BACKLOG #96 + #97 (Acer live pass). Battery limit: the System row now gates on battery presence (same rule as Power profile) instead of the charge-threshold sysfs node, so firmware without the control gets the leaf's explanation ("no charge_control_end_threshold — hardware capability") rather than a silently missing row that reads as a broken feature. Bluetooth: the leaf checks bluetooth.service before launching blueman-manager and replaces the raw "Connection to BlueZ failed" with a state-aware message (service stopped vs no adapter in /sys/class/bluetooth, with rfkill/firmware hints). Verified: V1 — nomarchy-menu builds, bash -n green, both paths in the generated script; V0 flake check green. QEMU can fake neither a threshold-less battery nor a BT adapter: #96 behavioral check queued in HARDWARE-QUEUE (Acer + T14s); #97's no-adapter message will be click-checked in the next VM run (V2 pending). Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>