max / quasi

Say when a selection is live, and what a press on it meant quasi 0.78.0. `Cells::current` was the only thing that lit a row, so an app whose list carries a real multi-selection could not draw one: audiofiles' `Cmd+A` over five hundred samples looked exactly like a click on one. And nothing could say a press was ctrl-held, so the only multi-select it had left was the keyboard. Picking eleven kicks out of four hundred by hand -- close to what that app is for -- could not be done at all. `1894e95d`. Two members, and the split between them is the point. `Cells::chosen` and `Row::chosen` say the row is part of a selection already in force. The third state, and three-valued for the reason `selected` is: a ctrl-click lands on an *unchosen* row, so a renderer has to know that row can join a set before anything is in one. It is never a checkbox -- a box is the affordance for staging a set, and this set is not staged -- and the app owns the set rather than the renderer holding a copy that can disagree. `Choosing { Only, Also, Through }` is what a press meant, said by the renderer because the idiom is the host's, travelling under `Node::CHOOSING`. It looks like input state, which every ruling here has refused to carry, and the difference is that it is not the gesture but its *meaning*: a description carrying "ctrl was held" would be naming a keyboard, and this names an intention a touch host can honour with none. The test it passes and a modifier would not is that a terminal can implement it. The three renderers: - egui highlights a chosen row through the same `Body::selected` predicate `current` already used, and reads command/shift off the frame. Shift wins when both are held, which `Choosing` rules on rather than leaving to each renderer. - The terminal marks chosen rows in the gutter it already draws ticks in, and binds Enter to `Only` and Space to `Also`. `Through` gets no key: `Key` carries no modifiers, and widening it is a change to every host driving that renderer. Stated rather than invented around. - The webview emits `row-chosen`/`table-row-chosen` and `aria-selected`, which is the one place ARIA's own names line up with the vocabulary's distinction, and computes the modifier at click time through a `js:` `hx-vals`. `Anchor::Selection` resolves against a live selection now and not only against staged ticks, which is what it was written for: audiofiles was the measured consumer and could not take it. ALSO CARRIED, and not mine: an uncommitted `Outcome::Started` / `Slot::consults` change and the makeover-layout 0.39 cascade were in this working tree from a parallel session, interleaved with this in `screen.rs`. They cannot be separated by file, so they land here. Split them out if the history matters.