max / goingson

Take quasi 0.5 and the makeover 0.23.0/0.40.0 cascade goingson was pinned at quasi ^0.2 against a published 0.5.0, so `cargo check --all-features` could not resolve at all -- the `version` requirement on the git deps caught it at resolution time, which is what it is there for. The makeover half was a partially-applied cascade left uncommitted in the tree: build 0.31, webview 0.38, layout 0.22, tui 0.20, each one release behind. Forward-fixed in one pass, per the same-pass rule: - quasi-{router,http,webview,tauri} 0.2 -> 0.5 - makeover-build 0.32 -> 0.33, webview 0.38 -> 0.40, layout 0.22 -> 0.23, tui 0.20 -> 0.21 makeover-build needed releasing first. Its main took makeover-webview 0.40.0 in 05e001a without a version bump, so the published 0.32.0 still asked for ^0.39.0 while the rest of the suite was on 0.40.0, and under `links` that is a resolver error rather than a warning. Released as 0.33.0. The quasi 0.2 -> 0.5 API delta reaches this repo in exactly one place: `Outcome::Over(Screen)`, an app-level overlay that arrived alongside the chrome bindings. Six test helpers match on `outcome` and none used a wildcard, deliberately, so each gets an arm. It panics rather than rendering: an overlay is a screen, but not the screen the route was asked for, and drawing it would let a route answering with the command palette pass as the page. No route here returns one today. DEAD_VOCABULARY_HIGH_WATER 21 -> 23 for `.showing-frame` and `.showing-position`, generated by makeover-webview 0.40.0's derived showing-chrome. goingson draws no carousel, so both are members this app has no use for rather than members it stopped using -- the same mechanical rise as the picture-* classes, documented at the constant. cargo check --all-features clean, cargo test --all-features 541 passed / 0 failed / 2 ignored (the count recorded on 2026-08-12, restored), clippy --all-features --all-targets clean.