/* ============================================================================
   theme-dark-polish.css
   [2026-09-11]  DARK ONLY.  LOADS LAST - after theme-dark-guard.css.

   ---------------------------------------------------------------------------
   WHAT THIS IS FOR
   ---------------------------------------------------------------------------
   The three files before it make dark mode CORRECT:

       theme-token-bridge.css    re-points --cc-* / --bds-* (753 sites)
       theme-dark-surfaces.css   305 generated rules for literal colours
       theme-dark-guard.css      inline style="" attributes

   Correct is not the same as good. Those are mechanical - they map every light
   value onto one of two greys, which removes the glare but also flattens the
   interface into a single plane. This file is the HAND-TUNED pass that puts
   depth, hierarchy and finish back, and it covers the whole journey: sign-in,
   the top bar, the notification strip, loaders, floating layers, sign-out.

   It is deliberately NOT generated. Everything here is a judgement about a
   specific element, which is exactly what a generator cannot make - and why
   re-running the generator will never overwrite it.

   ---------------------------------------------------------------------------
   THE ELEVATION MODEL - WHY SURFACES GET LIGHTER, NOT DARKER
   ---------------------------------------------------------------------------
   This is the single rule that separates a professional dark theme from a
   crude one, and it is the opposite of the light-theme instinct.

   In a LIGHT theme, elevation is expressed with SHADOW: a raised card casts a
   darker shadow onto the surface below it.

   In a DARK theme a shadow is nearly invisible - dark on dark - so shadow
   alone leaves every panel looking like it is painted onto the same flat
   sheet. Both Material and Fluent solve it the same way: elevation is
   expressed as LIGHTNESS. The higher a surface sits, the lighter it is,
   because it catches more ambient light.

       ground / page        #0B1220     --bz-bg
       sunken (inset)       #0F1829     --bz-bg-2
       resting card         #131C2E     --bz-surface
       raised panel         #172236     --bz-surface-2
       floating overlay     lighter still, plus a hairline

   Shadow is still used, but as a SEPARATOR under floating layers, never as the
   primary depth cue.

   The second half of the effect is a 1px top highlight - `inset 0 1px 0
   rgba(255,255,255,.04)`. A real raised edge catches light along its top
   rim; that hairline is what makes a panel read as a physical object rather
   than a rectangle of slightly different grey. It is the whole of the "HD"
   impression and it costs one declaration.

   ---------------------------------------------------------------------------
   TRANSPARENCY: USED ON FLOATING LAYERS, NEVER ON A CONTAINER
   ---------------------------------------------------------------------------
   backdrop-filter is applied ONLY to elements that float above the page and
   contain no positioned widgets of their own.

   It is deliberately NOT applied to .headerMain or any page container.
   backdrop-filter creates a CONTAINING BLOCK for absolutely-positioned
   descendants, which silently relocates any JavaScript-positioned popup
   rendered inside it - DevExpress computes dropdown coordinates against the
   document, so a new containing block moves the dropdown away from its input.
   A glass header is not worth a misplaced dropdown.

   ASCII-only. Chrome 59 floor - backdrop-filter is 47+ and every use below is
   paired with a background opaque enough to read on its own if it is ignored.
   ============================================================================ */

/* ===========================================================================
   1. TOP BAR
   The header is the one piece of chrome present on every screen, so it sets
   the impression for the whole theme.
   =========================================================================== */
[data-bz-theme="dark"] .headerMain {
    background-color: #101A2B !important;
    background-image: linear-gradient(180deg, #142033 0%, #0E1726 100%) !important;
    border-bottom: 1px solid rgba(148, 163, 184, .14) !important;
    box-shadow: 0 1px 0 rgba(255, 255, 255, .03) inset,
                0 2px 10px rgba(0, 0, 0, .35) !important;
}

/* The profile chip. It was reported as "Welcome admin text not showing":
   the greeting inherited a light ink while the chip behind it kept an ambient
   light fill, so light sat on light. Both halves are stated explicitly here
   rather than relying on inheritance - the chip is a transparent pill that
   only fills on hover, and the ink is pinned. */
[data-bz-theme="dark"] .prof .nav > li > a,
[data-bz-theme="dark"] .prof .nav-link,
[data-bz-theme="dark"] .prof .dropdown > a {
    background-color: transparent !important;
    background-image: none !important;
    border-radius: 999px !important;
    color: var(--bz-text) !important;
}

[data-bz-theme="dark"] .prof .nav > li > a:hover,
[data-bz-theme="dark"] .prof .nav-link:hover,
[data-bz-theme="dark"] .prof .dropdown > a:hover,
[data-bz-theme="dark"] .prof .dropdown > a[aria-expanded="true"] {
    background-color: rgba(255, 255, 255, .07) !important;
}

/* The greeting. --bds-ink is bridged, but .prof .nav > li > a .bds-user-name
   in bds.css is (0,3,3) and outranks the (0,2,0) rule in theme-shell.css, so
   the name is restated at a specificity that actually lands. */
[data-bz-theme="dark"] .prof .nav > li > a .bds-user-name,
[data-bz-theme="dark"] .bds-user-name {
    color: #F1F6FD !important;
    font-weight: 600 !important;
}

[data-bz-theme="dark"] .prof .nav > li > a .bds-welcome-word,
[data-bz-theme="dark"] .bds-welcome-word {
    color: #A7B4C8 !important;
}

[data-bz-theme="dark"] .prof .nav > li > a .lnr,
[data-bz-theme="dark"] .headerMain .arrow-down,
[data-bz-theme="dark"] .headerMain .lnr-chevron-down {
    color: #A7B4C8 !important;
}

/* The avatar needs a rim, or a dark-edged portrait dissolves into a dark bar. */
[data-bz-theme="dark"] .prof a .user img,
[data-bz-theme="dark"] .headerMain .user img {
    border-radius: 50% !important;
    box-shadow: 0 0 0 2px rgba(255, 255, 255, .14),
                0 2px 6px rgba(0, 0, 0, .45) !important;
}

[data-bz-theme="dark"] .headerMain .dateTime,
[data-bz-theme="dark"] .headerMain .dateTime * {
    color: #C6D2E4 !important;
}

/* Brand lockup. */
[data-bz-theme="dark"] .bz-lockup-txt,
[data-bz-theme="dark"] .logoWrap,
[data-bz-theme="dark"] .logoWrap * {
    color: #F1F6FD !important;
}

/* ---- header search ------------------------------------------------------ */
[data-bz-theme="dark"] .middleWraper .inputcontainer,
[data-bz-theme="dark"] .bds-hsearch .searcherInput,
[data-bz-theme="dark"] .prof .searcherInput > input {
    background-color: #0C1524 !important;
    background-image: none !important;
    border: 1px solid rgba(148, 163, 184, .20) !important;
    color: var(--bz-text) !important;
    box-shadow: 0 1px 0 rgba(255, 255, 255, .03) inset !important;
}

[data-bz-theme="dark"] .prof .searcherInput > input:focus {
    border-color: var(--bz-primary) !important;
    box-shadow: 0 0 0 3px var(--bz-ring) !important;
}

/* ===========================================================================
   2. THE NOTIFICATION STRIP  (#dueMessage)
   ---------------------------------------------------------------------------
   Injected by _Layout.cshtml as

       <div id="dueMessage" style="width:500px">
         <marquee style="color:red; font-size:1em; font-weight:bold;">
           <b>[warning emoji] Payment Due Reminder: ...</b>

   `red` (#FF0000) on a dark bar measures about 3.9:1 - under AA, and the
   harshest hue available on a dark ground. The inline style means only an
   !important rule can reach it.

   [2026-09-11] REVISED: it was a RED veil, and that was the wrong family.

   The message opens with a warning emoji, which the font renders in its own
   amber whatever we do - it is a colour glyph, not text, so `color` does not
   touch it. Putting red ink on a red veil next to a fixed amber glyph gave the
   strip three hues at once, which is what made it read as muddy rather than
   themed: brown-red ground, salmon text, yellow icon.

   It is now one family, amber, chosen to match the glyph we cannot recolour
   rather than fighting it. That is also the correct semantics - a due REMINDER
   is a warning, not an error; the error red in this palette is reserved for
   things that have already failed.

   Ink is #FCD34D (--bz-warning-ink), roughly 11:1 over the veil, so a bar the
   user is meant to act on is the most legible thing in the header instead of
   the murkiest.

   Padding and box-sizing are set because the div carries an inline
   `width: 500px` and the text otherwise sits flush against the new border.
   `display` is deliberately NOT set: the page shows and hides this with
   jQuery .show()/.hide(), and an !important display would make .hide() stop
   working - the strip would be permanently visible to users with no dues.
   =========================================================================== */
/* [2026-09-11] OPAQUE, not a veil - second revision.
   A translucent amber over the header does not produce amber. The header is a
   blue-grey GRADIENT (theme-dark-polish section 1), and a 12% warm wash
   multiplied against a cool moving ground came out olive-brown and muddy -
   reported twice as "not proper dark mode". A translucent overlay only works
   over a flat, known ground.
   So the strip owns its colour outright: an opaque raised surface, an amber
   hairline, and a 3px amber rule down the leading edge. That left rule is what
   makes it read as an ALERT rather than a slightly different rectangle - it is
   the one part of the bar that is pure, unmixed brand amber, and it stays put
   while the marquee text scrolls past it. */
[data-bz-theme="dark"] #dueMessage {
    background-color: #1A2133 !important;
    background-image: none !important;
    border: 1px solid rgba(251, 191, 36, .34) !important;
    border-left: 3px solid #FBBF24 !important;
    border-radius: 10px !important;
    box-shadow: inset 0 1px 0 rgba(255, 255, 255, .05),
                0 1px 3px rgba(0, 0, 0, .35) !important;
    padding: 6px 12px !important;
    box-sizing: border-box !important;
}

[data-bz-theme="dark"] #dueMessage marquee,
[data-bz-theme="dark"] #dueMessage marquee b,
[data-bz-theme="dark"] #dueMessage b,
[data-bz-theme="dark"] #dueMessage [style*="color:red" i],
[data-bz-theme="dark"] #dueMessage [style*="color: red" i] {
    color: #FCD34D !important;
    letter-spacing: .01em !important;
}

[data-bz-theme="dark"] #dueMessage .fa-exclamation-circle,
[data-bz-theme="dark"] #dueMessage .fa-exclamation-triangle {
    color: var(--bz-warning) !important;
}

/* ===========================================================================
   3. LOADERS
   ---------------------------------------------------------------------------
   Both loader bugs were self-inflicted and are documented where they were
   introduced; this section states the CORRECT end result in one place.

     * .bz-page-loader is a translucent dark SCRIM. It must stay translucent -
       an opaque panel hides the page instead of dimming it. Deepened slightly
       here because the page beneath is now dark too, so .55 no longer reads as
       a veil.
     * .bz-load-orb / .cc-aiload-orb is the WHITE DISC the dark BreezeFSM mark
       sits on. It must stay light or the loader becomes a featureless dark
       circle - which is exactly what was reported.
   =========================================================================== */
[data-bz-theme="dark"] .bz-page-loader {
    background-color: rgba(6, 11, 20, .78) !important;
    background-image: none !important;
    -webkit-backdrop-filter: blur(3px);
    backdrop-filter: blur(3px);
}

/* [2026-09-13] This orb was pinned WHITE, and .bz-load-orb was added to the
   audit's KEEP_LIGHT list so nothing would report it. Both were workarounds
   for one thing: bzLoaderHtml and command-center-common.js build the orb
   around <img src="logo.webp">, and that file is opaque - the fourth place
   in this product where that has bitten. With the transparent mark swapped
   in below, the plate no longer has to be white. */
[data-bz-theme="dark"] .bz-load-orb,
[data-bz-theme="dark"] .cc-aiload-orb {
    background-color: var(--bz-surface-2) !important;
    background-image: none !important;
    box-shadow: 0 0 0 1px rgba(255, 255, 255, .22),
                0 6px 26px rgba(37, 99, 235, .45) !important;
}

[data-bz-theme="dark"] .bz-load-phrases,
[data-bz-theme="dark"] .bz-load-dots,
[data-bz-theme="dark"] .cc-aiload,
[data-bz-theme="dark"] .cc-aiload-text {
    color: #E6EDF8 !important;
}

/* [2026-09-13] A 10% white band behind the loader caption. On the dark
   overlay it reads as a grey box around the text rather than as a chip. */
[data-bz-theme="dark"] .bz-load-line {
    background-color: transparent !important;
}

/* ===========================================================================
   4. ELEVATION - the depth pass
   ---------------------------------------------------------------------------
   The generated layer painted nearly every panel --bz-surface, which is
   correct and completely flat. Here the planes are separated again, using the
   lightness model described in the header.
   =========================================================================== */

/* Resting cards and panels: a raised edge and a real separator. */
[data-bz-theme="dark"] .panel,
[data-bz-theme="dark"] .card,
[data-bz-theme="dark"] .widgBox,
[data-bz-theme="dark"] .boxWidget,
[data-bz-theme="dark"] .cc-card,
[data-bz-theme="dark"] .fsm-cc-block {
    border: 1px solid rgba(148, 163, 184, .13) !important;
    box-shadow: 0 1px 0 rgba(255, 255, 255, .04) inset,
                0 2px 8px rgba(0, 0, 0, .30) !important;
}

/* Sunken areas - filter bars, toolbars, search strips - go DARKER than the
   card they sit in. Without this they read as another card and the eye cannot
   tell a container from its contents. */
[data-bz-theme="dark"] .fsm-filterbar,
[data-bz-theme="dark"] .fsm-orderbar,
[data-bz-theme="dark"] .fsm-head-tools,
[data-bz-theme="dark"] .dataTables_filter,
[data-bz-theme="dark"] .dataTables_length,
[data-bz-theme="dark"] .party-list-buttons {
    background-color: #0D1522 !important;
    background-image: none !important;
    border-color: rgba(148, 163, 184, .12) !important;
}

/* Table headers sit ABOVE their rows, so they are lighter, not darker. */
[data-bz-theme="dark"] table.dataTable thead th,
[data-bz-theme="dark"] .table > thead > tr > th {
    background-color: #1A2436 !important;
    background-image: none !important;
    color: #C6D2E4 !important;
    border-color: rgba(148, 163, 184, .16) !important;
}

[data-bz-theme="dark"] table.dataTable tbody tr:hover > td,
[data-bz-theme="dark"] .table > tbody > tr:hover > td {
    background-color: #1B2740 !important;
}

/* ===========================================================================
   5. FLOATING LAYERS
   The only place transparency is used - see the header note on why it is kept
   away from containers.
   =========================================================================== */
[data-bz-theme="dark"] .dropdown-menu,
[data-bz-theme="dark"] .profDrop {
    background-color: rgba(23, 34, 54, .96) !important;
    background-image: none !important;
    border: 1px solid rgba(148, 163, 184, .20) !important;
    box-shadow: 0 1px 0 rgba(255, 255, 255, .05) inset,
                0 18px 44px rgba(0, 0, 0, .60) !important;
    /* [2026-09-11] backdrop-filter removed here too. A Bootstrap dropdown can
       host a DevExpress editor, and the cost of being wrong is a dropdown in
       the wrong place. .96 alpha already reads as solid. */
}

[data-bz-theme="dark"] .modal-content {
    background-color: #16203A !important;
    border: 1px solid rgba(148, 163, 184, .20) !important;
    box-shadow: 0 1px 0 rgba(255, 255, 255, .05) inset,
                0 28px 70px rgba(0, 0, 0, .68) !important;
}

[data-bz-theme="dark"] .modal-backdrop,
[data-bz-theme="dark"] .modal-backdrop.in {
    background-color: #04070E !important;
    opacity: .72 !important;
}

/* DevExpress popups get the surface and the separator but NO backdrop-filter:
   a DX popup can host another DX dropdown, and a containing block here would
   move that child popup off its anchor. */
[data-bz-theme="dark"] [class*="dxpcLite"],
[data-bz-theme="dark"] [class*="dxpcControl"],
[data-bz-theme="dark"] [class*="dxpcDropDown"] {
    background-color: #172236 !important;
    background-image: none !important;
    border-color: rgba(148, 163, 184, .22) !important;
    box-shadow: 0 18px 44px rgba(0, 0, 0, .60) !important;
}

/* Tooltips and the guided tour. */
[data-bz-theme="dark"] .tooltip-inner,
[data-bz-theme="dark"] .bz-menu-tip,
[data-bz-theme="dark"] .introjs-tooltip {
    background-color: #1F2A40 !important;
    color: #E6EDF8 !important;
    border: 1px solid rgba(148, 163, 184, .22) !important;
    box-shadow: 0 10px 30px rgba(0, 0, 0, .55) !important;
}

/* SweetAlert2 - used for every confirm and every session-expiry prompt, so it
   is part of the sign-out path. */
[data-bz-theme="dark"] .swal2-popup {
    background-color: #16203A !important;
    color: var(--bz-text) !important;
    border: 1px solid rgba(148, 163, 184, .20) !important;
    box-shadow: 0 28px 70px rgba(0, 0, 0, .68) !important;
}

[data-bz-theme="dark"] .swal2-title,
[data-bz-theme="dark"] .swal2-html-container,
[data-bz-theme="dark"] .swal2-content {
    color: var(--bz-text) !important;
}

[data-bz-theme="dark"] .swal2-container.swal2-backdrop-show,
[data-bz-theme="dark"] .swal2-container {
    background-color: rgba(4, 7, 14, .72) !important;
}

/* ===========================================================================
   6. FORM CONTROLS
   The most-touched surface in the product, and the one a flat conversion
   makes hardest to use: a field and its container end up the same colour, so
   the input target is invisible until it is focused.
   =========================================================================== */
[data-bz-theme="dark"] .form-control,
[data-bz-theme="dark"] input[type="text"],
[data-bz-theme="dark"] input[type="password"],
[data-bz-theme="dark"] input[type="email"],
[data-bz-theme="dark"] input[type="number"],
[data-bz-theme="dark"] input[type="search"],
[data-bz-theme="dark"] input[type="date"],
[data-bz-theme="dark"] textarea,
/* :not(.btn) - "Export to" is <select class="btn btn-sm btn-primary">. Without
   the exclusion this !important rule beat components.css (which carries none)
   and painted a brand button #0C1524. glass-theme.css and
   theme-dark-surfaces.css already scope their select rules the same way. */
[data-bz-theme="dark"] select:not(.btn) {
    background-color: #0C1524 !important;
    background-image: none !important;
    border: 1px solid rgba(148, 163, 184, .22) !important;
    color: var(--bz-text) !important;
    box-shadow: 0 1px 0 rgba(255, 255, 255, .03) inset !important;
}

[data-bz-theme="dark"] .form-control:focus,
[data-bz-theme="dark"] input:focus,
[data-bz-theme="dark"] textarea:focus,
[data-bz-theme="dark"] select:not(.btn):focus {
    background-color: #0E1828 !important;
    border-color: var(--bz-primary) !important;
    box-shadow: 0 0 0 3px var(--bz-ring) !important;
    outline: none !important;
}

[data-bz-theme="dark"] .form-control[disabled],
[data-bz-theme="dark"] .form-control[readonly],
[data-bz-theme="dark"] input[disabled],
[data-bz-theme="dark"] select[disabled] {
    background-color: #131B29 !important;
    color: var(--bz-muted) !important;
}

/* The native picker glyphs render as black-on-black without this. */
[data-bz-theme="dark"] input[type="date"]::-webkit-calendar-picker-indicator,
[data-bz-theme="dark"] input[type="time"]::-webkit-calendar-picker-indicator {
    -webkit-filter: invert(1) brightness(1.6);
    filter: invert(1) brightness(1.6);
    opacity: .75;
}

/* ===========================================================================
   7. SIGN-IN AND SIGN-OUT
   The journey starts and ends here, and both screens render outside the
   portal shell - so neither inherits anything above.
   =========================================================================== */
[data-bz-theme="dark"] .mainLogin .formArea .lg-card,
[data-bz-theme="dark"] .mainLogin .formArea form {
    box-shadow: 0 1px 0 rgba(255, 255, 255, .06) inset,
                0 30px 70px rgba(0, 0, 0, .55) !important;
}

/* Session-expiry, sign-off and error shells. */
[data-bz-theme="dark"] .signoff-wrap,
[data-bz-theme="dark"] .error-wrap,
[data-bz-theme="dark"] .maintenance-wrap,
[data-bz-theme="dark"] .alert-message-wrap {
    background-color: var(--bz-surface) !important;
    color: var(--bz-text) !important;
    border: 1px solid rgba(148, 163, 184, .16) !important;
    box-shadow: 0 1px 0 rgba(255, 255, 255, .04) inset,
                0 18px 44px rgba(0, 0, 0, .45) !important;
}

/* ===========================================================================
   8. SCROLLBARS
   color-scheme:dark in design-system.css already darkens the native bar in
   Chrome. These pages also use -webkit-scrollbar in several places, and a
   styled light scrollbar survives color-scheme, so it is restated.
   =========================================================================== */
[data-bz-theme="dark"] ::-webkit-scrollbar {
    width: 10px;
    height: 10px;
}

[data-bz-theme="dark"] ::-webkit-scrollbar-track {
    background: #0A111E;
}

[data-bz-theme="dark"] ::-webkit-scrollbar-thumb {
    background: #2A3750;
    border-radius: 999px;
    border: 2px solid #0A111E;
}

[data-bz-theme="dark"] ::-webkit-scrollbar-thumb:hover {
    background: #3A4A68;
}

/* ===========================================================================
   9. IMAGERY
   Photographs and brand artwork are never filtered - see theme-dark-guard.css
   on why inversion is the wrong tool. A full-strength white image on a dark
   ground does glare, so it is softened very slightly and restored on hover,
   which costs nothing and keeps the content honest.
   =========================================================================== */
[data-bz-theme="dark"] .content-wraper img:not(.user img):not([class*="logo"]) {
    opacity: .94;
}

[data-bz-theme="dark"] .content-wraper img:hover {
    opacity: 1;
}

/* ===========================================================================
   10. DATATABLES  [2026-09-11]
   ---------------------------------------------------------------------------
   THE BUG: on /MYSHOP/QualifiedAttendanceConfig/QualifiedAttendanceConfigListing
   every alternating row rendered as a WHITE BOX, and hovering one fixed it.
   "Hover is correct, rest is not" is the signature of a half-covered widget:
   section 4 above themed `tbody tr:hover` and the header, and nothing else.

   WHY NOTHING CAUGHT IT. Two independent gaps:

     1. Tools/theme-extract-literals.py scans assests/css/*.css. The DataTables
        stylesheet is not there - it lives in assests/pluggins/DataTable/,
        assests/vendor/datatables/ and Content/vendors/, and this page loads it
        from a CDN (cdn.datatables.net), so there is no local file to scan at all.
     2. DataTables paints the BASE row `table.dataTable tbody tr` #ffffff and
        then only overrides `tr.odd` to #f9f9f9. Both are light, so a dark theme
        covering neither shows white rows wherever the container does not happen
        to paint behind them.

   FIVE STATES, KEPT DISTINCT. DataTables declares 56 light backgrounds across
   base / stripe / hover / selected / sorted-column. Collapsing them to one dark
   value is the tempting shortcut and it destroys the table: the stripe
   disappears, the sorted column stops being visible, and selection stops
   reading. Each state gets its own value, ordered so the hierarchy survives:

       base           #131C2E   resting row
       stripe (odd)   #172236   one step lighter - this IS the stripe
       sorted column  one step lighter again, per row state
       hover          #1B2740   clearly above both
       selected       brand fill + --bz-on-primary

   Specificity: DataTables ships selectors as deep as
   `table.dataTable.display tbody tr.odd.selected > .sorting_1` (0,5,3).
   !important is used so the prefix need not be deepened to match, and because
   this is DARK overriding a hardcoded LIGHT literal - the case set out in
   theme-dark-surfaces.css.
   =========================================================================== */

/* ---- base + stripe ------------------------------------------------------- */
[data-bz-theme="dark"] table.dataTable tbody tr {
    background-color: var(--bz-surface) !important;
    color: var(--bz-text) !important;
}

[data-bz-theme="dark"] table.dataTable.stripe tbody tr.odd,
[data-bz-theme="dark"] table.dataTable.display tbody tr.odd {
    background-color: var(--bz-surface-2) !important;
}

[data-bz-theme="dark"] table.dataTable tbody tr > td,
[data-bz-theme="dark"] table.dataTable tbody tr > th {
    background-color: transparent !important;
    border-color: rgba(148, 163, 184, .12) !important;
    color: var(--bz-text) !important;
}

/* ---- hover -------------------------------------------------------------- */
[data-bz-theme="dark"] table.dataTable.hover tbody tr:hover,
[data-bz-theme="dark"] table.dataTable.display tbody tr:hover,
[data-bz-theme="dark"] table.dataTable tbody tr:hover {
    background-color: #1B2740 !important;
}

/* ---- selected ----------------------------------------------------------- */
[data-bz-theme="dark"] table.dataTable tbody tr.selected,
[data-bz-theme="dark"] table.dataTable.stripe tbody tr.odd.selected,
[data-bz-theme="dark"] table.dataTable.display tbody tr.odd.selected,
[data-bz-theme="dark"] table.dataTable.hover tbody tr:hover.selected,
[data-bz-theme="dark"] table.dataTable.display tbody tr:hover.selected {
    background-color: var(--bz-primary-fill) !important;
    color: var(--bz-on-primary) !important;
}

[data-bz-theme="dark"] table.dataTable tbody tr.selected > td,
[data-bz-theme="dark"] table.dataTable tbody tr.selected a {
    color: var(--bz-on-primary) !important;
}

/* ---- sorted-column emphasis --------------------------------------------- */
/* One step lighter than the row it sits in, for every row state, so the sorted
   column stays visible whether the row is resting, striped or hovered. */
[data-bz-theme="dark"] table.dataTable.order-column tbody tr > .sorting_1,
[data-bz-theme="dark"] table.dataTable.display tbody tr > .sorting_1 {
    background-color: #1A2438 !important;
}

[data-bz-theme="dark"] table.dataTable.order-column tbody tr > .sorting_2,
[data-bz-theme="dark"] table.dataTable.display tbody tr > .sorting_2 {
    background-color: #182134 !important;
}

[data-bz-theme="dark"] table.dataTable.order-column tbody tr > .sorting_3,
[data-bz-theme="dark"] table.dataTable.display tbody tr > .sorting_3 {
    background-color: #171F31 !important;
}

[data-bz-theme="dark"] table.dataTable.display tbody tr.odd > .sorting_1,
[data-bz-theme="dark"] table.dataTable.order-column.stripe tbody tr.odd > .sorting_1 {
    background-color: #1E2945 !important;
}

[data-bz-theme="dark"] table.dataTable.display tbody tr.odd > .sorting_2,
[data-bz-theme="dark"] table.dataTable.order-column.stripe tbody tr.odd > .sorting_2 {
    background-color: #1C2740 !important;
}

[data-bz-theme="dark"] table.dataTable.display tbody tr.even > .sorting_1,
[data-bz-theme="dark"] table.dataTable.order-column.stripe tbody tr.even > .sorting_1 {
    background-color: #1A2438 !important;
}

[data-bz-theme="dark"] table.dataTable.display tbody tr.even > .sorting_2,
[data-bz-theme="dark"] table.dataTable.order-column.stripe tbody tr.even > .sorting_2 {
    background-color: #182134 !important;
}

[data-bz-theme="dark"] table.dataTable.display tbody tr.even > .sorting_3,
[data-bz-theme="dark"] table.dataTable.order-column.stripe tbody tr.even > .sorting_3 {
    background-color: #171F31 !important;
}

[data-bz-theme="dark"] table.dataTable.display tbody tr:hover > .sorting_1,
[data-bz-theme="dark"] table.dataTable.order-column.hover tbody tr:hover > .sorting_1 {
    background-color: #223255 !important;
}

[data-bz-theme="dark"] table.dataTable.display tbody tr:hover > .sorting_2,
[data-bz-theme="dark"] table.dataTable.order-column.hover tbody tr:hover > .sorting_2 {
    background-color: #20304F !important;
}

[data-bz-theme="dark"] table.dataTable.display tbody tr:hover > .sorting_3,
[data-bz-theme="dark"] table.dataTable.order-column.hover tbody tr:hover > .sorting_3 {
    background-color: #1E2D4A !important;
}

/* Selected rows keep the brand fill through every sorted-column variant - the
   twelve `.selected > .sorting_*` rules DataTables ships would otherwise
   repaint them in pale blue-grey. */
[data-bz-theme="dark"] table.dataTable tbody tr.selected > .sorting_1,
[data-bz-theme="dark"] table.dataTable tbody tr.selected > .sorting_2,
[data-bz-theme="dark"] table.dataTable tbody tr.selected > .sorting_3,
[data-bz-theme="dark"] table.dataTable tbody tr.odd.selected > .sorting_1,
[data-bz-theme="dark"] table.dataTable tbody tr.odd.selected > .sorting_2,
[data-bz-theme="dark"] table.dataTable tbody tr.odd.selected > .sorting_3,
[data-bz-theme="dark"] table.dataTable tbody tr.even.selected > .sorting_1,
[data-bz-theme="dark"] table.dataTable tbody tr.even.selected > .sorting_2,
[data-bz-theme="dark"] table.dataTable tbody tr.even.selected > .sorting_3,
[data-bz-theme="dark"] table.dataTable tbody tr:hover.selected > .sorting_1,
[data-bz-theme="dark"] table.dataTable tbody tr:hover.selected > .sorting_2,
[data-bz-theme="dark"] table.dataTable tbody tr:hover.selected > .sorting_3 {
    background-color: var(--bz-primary-fill) !important;
    color: var(--bz-on-primary) !important;
}

/* ---- the chrome around the table ---------------------------------------- */
[data-bz-theme="dark"] .dataTables_wrapper,
[data-bz-theme="dark"] .dataTables_info,
[data-bz-theme="dark"] .dataTables_length,
[data-bz-theme="dark"] .dataTables_filter,
[data-bz-theme="dark"] .dataTables_paginate {
    color: var(--bz-muted) !important;
}

[data-bz-theme="dark"] .dataTables_filter input,
[data-bz-theme="dark"] .dataTables_length select {
    background-color: #0C1524 !important;
    border: 1px solid rgba(148, 163, 184, .22) !important;
    color: var(--bz-text) !important;
}

/* [2026-09-11] `border-color` REMOVED from the resting state.
   ---------------------------------------------------------------------------
   THE BUG: the pager rendered as a strip of empty outlined boxes in Dark, and
   Standard draws nothing of the kind.

   DataTables gives every pager element `border: 1px solid TRANSPARENT` and then
   paints a visible border only on `.current` and `:hover`. That transparent
   border is load-bearing: it reserves the 1px so buttons do not shift when one
   becomes current, and it is why a resting pager in Standard shows no outlines
   at all.

   Setting `border-color` on that rule does not add a border - the border was
   always there - it REVEALS it, on every element carrying the class. That
   includes the ones with no text: the `first`/`last`/`ellipsis` members of a
   full_numbers pager, which Standard renders invisibly. Hence a row of empty
   boxes trailing off after Next.

   The rule for dark mode is the same as everywhere else in this feature: match
   what Standard PAINTS, not what it merely declares. Border stays transparent
   at rest; `.current` and `:hover` below give it one, exactly as Standard does.

   Do not re-add a resting border here. If the pager needs more definition in
   dark, give it to `.current`/`:hover`, or to the container. */
[data-bz-theme="dark"] .dataTables_paginate .paginate_button {
    color: var(--bz-text) !important;
    background: transparent !important;
    border-color: transparent !important;
}

/* An element carrying the class but no content is structural - the ellipsis
   slot and the first/last stubs. Standard shows nothing there, so neither does
   Dark. Belt and braces alongside the transparent border above: this also
   covers any skin that gives the resting state a real border of its own. */
[data-bz-theme="dark"] .dataTables_paginate .paginate_button:empty,
[data-bz-theme="dark"] .dataTables_paginate .paginate_button:empty:hover {
    background: transparent !important;
    border-color: transparent !important;
    box-shadow: none !important;
}

[data-bz-theme="dark"] .dataTables_paginate .paginate_button.current,
[data-bz-theme="dark"] .dataTables_paginate .paginate_button.current:hover {
    background: var(--bz-primary-fill) !important;
    color: var(--bz-on-primary) !important;
    border-color: transparent !important;
}

[data-bz-theme="dark"] .dataTables_paginate .paginate_button:hover {
    background: #1B2740 !important;
    color: var(--bz-text) !important;
}

[data-bz-theme="dark"] .dataTables_paginate .paginate_button.disabled,
[data-bz-theme="dark"] .dataTables_paginate .paginate_button.disabled:hover {
    color: var(--bz-muted) !important;
    background: transparent !important;
}

/* ===========================================================================
   11. CHART TEXT  [2026-09-11]
   ---------------------------------------------------------------------------
   THE BUG: on the FSM Dashboard's Order tab the donut legends rendered in near
   black on a dark card - "COMP... 20,100,000 (98.3%)" was there and unreadable.

   WHY NO AUDIT COULD SEE IT. These labels are not styled by CSS at all. They
   are SVG <text> drawn by amCharts 4, and their colour comes from the
   library's DEFAULT THEME, which is built for a white page. Nothing in this
   repository declares that colour, so a tool that measures declared colours
   has nothing to measure. Same for ApexCharts, Morris and Google Charts.

   That is the third distinct category this feature has had to learn:
       stylesheets  ->  inline <style> blocks  ->  colours no CSS declares
   The first two were found by scanning. This one can only be found by knowing
   the library has a light default.

   WHY A BLANKET FILL IS SAFE HERE. Checked before writing it: across all 27
   chart files there are exactly nine explicit label fills and every one of
   them is already `white`. So no chart in this product deliberately draws a
   DARK label that this rule would override - it only reaches the ones falling
   back to the library default. Slice labels that are already white stay white.

   CSS beats an SVG presentation attribute, so no !important is needed for the
   fill itself; it is used only to outrank the library's inline style when one
   is set.
   =========================================================================== */
[data-bz-theme="dark"] svg text,
[data-bz-theme="dark"] svg tspan {
    fill: var(--bz-text) !important;
}

/* ApexCharts draws its legend as HTML, not SVG, so it needs `color` too. */
[data-bz-theme="dark"] .apexcharts-legend-text,
[data-bz-theme="dark"] .apexcharts-tooltip-text,
[data-bz-theme="dark"] .apexcharts-datalabel-label {
    color: var(--bz-text) !important;
}

/* MAPS: THE TILES THEMSELVES  [2026-09-12]
   ---------------------------------------------------------------------------
   This section used to leave raster tiles alone deliberately, reasoning that an
   inverted map misreads terrain and road colours. That reasoning was about bare
   `invert(1)`, and it left the actual defect standing: on a dark page an
   OpenStreetMap tile is a WHITE RECTANGLE - the brightest object on the screen -
   across nine route and tracking views.

   `invert(1) hue-rotate(180deg)` is the pair that solves it. The inversion
   darkens the paper; the hue rotation puts the hues back, so water stays blue
   and parks stay green instead of turning orange and magenta.

   It is applied to .leaflet-tile-pane ONLY, never to .leaflet-container:

       tiles                       -> .leaflet-tile-pane     INVERTED, goes dark
       markers, popups, controls,
       vector overlays             -> SIBLING panes          untouched, true colour

   Scoping it to the tile pane is also what keeps it clear of the containing
   block hazard: that pane holds <img> tiles and nothing positioned, which is
   the case Tools/theme-containing-block-audit.py explicitly allows.

   Every tile layer in this product is OSM line-art cartography - there is no
   satellite or photographic layer that inversion would turn into a negative.
--------------------------------------------------------------------------- */
[data-bz-theme="dark"] .leaflet-tile-pane {
    -webkit-filter: invert(1) hue-rotate(180deg) brightness(.92) contrast(.94);
    filter: invert(1) hue-rotate(180deg) brightness(.92) contrast(.94);
}

/* The vector overlay SVG lives in a SIBLING pane, so it is not inverted - and
   the ground beneath it just went dark. This rule previously forced a DARK ink
   (#1F2937) so labels stayed readable on light tiles; with the tiles now dark
   that same value is the invisible-text bug in reverse, so it flips to light.
   The two are a pair: neither may change without the other. */
[data-bz-theme="dark"] .leaflet-container svg text,
[data-bz-theme="dark"] .leaflet-container svg tspan {
    fill: #E5E7EB !important;
}

/* ===========================================================================
   12. GRID BLOCKS READ AS ONE PANEL  [2026-09-11]
   ---------------------------------------------------------------------------
   THE BUG: on the Leave List the strip holding "Search:" rendered as a darker
   band across the card, with the pager and rows on a lighter one - reported as
   an "imbalance color row".

   THE CAUSE IS STRUCTURAL, NOT A WRONG COLOUR. Section 10 paints DataTables
   ROWS (`table.dataTable tbody tr` -> --bz-surface). The wrapper around them -
   .dataTables_wrapper, .dt-grid-wrap, .form_main - declares no background at
   all and never has. In STANDARD that is invisible: the page is white, the
   rows are white, so a transparent wrapper between them reads as one
   continuous white panel. In DARK the page ground (#0B1220) and the card
   (#131C2E) are deliberately different, so every transparent gap between
   painted children becomes a visible band.

   This is the general shape of the remaining dark-mode defects and worth
   naming: LIGHT MODE HIDES MISSING BACKGROUNDS, because everything defaults to
   the same white. Dark mode cannot. A container that only LOOKED like part of
   a card has to actually become one.

   So the grid block is painted as a whole, which is what Standard reads as.
   One rule covers every DataTable in the product, because .dataTables_wrapper
   is the library's own root element - no page-by-page chasing.

   Not !important: these wrappers declare no background, so there is nothing to
   outrank, and a page that DOES set its own keeps it.
   =========================================================================== */
[data-bz-theme="dark"] .dataTables_wrapper,
[data-bz-theme="dark"] .dt-grid-wrap,
/* .GridViewArea is the same shape from the older WebForms grids - a wrapper
   with no background of its own around painted rows. Found by sweeping the
   container classes used across every view against the dark rules that exist;
   it was the only one of sixteen with no painted parent to fall back on. */
[data-bz-theme="dark"] .GridViewArea {
    background-color: var(--bz-surface);
}

/* The chrome inside the block sits on that surface and must not re-declare a
   different one, or the banding simply moves. */
[data-bz-theme="dark"] .dataTables_wrapper .dataTables_filter,
[data-bz-theme="dark"] .dataTables_wrapper .dataTables_length,
[data-bz-theme="dark"] .dataTables_wrapper .dataTables_info,
[data-bz-theme="dark"] .dataTables_wrapper .dataTables_paginate,
[data-bz-theme="dark"] .dt-top-pager {
    background-color: transparent;
}

/* ===========================================================================
   13. CKEDITOR   [2026-09-11]
   ---------------------------------------------------------------------------
   WHY IT WAS MISSED. CKEditor's skin is not linked by any view - ckeditor.js
   injects it at runtime. The whole-solution audit only considers a stylesheet
   a page actually <link>s, which is what keeps its signal high, and it is
   exactly why this one was invisible: the file is in the repository, but
   nothing in the markup points at it. It is now named explicitly in the
   generator manifest.

   The generated rules cover the toolbar, panels and menus. The three things
   below are judgements a generator cannot make.
   =========================================================================== */

/* 1. THE EDITING AREA. [2026-09-14 - SUPERSEDED, read this before re-arguing it]
   This block used to say the canvas stays white ON PURPOSE: the author is
   composing something that will be READ on white - an email body, a printed
   template - so a dark canvas misrepresents the result, which is why Word and
   Docs keep the page light. That reasoning is still sound and is why the
   canvas was left white for three rounds.

   It was reported as a defect anyway, and the product owner's call is the one
   that counts: against a dark application a white slab reads as a bug, not as
   paper. The canvas is now dark, and the WYSIWYG objection is answered where
   it actually matters - CKEDITOR saves the body's innerHTML, never the canvas
   styling, so a template authored in dark still renders black-on-white in the
   email it becomes. The one real cost is that an author who explicitly PICKS
   a light text colour because the canvas is dark will produce content that is
   unreadable on white; nothing in CSS can prevent that.

   The canvas itself cannot be styled from here - it is an iframe, and its
   document is not reachable from this stylesheet. bz-theme.js copies the
   theme attribute onto the iframe's <html> and Scripts/ckeditor/contents.css
   carries the rules. The frame below is still drawn, so the editor reads as a
   panel with an edge rather than a hole in the page. */
[data-bz-theme="dark"] .cke_wysiwyg_frame,
[data-bz-theme="dark"] .cke_wysiwyg_div {
    border: 1px solid var(--bz-border-2) !important;
    border-radius: 6px !important;
    box-shadow: 0 2px 10px rgba(0, 0, 0, .35) !important;
}

/* 2. THE OUTER FRAME. Without this the editor floats with no edge against the
   page, and the toolbar appears to belong to nothing. */
[data-bz-theme="dark"] .cke,
[data-bz-theme="dark"] .cke_chrome {
    border: 1px solid var(--bz-border) !important;
    border-radius: 10px !important;
    overflow: hidden !important;
    box-shadow: var(--bz-shadow) !important;
}

/* 3. THE TOOLBAR ICONS ARE A SPRITE, NOT A FONT.
   moono ships dark-grey artwork on transparency, drawn for a light toolbar.
   On a dark toolbar it is nearly invisible, and no colour property reaches a
   background-image. Inverting the sprite is the standard answer and the only
   one available: CSS cannot recolour pixels, but it can flip them.

   `invert(1)` alone renders the grey slightly too bright and flat, so a small
   brightness pull-back keeps the icons reading as icons rather than glare.
   The few COLOURED icons (text colour, background colour) invert to their
   complement - accepted deliberately, because an unreadable toolbar is a much
   worse outcome than two swatches in the wrong hue. */
[data-bz-theme="dark"] .cke_button_icon,
[data-bz-theme="dark"] .cke_menubutton_icon {
    -webkit-filter: invert(1) brightness(.86) !important;
    filter: invert(1) brightness(.86) !important;
}

/* The combo arrows and separators are drawn from the same sprite. */
[data-bz-theme="dark"] .cke_combo_open,
[data-bz-theme="dark"] .cke_toolbar_separator {
    -webkit-filter: invert(1) brightness(.86) !important;
    filter: invert(1) brightness(.86) !important;
}

/* ===========================================================================
   14. THE ERP PAGE-TITLE TAB  (.breadCumb > span)   [2026-09-12]
   ---------------------------------------------------------------------------
   [2026-09-12 CORRECTION] The paragraph that stood here said ftsNewScreen.css
   declares `background: #fff` and then `background: url(../images/a.png)` on
   the SAME rule, with the image winning. That was wrong, and the mistake cost
   a second report - see section 15. The span carries only `background: #fff`.
   The PNG is on `.breadCumb > span::before` and `::after`, which are separate
   elements that section 14 never touched.

   theme-dark-surfaces.css paints the span, which is what section 14 refines.

   Correct as far as it goes, but it left the tab with no edge: a flat rectangle floating above
   the panel with nothing tying it to anything, which is what was marked as
   "alignment". The geometry is NOT touched - `border-radius: 0 0 14px 14px`
   and the padding are the existing design, and it hangs from the top edge by
   intent. It is given the raised surface and a hairline on the three sides it
   actually has, so it reads as a tab attached to the edge above rather than a
   loose block.
   =========================================================================== */
/* [2026-09-12] THE BORDER IS GONE AGAIN - it was invented.
   The previous revision added `border: 1px solid` to give the tab "definition".
   Standard has no border here at all: the shape comes entirely from the PNG
   plus `border-radius: 0 0 14px 14px`. Adding an outline to a shape with two
   rounded corners and two square ones drew visible notches down each side -
   the side-by-side shows them clearly against Standard's clean tab.

   Third time this feature has invented an edge (see 24.2 and 32.2). The rule
   is the same every time: match what Standard PAINTS. Surface and ink only,
   with a soft shadow for separation - no border. */
[data-bz-theme="dark"] .breadCumb > span {
    background-color: var(--bz-surface-2) !important;
    border: 0 !important;
    box-shadow: 0 2px 8px rgba(0, 0, 0, .34) !important;
    color: var(--bz-text) !important;
}

[data-bz-theme="dark"] .breadCumb > span,
[data-bz-theme="dark"] .breadCumb > h3 > span,
[data-bz-theme="dark"] .breadCumb > span * {
    color: var(--bz-text) !important;
}

/* The circular count badge on the Project Report filter list. Its view declares
   a bare `.badge { background-color:#fff; color:#7e7e7e }`, and `.badge` is
   withheld from the generator as a Bootstrap primitive (section 32), so nothing
   covered it. Scoped to the list it belongs to, which cannot reach any other
   badge in the product. */
[data-bz-theme="dark"] .mainFilterList .badge,
[data-bz-theme="dark"] .mainFilterList > li .badge {
    background-color: var(--bz-surface-2) !important;
    color: var(--bz-text) !important;
    border: 1px solid var(--bz-border) !important;
}

/* ===========================================================================
   15. THE TWO WHITE WINGS BESIDE THE PAGE-TITLE TAB   [2026-09-12]
   ---------------------------------------------------------------------------
   Reported on /OMS/Management/Master/Employee.aspx: "unwanted borders color
   fill for employees tab at top, background is huge noise for dark mode".

   Section 14 painted `.breadCumb > span` and stopped there. The noise is not
   on the span. ftsNewScreen.css (ERP line 232, MyShop line 272):

       .breadCumb>span::before, .breadCumb>span::after {
           content: '';
           position: absolute;
           width: 18px;  height: 35px;
           background: url(../images/a.png) no-repeat top left;
           left: -18px;  top: 0;
       }
       .breadCumb>span::after { left:auto; right:-26px; transform:rotate(-90deg); top:-9px; }

   Those are the concave corner fillers that blend a white tab into a white
   page - an 18x35 bitmap of the PAGE colour with a quarter-circle bitten out.
   The technique only works while the page is the colour the artwork was drawn
   in. On #0B1220 the artwork is simply two bright 18x35 rectangles flanking
   the tab, which is exactly the "border colour fill" in the screenshot.

   No amount of painting the span could ever have reached them, because they
   are not the span. Grepping for the image is what found it:

       grep -rn 'images/a.png' */assests/css/*.css
       -> ftsNewScreen.css:237  (ERP)    ::before/::after only
       -> ftsNewScreen.css:277  (MyShop) ::before/::after only
       -> no other reference anywhere in the repo

   THE FIX
   -------
   A concave corner is a trick for faking a join between two opaque surfaces.
   In Dark the tab already separates from the page by elevation and shadow, so
   the join does not need faking - the corners are simply retired. The tab
   keeps `border-radius: 0 0 14px 14px` and every dimension it has in Standard;
   only the two decorative pseudo-elements stop painting.

   `content: none` rather than `display: none` so the boxes are never generated
   at all - nothing is left to receive a stray background from a later rule.
   ========================================================================== */
[data-bz-theme="dark"] .breadCumb > span::before,
[data-bz-theme="dark"] .breadCumb > span::after,
[data-bz-theme="dark"] .breadCumb > h3 > span::before,
[data-bz-theme="dark"] .breadCumb > h3 > span::after {
    content: none !important;
    background: none !important;
}

/* The same artwork trick appears one level out: the bar itself is 64px of
   padding with nothing in it, and anything that paints that strip re-creates
   the band. Kept explicitly transparent so the tab floats on the page ground
   rather than on a slab of its own. */
[data-bz-theme="dark"] .breadCumb {
    background-color: transparent !important;
    background-image: none !important;
    border: 0 !important;
}

/* ===========================================================================
   16. THE BRAND MARK: PLATE OFF, ARTWORK LIFTED   [2026-09-12]
   ---------------------------------------------------------------------------
   Reported: "logo not transparent (make auto transparent with css for logo)".

   The logo file is not the problem. logo.png was decoded and measured rather
   than assumed:

       183x60, colour type 6 (RGBA)
       46.0% of pixels fully transparent
        0.0% opaque near-white
       dominant opaque colours  #094E8C (3085px)   #258FCE (1568px)

   It is already a two-tone blue mark on transparency. What reads as "not
   transparent" is a CSS PLATE the shell puts behind it:

       .logoWrap .bz-lockup-mark {          shell-erp-adapter.css : 808
           background: linear-gradient(180deg, #FFFFFF, #F1F5FB);
           border: 1px solid #E6EBF2;
           box-shadow: 0 1px 3px rgba(15,23,42,.08);
       }
       (MyShopProject/assests/css/ftsNewScreen.css : 2657, same rule)

   WHY THE PLATE EXISTS, AND WHY REMOVING IT IS NOT ENOUGH
   ---------------------------------------------------------------------------
   Measured against the dark header #101A2B:

       #094E8C  2.06:1     the mark's dominant navy - BELOW the 3:1 that
                           WCAG 1.4.11 asks of a graphical object
       #258FCE  4.90:1     the lighter accent, fine on its own

   So simply deleting the plate leaves the main body of the mark barely
   visible. The plate was doing real work; it just does it in the wrong
   century.

   THE TRANSFORM, AND WHY IT IS NOT `brightness()` ALONE
   ---------------------------------------------------------------------------
   `brightness(k)` MULTIPLIES, so lifting the navy far enough to clear 3:1
   drives the accent's blue channel past 255 and clips it toward cyan:

       brightness(1.40)   navy 3.32:1   accent #34C8FF   CLIPS
       brightness(1.60)   navy 4.17:1   accent #3BE5FF   CLIPS - visibly cyan

   `contrast(<1)` pulls both tones toward mid-grey first, which leaves room to
   brighten without hitting the ceiling:

       contrast(.70) brightness(1.35)   navy #3C7DB8  4.00:1
                                        accent #57BBF6  8.17:1   no clipping

   Both tones clear AA, the hue is preserved, and the two-tone structure of the
   mark survives. That is the pair used below.

   `filter` is a containing-block hazard everywhere else in this theme, which
   is why Tools/theme-containing-block-audit.py exists - but an <img> has no
   positioned descendants to capture, and the audit's SAFE list allows it on
   image elements for exactly this reason.
   =========================================================================== */
[data-bz-theme="dark"] .logoWrap .bz-lockup-mark {
    background: transparent !important;
    background-image: none !important;
    border: 0 !important;
    box-shadow: none !important;
}

[data-bz-theme="dark"] .logoWrap .bz-lockup-mark img,
[data-bz-theme="dark"] .headerMain .logoWrap img {
    -webkit-filter: contrast(.70) brightness(1.35);
    filter: contrast(.70) brightness(1.35);
}

/* ===========================================================================
   17. ROW ACTIONS READ AS A PAIR OF CONTROLS   [2026-09-12]
   ---------------------------------------------------------------------------
   Reported: "modern icons sleek in dark mode".

   Edit.png and Delete.png are 24x24 bitmaps - decoded and measured, not
   guessed:

       Edit.png    green disc #48C090 with a white glyph, 16% transparent
       Delete.png  red disc   #F00000 with a white glyph, 16% transparent

   237 references across 91 views, so this is the product's row-action idiom
   and not one page's decoration.

   Two things are wrong with them on a dark grid, and NEITHER is contrast - the
   green measures 5.54:1 and the red 3.83:1 against --bz-surface, so both are
   perfectly legible as they are:

     1. They are STICKERS, not controls. Two loose discs with no shared
        geometry, no hit area and no hover state. Every modern table has moved
        away from this because a user cannot tell where the click target is
        until the cursor changes.

     2. #F00000 is a pure primary red. On a light grid it reads as an accent;
        on #131C2E it is the most saturated thing on screen, so the eye is
        pulled to the DESTRUCTIVE action on every row of every page.

   THE CHIP IS PUT ON THE <img>, NOT ON ITS ANCHOR
   ---------------------------------------------------------------------------
   The obvious selector is `a:has(> img[src*="Edit.png"])`. It is not used
   here: :has() is Chrome 105, and this product's floor is Chrome 59, so that
   rule would be dead code for the browsers it was written for.

   An <img> is a replaced element but it still takes background, border,
   padding and border-radius. Putting the chip on the image itself needs no
   :has(), no new class, and no change to 91 views - and it works on 59.

   THE FOOTPRINT MUST NOT GROW - THIS WAS SHIPPED WRONG ONCE
   ---------------------------------------------------------------------------
   The first version of this rule used `box-sizing: content-box` with 3px of
   padding and a 1px border, arguing that not resizing the bitmap avoided
   resampling. That reasoning was right about the image and wrong about the
   page: it grew each control from 24px to 32px, and the Actions column is
   declared `Width="6%"`.

       6% of a ~1450px grid        ~87px
       less the cell's own padding ~67px usable
       two 32px chips + the space between the two <a> elements   ~68px

   One pixel over, so the second button wrapped to a new line and every grid
   row in the product doubled in height. Reported immediately, and correctly.

   `box-sizing: border-box` with an explicit 24px absorbs the padding and
   border INTO the original footprint. The rendered box is 24px - byte for
   byte what it was before this section existed - so no column, row height or
   toolbar anywhere in 91 views can move. The glyph draws at 18px inside it,
   which is a downscale of a 24px source and the price of the affordance.

   The lesson is not about this rule. It is that a purely visual change to an
   element inside a FIXED-WIDTH column is a layout change, and the width was
   declared right there in the markup.

   Scoped by the image's own src, which is exact: it cannot reach any other
   image in the product.
   =========================================================================== */
[data-bz-theme="dark"] img[src*="Edit.png" i],
[data-bz-theme="dark"] img[src*="Delete.png" i] {
    box-sizing: border-box;
    width: 24px;
    height: 24px;
    padding: 2px;
    border-radius: 7px;
    border: 1px solid transparent;
    vertical-align: middle;
    /* Small, and applied to both, so the pair stays consistent while the red
       stops shouting. */
    -webkit-filter: saturate(.86);
    filter: saturate(.86);
    transition: background-color var(--bz-t) var(--bz-ease),
                border-color var(--bz-t) var(--bz-ease);
}

[data-bz-theme="dark"] img[src*="Edit.png" i] {
    background-color: rgba(74, 222, 128, .10);
    border-color: rgba(74, 222, 128, .22);
}

[data-bz-theme="dark"] img[src*="Delete.png" i] {
    background-color: rgba(248, 113, 113, .10);
    border-color: rgba(248, 113, 113, .22);
}

[data-bz-theme="dark"] a:hover > img[src*="Edit.png" i],
[data-bz-theme="dark"] img[src*="Edit.png" i]:hover {
    background-color: rgba(74, 222, 128, .20);
    border-color: rgba(74, 222, 128, .46);
}

[data-bz-theme="dark"] a:hover > img[src*="Delete.png" i],
[data-bz-theme="dark"] img[src*="Delete.png" i]:hover {
    background-color: rgba(248, 113, 113, .20);
    border-color: rgba(248, 113, 113, .46);
}

/* ===========================================================================
   18. A LOADER SCRIM IS TRANSLUCENT ON PURPOSE   [2026-09-12]
   ---------------------------------------------------------------------------
   FSMDashboard.cshtml declares its grid loader as

       #gridLoader { position:absolute; top:0; left:0; width:100%; height:100%;
                     background: #ffffffa3; color: black; z-index: 999999; }

   A full-viewport white sheet at 64% opacity with black text, over a dark
   page. It had never once been reported by the audit, and the reason is
   worth keeping: `#ffffffa3` is EIGHT-digit hex, and parse_color in both
   tools handled #RGB and #RRGGBB only. An 8-digit value returned None and was
   treated as "not a colour" - so the brightest element on the page was
   invisible to the check that exists to find bright elements.

   Both parsers understand #RRGGBBAA and #RGBA now, and the generator duly
   produced a cover for it. That cover is opaque, because a generator cannot
   know that the alpha was the POINT: at 64% you can still see which grid is
   loading behind the scrim, and that is the difference between "the page is
   busy" and "the page is gone".

   So the intent is restored by hand - the same veil, in the page's colour
   instead of white - and the generator defers to it via --skip-covered.
   =========================================================================== */
[data-bz-theme="dark"] #gridLoader {
    background: rgba(11, 18, 32, .72) !important;
    background-color: rgba(11, 18, 32, .72) !important;
    color: var(--bz-text) !important;
}

/* ===========================================================================
   19. THE WHITE LINE THAT IS NOT A BORDER  [2026-09-12]
   ---------------------------------------------------------------------------
   "Extra white line in many places" kept being reported after the border audit
   read 0. The audit was right and incomplete: it matches `border-*` only, and
   a line can also be drawn by `box-shadow`, `outline` or `border-image`.

   The classic offender is the bevel highlight that light UIs put along a top
   edge - `inset 0 1px 0 rgba(255,255,255,.95)`. On a light card that reads as
   a soft sheen. On #131C2E it is a hard white rule across the top of the
   element, which is exactly what was being reported.

   Scanning all nine projects for light-coloured box-shadow/outline in rules
   not already theme-scoped found 18 distinct declarations. Most were not
   defects and are deliberately untouched:

     * .mCS-3d* scrollbar variants - verified UNUSED in markup, dead theme
       variants shipped with the customScroll plugin;
     * .bzh-* focus rings - a white ring on an indigo FAB, in a tour overlay
       that carries no theme rules at all and is the same in every appearance;
     * a .24-alpha bevel on a button, which reads as a bevel either way.

   What is corrected below is the six that genuinely paint a light line on a
   dark surface. The intent of each is preserved rather than removed - a bevel
   still bevels, at an alpha that belongs on a dark ground.
--------------------------------------------------------------------------- */

/* A near-white 35px inner glow inside the active tab. */
[data-bz-theme="dark"] #v-nav > ul > li.current,
[data-bz-theme="dark"] #v-nav > div.tab-content {
    box-shadow: inset 0 0 35px 5px rgba(255, 255, 255, .04) !important;
}

/* 1px white top bevel on the four dashboard tabs. */
[data-bz-theme="dark"] .tabOrg,
[data-bz-theme="dark"] .tabSk,
[data-bz-theme="dark"] .tabSg,
[data-bz-theme="dark"] .tabG {
    box-shadow: inset 0 1px 0 rgba(255, 255, 255, .06) !important;
}

/* .95 alpha is all but solid white - a hard rule across the modal's top. */
[data-bz-theme="dark"] #imgModal .modal-box {
    box-shadow: inset 0 1px 0 rgba(255, 255, 255, .06),
                0 18px 44px rgba(0, 0, 0, .55) !important;
}

/* Its own button carries the same bevel at .24. Low enough to read as a bevel
   either way, but its siblings on this dialog are already restated and a lone
   brighter edge among them is what gets noticed. */
[data-bz-theme="dark"] #imgModal #Duemessagebtn:hover {
    box-shadow: inset 0 1px 0 rgba(255, 255, 255, .10) !important;
}

/* ===========================================================================
   20. CONTROLS THAT VANISH INTO THE PAGE  [2026-09-13]
   ---------------------------------------------------------------------------
   Reported: the "Show Data" button looks broken in dark.

   Its label was never the problem. `.btn-show { background:#011a9d }` puts
   WHITE on that fill at 12.84:1 - the text is perfect. The fill itself is
   1.46:1 against the page, so the BUTTON is invisible and only floating text
   remains. That is the failure mode this file's own rule warns about: measure
   a fill against its PAGE, not only against its label.

   A dedicated pass over every rule that paints a `btn` and has no dark
   override found eight such controls. Each is restated below at a fill that
   actually reads, keeping the author's hue wherever the hue was the point.

   Deliberately NOT changed: `.bz-theme-switch__btn[aria-pressed]`, which the
   scan also flagged at 1.28. That widget already carries its own dark rules
   (#1E293B on #E6EDF8), its pressed pill sits on the switch's own track rather
   than on the page, and it is theme-aware by design.
--------------------------------------------------------------------------- */

/* #011a9d / #031366 -> the primary ramp, matching every other toolbar button.
   These live in per-view <style> blocks at (0,0,1,0), so a theme rule at
   (0,0,2,0) wins without !important. */
[data-bz-theme="dark"] .btn-show,
[data-bz-theme="dark"] .show-btn {
    background: #2563EB;
    background-image: linear-gradient(135deg, #3B82F6 0%, #2563EB 100%);
    border-color: transparent;
    color: #fff;
}
[data-bz-theme="dark"] .btn-show:hover,
[data-bz-theme="dark"] .show-btn:hover {
    background: #1D4ED8;
    background-image: linear-gradient(135deg, #2563EB 0%, #1D4ED8 100%);
    color: #fff;
}

/* Purple is the point of this one, so the hue is kept and only the hover -
   #440662, 1.29:1 - is lifted to something that survives a dark ground. */
[data-bz-theme="dark"] .btn-view-log:hover {
    background: #9333EA;
    color: #fff;
}

/* Rest is green and visible; the hover was a near-black navy at 1.57:1, so the
   button disappeared under the cursor. Kept in the blue family the author
   chose, at a lightness that reads. */
[data-bz-theme="dark"] #btnshow:hover {
    background: #1D4ED8 !important;
    border-color: #1D4ED8 !important;
    color: #fff !important;
}

/* A button whose whole identity is "dark" has nowhere to go on a dark page.
   Raised slate keeps it neutral and subordinate without making it invisible. */
[data-bz-theme="dark"] .btn-dark {
    background-color: #475569;
    background-image: none;
    border-color: #64748B;
    color: #fff;
}
[data-bz-theme="dark"] .btn-dark:hover {
    background-color: #64748B;
    color: #fff;
}

/* The tick and the radio dot are drawn as ::before in near-black. The BOX
   (::after) is already darkened by the surfaces layer, so the mark was black
   on dark - a checkbox that cannot show it is checked. */
[data-bz-theme="dark"] .checkbox-btn label::before {
    border-color: var(--bz-text) !important;
}
[data-bz-theme="dark"] .radio-btn label::before {
    background-color: var(--bz-text) !important;
}

/* ===========================================================================
   21. THE HEADER MARK HAS ITS WHITE BAKED IN  [2026-09-13]
   ---------------------------------------------------------------------------
   Reported: the "b" mark top-left keeps a white background in dark, while the
   same brand on the login screen is clean.

   Section 16 already sets `background: transparent` on the plate, and it works
   - the white is not coming from CSS. `logo.webp` is a 512x512 VP8X with the
   alpha flag NOT SET: the white is INSIDE the image, and no stylesheet can
   remove it. The login screen looks right because it uses a different asset,
   `NLogin/logo.png`, which is RGBA.

   So the fix is to stop showing that file in dark. `logo-mini.png` is 50x66
   RGBA - the compact mark already used as #miniLogo for the collapsed sidebar
   - and it is painted as a background while the opaque <img> is hidden.

   Scoped to dark only: Standard and Nextgen keep the white plate, which is
   deliberate there (ftsNewScreen.css gives it a white gradient and a border).
--------------------------------------------------------------------------- */
[data-bz-theme="dark"] .logoWrap .bz-lockup-mark img {
    display: none !important;
}
[data-bz-theme="dark"] .logoWrap .bz-lockup-mark {
    background: transparent !important;
    background-image: url("../images/logo-mini.png") !important;
    background-repeat: no-repeat !important;
    background-position: center !important;
    /* height matched to the 25px the <img> used, width follows the aspect */
    background-size: auto 25px !important;
    border: 0 !important;
    box-shadow: none !important;
}

/* ===========================================================================
   22. THE NUDGE ENGINE LOADS A DIFFERENT STYLESHEET SET  [2026-09-13]
   ---------------------------------------------------------------------------
   A fix is only a fix if the page loads the file it is written in.

   `_NudgeEngineLayout.cshtml` is a STANDALONE shell - its _ViewStart says so
   explicitly, and deliberately so: Nudge Engine is a Settings page and must
   not read as a Command Center sub-page. It pulls nudge-engine*.css plus
   @Html.Partial("_BzThemeAssets"), which is the STANDARD theme stack. It does
   NOT load command-center-theme.css.

   The white-bevel correction for these cards was written into that file
   earlier today, where the only page that renders `.ne-kpi-card` can never
   see it. Moved here, which the Nudge Engine does load.

   Its dark palette is fine and arrives another way: theme-token-bridge.css
   maps 15 of the 18 --cc-* tokens onto --bz-* under [data-bz-theme="dark"]
   (the 3 it skips are font and radius, not colour). That is also why the
   print block in design-system.css reaches these pages - the bridge carries
   the flipped --bz-* values straight through.

   A box-shadow is the exception the bridge cannot reach, because a shadow
   carries its own colour rather than reading one from a token. Hence this. */
[data-bz-theme="dark"] .ne-kpi-row .ne-kpi-card,
[data-bz-theme="dark"] .ne-rule-grid .ne-rule-card {
    box-shadow: inset 0 1px 0 rgba(255, 255, 255, .06),
                0 1px 2px rgba(0, 0, 0, .40), 0 1px 3px rgba(0, 0, 0, .45) !important;
}
[data-bz-theme="dark"] .ne-rule-grid .ne-rule-card:hover {
    box-shadow: inset 0 1px 0 rgba(255, 255, 255, .08),
                0 1px 2px rgba(0, 0, 0, .40), 0 1px 3px rgba(0, 0, 0, .45) !important;
}

/* ---------------------------------------------------------------------------
   THE SAME OPAQUE LOGO, IN THE NUDGE ENGINE TOP STRIP
   ---------------------------------------------------------------------------
   Section 21 replaced logo.webp in the header because the file has no alpha.
   The same file is used at 20x20 here, and .ne-topstrip is darkened by the
   surfaces layer - so it was a small white square on a dark strip.

   ::before rather than a background on the span: the span is an inline-flex
   holding the mark AND the word "BreezeFSM", so the image has to stay a
   separate box to keep the 6px gap. */
[data-bz-theme="dark"] .ne-topstrip-brand img {
    display: none !important;
}
[data-bz-theme="dark"] .ne-topstrip-brand::before {
    content: "";
    display: inline-block;
    width: 20px;
    height: 20px;
    background-image: url("../images/logo-mini.png");
    background-repeat: no-repeat;
    background-position: center;
    background-size: auto 20px;
}

/* ---------------------------------------------------------------------------
   THE ONE OPAQUE ROW ICON  [2026-09-13]
   ---------------------------------------------------------------------------
   Every action icon on root_user.aspx is RGBA - Add, Edit, Delete, copy,
   clear, reset-status, activeState, inactiveState, left-arw - except one.
   `change-password.png` is colour-type 2, no alpha, coloured artwork on a
   WHITE ground, so on a dark grid row it is a 24x24 white square.

   Inverting is the wrong tool here: the artwork is coloured, and inversion
   would turn it into a negative (the note at the top of theme-dark-guard.css).

   The right asset already exists and is sitting in the file, commented out:
   `change-dark.png`, 18x18 RGBA, the "Rev 2.0" variant this icon replaced. So
   dark simply shows that one instead.

   The 24x24 BOX is preserved exactly, with the 18px glyph centred inside it.
   Section 17 is the reason that matters: this is a grid action column, and
   changing an icon's footprint is what wrapped every row in the product once
   already. */
[data-bz-theme="dark"] a[title="Change Password"] img {
    display: none !important;
}
[data-bz-theme="dark"] a[title="Change Password"]::before {
    content: "";
    display: inline-block;
    width: 24px;
    height: 24px;
    vertical-align: middle;
    background-image: url("../images/change-dark.png");
    background-repeat: no-repeat;
    background-position: center;
    background-size: 18px 18px;
    /* [2026-09-13] change-dark.png is TRANSPARENT but its artwork is dark
       (mean ink luminance .133 - the name means "dark ink for a light UI",
       not "the dark-mode variant"). Chosen for its alpha without measuring
       its ink, which is the same mistake in reverse as the opaque logo. */
    -webkit-filter: brightness(0) invert(1);
    filter: brightness(0) invert(1);
    opacity: .85;
}

/* ===========================================================================
   24. THE DATE PICKER'S TRIGGER ICON  [2026-09-13]
   ---------------------------------------------------------------------------
   Reported: "date selector not available in dark mode" - and it was not
   missing, it was invisible.

   calendar-icon.png is 18x18 RGBA, so nothing covers it and nothing plates it.
   The ARTWORK is the problem. Decoding the file and measuring only the pixels
   with alpha:

       mean ink luminance      0.073
       against the page        2.01:1      invisible
       if flipped to white    16.02:1

   Alpha was never the question. Line art drawn near-black on transparency
   disappears on #0B1220 exactly as an opaque white plate shouts on it.

   `brightness(0) invert(1)` renders it as flat white rather than inverting it
   in place: the artwork measures chroma 143, so it is coloured, and a plain
   invert would produce a colour-shifted negative - the failure the note at the
   top of theme-dark-guard.css warns about. Flattened to white it is simply a
   white glyph, which is what every other icon in this chrome already is. The
   same treatment login-theme.css gives .mlogos.

   `filter` on an <img> is the case theme-containing-block-audit.py allows.

   This is one rule for 246 occurrences across 230 views - every date field in
   the product uses this class.
--------------------------------------------------------------------------- */
[data-bz-theme="dark"] img.calendar-icon,
[data-bz-theme="dark"] img.calendar-icon-2,
[data-bz-theme="dark"] img.calendar-icon-new {
    -webkit-filter: brightness(0) invert(1);
    filter: brightness(0) invert(1);
    opacity: .85;
}

/* ---------------------------------------------------------------------------
   THE PRINT ROW ICON  [2026-09-13]
   ---------------------------------------------------------------------------
   Measured the same way as the calendar trigger: print.png is 16x16 RGBA with
   a mean ink luminance of .168, which is 3.57:1 against the page and less
   against a row. It sits in a grid action column beside Edit and Delete, both
   of which section 17 already treats.

   Scoped by src like section 17, which cannot reach any other image, and the
   BOX is left alone - only the artwork is flipped. */
[data-bz-theme="dark"] img[src*="print.png" i] {
    -webkit-filter: brightness(0) invert(1);
    filter: brightness(0) invert(1);
    opacity: .85;
}

/* ===========================================================================
   25. THE CALENDAR ICON IS BEHIND THE FIELD, SO THE FILL HAD NOWHERE TO GO
       [2026-09-13, corrected 2026-09-14]
   ---------------------------------------------------------------------------
   Section 24 flipped calendar-icon.png to white and it was STILL not visible,
   because the ink was only half the story. The icon is not beside the field -
   it is layered UNDERNEATH it, and the view says so itself:

       .for-cust-icon  { position: relative; z-index: 1; }   <- stacking context
       #dtFrom, #dtTo  { position: relative; z-index: 1; background: transparent }
       .calendar-icon  { position: absolute; z-index: 0; }
       #dtFrom_B-1     { background: transparent !important; border: none; }
       #dtFrom_B-1Img  { display: none; }

   The DevExpress drop button is made invisible, the custom PNG sits BEHIND the
   field at z-index 0, and every layer of the field is transparent so the icon
   shows through it. Clicks land on the DX button, which is what opens the
   calendar. The icon itself is covered, and has never been clickable.

   The theme layer broke that: `[class*="dxeEditArea"]` is given
   `background-color: var(--bz-surface) !important`, and !important beats the
   view's id selector no matter that `#dtFrom_I` is far more specific. The
   field became opaque and buried the icon.

   THE FIRST FIX WAS WRONG. It moved the fill to `.for-cust-icon` - the only
   ancestor below the icon - and that did make the icon visible again. But the
   wrapper is not the field. Measured across the repo:

       238 wrappers in 222 views
       210 of them hold the <label> as well as the field
         7 have a <div> between the wrapper and the editor

   So filling the wrapper drew a shaded, rounded, bordered box around the LABEL
   AND THE FIELD TOGETHER on 210 of 238 date fields, while the plain <select>
   beside it showed a single field edge. Reported as "shade and border in from
   date, today like Branch". And there is nothing tighter to paint instead:
   218 of the 238 have no wrapper div at all.

   THE FIX: stop painting the wrapper, and let the FIELD carry its own fill and
   edge like every other DevExpress editor (theme-dx-adapter.css sections 10
   and 16 - the outer table takes fill, border and radius; the inner input is
   transparent and borderless; the two read as one box). A date field then
   matches both the Branch <select> and the Employee(s) ButtonEdit beside it.

   That puts an opaque field back over the icon, so the ICON comes up instead.
   The first fix rejected exactly that, on the grounds it would cover the DX
   button and stop the calendar opening - which it would have, on its own.
   `pointer-events: none` is what makes it safe: the icon paints above the
   field and every click passes through to the DX button beneath. The click
   target does not move, and the icon was not clickable to begin with.

   NOT SCOPED TO THE WRAPPER. 43 of the 254 layered icons sit in a view that
   has no `.for-cust-icon` at all - 41 of those still lower the icon to
   z-index 0 behind the field, so section 25 never reached them and their icon
   was buried too. Every one of the 246 view rules sets `z-index: 0` and not
   one raises it, and no icon anywhere carries a click handler, inline or
   bound - so raising all of them is safe and fixes the other 41 with it.

   Specificity: the view rules are all the bare `.calendar-icon {` (0,0,1,0)
   and this is (0,0,2,0), so it wins on merit and needs no !important even
   though the page <style> block comes after the stylesheet link.
--------------------------------------------------------------------------- */
[data-bz-theme="dark"] .calendar-icon,
[data-bz-theme="dark"] .calendar-icon-2,
[data-bz-theme="dark"] .calendar-icon-new {
    z-index: 2;
    pointer-events: none;
}

/* ===========================================================================
   26. THE GOOGLE MAP'S OWN CONTROLS  [2026-09-13]
   ---------------------------------------------------------------------------
   The Map / Satellite switch is drawn by Google, not by us, and it ships a
   white panel. Section 45 deliberately declined to filter `.gm-style` because
   tiles and markers share that subtree with no class between them - but the
   CONTROLS are a different matter: `.gm-style-mtc` and `.gm-control-active`
   are Google's own class names for its chrome, and nothing else is inside
   them. Recolouring those touches no tile and no marker.
--------------------------------------------------------------------------- */
[data-bz-theme="dark"] .gm-style .gm-style-mtc > button,
[data-bz-theme="dark"] .gm-style .gm-style-mtc > div,
[data-bz-theme="dark"] .gm-style .gm-control-active,
[data-bz-theme="dark"] .gm-style button.gm-control-active {
    background-color: #131C2E !important;
    background-image: none !important;
    color: #E6EDF8 !important;
    border-color: #24324A !important;
    box-shadow: none !important;
}

[data-bz-theme="dark"] .gm-style .gm-style-mtc > button:hover,
[data-bz-theme="dark"] .gm-style .gm-style-mtc > div:hover,
[data-bz-theme="dark"] .gm-style .gm-control-active:hover {
    background-color: #172236 !important;
    color: #FFFFFF !important;
}

/* The selected map type has to stay distinguishable from the other one. */
[data-bz-theme="dark"] .gm-style .gm-style-mtc > button[aria-checked="true"],
[data-bz-theme="dark"] .gm-style .gm-style-mtc > div[aria-checked="true"] {
    background-color: #2563EB !important;
    color: #FFFFFF !important;
}

/* ===========================================================================
   27. TWO HEADER ACTIONS BUILT TWO DIFFERENT WAYS  [2026-09-13]
   ---------------------------------------------------------------------------
   On the live-track header the close and the search are laid out by different
   mechanisms, which is why they do not line up:

       <span class="closerCss clstyle">   position: absolute; right: 2px; top: 0
       <i class="fa fa-search" style="float: right">   normal flow

   One is taken out of the flow and pinned to the top-right; the other floats
   inside the line box and lands wherever the text leaves it. They were never
   aligned to each other - they were never aligned at all.

   Both are pinned to the same top edge here, 25px apart, and given the same
   circular shape so they read as a pair. `float` has to be beaten with
   !important because it is written inline on the element.

   Colours follow the palette the rest of the theme uses: the close takes
   #DC2626 rather than the base #f73e2c (4.83:1 with white instead of 3.6:1),
   and the search takes the primary fill at 5.17:1.

   Scoped to `.Widgheading.relative`, which is the map/panel header pattern -
   the .dashboardHighlightWrap headings carry their own chip treatment and are
   not touched.
--------------------------------------------------------------------------- */
[data-bz-theme="dark"] .Widgheading.relative > i.fa-search,
[data-bz-theme="dark"] .Widgheading.relative > i.fa-close,
[data-bz-theme="dark"] .Widgheading.relative > .clstyle {
    position: absolute !important;
    float: none !important;
    top: 0;
    width: 25px;
    height: 25px;
    line-height: 25px;
    text-align: center;
    font-size: 12px;
    border-radius: 50%;
    cursor: pointer;
    box-sizing: border-box;
}

[data-bz-theme="dark"] .Widgheading.relative > .clstyle {
    right: 2px;
    background: #DC2626;
    color: #FFFFFF;
}
[data-bz-theme="dark"] .Widgheading.relative > .clstyle:hover {
    background: #B91C1C;
    color: #FFFFFF;
}

[data-bz-theme="dark"] .Widgheading.relative > i.fa-search {
    right: 33px;
    background: #2563EB;
    color: #FFFFFF;
}
[data-bz-theme="dark"] .Widgheading.relative > i.fa-search:hover {
    background: #1D4ED8;
    color: #FFFFFF;
}

/* The glyph inside the close span must not carry its own box. */
[data-bz-theme="dark"] .Widgheading.relative > .clstyle > i {
    line-height: inherit;
    font-size: inherit;
    color: inherit;
}

/* ---------------------------------------------------------------------------
   ...AND THE SEARCH ICON IS STYLED ON ITS ID  [2026-09-13]
   ---------------------------------------------------------------------------
   The rule above set the pair to matching circles and only half of it took.
   The reason is specificity, again: the map partial styles the search icon on
   its ID, in a view-level <style>, and an id beats any number of classes.

       #showMapSearch, #showMapSearchFV {          (0,1,0,0)
           float: right;  margin-right: 39px;  margin-top: -3px;
           background: #57b4ea;  padding: 4px 5px;  border-radius: 3px;
       }

   `float` and `position` were taken with !important, so the element did become
   absolute - but the id kept the radius, the padding, the margins and the
   colour. The result is a blue ROUNDED SQUARE pushed 39px left and 3px up,
   which is precisely what was on screen: not a misalignment, a half-applied
   rule.

   Matching the id lifts this to (0,1,1,0), which outranks (0,1,0,0) on the
   plain arithmetic - no !important needed, and nothing else on the page moves.
   All six views that carry this control use the same two ids.
--------------------------------------------------------------------------- */
[data-bz-theme="dark"] #showMapSearch,
[data-bz-theme="dark"] #showMapSearchFV {
    position: absolute;
    float: none;
    top: 0;
    right: 33px;
    margin: 0;
    padding: 0;
    width: 25px;
    height: 25px;
    line-height: 25px;
    text-align: center;
    font-size: 12px;
    border-radius: 50%;
    background: #2563EB;
    color: #FFFFFF;
    cursor: pointer;
    box-sizing: border-box;
}

[data-bz-theme="dark"] #showMapSearch:hover,
[data-bz-theme="dark"] #showMapSearchFV:hover {
    background: #1D4ED8;
    color: #FFFFFF;
}

/* ===========================================================================
   29. THE DEVEXPRESS PAGER IS HYPHENATED TOO  [2026-09-13]
   ---------------------------------------------------------------------------
   Same shape as section 14: the adapter carries `dxpLite` - the pager SHELL -
   and nothing for anything inside it. Every real pager class is hyphenated and
   had no rule at all:

       dxp-button   dxp-disabledButton   dxp-num      dxp-current
       dxp-comboBox dxp-dropDownButton   dxp-summary  dxp-pageSizeItem
       dxp-ellip    dxp-right

   So "< Prev" and "Next >" stayed light grey slabs and the page-size box
   stayed a white field with a bright caret, on an otherwise dark grid.
--------------------------------------------------------------------------- */
[data-bz-theme="nextgen"] [class*="dxp-button"],
[data-bz-theme="dark"] [class*="dxp-button"],
[data-bz-theme="nextgen"] [class*="dxp-num"],
[data-bz-theme="dark"] [class*="dxp-num"],
[data-bz-theme="nextgen"] [class*="dxp-ellip"],
[data-bz-theme="dark"] [class*="dxp-ellip"] {
    background-color: var(--bz-surface-2) !important;
    background-image: none !important;
    color: var(--bz-text) !important;
    border-color: var(--bz-border) !important;
}

[data-bz-theme="nextgen"] [class*="dxp-button"]:hover,
[data-bz-theme="dark"] [class*="dxp-button"]:hover,
[data-bz-theme="nextgen"] [class*="dxp-num"]:hover,
[data-bz-theme="dark"] [class*="dxp-num"]:hover {
    background-color: var(--bz-bg-2) !important;
    color: var(--bz-text) !important;
}

/* The current page is the one thing in a pager that must stand out. */
[data-bz-theme="nextgen"] [class*="dxp-current"],
[data-bz-theme="dark"] [class*="dxp-current"] {
    background-color: var(--bz-primary-fill) !important;
    background-image: none !important;
    color: var(--bz-on-primary) !important;
    border-color: transparent !important;
}

/* A disabled pager button must read as unavailable, not as a light slab. */
[data-bz-theme="nextgen"] [class*="dxp-disabledButton"],
[data-bz-theme="dark"] [class*="dxp-disabledButton"] {
    background-color: transparent !important;
    background-image: none !important;
    color: var(--bz-muted) !important;
    border-color: var(--bz-border) !important;
}

/* Page-size box: the field, its drop-down button and the list it opens. */
[data-bz-theme="nextgen"] [class*="dxp-comboBox"],
[data-bz-theme="dark"] [class*="dxp-comboBox"],
[data-bz-theme="nextgen"] [class*="dxp-pageSizeItem"],
[data-bz-theme="dark"] [class*="dxp-pageSizeItem"] {
    background-color: var(--bz-surface) !important;
    background-image: none !important;
    color: var(--bz-text) !important;
    border-color: var(--bz-border-2) !important;
}

[data-bz-theme="nextgen"] [class*="dxp-dropDownButton"],
[data-bz-theme="dark"] [class*="dxp-dropDownButton"] {
    background-color: var(--bz-surface-2) !important;
    background-image: none !important;
    color: var(--bz-text) !important;
    border-color: var(--bz-border) !important;
}

[data-bz-theme="nextgen"] [class*="dxp-summary"],
[data-bz-theme="dark"] [class*="dxp-summary"] {
    color: var(--bz-muted) !important;
    background-color: transparent !important;
}

/* ===========================================================================
   30. A CHECKED BOX THAT LOOKED UNCHECKED  [2026-09-13]
   ---------------------------------------------------------------------------
   `.styled-checkbox` draws its box with `label:before` and its tick with
   `label:after`. The base is already dark-friendly:

       :checked  + label:before { background: #094e8c }   brand blue
       :checked  + label:after  { background: white }     the tick
       :disabled + label:before { background: #ddd }      light - needs flipping

   The generated layer flipped the CHECKED state as well, to
   `var(--bz-surface)`. Unchecked is `--bz-surface-2` (#172236) and checked
   became `--bz-surface` (#131C2E) - two shades of the same dark, so a ticked
   box was indistinguishable from an empty one.

   The disabled flip was right (#ddd is light); the checked flip was not, and
   `#094e8c` was never light to begin with. Restated as the brand fill, which
   is what the control was always saying: white tick at 5.17:1 on it, and the
   box itself at 3.29:1 against the card so it reads as filled.

   `.styled-checkbox` appears in 222 views - this is one rule for all of them.
--------------------------------------------------------------------------- */
[data-bz-theme="nextgen"] .styled-checkbox:checked + label:before,
[data-bz-theme="dark"] .styled-checkbox:checked + label:before,
[data-bz-theme="nextgen"] .styled-checkbox input:checked + label:before,
[data-bz-theme="dark"] .styled-checkbox input:checked + label:before {
    background-color: var(--bz-primary-fill) !important;
    background-image: none !important;
    border-color: var(--bz-primary-fill) !important;
}

/* ===========================================================================
   31. THE REPORT VIEWER AND DESIGNER  [2026-09-13]
   ---------------------------------------------------------------------------
   Three pages embed one - all in the Reports project; ERP.UI and MyShopProject
   have none. Their own stylesheets are fully covered already; what had no rule
   at all is the chrome DevExpress emits at runtime.

   That vocabulary cannot be grepped from source, so it was read out of the
   assemblies instead:

       dxXtraReports_Btn*          18   toolbar buttons
       dxXtraReports_PageBorder_*   8   the frame around the PAPER
       dxrd-image-*               240   designer sprite icons
       dxrd-*                     670   designer chrome
       documentViewer, dxmLiteReportToolbarPane

   THE PAPER STAYS LIGHT. A report is a document; the sheet, its border and the
   report's own inline-styled content are deliberately untouched. What goes dark
   is the canvas the sheet floats on and the chrome around it - which is exactly
   what a PDF viewer does.

   WHY THE ICONS ARE SAFE. The blocker was 258 sprite icons embedded in the DLL:
   darkening a toolbar whose glyphs are near-black makes it unusable. Rather
   than guess, the PNG streams were extracted from the assembly and their ink
   measured over the pixels that have alpha:

       21 sprite sheets decoded, mean ink luminance 0.41 - 0.46
       darkest sheet 0.289

   Mid-tone, not near-black - DevExpress drew them to work on either ground.
       0.42  on --bz-surface-2   7.12:1
       0.289 on --bz-surface-2   5.14:1

   So the chrome can go dark without touching a single icon.

   The designer is themed by NAMED GROUP rather than by a blanket
   `[class*="dxrd-"]` with exclusions: a positive list can only affect what it
   names, and the canvas groups (surface, preview, band, page, brick, control)
   are simply never listed.
--------------------------------------------------------------------------- */

/* ---- viewer: the canvas the sheet floats on, and the toolbar -------------- */
[data-bz-theme="dark"] [class*="documentViewer"],
[data-bz-theme="dark"] [class*="dxmLiteReportToolbarPane"] {
    background-color: var(--bz-bg-2) !important;
    background-image: none !important;
    color: var(--bz-text) !important;
    border-color: var(--bz-border) !important;
}

[data-bz-theme="dark"] [class*="documentViewerSeparatorDivElement"] {
    background-color: var(--bz-border) !important;
    border-color: var(--bz-border) !important;
}

/* ---- designer chrome, by name. No canvas group appears in this list. ------ */
[data-bz-theme="dark"] [class*="dxrd-toolbar"],
[data-bz-theme="dark"] [class*="dxrd-menu"],
[data-bz-theme="dark"] [class*="dxrd-properties"],
[data-bz-theme="dark"] [class*="dxrd-accordion"],
[data-bz-theme="dark"] [class*="dxrd-treelist"],
[data-bz-theme="dark"] [class*="dxrd-right"],
[data-bz-theme="dark"] [class*="dxrd-group"],
[data-bz-theme="dark"] [class*="dxrd-editor"],
[data-bz-theme="dark"] [class*="dxrd-datasource"],
[data-bz-theme="dark"] [class*="dxrd-collectioneditor"],
[data-bz-theme="dark"] [class*="dxrd-wizard"],
[data-bz-theme="dark"] [class*="dxrd-table"],
[data-bz-theme="dark"] [class*="dxrd-pivot"],
[data-bz-theme="dark"] [class*="dxrd-formatting"],
[data-bz-theme="dark"] [class*="dxrd-multivalue"],
[data-bz-theme="dark"] [class*="dxrd-action"],
[data-bz-theme="dark"] [class*="dxrd-boolean"] {
    background-color: var(--bz-surface) !important;
    background-image: none !important;
    color: var(--bz-text) !important;
    border-color: var(--bz-border) !important;
}

/* A designer icon is a sprite: give it a box, never a colour. */
[data-bz-theme="dark"] [class*="dxrd-image-"] {
    background-color: transparent !important;
}

/* ===========================================================================
   32. THE LOADING OVERLAY  [2026-09-13]
   ---------------------------------------------------------------------------
   `.overlay` is a SCRIM: its base is `rgba(0,0,0,.5)`, deliberately
   see-through so the page stays visible behind it while data loads. The
   generated layer replaced it with an opaque `var(--bz-surface-2)`, which is
   why the page behind disappeared - reported as "background not visible".

   Restated as a scrim in the dark palette. Translucency is the POINT of the
   element; a flat fill is not a darker version of it, it is a different
   control. */
[data-bz-theme="dark"] .overlay,
[data-bz-theme="dark"] #loading-overlay {
    background-color: rgba(11, 18, 32, .72) !important;
    background-image: none !important;
}

/* The opaque logo, in the loader orb - same swap as sections 21 and 24. The
   orb is a 64px flex-centred circle, so the replacement is a flex item at the
   same 66% the <img> used, and `brightness(0) invert(1)` renders the mark flat
   white on the dark plate. */
[data-bz-theme="dark"] .bz-load-orb > img,
[data-bz-theme="dark"] .cc-aiload-orb > img.cc-aiload-logo {
    display: none !important;
}

[data-bz-theme="dark"] .bz-load-orb::before,
[data-bz-theme="dark"] .cc-aiload-orb::before {
    content: "";
    display: block;
    width: 66%;
    height: 66%;
    background-image: url("../images/logo-mini.png");
    background-repeat: no-repeat;
    background-position: center;
    background-size: contain;
    -webkit-filter: brightness(0) invert(1);
    filter: brightness(0) invert(1);
}

/* ===========================================================================
   REVERTED: the mark swap was wrong  [2026-09-13]
   ---------------------------------------------------------------------------
   Sections 21, 22, 32 and the Command Center equivalents replaced logo.webp
   with logo-mini.png, on the reasoning that logo.webp is opaque and
   logo-mini.png has an alpha channel. The alpha was right and the CONTENT was
   never checked.

   Decoded and previewed, the two files are different artwork:

       logo.webp       the "b" brand mark          512x512, opaque
       logo-mini.png   a speech-bubble glyph        50x66,  RGBA
       logo.png        the full "BreezeFSM" wordmark 183x60, RGBA

   So the swap did not make the mark transparent - it replaced the brand with a
   different symbol, in four places. Reported as "b breeze logo missing", which
   is exactly what had happened.

   There is NO transparent "b" in this repository - every square RGBA candidate
   was checked, including android-icon.png, which is the Android robot.

   So the <img> goes back, and the only honest treatment for an opaque
   white-backed brand mark on a dark UI is a DELIBERATE light chip: a rounded
   plate sized to the mark, which reads as a brand lockup rather than as a
   stray white box. A proper fix needs a transparent "b" asset that does not
   exist yet.

   > Checking that an image has an alpha channel is not checking what the image
   > is a picture of.
--------------------------------------------------------------------------- */
[data-bz-theme="dark"] .logoWrap .bz-lockup-mark img,
[data-bz-theme="dark"] .ne-topstrip-brand img,
[data-bz-theme="dark"] .bz-load-orb > img,
[data-bz-theme="dark"] .cc-aiload-orb > img.cc-aiload-logo {
    display: block !important;
}

[data-bz-theme="dark"] .logoWrap .bz-lockup-mark::before,
[data-bz-theme="dark"] .ne-topstrip-brand::before,
[data-bz-theme="dark"] .bz-load-orb::before,
[data-bz-theme="dark"] .cc-aiload-orb::before {
    content: none !important;
}

/* The deliberate chip. White, because the mark's own ground is white. */
[data-bz-theme="dark"] .logoWrap .bz-lockup-mark {
    background: #FFFFFF !important;
    background-image: none !important;
    border: 1px solid rgba(148, 163, 184, .22) !important;
    border-radius: 11px !important;
}

[data-bz-theme="dark"] .bz-load-orb,
[data-bz-theme="dark"] .cc-aiload-orb {
    background-color: #FFFFFF !important;
    background-image: none !important;
}

/* ===========================================================================
   33. THE SELECT'S CARET WAS BURIED THE SAME WAY  [2026-09-14]
   ---------------------------------------------------------------------------
   Section 25 was not one page's bug, and it was not only the calendar icon.
   Auditing both projects for the signature of "something is layered behind
   this control" -

       position: relative;  z-index: 1;  background: transparent;

   - returns 1,099 occurrences across 29 selectors, and the things parked
   behind them at z-index 0 are two families, not one:

       .calendar-icon (+ -2, -new)        238    fixed in section 25
       .h-branch-select::after            176    <- this
       .h-branch-select-new::after         26    <- this
       .custom-select/-2::after             1    <- this

   The caret is not a glyph in the select. The view removes the native arrow
   with `-webkit-appearance: none`, draws its own - a 28x18 #094e8c plate with
   a rotated `<` in it - as an ::after on the WRAPPER at z-index 0, and makes
   the select transparent at z-index 1 so the plate shows through it:

       .h-branch-select        { position: relative; }
       .h-branch-select::after { content: "<"; position: absolute; z-index: 0;
                                 background: #094e8c; color: #fff; }
       #ddlState, #slmonth...  { -webkit-appearance: none;
                                 position: relative; z-index: 1;
                                 background-color: transparent; }

   `[data-bz-theme="dark"] select:not(.btn)` then fills the select
   `#0C1524 !important`. The select paints at z-index 1, the plate at 0, so
   the plate goes under it - and because the native arrow was removed, the
   control is left with NO drop indicator at all in dark mode. Light mode
   cannot show this: there the select is transparent over a white page, so
   the plate reads normally.

   Same fix as the icon, for the same reason, with the same safeguard. The
   caret comes up above the field, and `pointer-events: none` keeps the click
   going through to the select underneath - without it the plate would swallow
   the click on exactly the spot users aim at to open the dropdown.

   Not scoped to any one wrapper class: all four selectors are listed, so the
   176 + 26 + 1 rule blocks are covered wherever the view puts them.

   The other things found parked behind something were checked and are not
   burials: `.cluster > div:before` is a Leaflet marker ring, `.tool::*` is a
   tooltip held at opacity 0, `.cke_iframe_shim` is a CKEditor utility, and
   `.corner` is already covered (theme-dark-surfaces.css). `.fsm-date-input
   input` is transparent for a different reason and is already named in
   command-center-theme.css. The Chosen widget's caret carries no z-index at
   all, so nothing ever buried it.
--------------------------------------------------------------------------- */
[data-bz-theme="dark"] .h-branch-select::after,
[data-bz-theme="dark"] .h-branch-select-new::after,
[data-bz-theme="dark"] .custom-select::after,
[data-bz-theme="dark"] .custom-select-2::after {
    z-index: 2;
    pointer-events: none;
}

/* ===========================================================================
   34. THE POST-LOGIN LOADER WAS A LIGHTER SLAB  [2026-09-14]
   ---------------------------------------------------------------------------
   Reported as: signing in, before the dashboard arrives, the background is a
   blank panel instead of looking like the rest of the app.

   #pageLoader is the full-screen cover _Layout.cshtml paints as the very first
   thing in <body> and hides once the page is ready - so it IS the screen you
   look at between the sign-in click and the dashboard. The login page itself
   sets Layout = "" and never renders it, which is why this shows up only on
   the way IN.

   The layout declares `#pageLoader { background: #fff }`, and the cover for it
   was written by theme-gen-dark-surfaces.py, which maps a light fill to
   `var(--bz-surface)`. That is the right answer for a card and the wrong one
   for a full-page cover: --bz-surface is #131C2E, the CARD colour, while the
   page itself is --bz-bg #0B1220. The loader therefore rendered as a slab a
   full step lighter than the application behind it.

   Every loader that was written by hand is either the page ground or a
   translucent scrim over it:

       .bz-page-loader              rgba(6, 11, 20, .78)
       #gridLoader                  rgba(11, 18, 32, .72)
       .overlay / #loading-overlay  rgba(11, 18, 32, .72)
       #pageLoader                  var(--bz-surface)      <- the odd one out

   It stays OPAQUE, unlike those three. They dim a page that is already painted
   and dark; this one covers a page that has not painted yet, so a translucent
   scrim would let the unstyled document show through - a white flash, which is
   the one thing a first-paint cover exists to prevent. Opaque, but the PAGE
   ground, so the loader is indistinguishable from the app it is standing in
   for and only the orb and caption are visible on it.

   theme-dark-polish.css is linked after theme-dark-surfaces.css in every
   shell, and both rules are (0,1,1,0) with !important, so this wins on source
   order. The generated rule is left exactly as it is - it is regenerated from
   the product's own declarations, and editing it by hand would be undone the
   next time the generator runs.
--------------------------------------------------------------------------- */
[data-bz-theme="dark"] #pageLoader {
    background-color: var(--bz-bg) !important;
    background-image: none !important;
}
