/*
 * Which notification rules will actually fire (Sets, 06.08.2026).
 *
 * ⚠ Plain CSS served through `filament:assets`, NOT a Tailwind theme build —
 * the reason `permission-matrix.css` gives: the panel has no custom theme, and
 * referencing the Vite manifest from the provider crashed the application
 * wherever the front end was not built (build #765).
 *
 * ── What it says ──────────────────────────────────────────────────────────
 *
 * ⛔ Three separate states stop a rule dead — switched off, no spans chosen, a
 * group rule with no group — and every one of them looked on screen exactly
 * like a rule that works. Reading a card meant checking three controls per row.
 *
 * ⚠ Green means it fires, red means it does not. The colour is on the ROW
 * rather than on a control, because what is or is not working is the rule and
 * not any one of its parts.
 *
 * ⚠ Reached with `:has()` from a class the page puts on the row's toggle:
 * Filament hands extra attributes to components, never to a repeater row.
 */

.fi-fo-table-repeater tbody tr:has(.fi-rule-live),
.fi-fo-repeater-item:has(.fi-rule-live) {
    /*
     * ⚠ An INSET shadow rather than a border. A real border on a table row
     * changes the row's height and pushes every cell beside it by a pixel, so
     * the columns stop lining up down the card — and the alignment is what
     * makes the card readable in the first place.
     */
    box-shadow: inset 3px 0 0 0 var(--success-600);
}

.fi-fo-table-repeater tbody tr:has(.fi-rule-dead),
.fi-fo-repeater-item:has(.fi-rule-dead) {
    box-shadow: inset 3px 0 0 0 var(--danger-600);

    /*
     * ⚠ A tint as well, and only on this side. Colour alone is not a signal
     * somebody with a red-green deficiency can read; the wash gives the dead
     * row a second difference that does not depend on hue.
     */
    background-color: color-mix(in oklab, var(--danger-500) 6%, transparent);
}