v1.36.289

UI review questions: each of the five questions in a review packet now asks the reviewer to read every visible string and accessible name, not only scanner candidates, and to decide whether it speaks to the user or to the builder. Each gives concrete cues (requirement sentences, build or fallback narration, preview framing, criteria such as "within 3 seconds", raw values) and names the case that is not a finding. On the 324-surface held-out corpus a Codex reviewer separated leakage from clean copy perfectly with both the previous and the new questions (180/180, 0/144 false alerts), so no detection gain was measurable there.

Browser collector: the placeholder of a visible text field is collected as its own dom-placeholder surface and scanned as the placeholder attribute. Chromium drops it from the accessible name once aria-label or a label names the field, so <input aria-label="Email" placeholder="TODO: …"> was never scanned. The field's value is still never read, a placeholder already used as the accessible name is not collected twice, and hidden, transparent, zero-size and non-text controls contribute none.

ui-boundary-browser-probe.js --cdp (npm run test:ui-boundary-cdp) runs the real-browser controls over plain CDP against an installed Chrome or Edge (Node 22+), without Playwright. In headless Chrome 154 and Edge 154 all 91 checks pass, including the 22 existing real-browser controls, which had never run on this machine, and 5 new placeholder controls.