max / goingson

Put the bypassed scale tokens back to work The six tokens the dead-token audit turned up were not dead, they were bypassed by literals that matched their values exactly. Converting the consumers rather than deleting the tokens: every custom property in the file now has a reader. 26 font sizes move onto --font-size-xl through 4xl, 38 spacing literals onto --space-6, and .day-plan-sidebar's width onto --width-sidebar. Two places the value match was a coincidence rather than a use of the scale, and both keep their literal. .context-menu's max-width is 280px because that is a readable menu width, not because it is a sidebar. The @media print block sets fixed sizes deliberately, since a themed scale is the wrong thing to print against. Tokenising only the 1.5rem component left 11 shorthands with a token beside a bare literal, which reads worse than either extreme, so their on-scale companions went too: 8 more onto --space-1 through 5. Three companions had nowhere to go, and they are the useful finding here. .main-content pads 1.75rem and 2rem, .settings-content 2rem, .finish-review-btn 0.65rem. The spacing scale stops at 1.5rem, so the app's largest paddings are all off-scale by construction. Either the scale wants a step or two above --space-6, or those three want to come down onto it.