2026.5.8 — opt-in diagnostics: -V hex-dump + -B force-bl

Diagnostic improvements (no production-default behavior change)

-V very-verbose actually traces now

run_raw_uart_shim() was called with verbose (1) instead of verbose + very_verbose (2), so the verbose > 1 hex-dump branch never fired. With -V you now get up to 64 hex bytes per shim TX/RX frame — useful for diagnosing the multimacd ↔ EFM handshake without attaching strace to a moving target.

-B force-bootloader (opt-in recovery tool)

Calls copro_start_bootloader() before handing the PTY to multimacd, then drains residual push-confirmations so multimacd sees a clean PTY state.

Recovery tool for hung App-states. Not a production default — multimacd's own boot sequence usually handles the transition without -B. Marginal value; ship it only because it's flag-gated and harmless when unused.

Related

Used together with headlessCCU 2026.5.19 — but the actual fix for that release (device-cgroup c 509:* rwm) is entirely in the container compose-file, not in bmcond.

Verified

livetest_actors.sh: 3/3 BidCoS + 3/3 HmIP PASS against the 2026.5.7 image after rebuild. The bmcond changes here are opt-in diagnostics — no behavior change for the default run path.