laser power-good: the line characterized, the kernel-drill guard, the probe, the dev image's mmap and ctypes

The supply's power-good line is active high, static across HV enable and emission, and driven; the facts bank and CAMPAIGN-LOG carry the measurement and the item closes. The kernel-drill latch-unlock guard read the old inverted value as HV not good, a check that was vacuous and would refuse every run once the module reads the line correctly; it now uses the chain's own witnesses, the charge-pump watchdog and the engine state. pgood_probe.py watches the line beside the chain through the kernel readbacks and is registered on the bench page. The dev image lists python3-mmap and python3-ctypes again for the pad-level bench tools the python trim had left without them.

meta-forgefirm/recipes-forgefirm/images/forgefirm-image-dev.bb

@@ -12,9 +12,16 @@ IMAGE_INSTALL += " \
   forgectrl \
   forgetest \
   python3-gfutilities-emulator \
+  python3-mmap \
+  python3-ctypes \
   htop \
 "
 
+# python3-mmap and python3-ctypes serve the bench scripts that read the SoC
+# pads through /dev/mem (resume_dark_lead.py, cp_watchdog_timing.py, the
+# accelerometer probes). They are bench tooling: the release image carries
+# neither, and forgetest itself imports neither.
+
 # The release recipe trims nano from the shared base list (bench
 # convenience, 8.7 MB with libmagic); the dev image keeps it. Removal specs
 # accumulate and apply after every append, so the variable inside the