Address CR: timing table — mark K2 Turbo as historical, add K2.6 TBD row

aallan · claude · aallan · commit b35e4da6a225 · 2026-05-12T10:16:03.000+01:00
The 'Timing expectations' table in scripts/README.md still showed 'Moonshot K2 Turbo | ~1.5 h' after the migration, which mismatched the sweep recipe that loops over moonshot/kimi-k2.6. Both rows now appear: K2.6 with TBD pending the first sweep, and K2 Turbo kept with an explicit 'historical; SKU deprecated 2026-05-25' annotation so the prior real-world data point isn't lost.

Co-Authored-By: Claude Opus 4.6 &lt;noreply@anthropic.com&gt;
diff --git a/scripts/README.md b/scripts/README.md
@@ -109,10 +109,12 @@ Rough per-model totals observed on v0.0.9 (60 problems, 2026-04):
 | Claude Sonnet 4 | ~15 min |
 | GPT-4.1 / GPT-4o | ~10–12 min |
 | Moonshot K2.5 | ~3.5 h (slow provider; Aver especially) |
-| Moonshot K2 Turbo | ~1.5 h |
+| Moonshot K2.6 | TBD (no sweep against this model yet — see #68) |
+| Moonshot K2 Turbo *(historical; SKU deprecated 2026-05-25)* | ~1.5 h |
 
-The full six-model sweep is dominated by the two Moonshot models. Expect
-5–8 hours end-to-end.
+The Moonshot models dominate the sweep wall-clock; expect 5–8 hours
+end-to-end. K2.6 timings will be filled in after the first full sweep
+once we have data to attribute.
 
 ### Output files
 
