/* ─────────────────────────────────────────────────────────────────
   MudBlazor overrides.

   This file exists SEPARATELY from app.css because of load order: app.css is
   linked before MudBlazor.min.css, so an equal-specificity rule there loses
   the tie. Everything here is linked AFTER MudBlazor and therefore wins on
   source order, without needing !important and without having to out-specify
   MudBlazor's own state rules — which must keep winning.

   Mirrored verbatim in Web.Client/wwwroot/css/mud-overrides.css. Edit BOTH.
   ───────────────────────────────────────────────────────────────── */

/* An empty field's label sits INSIDE the box, in the same place a value would
   be. MudBlazor paints it TextSecondary (#4B5675 in our palette) — the same
   weight of ink as real content — so an empty form reads as a filled one.
   Drop the resting state to the disabled tone, which is what "nothing here
   yet" is supposed to look like.

   Deliberately matched at the same specificity as MudBlazor's base rule
   (0,3,0) rather than higher: its shrink rule (.mud-shrink~label…, 0,3,1) and
   its focus, error and disabled rules are all more specific and keep winning.
   Once the label floats into the notch it is a heading for real content and
   goes back to being dark. */
.mud-input-control > .mud-input-control-input-container > .mud-input-label-inputcontrol {
    color: var(--mud-palette-text-disabled);
}