clay-borg/trials
tegwick 25b18bddf7
Some checks failed
ci / check (push) Failing after 4s
CB-WP-0044: the page says which rules it plays
Reported as "I did a session and noted no changes" — correct, and the
fault was ours twice.

make ground passes no --variant, so the session was baseline, and
CB-WP-0043 deliberately leaves the baseline layout untouched because a
variant that redraws the baseline invalidates every prior look at it.

But the deeper defect is that nothing said so. The page named the round,
the step, the Lead, the scoring mode and the viewer, and never which rules
it was playing — GroundView did not even carry the variant. There was no
way from the screen to tell baseline from H1 from H2. A session that
cannot say which rules it is playing cannot report a rules change; the
player did the right thing and the instrument had nothing to tell them.

Now: variant on GroundView, `rules <id>` in the page header beside the
scoring mode, `rules <id>` in the inspector because a replay that cannot
say which rules produced it is the same defect in the other tool, and
make ground VARIANT=h2 so the capability is reachable.

Both coverage probes caught the new field independently — the render
crate's and cb-play's — the second time in two passes that they have
turned an addition into a legibility requirement instead of letting it be
silent state.

Verified by fetching the served page rather than by reading the code:
make ground VARIANT=h2 prints "rules: h2" and the page carries
"rules h2-scoped-problem-stress" with the scope labels; the baseline says
"rules ground-darvo-r0" and keeps its row.

Still open: nothing explains what a scope DOES, and the trial log header
does not record the variant either — the same defect one artifact along.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-08-08 17:47:31 +02:00
..
2026-08-06-2213.md fix: a click target wearing a drag affordance made the controls look dead 2026-08-06 22:25:06 +02:00
2026-08-06-2213.yaml fix: a click target wearing a drag affordance made the controls look dead 2026-08-06 22:25:06 +02:00
2026-08-06-2230.md fix: the controls sit below the log, and ending a session greys the page 2026-08-06 22:38:32 +02:00
2026-08-06-2230.yaml CB-WP-0029: the tokens on the table — declare and register 2026-08-07 09:45:41 +02:00
2026-08-06-2252.yaml CB-WP-0029 T01-T03: components you can count, and a supply that does not bind 2026-08-07 09:54:20 +02:00
2026-08-07-1252.yaml CB-WP-0031: the comment box outlives the game 2026-08-07 13:08:56 +02:00
2026-08-07-1558.md CB-WP-0032: the comments in the account 2026-08-07 16:09:36 +02:00
2026-08-07-1558.yaml CB-WP-0033: a game is the unit 2026-08-07 17:41:11 +02:00
2026-08-07-1612.md CB-WP-0033: a game is the unit 2026-08-07 17:41:11 +02:00
2026-08-07-1612.yaml CB-WP-0033: a game is the unit 2026-08-07 17:41:11 +02:00
2026-08-07-1829.yaml CB-WP-0035: a session that answers nothing 2026-08-07 20:31:32 +02:00
2026-08-08-0019.yaml CB-WP-0037 done: T03 classification and T04 evidence 2026-08-08 00:33:24 +02:00
2026-08-08-0104-2.yaml CB-WP-0039: a seat that does not regulate — and it changes H1's verdict 2026-08-08 01:08:40 +02:00
2026-08-08-0104.yaml CB-WP-0039: a seat that does not regulate — and it changes H1's verdict 2026-08-08 01:08:40 +02:00
2026-08-08-1648-2.yaml H2's ATTACK dynamics, and a construction hazard found while measuring them 2026-08-08 16:56:27 +02:00
2026-08-08-1648.yaml H2's ATTACK dynamics, and a construction hazard found while measuring them 2026-08-08 16:56:27 +02:00
2026-08-08-1734.md CB-WP-0044: the page says which rules it plays 2026-08-08 17:47:31 +02:00
2026-08-08-1734.yaml CB-WP-0044: the page says which rules it plays 2026-08-08 17:47:31 +02:00