CB-WP-0008-T03: prove the 2-6 player range

GR-O01 states 2-6 players; every scenario in the corpus was 3-player.
Now all five counts play to GameEnded under both policies and reproduce
at the same seed, with scenarios at both boundaries and the CLI
transcript run at 2p, 3p and 6p.

Nothing broke — the rules are seat-count-generic. What the boundaries
exposed is arithmetic: with the standard preset's placeholder Problem
values (value = priority), the best total any game can reach is 3 at 2p,
6 at 3-4p, 10 at 5-6p, against GR-E01 thresholds of 5, 7 and 9. Group
success is unreachable below five seats regardless of play, and no
scenario noticed because none had played to scoring with everything
claimed.

GR-S01 calls the fixture a stand-in for scenario Problem data, so this
is evidence the stand-in is not neutral, not that GR-E01 is wrong. It is
pinned by a passing scenario, an arithmetic test, and a provisional
marker owned by ground-game so it ages in `make coverage`. The test
states its own delete-by: it is expected to fail when Problem values
become real data, and that failure is the signal to delete it.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This commit is contained in:
tegwick 2026-08-01 15:20:04 +02:00
parent 25531e9d01
commit d97e8e825d
7 changed files with 289 additions and 28 deletions

View file

@ -97,7 +97,7 @@ records as a scenario and as a `.cbreplay` bundle. Notes in
```task
id: CB-WP-0008-T03
status: todo
status: done
priority: medium
state_hub_task_id: "438d21b7-98f3-43c0-b17f-6ae32bf176bd"
```
@ -112,6 +112,12 @@ all-bot game at each, and report what breaks. Finding that 2p or 6p does
*not* work is a legitimate and likely outcome — record it rather than
quietly narrowing GR-O01.
**Done 2026-08-01.** All five counts play to `GameEnded` under both
policies and reproduce at the same seed; three new scenarios; and the
finding is arithmetic, not a crash — GR-E01's threshold is **unreachable
at 2, 3 and 4 players** with the placeholder Problem values. Table in
`history/260801-cb-wp-0008-log.md`.
## Task: evidence and retrospective
```task