/*
 * Extra dark-mode surface for neutral ("gray") buttons, on every panel.
 *
 * CAUSE: Filament's own dark-mode background for a gray button is a white
 * overlay at 5% opacity at rest / 10% on hover
 * (vendor/filament/support/resources/views/components/button/index.blade.php).
 * Composited over this panel's actual dark background — rgb(9,9,11), not
 * pure black — that measures a WCAG contrast of ~1.09 against the page: the
 * button is visible only because of its ring, not its own surface. The
 * outlined variant (ViewAccount's "Saldo Inicial ..." controls) has NO
 * background at rest at all — 1.00, fully transparent, since "outlined"
 * means border-only by design.
 *
 * This file raises the white-overlay opacity for both the solid and the
 * outlined gray button, in dark mode only, without touching any other
 * color — "Conciliar" (this panel's purple) included, by explicit
 * instruction — and without touching light mode.
 *
 * Selector: .fi-btn.fi-color-gray. button/index.blade.php adds
 * fi-color-{color} for any string color unconditionally, and gray is the
 * one color that does NOT also get fi-color-custom (every OTHER color
 * does, including this panel's own 'primary' and 'purple') — so
 * fi-color-gray is the one class a gray button carries that a colored one
 * never does. .fi-icon-btn (icon-only triggers, e.g. table row actions) and
 * .fi-link (plain text-link actions, e.g. "Alterar"/"Ver transferências")
 * use their own, different marker classes — neither carries .fi-btn at
 * all — so this rule cannot reach them; nobody asked about those, and both
 * are meant to read as lighter-weight than a bordered button.
 *
 * Values: 16% white at rest (contrast ≈ 1.52 against rgb(9,9,11)), 24% on
 * hover (≈ 2.04) — inside the 1.5–2.0 "perceptible surface" band asked for,
 * with hover still reading as visibly MORE than rest, same as before this
 * file existed. Button text stays white either way (contrast ≈ 13 at rest,
 * ≈ 9.7 on hover) — nowhere near the 4.5 floor. The focus-visible ring
 * itself is untouched: this file only ever sets background-color, so the
 * ring's own color and width (Filament's own CSS) keep deciding the focus
 * state exactly as they did before.
 *
 * Specificity: this project has no active Tailwind build, so the generated
 * dark:bg-white/5 utility this overrides was read from the compiled bundle,
 * not assumed — it compiles to a two-part selector (its own class plus
 * Tailwind's :is(.dark *) form for the ancestor check). Three plain classes
 * (.fi-btn.fi-color-gray under .dark) already out-specify that, so no
 * !important is needed anywhere below.
 */

.dark .fi-btn.fi-color-gray {
    background-color: rgba(255, 255, 255, 0.16);
}

.dark .fi-btn.fi-color-gray:hover {
    background-color: rgba(255, 255, 255, 0.24);
}