max / quasi

Cap a run in the terminal and in egui, so a row is a line again Settles 7bfb554a: Flow::Tight is a cap and not a default reading. A row is an inline run and the rows around it are relying on that, so a part that grows without bound is a block wearing a run's clothes. Both renderers gave a row as many lines as the words needed. quasi-tui now gives it row_lines(row) -- the max of its parts' budgets, because parts here share one wrapped flow rather than stacking the way a webview's spans do, so a part asking for two lines is asking the run for a second line. quasi-immediate puts a text leaf through a LayoutJob with max_rows, which is the only way egui counts rows; max_width comes off the Ui, or a job stays infinitely wide and the budget silently does nothing. Both mark what they cut. The webview never had to: -webkit-line-clamp writes the ellipsis itself. The terminal spends the last cell of the last allowed line on it, and egui gets it from overflow_character. What this changes for a consumer: audiofiles is the one shipping app rendering described rows through egui, and a filename too long for the pane now elides on one line rather than wrapping onto three. That is the intended reading of a row. 0.22.0 rather than a patch. Nothing in the API moved, but every described list in a terminal or an egui pane draws differently, and the pin is how a consumer records which side of that it was written against.