max / makenotwork

Retire the --shadow-1/2/3 scale onto the elevation intent Wave 2 tier B5. The three were hard rgba-black offsets picked against parchment and then applied to all 31 themes a creator can select, which is the same defect the bevel trio was rewritten to undo; mnw-platinum phase 4 retargeted the bevels and never touched the blurred scale, so these survived. makeover 2.5.0 derives the elevation intent that replaces them. Ten consumers, not the nine the task counted. wizard.css carried a tenth that the style.css-only inventory missed. Eight are genuine floats and take --elevation-overlay from layout.css: the tab overflow menu, the toast, the docs search results, both suggestion dropdowns, the collection picker, the save badge on a discover card, and the context menu. One is not a float. .buy-page .buy-card is the whole content of its page rather than something laid over it, so by the intent's own scope rule it takes .raised, which carries the surface and the edge together; the local rule keeps only the geometry the generated primitive does not. Its fill moves --surface-overlay to --surface-raised, equal on the platform default, the same move .card made. The landing carousel keeps a local box-shadow because geometry is consumer-side: --elevation-overlay is calibrated for popovers a few hundred pixels across and its blur disappears on a full-width plate. It now composes two layers of var(--elevation) for that weight instead of a black literal. The rule stays scoped to .landing-showcase, but the reason is weaker than the comment used to claim: the technical argument was that the literal was only true on parchment, and that argument leaves with the literal. What remains is a look call for the F2 screenshot pass. Also adds --elevation to the default :root in style.css, which had drifted from `dump_intents makenotwork` since 2.5.0. Pages that inject no theme block (buy, landing, docs) read that block, and without this every one of the sites above would have resolved to nothing.