Pin forgectrl 42cdb71; add the coolant offset check; record the compensation on the bench

The pin carries the calibrate tool's sampling fix (3 s at 8 Hz a side).
aa_offset_check.py proves the correction on a machine: M8 brings the fans
to the run profile, dark, while the raw coolant counts, /status and the
engine's readings are averaged before, during and after; it turns the
flow check off for its session and restores it. On the bench page as
aa-offset-check. CAMPAIGN-LOG records the tool's first run, the applied
value (16 counts) and the proof: the readings held within 0.1 C under
the run profile where they dropped 1.0 C uncorrected. BRINGUP item 21
names what remains.

No catalog consequence: a bench tool and records.

docs/BRINGUP.md

@@ -1476,9 +1476,10 @@ Open items only. Anything closed is in `CAMPAIGN-LOG.md`.
     gates read the coolant about 1.2 C cooler than it is while the air
     assist runs unless `cool_aa_offset_counts` carries the machine's value
     (the `aa-offset-calibrate` diagnostic measures it, the panel's Apply
-    writes it; zero is the factory's uncorrected reading). Owed: the
-    calibrate run on this machine and its value applied, a second
-    machine's value when one is on the bench; and the mid-run
+    writes it; zero is the factory's uncorrected reading; the bench
+    machine carries 16). Owed: the calibrate tool's recommendation
+    accepted on an image (its first sampling refused its own result), a
+    second machine's value when one is on the bench; and the mid-run
     toggling between two levels (0.6 to 1.1 C, both sensors together),
     which comes only with the tube lit: not with the fans alone, not under
     motion, not in an armed dark window. The HV supply's input current on

docs/CAMPAIGN-LOG.md

@@ -4492,6 +4492,38 @@ two sensor lines during a cut is the next instrument. Its size is 0.6 to
 1.1 C either way, inside the over-temperature ceiling's 2 C hysteresis,
 and the flow check reads means.
 
+## 2026-08-29: the air-assist offset taken off the coolant readings, on the bench
+
+forgectrl `cool_aa_offset_counts` (f9b4893, the status link fix 25cf969),
+image 20260829214735 flashed by the operator. The correction is in ADC
+counts, keyed to the air-assist duty the engine commands, taken off both
+raw readings in the engine and in `/status` (more counts read colder, so
+the fan's ground lift reads as a drop and the correction subtracts; the
+host test caught the first cut adding it).
+
+**The calibrate tool** (`aa-offset-calibrate`, the panel's "Calibrate
+coolant offset") ran end to end on the bench: three idle-to-run cycles,
+six edges reading 12.7/18.3, -15.8/-18.5, 16.3/16.8, -12.5/-10.3,
+15.7/17.8, -15.7/-21.0 counts (down/up), mean 16.0. It refused its own
+result on the spread (10.7 counts against its 8-count limit): 1.5 s at
+4 Hz is six samples a side against about 5 counts of single-sample noise.
+The tool now reads 3 s at 8 Hz a side (forgectrl 42cdb71, the next
+image); the value was applied directly, `cool_aa_offset_counts = 16`, this
+machine's number.
+
+**The proof** (`scripts/bench/aa_offset_check.py`, dark, no press: M8
+brings the fans to the run profile, the raw counts, `/status` and the
+engine's readings averaged before, during and after). Uncorrected, the
+upstream reading dropped 1.02 C under the run profile (raw +15.2 counts).
+Corrected, with the flow check off for the session so its heater stayed
+out of the downstream sensor: the raw counts stepped +15.4 / +13.3 and
+`/status` read 23.96 / 23.94 against 23.87 / 23.96 before, +0.09 and
+-0.02 C; the engine's own readings +0.31 / +0.25 inside the same window.
+The readings hold still while the fan runs. A first run of the check had
+left `cool_flow_check_s` at 0 (the script's restore posted an empty value
+and got a 400; fixed); the setting was put back to 50 and the engine
+re-read it at the next session.
+
 ## Superseded status notes
 
 ### Shared machine services — remaining polish, as listed 2026-08-13