max / quasi

0.20.0: a table row offers what it does not show Cells::menu, the member Row has had since 5e02fbce. Absent on selected's stated grounds -- no table asked, and a member added because its sibling has one has no consumer to say what it should mean -- and audiofiles' file list is the consumer that ends that: draw_context_menu is 14 entries branching on node type over a described Node::Table. It takes no column and no renderer draws it in the grid. The webview emits the list row's own data-menu="row" so a host binds one gesture for both, under a table-row-menu class for the positioning. The TUI carries the acts on Spot::Row and counts a menu-only row as reachable, since in a terminal the menu is reached from the row and nowhere else. Submenus stay out: Vec<Act> is flat, matching Row::menu, and audiofiles' one nested entry wants a second consumer before Act grows a child list. Two things this turned up, neither about the member. quasi-immediate drew no menu at all, for Row either -- no arm, no comment, so audiofiles' detail pane has described tag-row menus that have never opened. It has one now, on Response::context_menu, collected rather than fired for the reason every other press in that file is. The rect it hangs on is the horizontal's own response and not ui.min_rect(): a list draws every row into one shared Ui, so min_rect grew per row and the fourth row's target covered the first four. quasi-tui's draw_table claimed only rows with an activate while focus.rs pushed a stop for activate, selected or menu. The claim counter decides which control draws lit, so a table of tickable rows left everything below it drawing the caret in the wrong place. Both now read the same predicate, with a test that fails on the old one. The template's version requirements were still 0.18, missed in the last bump; a fresh scaffold could not have resolved. Consumers forward-fixed to 0.20 in their own repos.