max / quasi

0.27.0: a consult says how little is too little to ask about N8's two comboboxes measured against the member that landed for N14. Both refuse to ask under two characters and neither route does: MNW's tag-suggest and search-suggest handlers guard emptiness and nothing else, so a described field without the floor asks them on the first letter -- an ILIKE 'a%' over every tag, project and item in the catalogue, which is the query the floor exists to refuse. So Consult carries two numbers rather than one. `after` says the value has stopped moving; `at_least` says there is enough of it to be worth asking about. Both are the description's for the same reason, and the corpus disagrees about both: the four wizard fields wait 500ms and ask about a single letter, because one letter can already be taken, while the two comboboxes wait 150ms and 200ms above two characters. `Consult::asks_about` states the rule once instead of three times. The count is characters and not bytes, and the terminal is where that difference is a wrong answer rather than a slow one. Each renderer answers it in its own terms. The webview puts the floor on the event rather than beside the delay, since htmx takes the filter first and the modifiers after, and reads `event.target` because the trigger sits on the wrapper while the value sits on the control inside it. The terminal returns Idle: nothing is outstanding there, the wait belonging to the host, so a keystroke under the floor costs nothing. egui holds a deadline, so deleting back under the floor cancels it rather than letting it fire against a value too short to ask about. Forward-fixed in the same pass: MNW server, goingson, audiofiles.