TEST BUILD 2 — B&W mode + magenta auto-heal

TEST PRERELEASE — not for the fleet (no latest.json; the app keeps offering v1.0.1.82). Supersedes v1.0.2-bw-magenta-test.1. Built from loop-firmware combo/bw-mode-magenta-catch @ 0dee75a.

Adds on top of test.1 / v1.0.1.82: the magenta AUTO-HEAL (two layers)

1. S3 AWB register probe (every 60 s while awake, post-warmup): two masked SCCB reads of 0x3406 (AWB manual latch) + 0x5001 (AWB engine enable). Nothing writes these at runtime, so any unexpected state = the glitch. Heal: direct register fix with readback, escalating to SOFT_RESET only if it doesn't stick. Max 3/boot. (Startup frame-probing was rejected by design: a restart clears the wedge — first frames are the provably-clean moment — and a solo cam can't tell a wedged AWB from a pink scene.)
2. P4 fleet-gated auto soft-reset: when the per-capture cast telemetry flags EXACTLY ONE cam magenta (rg>22 && bg>22) while ≥2 siblings on the same capture read neutral, fire SENSOR_SOFT_RESET (~150 ms) at that cam. A genuinely pink scene flags all cams and the gate refuses. 5-min/cam cooldown, 6/boot, never during a capture.

Validation status — honest

Deployed + running on the bench P4X + 4 cams; both layers compile clean and the P4 gate is pure arithmetic over the already-proven cast telemetry. The end-to-end induced-wedge proof (cam_setreg AWB latch + magenta gains → detect → heal → neutral) is built but blocked: the bench SD card died mid-run (terminal 0x107 wedge, physical reseat needed) — without SD there are no saves, so the telemetry path can't execute. The harness re-runs immediately after a card reseat. Watch for MAGENTA AUTO-HEAL / AWB PROBE log lines in the field.

Promotable to v1.0.1.83 (fleet) once validated.