max / quasi

One question inside a form can say what reveals it `079a011e` put the condition on the region and that is the shape for a block of several things. goingson's event form, the consumer it was ruled for, needs it for exactly one box: `initTzKindConfig` shows "Anchored to" on one of the three zone kinds, and that box has to sit inside the form it submits with. A form's questions are a flat list, so there was nowhere to put the fact. `Field::revealed_by` is the same `Reveal` on the thing revealed, which is the direction the ruling was made in: what it refuses is the condition living on the watched control, and that is refused here too. - quasi-webview draws the question inside a `field-reveal` box carrying the three `data-reveal` marks, so `reveal.js` settles it exactly as it settles a region and the control stays inside the form. - quasi-tui and quasi-immediate leave it out, which is what both already do with a region that does not apply. `reveal::hidden` answers regions and questions in one walk and returns one `Hidden`, so the drawing, the height arithmetic and the focus walk cannot disagree about how many stops a screen has. A question that stopped applying keeps its value and still submits it, matching a browser sending a hidden input and matching what the client renderers already do with a closed section. Nine tests.