re: record that stale-instrument was run for the logger change, and returned nothing

R1 asks for tools/stale-instrument when an instrument improves. The draw
logger improved this iteration; all eight claims that <harness> killed are
about the SCREENSHOT harness -- polling cadence, x11grab latency, the
title/plate classifier -- and none of them ever used the draw logger, so
none re-open. Written down because 'ran it, nothing changed' and 'did not
run it' are otherwise the same absence.

docs/re/ui-splash-draw-pass.md

@@ -224,6 +224,26 @@ shaders and the register state and I would expect it to hold for every screen
 that uses the same three shaders — but that is a prediction, not a measurement,
 and the way to test it is the same census on the title and the menu.
 
+## R1 housekeeping — `tools/stale-instrument` was run, and the answer is "none"
+
+This iteration improved an instrument (the UI draw logger gained render-target,
+resolve and pixel-shader-constant fields), so R1 requires asking what that
+instrument had killed.
+
+```
+tools/stale-instrument harness      # 8 claims
+```
+
+**None of the eight re-open by this change.** All eight are about the *screenshot*
+harness — polling cadence, `x11grab` latency, the title/plate frame classifier,
+the locale runs — and the draw logger is a different instrument that none of them
+ever used. Recorded rather than left silent, because "I ran it and nothing
+changed" and "I did not run it" are indistinguishable in a corpus otherwise.
+
+The claims this capture *does* re-open are the four `render-vs-capture` and
+`our-reader` entries around the splashes, and they are addressed in the
+refutation section above rather than by the tool.
+
 ## What is NOT settled here
 
 * **Splash A's step size** — its rising run straddles dropped frames.