max / makenotwork

Hand four more primitives back to makeover: link, field, chip, segment, toggle The same element-vs-class overlap the button carried, measured across every element rule in style.css that could sit under a generated class. - `a { color: var(--content); text-decoration: none }` rendered a described link as body text. A reader could not tell it was a link. - `button.link` took the element rule's fill, border and 6px/12px padding, so a link that posts rendered as an ordinary raised button rather than flat. - `select` and `textarea` set background and box-shadow where the `input` rule sets neither, so a described field on either took --surface-sunken instead of the well, and the app's outer focus ring beat makeover's inset one. The shipped `.field` precedents survived on that accident, not by design. - `button { background; box-shadow }` beat `.chip.latched`, `.toggle.chosen` and `.segment.chosen`, so every one of those rendered raised. The selected state was invisible, which is the defect `.tab.chosen` was fixed for. All handoffs are `revert-layer`, so each rolls back to whichever makeover arm matches the element -- the latched arm for a latched chip, the base arm otherwise -- rather than naming a value. `font` is handed back on the button arm of `.link` alone: an `a.link` has no lower-layer font to roll back to and would land on the UA face. Verified by rendering, before and after, with the four sheets and the layer statement: a described link is --action and underlined, a link button is transparent with no padding or border, select and textarea take the well, and latched chip, chosen toggle and chosen segment take the inset bevel. Left alone and recorded in build.rs: `.facet-prune` and `.facet-take` (nothing in the layer to roll back to, so the app's chrome has to be withdrawn by hand), `.badge` and `.card`, and the disabled treatment, which is a charter decision.