- **The record itself, and the only one that caught the dip (hertz, 2026-09-09):**
  `.spt/preserved/hertz-leak-670-legs/disk-full-trace.log` — **139 samples, 11:52:46Z–13:57:07Z, one
  per minute**, max **238.41 GiB** @12:45:20Z, min **12.53 GiB** @12:12:45Z. Two samples fall under
  15 GiB — **14.85** @12:12:11Z and **12.53** @12:12:45Z — both inside the #209 leak lane's
  build-and-teardown window, i.e. AFTER a start floor would have passed the run at **136.15 GiB**
  (the window's first sample). Two caveats, both binding on any reading of it: **the true minimum is
  unbounded below 12.53 — the sampler cannot see between its samples**, and **it attributes nothing:
  hertz's own legs and the runner's CI job are indistinguishable in it.** It is the SECOND instrument
  on this incident and the only one covering the dip: doyle's 30 s trace, preserved at
  `.spt/preserved/ir90-free-space-trace-2026-09-09/free-sampler-12-13Z-to-12-28Z.txt`, runs
  12:15:37Z–12:31:10Z and so begins after hertz's reap — it records the RECOVERY, this one records
  the FALL. sha256 `d58ce838b677e62d4a017e77524f899fda81e7bacf73a0e2a05a1192e60abaf2`
  (doyle's, `8bdae01bc151597070d7011443a2cdc74614232dbc962faec1b1b1833c71f22a`).