max / quasi

Add quasi-immediate: the egui renderer for a described screen The third renderer, and the one the stack was missing. quasi-webview and quasi-tui have consumed a Screen since the beginning and nothing did in egui, so an egui app describing a screen had nowhere to send it. What looked like the egui renderer was makeover-immediate, which draws described nodes and takes no quasi-router dependency at all: it is the peer of makeover-webview and makeover-tui, one layer below this. Immediate mode makes it smaller than the terminal's rather than larger. quasi-tui's View holds five things a browser provides quietly; egui provides three of them, so reach, focus and scroll are egui's and there is no focus.rs here. What is left is what is typed and what is ticked, because a described field is rebuilt every frame and its buffer has to outlive one, which is the same conclusion makeover-immediate's Filling reached a layer down. The node walk is exhaustive with no catch-all, because Node carries no non_exhaustive and that is deliberate upstream: a node added to the vocabulary should stop every renderer compiling until each decides what it looks like. Same argument Outcome documents. Chrome and Outcome::Over are both answered -- bindings read off the context before the frame, so a screen cannot capture the palette's key, and an overlay is an Area at Order::Foreground over a layer stack that leaves history alone. Two things are deliberately not drawn and say so rather than failing quietly: a described table, which wants makeover_immediate::table's cell closures wired through, and Node::Rich, which takes the plain rendering until egui has a markdown widget worth adopting.