/* Shared button vocabulary. * * See docs/BUTTON-VOCABULARY.md for the reasoning, the audit it came from, and * the migration map. Six roles and three sizes, replacing 119 class * combinations across the tools. * * Load AFTER the tool's own styles.css. This file relies on source order rather * than !important, so a tool can still override a rule where it genuinely needs * to. * * Roles, by meaning rather than colour: * * btn an ordinary action; the default and most common choice * btn btn-primary the one action that completes the screen's purpose * btn btn-ghost low emphasis: filters, toggles, cancel, in-place controls * btn btn-danger destructive or irreversible; never also primary * btn btn-link a low-emphasis action rendered as inline text * * FIVE roles, not six. btn-success was dropped after the migration found it at * zero uses: it requires a *different* primary beside it, and on a screen whose * purpose is approving something the approval IS the primary. Approve is * btn-primary and reject is btn-danger. Do not reintroduce a green role without * amending docs/BUTTON-VOCABULARY.md first. * * Sizes: btn-sm for dense rows and toolbars, default for everything else, * btn-lg for empty-state and sign-in calls to action only. * * Every rule states `color` explicitly. A