max / makenotwork

Adopt the makeover cascade layer in the server Bumps makeover-build 0.3.1 -> 0.7.0, so geometry.css and layout.css are emitted inside @layer makeover, and declares the order in the generated head partial ahead of every stylesheet link. The declaration goes in build.rs rather than style.css because a layer's position is fixed where its name is first seen. Left to link order the two generated sheets would establish `makeover` by loading first, and it also has to precede the per-page sheets (wizard.css, media-player.css) that _head_assets.html does not link. NO RULE DELETIONS, and that is the finding rather than an omission. The task expected 21 hand-written focus and disabled rules to fall out. Measured with both parses, none of them should: - The server never adopted makeover's component vocabulary. `.card`, `.tab` and `.badge` here are the server's own components that share a name: `.tab` is surface-sunken with no border where makeover's is a raised chip, `.card` is surface-overlay with --shadow-card where makeover's is surface-raised with the bevel. Generated rules lose on every property the server sets, which is correct, and win where it is silent. Retargeting those at the bevel is Platinum phases 4 and 5, not this task. - The focus ring is already `*:focus-visible`, universal, at 2px offset 2px on --focus-ring. That is byte-identical to what makeover now emits and covers far more than makeover's eight selectors, so it stays. It also defeats the generated per-primitive rings, including the depth-derived inset ring on .field, since an unlayered universal rule outranks a layered class rule. - The disabled block is on `button`, `[aria-disabled]` and the .btn-* variants, which are element and app selectors makeover does not emit. What the server does gain is real: it had 0 generated :focus-visible and 0 :disabled before, and the primitives it HAS adopted (.button, .chip, .toggle, .field, .progress, all of which style.css is silent about) now carry the full state set.