max / quasi

0.56.0: this renderer says which classes it is responsible for goingson `43a682b0`. `makeover_build::check_vocabulary_use` asked "which generated classes does no markup emit" by reading an app's own `index.html` and the scripts beside it. goingson's swap deleted all of them, so the call was left out of that app's build rather than run against nothing: an app cannot see its own document any more, because its document is Rust in a dependency. That dependency is this crate, so the question moves here. THE SET IS CLOSED, WHICH IS THE USEFUL PART. A description has no word for a class. Measured across goingson's src/quasi/, the largest described app in the tree: zero class names, because the vocabulary offers no way to write one. So `covers` is not a lower bound on what an app's stylesheet may legitimately match, it is the whole of it, and a selector outside it is dead rather than merely unaccounted for. That is what turns a drift check on a stylesheet from advisory into exact, and it is what tells goingson how much of a 9,830-line sheet to delete. ONE FAMILY IS OPEN AND IT IS NOT OURS. `col-<name>` comes from makeover_webview::list, built from an app-declared column name. No list can hold it, which is why `covers` exists beside `names` and is the function to check with: an app comparing against `names` alone would call every table rule dead and delete the styling. WRITTEN DOWN RATHER THAN SCRAPED, because there is nothing to scrape. makeover parses the stylesheet it just generated and has no second source to drift from; this crate generates no CSS. So the honesty comes from two tests instead, and both directions are needed: - every class the corpus emits is one `vocabulary` covers. A name added to an emitter and not to the list fails here, rather than quietly shrinking the set an app checks against. - every name in OWN is one the corpus still emits. This is the direction that fails unsafely if it is missing: a stale entry is a class an app believes is live, so it keeps a rule for markup nothing produces -- the dead CSS the check exists to find, preserved by the check itself. The corpus is one screen carrying every node kind, every notice, every row and table affordance, plus one screen per region kind, arrangement and measure. Writing it was not ceremony: a careful read of the emitters produced 35 names, and the corpus found 14 more, the `col-` family among them. MAKEOVER_UNLISTED is three classes makeover emits that its own `vocabulary::names` does not contain -- `cell-fill`, `form-group`, `form-label` -- found by the same guard. Kept separate from OWN because they are not this crate's to name; when makeover's set grows to include them the constant becomes empty and can go. Until then an app checking against makeover alone would call three live rules dead. 0.56.0 rather than a patch: a new public module is additive, but the workspace versions in lockstep and consumers take the whole set.