docs: the SoC under a full core, measured; the heatsink question closes

CAMPAIGN-LOG gains the 2026-08-24 drill: five minutes of openssl speed on
the one core over the live camera stream, 30 C chassis, plateau 70.8 C
with no throttle and every cooling device at state 0. BRINGUP's facts bank
drops its open question (whether ForgeFIRM's load wants the heatsink the
factory never fitted) for the measured fact: 14 C of headroom to the
passive trip under full load, a hot-chassis case above roughly 44 C.

Docs only, outside every layer; no acceptance consequence.

docs/BRINGUP.md

@@ -714,9 +714,13 @@ is committed.
   both GPU cooling devices; the critical trip is the kernel's orderly
   poweroff. A throttle slows the engine, the camera and the protocol thread
   before the step stream (the ring is in hand). The factory board carries
-  **no heatsink or fan on the SoC**, only the mounting holes for one; the
+  **no heatsink or fan on the SoC**, only the mounting holes for one, and
-  factory's load never needed it, and ForgeFIRM's may, which is what the
+  needs none: under a full core for five minutes on top of the live camera
-  per-job SoC range and the throttle log line are there to show.
+  stream, in a 30 C chassis, the bare die plateaus at **70.8 C**, 14 C under
+  the passive trip, with the core at 996 MHz and no cooling device off
+  state 0. The die-to-chassis delta at full load is about 41 C, so the
+  passive trip is a hot-chassis case (above roughly 44 C), not a load case.
+  The per-job SoC range and the throttle log line are the running record.
 - **Fan speeds at the cut profile** (exhaust duty 65535, intake 43278, air
   assist 1023; sampled at 1 Hz over 120 s from idle, the exhaust duct's
   inline booster fan off): exhaust **11640 rpm** steady (spread 11444 to

docs/CAMPAIGN-LOG.md

@@ -4020,6 +4020,31 @@ status section is the record of what changed). Their texts, as they stood,
 are in "Superseded status notes" below; what stays open went into BRINGUP
 items 12, 13, 16 and the new item 20.
 
+## 2026-08-24: the SoC under a full core, and where it settles
+
+The die read 65.6 C (150 F) with the camera stream running and nothing
+else, in a 30 C chassis, which was enough of a number to ask what a full
+core does to it. The drill: `openssl speed -seconds 50 sha256` on the one
+core for 300 s, on top of the live stream, cloud mode at idle with the
+laser locked, a monitor sampling the thermal zone, `cpufreq-cpu0`, both GPU
+cooling devices and the load average every 5 s. The die climbed 2.9 C in
+the first 30 s and 4.6 C by 2.5 minutes, then sat at **70.8 C (159 F)** from
+3.5 minutes to the end, at 0 percent idle and a load average near 3. No
+cooling device left state 0, the core stayed at 996 MHz, `/status` read
+`soc_throttle 0` throughout, and the driver's grade line in dmesg is the
+one the facts bank quotes: `Commercial CPU temperature grade - max:95C
+critical:90C passive:85C`. Thirty-five seconds after the load ended the
+die was back at 67.9 C.
+
+Read: the bare SoC, no heatsink, holds **14 C of headroom to the passive
+trip and 19 C to the poweroff** under the worst load the one core can
+produce, in a 30 C chassis. The die-to-chassis delta at full load is about
+41 C, so by arithmetic, not measurement, a chassis above roughly 44 C is
+what reaches the passive trip; the load alone does not. The facts bank's
+open question, whether ForgeFIRM's load wants the heatsink the factory's
+never did, closes with this entry: it does not. The per-job SoC range and
+the throttle log line stay as the running record.
+
 ## Superseded status notes
 
 ### Shared machine services — remaining polish, as listed 2026-08-13