max / quasi

Field::consults hears a select, and a discrete question waits for nothing Decided in quasicoherent aeb44860 (Max): grow the member, do not add one. Field::consults and Slot::consults are one idea at two scopes, and only the region's heard a discrete control. The field's question was hung on `keyup changed`, which a select never raises: a pointer releases no key over one. Slot::consults had already met this -- MNW's fee calculator has a radio group its four number boxes sit beside -- and answered it with `input`, which fires for a radio, a checkbox, a select and a slider, and for typing as well. So the webview picks the event from the control rather than assuming one. `typed_into` is the question, and it is deliberately not the offers_options/takes_files/offers_themes triple the three renderers already share: that one asks whether a value is complete the moment it changes, and a range answers no to it while still being something nobody types into. An unknown kind falls to `input`, since it is the wider event of the two. The wait stays the description's. Consult::at_once is the constructor a control chosen in one gesture wants -- it is at its next value or its last one, never on the way between them -- and zero is a real number for it rather than a missing one. Not implied by the kind: a radio group inside a Slot::consults waits on purpose, and a kind deciding the wait would be a third party to a question the description and the renderer already split. The other two renderers needed nothing. quasi-immediate keys the deadline on the buffer moving, which a select does, and quasi-tui asks after any key that reaches the field; both were already right for the reason the webview was wrong -- neither has an event named after a keyboard.