coulomb/clay-borg
4
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

CB-WP-0010-T02: GR-E03 gets a scenario

Browse source 
COMMON PROBLEM was the only scoring mode with no scenario — implemented
since CB-WP-0001, referenced by nothing, and would not have failed if
deleted. Five players, where the threshold is reachable at all: every
Problem claimed for a total of 10 against 9, and the winner is decided
by Blame rather than by claimed value — P4 claimed the highest Problem
and loses to P3 because two Blame tokens sit in front of them.

No defect was found on the first execution of that path, which is worth
saying plainly rather than implying the scenario was hard-won.

The assertions were mutation-checked three ways instead of trusted,
because a dot-path expectation that silently fails to resolve would
report PASS: a wrong personal score, a wrong mastery, and removing the
Blame from the fixture each turn it red.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This commit is contained in:
tegwick 2026-08-02 02:16:51 +02:00
parent d07caca22b
commit 82fdb85173
3 changed files with 91 additions and 4 deletions
Download patch file Download diff file Expand all files Collapse all files

8
workplans/CB-WP-0010-consolidation.md
View file

@ -46,7 +46,7 @@ is what it has been doing for two passes.
```task
id: CB-WP-0010-T02
status: todo
status: done
priority: high
state_hub_task_id: "89355b0a-9fc7-4d69-a27e-d3c94ff0730f"
```
@ -63,6 +63,12 @@ is actually reachable (10 available against 9).
**Finding a defect here is the likely outcome and is the point** — this
is the first execution of that code path.
**Done 2026-08-02.** `gr-e03-common-problem.yaml` passes, and **no
defect was found** — GR-E03 scored correctly on its first execution.
The assertions were mutation-checked three ways rather than trusted:
a wrong personal score, a wrong `mastery`, and removing the Blame from
the fixture each turn it red. Every scoring mode now has a scenario.
## Task: record CommitWindow's second failed use
```task