max / quasi

0.49.0: an interval, through the whole stack `Field::upper_name` and `Field::upper_value` mirror makeover-layout 0.34.0's `FieldKind::Interval`, and the three renderers draw the pair. The mirroring is what the cascade is for. `quasi_router::Field` declares itself independently of `makeover_layout::Field`, so a member that stopped at one of them would be silently absent everywhere downstream; `with_layout` is where the two meet and where a missing member shows up as nothing drawn. `upper_value` is the half a `pairs_with` member would not have paid for. A refusal has two values to hand back, and without a second one it returns the low end and drops the high one, so the user retypes half of an answer they already gave. `refilled` reads both names, and an absent end stays absent: "over 120 BPM" is an answer rather than a half-filled form. Renderer side, each host draws what it has. quasi-webview fills `Value::Between`, quasi-tui `Held::Between` off the view's two buffers, quasi-immediate `Filling::Between` off two of its own. The last of those also fires `changes` from either end with both ends in the payload: a handler reading only the box that moved would narrow the filter to a single bound every time either one was touched. `checkbox_node` and `upper_moved` are `field_node` split where the shapes genuinely differ, which is what kept it under the line-count lint.