max / quasi

Name app-level chrome and the screen drawn over another A description named one screen's content and nothing said that an affordance is available everywhere and draws over what is under it. Two additions cover the class, because an overlay turns out to be a Screen and nothing else: Chrome, a set of key bindings held beside the Router, and Outcome::Over, a screen drawn over what is already there. Over is not a navigation: it touches no history, and dismissing it reveals the screen the user never left. In the TUI that means an overlay stack of screen-and-view pairs, each layer holding its own reach, focus, edits and scroll. Sharing one View would take the user's typing with the palette when it closed, which is the regression the tests pin. In the webview it is a retarget into a container the shell emits, with the bindings as htmx key triggers and no custom JS. Outcome is deliberately exhaustive, so the variant breaks every host on purpose and each one had to answer it. quasi-router through quasi-tauri go 0.1.0 to 0.2.0 together; goingson's pins and the template's git deps move with them, and those deps now carry the version requirement they should have had all along. egui is not covered and says so in makeover-immediate's header, rather than reading as a renderer that needs no palette.