LintabOS 0.3.12

LintabOS 0.3.12 (pre-release)

A real-hardware bug found within hours of 0.3.11 shipping, fixed the same day, plus a new read-only diagnostic
for the experimental BCD write tool.

What was found

0.3.11's power gate (AC power + 40% battery minimum, before the experimental BCD write is attempted) was reading
the wrong battery on a real Duet 3. The tablet exposes two "Battery"-typed entries under
/sys/class/power_supply/:

BATX                                 capacity: 72   (the tablet's real battery)
hid-0018:4858:121A.0001-battery-2    capacity: 0    (a connected stylus/keyboard case's own battery, over HID)

battery_percent() returned whichever one directory listing happened to return first - on this tablet, the HID
peripheral, reporting 0%, which made the power gate refuse to even attempt the write regardless of the tablet's
actual charge. hid-<bus>:<vendor>:<product>...-battery-N is the Linux kernel's own, documented naming convention
for HID report-battery devices, so lintab.bcdbackup now skips any power supply named with that prefix when
looking for the AC adapter or the device's own battery - a real, general fix, not a one-off for this tablet.

New: read-only boot-entry inspection

Because of the above, it's still not actually confirmed whether the onetimeadvancedoptions write works as
intended on a real installed system - the write was being refused before it ever ran. Rather than guess again,
"Windows Boot Configuration (Experimental)" gains a third action, "Describe current boot entry": mounts the
Windows ESP read-only and lists every element on the default boot entry, with friendly names where known
(onetimeadvancedoptions, recoverysequence, ...). This is how to check whether a real Windows installation's
boot entry actually has recoverysequence and recovery enabled at all - without needing bcdedit or even to boot
into Windows; it works from LintabOS alone. Never writes anything.

Files: lintabos-core_0.3.12_all.deb + .minisig, SHA256SUMS.