|
Some checks failed
ci / check (push) Has been cancelled
turned out to be T03. One table_svg: seats around an elliptical table starting at the BOTTOM -- the viewer sits nearest the reader, as at a real table -- Problems and both stacks in the middle, each seat's played card between it and the centre, relations drawn between seats. Two renderers were DELETED: relations_svg and piles_svg. The task said one table not two diagrams, and leaving the old ones would have meant drawing the same thing twice and letting them drift. No coverage probe cost, through a restructure that merged three diagrams and removed two functions. Second confirmation of CB-WP-0027's finding: a probe naming a FACT survives a reflow, one naming a PRESENTATION does not. CB-WP-0024's "17 remaining" broke on a rendering change; this far larger reflow broke nothing. The new control is per seat count -- no two seat circles closer than 70px at 2 through 6 -- asserted rather than eyeballed at three, which is the only count anyone ever looks at. T08 (CB-EV-0026). Seven of nine observations were engine defects, one was a design finding, one was already true and nobody could tell. Observations 4 and 5 both dissolved and had ONE cause: nothing on the page said how drawing works, so a player built a mental model to fill the gap and reported the gap as two feature requests. The import gap was worse than "one of nineteen" -- 5 of 13 columns read from the file we DID vendor, discarded at parse time for eight days. Rule coverage was 59/59 throughout. The gate measures whether rules are EXERCISED; nothing measures whether a player can READ the game, and nothing cheaply could, which is why the person playing it is the instrument. TWO GATES WERE WRITTEN FOR A SMALLER WORLD, and neither was wrong when written. edition-check compared one recorded digest against Problems.csv regardless of which file it described -- correct with one vendored file, comparing across files with four. And a cb-play test asserted the literal "game over" and went red when a won game said "solved", which was T06 working; it now asserts the heading against the OUTCOME and covers the no-outcome case the original never touched. Chaos window 2 closes with zero overrides in eleven declarations at d8. Third and final statement of it: d8 bought rarity by spending evidence, and a mechanism producing no data across a full window cannot be evaluated by that window. make all: exit 0. 57 render tests, 26 cb-play, loop-lint clean. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> |
||
|---|---|---|
| .. | ||
| CB-WP-0001-inner-loop.md | ||
| CB-WP-0002-cost-accounting.md | ||
| CB-WP-0003-loop-hardening.md | ||
| CB-WP-0004-mechanical-work.md | ||
| CB-WP-0005-assertion-coverage.md | ||
| CB-WP-0006-instrument-the-table.md | ||
| CB-WP-0007-session-shape.md | ||
| CB-WP-0008-ship-stage-0.md | ||
| CB-WP-0009-adaptive-gates.md | ||
| CB-WP-0010-consolidation.md | ||
| CB-WP-0011-inspectable-table.md | ||
| CB-WP-0012-render-port.md | ||
| CB-WP-0013-instrument-corrections.md | ||
| CB-WP-0014-execute-the-javascript.md | ||
| CB-WP-0015-the-inert-clauses.md | ||
| CB-WP-0016-the-drop-target.md | ||
| CB-WP-0017-legible-interaction.md | ||
| CB-WP-0018-the-browser-is-a-client.md | ||
| CB-WP-0019-the-am4-family.md | ||
| CB-WP-0020-the-table-you-can-read.md | ||
| CB-WP-0021-import-the-edition.md | ||
| CB-WP-0022-the-design-instrument.md | ||
| CB-WP-0023-solve-legality.md | ||
| CB-WP-0024-the-table-you-can-watch.md | ||
| CB-WP-0025-could-we-have-won.md | ||
| CB-WP-0026-collect-the-rulings.md | ||
| CB-WP-0027-the-commentary-track.md | ||
| CB-WP-0028-the-table-you-sit-at.md | ||