/*
 * THE AUTH SHELL'S SHARED RULES — one file, because five pages were each carrying their own copy.
 *
 * WHY IT IS GLOBAL, and why that is the fix rather than a compromise. Blazor scopes a component's stylesheet to that
 * component, so Login, Forgot, Reset, Activate and Domains each carried a copy of these rules and each copy could only
 * reach its own page. Five copies of one rule is five chances for them to drift, and on 26 September 2026 they had
 * already drifted into a defect: every copy declared `color: inherit` for buttons, which outranks a class rule, so the
 * sign-in page's own `.submit-button { color: var(--auth-white); background: var(--auth-ink) }` never applied and the
 * word "Sign in" was #0b0d10 on #0b0d10 — a black bar with nothing on it, at a contrast of 1:1.
 *
 * A GLOBAL RULE LOSES TO A SCOPED ONE, and that is exactly what is wanted here: these are defaults for the shell, and
 * anything a page states about its own control wins. It is the same arrangement `css/decision-surface.css` already
 * uses for the two decision pages.
 *
 * SO THE DEFAULTS ARE TYPOGRAPHY ONLY, AND A BUTTON STATES ITS OWN COLOUR. `font: inherit` belongs on every form
 * control — a control that keeps the browser's own font is the classic mismatch between a page and its buttons. Colour
 * is different: text that is merely inherited is text nobody chose, and a button's background is not the page's.
 */

.auth-page button,
.auth-page input,
.auth-page a {
    font: inherit;
}

/* Inputs and links still inherit the shell's ink: neither declares a colour of its own, so the page's is the right
   one. A BUTTON IS DELIBERATELY ABSENT — see above. */
.auth-page input,
.auth-page a {
    color: inherit;
}