max / makenotwork

Take makeover-build 0.13.1, five minors of generator drift at once The server sat on makeover-build 0.8.0 while the rest of the tree moved. Through the lock that is makeover-layout 0.8.2 to 0.12.0, makeover-webview 0.16.1 to 0.21.1 and makeover-touch 0.4.0 to 0.8.1, so layout.css was being generated from a vocabulary five minors behind the one quasi-webview emits. That mismatch is why this gates the quasi adoption rather than running beside it: two class vocabularies in one document is not a thing to debug later. geometry.css and embed-geometry.css regenerate byte-identical. layout.css goes 280 to 293 lines and the diff is not additive: - .raised loses :hover, :active, :focus-visible and :disabled. That is makeover-webview 0.17.0 ruling depth classes to be surfaces and not controls, and it is the same elevation-versus-bevel line wave 2 draws. Inert here: .raised has zero uses in this server's markup. - .figure, .placeholder and .table-heading[data-sortable] arrive. The one collision worth checking was .placeholder, which the markup does use six times. Two are the bare class, both in embed templates, and neither has a .placeholder-text child, so the new rules match nothing. The other four are compound names that were never the generated class. makeover-geometry moves 0.6 to 0.7 alongside it, because build.rs reads SizeClass directly for the breakpoint guard and that pin has to track the one makeover-build resolves. Not pinning makeover-webview or makeover-layout directly. The task asked for both, but this build.rs names neither: only makeover-build and makeover-geometry. GoingsOn pins them because its build.rs really does call Column, Emit and narrowing_css. Two more pins to keep current here would buy nothing, and pin drift is the thing that just cost five minors.