tegwick
7fa395e377
Some checks failed
ci / check (push) Has been cancelled
CB-EV-0025. T05 asks whether a comment actually got written during play,
unprompted. It has not been, and that is the pass's real acceptance test.
Everything built here is evidence the mechanism works; none of it is
evidence it gets used. I exercised it myself, which proves the plumbing
and proves nothing about the ergonomics -- the person who wrote the
feature is the worst possible witness to whether it is worth using.
Stated plainly rather than answered optimistically, because CB-WP-0022
built a register whose first run found ten answers nobody had collected:
this project's failures are about whether things get READ.
ADR-0007 D5 turned out to be the easy part. PointerFact::parse already
refuses any unrecognised field, so a comment could not reach the command
path even by accident. That is strictness at a boundary paying off years
early, and the clearest instance in this project of it being cheaper than
vigilance across one.
esc() held against its first hostile input, and the test asserts the
harder half: the player's words are still READABLE after escaping. An
escaper that dropped the text would pass "no script tag in the output"
while destroying the note.
The reflow cost no coverage probe -- all 41 pre-existing render tests
passed through a full restructure into two columns. CB-WP-0024 saw the
opposite when a probe was tied to a rendering ("17 remaining"), and the
contrast is the useful part: a probe that names a FACT survives a reflow,
a probe that names a PRESENTATION does not.
Running it changed the design for the third pass running, after
CB-WP-0024's role column and CB-WP-0025's K=2 infeasibility. The pattern
is consistent enough to state: the ADRs in this project are good at
deciding and poor at predicting, and the loop's value comes
disproportionately from the code loop rather than from steps 1-3.
Chaos window 2 closes with zero overrides in twelve declarations, so its
retirement condition is untestable -- final now rather than projected. The
window's verdict should be that d8 made the mechanism unevaluable.
Also recorded rather than dismissed: make all failed once at env-test and
passed on re-run. A cb-play server and several cargo processes were
running concurrently, which is the likely cause -- but "likely" is doing
work in that sentence and I did not chase it. A gate that fails
intermittently and is re-run until green is a gate being trained not to
matter.
Not built, and named: promoting a comment to a register note is still
manual.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
|
||
|---|---|---|
| .. | ||
| CB-EV-0001-game-kernel.md | ||
| CB-EV-0002-cost-accounting.md | ||
| CB-EV-0003-mechanical-work.md | ||
| CB-EV-0004-assertion-coverage.md | ||
| CB-EV-0005-instrument-the-table.md | ||
| CB-EV-0007-stage-0.md | ||
| CB-EV-0008-adaptive-gates.md | ||
| CB-EV-0009-inspectable-table.md | ||
| CB-EV-0010-render-port.md | ||
| CB-EV-0011-instrument-corrections.md | ||
| CB-EV-0012-execute-the-javascript.md | ||
| CB-EV-0013-the-inert-clauses.md | ||
| CB-EV-0014-the-drop-target.md | ||
| CB-EV-0015-legible-interaction.md | ||
| CB-EV-0016-the-browser-is-a-client.md | ||
| CB-EV-0017-budgets.md | ||
| CB-EV-0018-the-table-you-can-read.md | ||
| CB-EV-0019-import-the-edition.md | ||
| CB-EV-0020-solve-legality.md | ||
| CB-EV-0021-the-design-instrument.md | ||
| CB-EV-0022-collect-the-rulings.md | ||
| CB-EV-0023-the-table-you-can-watch.md | ||
| CB-EV-0024-could-we-have-won.md | ||
| CB-EV-0025-the-commentary-track.md | ||