CAMPAIGN-LOG: cooling.gate-off passes on the bench

First bench run of the gate-settings pattern: PASS on dev image
20260821210903 after the harness fix in f274eb1; the entry records the
failed first attempt and why it was the test's fault. BRINGUP item 19
carries the bench result.

docs/BRINGUP.md

@@ -1323,7 +1323,8 @@ Open items only. Anything closed is in `CAMPAIGN-LOG.md`.
     start, `/status` and `/cool/status` carry `gates_off`, and an off gate
     keeps measuring. Applied to the coolant ceiling, its resume gate, the
     flow window and the flow rise (`forgectrl/src/gates.c`, `SERVICES.md`
-    "Gate settings", `COOLING.md` §8a, `cooling.gate-off` in the catalog).
+    "Gate settings", `COOLING.md` §8a, `cooling.gate-off` in the catalog,
+    bench PASS 2026-08-21 on dev image `20260821210903`).
     The fan gates, the pass-through of header limits, the coolant critical
     tier and the watch-only board temperatures follow on it.
 

docs/CAMPAIGN-LOG.md

@@ -3210,6 +3210,25 @@ YES" for that image's manifest (campaign `c-20260821182204-dc01`, exported
 2026-08-21T18:40:30Z, artifact sha256 `6f17f690...43273055`). No release is
 cut from it.
 
+## 2026-08-21: cooling.gate-off, first bench run
+
+PASS on dev image `20260821210903`, campaign `c-20260821213027-0b47`, at
+21:47:16Z: the coolant ceiling set to 6 C tripped `OVERTEMP` (hold, fire
+blocked) one second into its run session; set to 60 C the next session read
+`OK` with `gates_off` `["coolant_max"]` on `/cool/status` and `/status` and the
+run-start line in the forgectrl log; restored to 33/31 the third session read
+`OK` with nothing off, the settings back verbatim.
+
+The first attempt on the same image (21:18Z) failed in the test, not the
+engine: its M9 and the next M8 were 300 ms apart, the GRBL client reports
+level-triggered at 1 Hz and the engine samples at 1 Hz, so the engine never
+saw the session end and never re-read the ceiling; the restore-on-failure
+then rewrote the file without opening a session, which left the bench
+holding `OVERTEMP` against the test's ceiling until the next job. The fixed
+test (forgefirm f274eb1) waits for the engine's phase to leave `run` after
+every M9 and cycles a session after restoring; it was hot-deployed to the
+board for this run and is in the next dev image.
+
 ## Superseded status notes
 
 ### Shared machine services — remaining polish, as listed 2026-08-13