CB-WP-0017: legible interaction, and the chaos window's verdict

Provenance (tier M, structural S, chaos d4=4 -> OVERRIDE drawn M):
the maintainer could drag after CB-WP-0016 but could not tell what was
pickable, held, or droppable. Underneath that, the page was WRONG about
which moves exist: 9 legal commands rendered as 5 cards each claiming
all three target kinds, from a const string in the emitter. Investigate
is legal on problems 2 and 3 but not 1; Solve on 1 but not 2 or 3. The
live page now says 'Solve onto problem 1'.

ADR-0010 restates control 5, which this work would otherwise have
outgrown in silence: every game fact the page acts on must arrive from
Rust as data; the script may read, match and render it, never compute,
infer, filter or default one. The survey's real finding is that the
permitted and forbidden designs are indistinguishable from outside, so
the vocabulary grep is demoted to a cheap first line and two behavioural
properties become the controls -- the highlighted set EQUALS the set
Rust emitted, and anything the page marks legal must resolve. Both
mutation-proven; the derive-legality mutation produces a plausible
highlight (seat-0,1,2 where only seat-1 is legal) and is caught.

Visible now: .pick resting shadow, .held on the grabbed element, .dropok
on every legal target including BOTH drawings of a seat, and a ghost
following the pointer. Nothing perceptual is verified and ADR-0010 D5
says so.

The DOM stub now models classList/querySelectorAll/createElement and
builds its node set from the real emitted page. Trap recorded: QuickJS
fixes its stack limit at Context creation relative to that frame, so a
helper returning a Context makes every later eval report
'SyntaxError: stack overflow'.

CHAOS WINDOW CLOSED, 12 declarations, 2 overrides, one each way. Both
changed the outcome, so the retirement condition is not met. Verdict:
keep, and recommend d4 -> d8 with a second window of 12 -- that is a
change to the loop's own constraints and is owed to the next declaration
as tier-M work, not made here.

CB-EV-0014 corrected: it quoted CB-WP-0015 at $15.14/136 and called it
the first settled figure quoted. Now $22.70/166. The number had been
read during CB-WP-0015 itself, so there are two defects -- the boundary,
and quoting from memory instead of re-running the instrument.

make all exits 0.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

evidence/CB-EV-0014-the-drop-target.md

@@ -113,14 +113,21 @@ would have missed it.
 
 | pass | kind | responses | cost | $/response |
 |---|---|---|---|---|
-| **CB-WP-0015** | product | 136 | **$15.14** | 0.111 |
+| **CB-WP-0015** | product | ~~136~~ **166** | ~~$15.14~~ **$22.70** | ~~0.111~~ **0.137** |
 | CB-WP-0016 | product | *provisional — not quoted* | | |
 
-CB-EV-0013 §5 found the self-quoting rule fixes the wrong boundary: a
-pass's window runs to the *next* pass's first commit, so CB-WP-0015's
-figure was still open when quoted. It is quoted here after CB-WP-0016's
-declaration commit closed it, which is the first figure this project has
-quoted at a boundary that had actually settled.
+**CORRECTED 2026-08-02 (CB-EV-0015 §6).** This file originally reported
+CB-WP-0015 at **$15.14 / 136** and claimed that figure was *"the first
+this project has quoted at a boundary that had actually settled."* **The
+claim was false and the number was wrong.** $15.14/136 was read from
+`make status` during CB-WP-0015 itself and carried forward — it was that
+pass's own in-flight figure, which is precisely what CB-EV-0012's rule
+exists to forbid. Measured after CB-WP-0017's declaration closed the
+window: **$22.70 / 166**, higher by 50%.
+
+So the defect is not only the boundary CB-EV-0013 §5 identified. It is
+that a figure gets *read once and quoted later*, and a number read earlier
+in a session is an in-flight number no matter which pass's name is on it.
 
 ## 6. Open