R-267 closed: 26.2s -> 5.4s cold / 0.14s warm, and two corrections to my own measurements

Registry pruned to the newest 10 per package on the operator's confirmed rule. 33 deletions, all
HTTP 204; the live-vouched golden 0.210.0, agent 0.128.0 and floor 0.127.0 were asserted into the
KEEP set BEFORE any DELETE was issued and verified still fetchable after.

TWO CORRECTIONS TO WHAT I REPORTED EARLIER, both recorded rather than quietly dropped:

1. 'Only 50 generic versions exist' was NOT a count, it was a PAGE LIMIT. ?limit=1000 returns at most
   50, and the 50 I measured was exactly the cap. Three older agent versions (0.81.0/0.80.0/0.79.0)
   only became visible after the first 30 deletions moved them onto page one. An unpaginated listing
   is not evidence of a total — this repo's own 'an empty listing is not evidence of emptiness' rule,
   walked into while measuring it.

2. The operator's 'reduce the number of artifacts' was the better call and my measurement said
   otherwise. I reported it helps sub-linearly and is not the lever. Measured after: trimming to
   10+10 took the COLD load from 13.4s to 5.4s, a 2.5x improvement on exactly the path the memo
   cannot help, because the fan-out is per-version.

drill-r50 runs agent 0.113.0, now deleted; flagged before deleting, disposable nested drill VM, only
its re-download path is gone.

STATUS.md

@@ -92,10 +92,11 @@ being readable.*
   move has never survived a reboot; on PASS, 34 GB comes back. *(R-209a)*
 - **Backup scripts on DooPlex are unversioned host state** *(R-231)*, and the instruction-file
   follow-ups each need a decision rather than an edit *(R-229, R-230)*.
-- **The Configuration page is fixed: 26 s → a quarter of a second.** It was never hashing anything —
-  the hashes are already stored and simply read. It was making 42 calls one after another. Now they
-  overlap, the connections are kept, and the answer is held for a minute, so you see ~0.25 s except
-  at most once a minute (13 s on that one load). *(R-267 — closed.)*
+- **The Configuration page is fixed: 26 s → 0.14 s.** It was never hashing anything — the hashes
+  are already stored and simply read. It was making 42 calls one after another. Now they overlap,
+  connections are kept, the answer is held for a minute, and the old artifacts are gone. Worst case
+  is 5 s, once a minute at most. **Your instinct to prune was right and my measurement said
+  otherwise** — trimming to ten of each halved the slow path. *(R-267 — closed.)*
 - **I printed a live access token into a session log** while setting up today's drill, and I am
   telling you rather than quietly rotating it. It only opens the agent's private channel to one
   demo guest, on a wire that exists solely between that host and that guest — not reachable from