diff --git a/docs/qa-modes-bench-2026-04-30.md b/docs/qa-modes-bench-2026-04-30.md
index 8e41304..341f284 100644
--- a/docs/qa-modes-bench-2026-04-30.md
+++ b/docs/qa-modes-bench-2026-04-30.md
@@ -72,7 +72,9 @@ Fix landed in commit `f23d3a3`: pass `stop=["\n\n"]` to vLLM in JSON mode. Well-
 | baseline (no improvements) | morning n=3 | 31 | 14 | 26 | **19** | 38 |
 | post-retry + trim-and-verify | midday n=3 | 31 | 16 | **33** | 0 | 54 |
 | post-pointer-ID switch | evening n=3 | 27 | 15 | 31 | 0 | 56 |
-| post-stop-sequence | (in progress) | — | — | — | — | — |
+| post-stop-sequence | late-evening n=3 | 29 | 14 | **37** | 0 | **60** |
+
+JSON mode net: 26 → 37 STRICT (+11), 19 → 0 errors, 38 → 60 grounded (+22) over the day. Strict-rate climbed 39% → 56% (+17pp). Each of the four improvements addressed a named failure mode surfaced by the prior bench.
 
 Each step in the journey was a fix to a specific failure mode named by the prior step's bench. The methodology delivered: name the failure → fix in code → re-bench → confirm or surface the next failure.