Joseph Doherty
dc53f04b81
site.css declared `font-size: 0.82rem` literally on `.btn`. Bootstrap sizes buttons through `font-size: var(--bs-btn-font-size)`, and `.btn-sm` / `.btn-group-sm > .btn` do nothing but redefine that variable — so a literal at equal specificity, loaded after Bootstrap, silently flattened every small button in the dashboard into a padding-only difference. `btn-sm` was inert app-wide. The kit now owns the sizing: 0.4.0 shipped the four `--bs-btn-*` overrides in layout.css, which ThemeHead emits ahead of site.css, so removing the local literal restores `.btn-sm` without a local copy. 0.4.1 is a pin-only follow-up (it fixes `.rail-btn-block`, which this app does not use; `theme.css` is byte-identical and the `.btn` rule is unchanged between the two). The rest of the local rule is kept deliberately. 0.4.0 upstreamed sizing only, not `border-radius` / `font-weight` / `white-space`, so deleting the block wholesale would have dropped three app-specific declarations. `border-radius` also stays a literal rather than `--bs-btn-border-radius`, because `.btn-sm` redefines that variable and small buttons would shrink to Bootstrap's radius. Verified in a browser against the running dashboard: `.btn` 13.6px and `.btn-sm` 12.48px, btn-group seams intact, and `--bs-btn-font-size` now declared in exactly two sheets (bootstrap.min.css, layout.css) instead of three.