max / quasi

0.41.0: a control in a table cell is reached by stepping into the row `27f2331e`. Thirty table rows across the MNW templates carry a control in a cell, in 25 files, and a terminal could draw every one of them and reach none. The reason is layout: `makeover_tui::table` decides column widths, drops the columns a narrow window has no room for and answers no coordinates back, so nothing in quasi-tui knows where in a row a button ended up, and a focus order is a list of places the caret can stand. Max ruled it on 2026-08-18: **the row is one focus stop, and a key enters it and cycles the controls inside**. No coordinates, and no new public surface on a published makeover-tui. Per-cell rects stay available underneath this later without changing what a user does. The open half of the ruling was which key, and it is Right and Left. Enter is taken -- `Cells::activate` already means "this row opens", and every measured table with a control in a cell also opens its rows -- and Right and Left are the keys a grid is walked with everywhere else. They mean this before they mean the region they move: the caret standing on a row with controls in it beats the screen-wide search that arm falls back to, so a table inside a carousel steps between frames from any stop but that one. The smaller cost of the two, because the frames are reachable from everywhere else and the row's controls are reachable from nowhere else. Escape steps out before it dismisses or goes back, and the short circuit is what keeps one press from doing two of the three. `Spot::Row` gains `inside`, populated only for a table row: a list row's run is walked straight after the row, so its controls are stops of their own and there is nothing to step into. `View` gains the eighth thing a browser was quietly providing, `inside: Option<usize>`, held beside `focus` rather than folded into it so that nothing counting reachable things has to know a table is different. A control the caret has stepped onto draws with the focus style inside the row's own highlight, which is what the two-step has instead of a ring around a rect. `focus.rs` and `draw_table` now decide a row's reachability with one function (`row_reachable`) and pick the lit part from one list (`inside`), because that pair has drifted before: the walk and the count disagreeing shifts every stop below the table by one. A row that neither opens nor ticks is a stop now when its cells carry a control, which is the third case and the one this task was filed for. Not reachable inside a cell: a disabled control, as everywhere else, and an `Act::asks` that wants boxes a cell has no room to draw -- a stop on that would fire it with nothing gathered. quasi-webview and quasi-immediate need nothing. The browser builds the tab order from the document, and egui's cell controls are real widgets it focuses itself.