max / quasi

Close four vocabulary collisions and give a row its Nesting Four names in one description could mean two things each, and one type the crate had already ruled on was carrying a bare integer instead. - `screen::Fill` becomes `Prefill`. It collided with `layout::Fill`, the surface intent, and both are in scope in every description. Its own doc never defended the name, unlike `Picture` and `Tag`, which are the deliberate dodges for `layout::Image` and `layout::Token` and stay. - `Progress::Standing` becomes `Progress::Idle`, off `layout::Standing`, the facet state. Nothing serialised it; the three lowercase spellings a payload carries are hand-written and untouched. - `Richness::Prose` becomes `Richness::Sentence`, off the `Prose` type. Not `Plain`: the tier admits paragraphs, lists, code and links, and `docengine::render_plain` means the opposite thing three frames away. `Sentence` is the opposition the type's own doc already draws against `Document`. - `Row::depth` and `Cells::depth` carry `layout::Nesting` rather than a bare `usize`, which is what `edf33114` ruled on 2026-08-30 and what makeover-webview's comment already claimed was true. `Outline::depth` and `folded_by` follow. That deletes the three lossy narrowings the renderers were each doing by hand, and moves the one fallible conversion to audiofiles' tag sidebar, where the depth is a count of dots in a tag path. quasi-router's makeover-layout requirement said 0.41.0, in which `Nesting` does not exist; caret resolution to the installed 0.41.2 was hiding it. Fixed to 0.41.2. Breaking, so the workspace goes to 0.97.0 and its consumers follow in the same pass.