max / quasi

0.37.0: a verb can ask for a value before it fires `033ff3ca`, the last open half of the selection gap. `Screen::selecting`, `Row::ticking` and `Act::over` named the set on 2026-08-12 and `Field::over` added the picker applied to it on 2026-08-15. What nothing could say is the shape Max's 2026-08-18 ruling left open: a verb that needs a value first. MNW's content table has two, Set Price and Add Tag, each revealing one box behind the button. It is `Act::asks`, a list of fields on the control. `Act::confirm` is the yes/no shape of the same moment, a question raised after the press and before the call; this is the shape that comes back with a value. Said as a `Node::Form` the verb is lost, since nothing pairs the box with "Set Price" but where the two sit; said as a route answering a form fragment it is a round trip for a question whose shape the screen already knows, and a fragment is markup a terminal and an egui host have nowhere to put. Each asked field is sent under its own name, as a submit sends it, plus the ticks under `Node::TICKED` when the control acts over a selection. `Field::as_asked` is what every renderer draws: the field with `changes` and `over` dropped, because the press answers it and a write of its own would send the value twice. `consults` survives, since asking whether a slug is taken is a question about the value. The disclosure is each renderer's. quasi-webview uses `details`, which is the browser's own and needs no script, and the commit control inside it gathers by `closest details`. quasi-tui and quasi-immediate draw the boxes beside the control: neither has a popover, and standing in the open beats a disclosure invented here. Two bugs in quasi-immediate fell out of the tests, both from the 2026-08-12 half. `act_node` read `Act::over` from a parameter both callers passed `None` for, so no count was drawn, a press over an empty set went through, and no tick left with the call. `gathered` handed the selection's name to `View::gathering` as the name the values travel under, so it sent `chosen=i-1` where the other two renderers send `ticked=i-1`. Neither path had a test that pressed anything; both do now. quasi-webview takes makeover-webview 0.52, which MNW's makeover-build 0.47 already required. The two pins conflicted on the `links` key, so the server could not resolve at all until this moved.