max / quasi

Add Slot::revealed_by: a region says which control and which value reveal it `079a011e`, ruled 2026-08-25 (wiki `quasi-vocabulary-findings`, "A region says what reveals it"): the condition lives on the region. A region names the control it watches and the value that brings it out, and every renderer evaluates that from what it already holds, with no request in it. The host with no cursor decided the shape. On a terminal a hidden region is not hidden the way a browser hides one, and the honest reading is "this region is not applicable right now", which is a property of the region. On the control, a terminal asking whether a section applies would have to search outward across every control on the screen. Rejected with it: a back-pointer at both ends, which costs two members to keep in agreement and a rule for when they disagree. `Reveal` carries the control name and a `Held`: anything, nothing, one value, or one of several. Empty is nothing on every host, so an unticked box and a cleared box are one answer, and `Reveal::satisfied_by` is the one place that says so. `Screen::holds` is the described half, walking the node tree exhaustively rather than over a wildcard so a container member that grows a body cannot quietly hide fields from every conditional region on the screen. quasi-webview emits `data-reveal`, `data-reveal-when` and `data-reveal-values` on the region and ships `reveal.js` to read them. A script rather than a hyperscript program for `fill.js`'s reason: the watched values are app text, and no emitted program is built out of that. No verb, no trigger, no target, because a reveal is not a request. A page served without the script shows every conditional region, which is the direction the rest of this renderer degrades in. The two client renderers leave the region out and say so together: `reveal.rs` in each answers once per drawing, and the terminal's focus walk reads that same list so the caret and the picture cannot disagree about how many stops a screen has. What was typed into a section the reader has since closed stays in the view and is still submitted, exactly as a browser sends the value of a hidden input. The eight measured sites are covered by a test that names each one: MNW's six `window.<name>` toggles, goingson's zone picker and its recurrence detail. Breaking, so 0.59.0, with the consumer pins moved in the same pass.