test(web): stabilize and refresh the aria goldens for the speed readings

The TTFT and tok/s readings divide by measured wall time, so they are not reproducible: the same replayed scenario yielded 69 and 70 tok/s on consecutive local runs, and a 3 ms replayed stream reads 26333 tok/s. Baking those into committed goldens made the Web lane flaky by construction, and the goldens for the readings themselves were never refreshed. Three fixes, then a refresh: The footer's decorative dots are `aria-hidden`, so the readings concatenated into one accessible string — `Ran for 13sTTFT 0.2s12 tok/s`. That is a real defect on its own (a reader hears one run-on instead of three facts) and it also denied `{{duration}}` the word boundary it matches on, so even the previously-stable `Ran for` duration started leaking raw. The separators now carry flanking spaces. `normalizeAria` gains `{{throughput}}` beside `{{duration}}`, and its duration alternation accepts the stats line's compact `2m42s` as well as the message-chrome template's `2m 42s` — the compact form had no pattern at all, which is why `LLM 382m39s` survived the first refresh. Refreshed 17 goldens. They also record that the stats line's `LLM` group now renders at all: it folds assistant `timing`, which the live transcript adapter only began attaching in this branch, so the group was previously dead in Chat. Verified by running the lane in replay three times after the refresh: 41/41 files green each time, goldens untouched. Before this change two consecutive runs disagreed on both the values and the failure count.
2026-08-05 17:55:49 +08:00
parent 8745365547
commit 96c44c83d4
22 changed files with 69 additions and 37 deletions
@@ -27,3 +27,5 @@ The stats line reuses the same step reading in its window fold: `deriveStats` ac
 ## Consequences

 A settled in-window turn's footer reveals `TTFT`/`tok/s` on hover after the wall time, and the stats line shows window-average latency and throughput beside its wall times, all without new session events or host changes. Metrics degrade by omission: providers or steps without timing or usage samples drop individual figures rather than rendering zeros. Older history outside the loaded window stays uncounted, recorded in the package README's stats-line limitation.
+
+Both readings divide by measured wall time, so neither is reproducible: the same replayed scenario yielded 69 and 70 tok/s on consecutive local runs, and a 3 ms replayed stream reads 26333 tok/s. The Web aria goldens therefore normalize throughput to `{{throughput}}` beside the existing `{{duration}}`, and the footer's decorative separators gained flanking spaces — without them the readings concatenate into one accessible string (`Ran for 13sTTFT 0.2s12 tok/s`), which both loses the reading boundaries a screen reader needs and denies `{{duration}}` the word boundary it matches on.