diff --git a/docs/analysis/attack-pass-2026-10.md b/docs/analysis/attack-pass-2026-10.md
index d57f30269..f6f3826b3 100644
--- a/docs/analysis/attack-pass-2026-10.md
+++ b/docs/analysis/attack-pass-2026-10.md
@@ -150,7 +150,12 @@ O-1.14 route (coordinator, 7 October 2026, 10:1x UK): no US laptop is due, so th
 rented 2019-class CPU host through the fleet agent, capped at two hours of rent; the Linux `igneum-pow` from the box
 (the same binary as the proxies) runs `bench --warps 50` for v2, mx8, mx8+sh256x27, dr368 and dr736 (the
 known-fail) on it; INCOMPLETE with the numbers so far if the cap lands first. The Windows exe was also built on the
-box for the day a laptop appears (1,009,675 bytes, sha256 fbed7538...e6c9).
+box for the day a laptop appears (1,009,675 bytes, sha256 fbed7538...e6c9). Outcome, 09:40 UK: no 2019-class CPU
+host stood up. Vast accepted and dropped five CPU-class rents within 30 s each (i7-9700K, i5-8500, Xeon W-2133 and
+W-2123) under the account's automatic new-account spend limit (support ticket open since 6 October), and RunPod has
+no 2019-class CPU pod; so O-1.14 reads INCOMPLETE on the box proxies today and stays a precondition of the freeze.
+Next try: the US laptop when it registers on the relay (the exe is ready), or Vast once the spend limit lifts; the
+bench script is staged and runs in minutes.
 
 Result (average, verified on the box): class v4 `mx8+sh256x27` runs 4.90 to 5.06 ms per warp cold on one EPYC
 9454P core (nice 19, taskset), 8.23 ms on the half-core proxy (both SMT siblings busy). Under 10 ms. Status