max / quasi

Retire Node::Select; a tab strip is a region showing one child Decided in quasicoherent e9f61b46 (Max): one way to describe a tab strip. Node::Select had one tenant left in the tree and one in this repo's own scaffolder template, and no renderer honoured the distinction between its three Selector kinds -- quasi-immediate drew Segmented, Tabs and Toggle identically. Every former site passed None on every option, so the per-option destination the member was ruled in for was unused everywhere. The move was not free, and the gap is what most of this commit is. quasi-immediate read neither Slot::showing nor Slot::label: region_body walked the whole body whatever the description said, so a described tab group came out as every panel stacked with no strip. audiofiles is the egui host and the last tenant, so converting it needed the renderer first. node::showing_body is that renderer's third derivation of the same three shapes quasi-webview and quasi-tui already make: a labelled strip, a summary line that opens, or previous/position/next. A child carrying Slot::fed_by is fetched when its tab is pressed; a child holding its content is moved to locally with no request. View gains `shown`, keyed by region id and cleared on navigation, as Option<usize> where quasi-tui's is a bare usize -- a summary line here can be shut again and a terminal's prev/next row cannot reach the closed state. The region module headers in both renderers still recorded the three findings that motivated Showing, Slot::label and Arrangement::share. All three have been answered for a while; they now say so. quasi-immediate declared its own [lints.clippy] carrying pedantic alone, which replaces the workspace table rather than adding to it, so the house allow-list never reached it. On the workspace table now, like its eleven siblings. Template pins were four minors stale at 0.77 and makeover-tui seven at 0.34.0. Both current.