max / quasi

Name the source a field consults as it is typed N14 and N8 asked for the same thing from two directions: a field that asks the server about its value while it is being written, one wanting pending/ok/taken back and the other a list of suggestions. Naming the two answers would have put two mechanisms in the vocabulary for one idea. The member names the SOURCE instead -- a route and how long the value must stand still -- and says nothing about what comes back, so a verdict and a suggestion list are the same member with two routes behind it. Where the answer lands is Action::replacing, which already said that about every other action. Each renderer answers it its own way. The webview emits the `keyup changed delay:Nms` the four measured sites spell by hand. The terminal gains Step::CallAfter, which is what its own comment said it could not have: it debounced nothing because "nothing in the description says a delay is allowed", and a number it picked would be one the webview disagreed with. The clock stays with the host there, same as the router does. egui holds the deadline in its View and asks egui to wake up for it. The accepted costs, so they are not re-argued: a field points at a route for the first time in the vocabulary, and a host with nothing to ask cannot honour one.