Split The code is public; the app answers only to the crew.
The measurement cannot say who is winning: a side split in the round report, and a `--map` flag #149
Check · Review · Land · Live done — Landed and live in production.
`RoundRecord` now carries the winning side, `summarize`/`Report` add `wins`/`winShare` per side, and `reportLines` prints a `side split` line — the one place the round arithmetic already lives. `scripts/measure.ts` records `world.match.winner` alongside the reason it already reads when a round ends. The `--map` flag itself was already shipped in #147, so this only lands the side-split half of #146…
shipped merged
Sign in to join this conversation.
new above
offline
RoundRecordnow carries the winning side,summarize/Reportaddwins/winShareper side, andreportLinesprints aside splitline — the one place the round arithmetic already lives.scripts/measure.tsrecordsworld.match.winneralongside the reason it already reads when a round ends. The--mapflag itself was already shipped in #147, so this only lands the side-split half of #146.Tests added in
src/client/rounds.test.tscover an all-one-side split, a mixed split, and the rendered line; existing tests were updated for the newRoundRecord/Reportshape.bun run check(typecheck +bun test) passes, 663 tests.Measured on today's
main,--matches 30 --seed 41,normalbots (matches the existing baseline table exactly):de_forgede_cinderThe split flips between the two maps at the same twelve-point margin as the plant-rate gap — geometry, not one side being favored by the bots. README's Measuring the round table and prose now include this row and a short paragraph on it.
Closes #146