max / goingson

Mount quasi::protocol, so a described screen is reachable at all `src/quasi/mod.rs` defined `protocol()` and nothing called it. Grep for `quasi::protocol` outside the module returned one hit, in a test. So the thirteen described screens compiled under the feature and were reachable from tests only, and every task that said "turn the feature on" was describing a step that did not exist. Both entry points now register the scheme on the builder and fill its state in from `setup`, through quasi 0.47's `Late<AppState>`: the state needs an `AppHandle`, which does not exist until after every scheme is registered. Android is excluded, since its webview cannot read a request body. Nothing navigates there. The window still loads the JS frontend, and each screen moves over as its own flip; this is what those flips flip into. Three things the mount exposed, fixed here rather than left for the first flip to trip over: - The shell asked for one of the five stylesheets index.html links, so a described screen would have drawn without geometry, typography or tables. It now declares the same cascade in the same order, with the layer names. - Nothing served `/static` or `/fonts`. `quasi::assets` is the passthrough, embedding the sheets, the scripts and the three faces, because a bundled app has no directory to read them from. htmx is vendored under `frontend/vendor/` from the copy the MNW server serves; `build.rs` writes the clock script out beside the selection script it already wrote. Hyperscript is not vendored and is switched off rather than 404ing once per document. - The eleven `Outcome` matches in the screen tests predated quasi 0.45's `Suggestions`, so `--features quasi` had not compiled its tests since that bump. 712 pass now.