/* ============================================================================
   theme-nextgen.css - the MODERN + DARK sign-in design layer.

   NAMING DEBT, stated up front: the filename says nextgen and the file now
   carries Dark as well. It is linked from 46 places and declared in 9 csproj
   files, so renaming is churn with no user-visible benefit - but the name is
   misleading and that is worth knowing before opening it.
   [2026-09-16]

   Modern became the working appearance on 2026-09-16, and this is the file it
   grows in. Everything here is scoped to [data-bz-theme="nextgen"] with ONE
   deliberate exception, explained in section 1. Standard and Dark must come
   out byte-for-byte unchanged by anything in this file.

   WHY IT IS A SEPARATE FILE AND NOT MORE OF login-theme.css

   login-theme.css is the SIGN-IN stylesheet - it is linked by the two sign-in
   pages and a handful of password screens, and nothing else. The texture
   component below is meant for the whole of Modern, so it cannot live there:
   putting it in login-theme.css would mean every page that ever wants a
   textured surface has to pull in the sign-in stylesheet.

   This file is linked wherever the theme set is linked, so a surface anywhere
   in Modern can opt in by adding one element.

   LOAD ORDER
   It must come AFTER login-theme.css and after theme-dark-polish.css. Several
   rules here refine surfaces those files already theme, and they do it at
   matching specificity on purpose - source order is what settles it, so that
   removing this file restores the previous appearance exactly rather than
   leaving half-overridden rules behind.

   Shared byte-for-byte across all nine web roots, like the other theme files.
   ASCII-only. CRLF. Chrome 59 floor - no :has(), no :where(), no flex gap,
   no color-mix(), no conic-gradient.
   ============================================================================ */


/* ---------------------------------------------------------------------------
   1. THE TEXTURE LAYER  -  .bz-ng-tex

   A decorative element any surface can host. The reference for it is the silk
   ribbon that sweeps the top-right of a card: light blue into periwinkle,
   dissolving as it travels.

   WHY IT IS AN ELEMENT AND NOT A PSEUDO-ELEMENT

   Because pseudo-elements run out. On the sign-in panel both were already
   spent - login-modern.css uses .mainLogin .contentArea::before for the 56px
   grid and ::after for the anti-banding grain - and there is no third. The
   first version of this texture worked around that by hanging off
   .lg-stage::before and sizing itself with calc(100vw - 500px) to guess the
   panel's box back. That rendered correctly and was fragile for no reason: it
   had to know the form column's width at two breakpoints, and it would have
   drifted the moment either moved.

   An element sized `inset: 0` against its own host needs to know nothing.

   THE ONE UNSCOPED RULE

   `.bz-ng-tex { display: none }` is deliberately NOT scoped to nextgen. The
   markup is shared by all three appearances - there is no way to render an
   element in one theme only - so the default has to be "invisible", and only
   Modern turns it on. Standard and Dark therefore see an empty, unstyled,
   display:none span: no box, no paint, no layout, nothing to measure. That is
   the whole cost of the HTML change.

   STACKING

   `z-index: -1` puts the texture directly above its host's background and
   below every child, which is exactly what a surface texture is. For that to
   resolve against the HOST rather than leak upward, the host has to be a
   stacking context - hence `position: relative; z-index: 0` on the hosts in
   section 2. Without the z-index the texture would fall behind the host's own
   opaque background and vanish.

   `pointer-events: none` is not optional. This element covers the whole
   surface, including the card that holds the sign-in form.
--------------------------------------------------------------------------- */
.bz-ng-tex { display: none; }

[data-bz-theme="nextgen"] .bz-ng-tex,
[data-bz-theme="dark"] .bz-ng-tex {
    display: block;
    position: absolute;
    z-index: -1;
    top: 0;
    right: 0;
    bottom: 0;
    left: 0;
    border-radius: inherit;
    overflow: hidden;
    pointer-events: none;
    background-repeat: no-repeat;
    background-position: 50% 50%;
    background-size: 100% 100%;
}

/* THE TWO SURFACE TREATMENTS

   The reference is a deep blue field with rotated square PANELS clustered to
   one side: a few large ones at low alpha with a hairline edge, some nested
   outlines, a couple of restrained bright accents, and a single light source.
   Large negative space where the reading happens.

   Geometry is SVG because it is geometry - crisp edges are the design language
   here, not a failure to soften one (see 77.1, where blurred ribbons drew
   streaks). Resolution independent, so it stays clean on a UHD panel.

   `background-size: cover` with the SVG's own aspect ratio left alone, rather
   than `100% 100%`: stretching a 45-degree diamond to fit the host would turn
   it into a rhombus at every window size that is not 4:3. Geometry crops
   gracefully; it does not stretch gracefully.

   THE LIGHT comes from ONE source, top-right, as two soft radial gradients
   under the geometry. Both end at the same colour with alpha 0, so neither can
   draw an edge.

   NEGATIVE SPACE is structural, not a mask: nothing is drawn left of x=658 of
   the 1200-unit viewBox (55%), which is where the headline column sits. There
   is no artwork behind the copy to fight it - so there is no mask to keep in
   sync either.

   No shape uses a drop shadow; depth comes from overlap and alpha alone. */
[data-bz-theme="nextgen"] .bz-ng-tex--panel,
[data-bz-theme="dark"] .bz-ng-tex--panel {
    background-image:
        radial-gradient(34% 30% at 93% -6%, rgba(224, 242, 254, .19), rgba(224, 242, 254, 0) 66%),
        linear-gradient(90deg, rgba(4, 12, 34, 0) 80%, rgba(4, 12, 34, .18) 100%),
        url("data:image/svg+xml,%3Csvg xmlns='http://www.w3.org/2000/svg' viewBox='0 0 1600 900'%3E%3Cdefs%3E%3ClinearGradient id='g' x1='0' y1='0' x2='1' y2='1'%3E%3Cstop offset='0' stop-color='%23E0F2FE'/%3E%3Cstop offset='1' stop-color='%2338BDF8'/%3E%3C/linearGradient%3E%3C/defs%3E%3Cpolygon points='760 -40 950 150 760 340 570 150' fill='%23FFFFFF' opacity='.055' stroke='rgba(255,255,255,.11)' stroke-width='1.4'/%3E%3Cpolygon points='900 -90 1200 210 900 510 600 210' fill='%23FFFFFF' opacity='.055' stroke='rgba(255,255,255,.11)' stroke-width='1.4'/%3E%3Cpolygon points='1180 280 1460 560 1180 840 900 560' fill='%23FFFFFF' opacity='.055' stroke='rgba(255,255,255,.11)' stroke-width='1.4'/%3E%3Cpolygon points='1010 260 1180 430 1010 600 840 430' fill='%23071232' opacity='.26' stroke='rgba(255,255,255,.05)' stroke-width='1.4'/%3E%3Cpolygon points='430 460 630 660 430 860 230 660' fill='%23071232' opacity='.26' stroke='rgba(255,255,255,.05)' stroke-width='1.4'/%3E%3Cpolygon points='1340 30 1490 180 1340 330 1190 180' fill='%23FFFFFF' opacity='.055' stroke='rgba(255,255,255,.11)' stroke-width='1.4'/%3E%3Cpolygon points='640 180 760 300 640 420 520 300' fill='%23071232' opacity='.26' stroke='rgba(255,255,255,.05)' stroke-width='1.4'/%3E%3Cpolygon points='1290 570 1480 760 1290 950 1100 760' fill='%23071232' opacity='.26' stroke='rgba(255,255,255,.05)' stroke-width='1.4'/%3E%3Ccircle cx='180' cy='190' r='56' fill='none' stroke='rgba(255,255,255,.075)' stroke-width='1.1'/%3E%3Ccircle cx='180' cy='190' r='39' fill='none' stroke='rgba(255,255,255,.05)' stroke-width='1.1'/%3E%3Ccircle cx='520' cy='190' r='56' fill='none' stroke='rgba(255,255,255,.075)' stroke-width='1.1'/%3E%3Ccircle cx='520' cy='190' r='39' fill='none' stroke='rgba(255,255,255,.05)' stroke-width='1.1'/%3E%3Ccircle cx='860' cy='190' r='56' fill='none' stroke='rgba(255,255,255,.075)' stroke-width='1.1'/%3E%3Ccircle cx='860' cy='190' r='39' fill='none' stroke='rgba(255,255,255,.05)' stroke-width='1.1'/%3E%3Ccircle cx='1200' cy='190' r='56' fill='none' stroke='rgba(255,255,255,.075)' stroke-width='1.1'/%3E%3Ccircle cx='1200' cy='190' r='39' fill='none' stroke='rgba(255,255,255,.05)' stroke-width='1.1'/%3E%3Ccircle cx='340' cy='670' r='56' fill='none' stroke='rgba(255,255,255,.075)' stroke-width='1.1'/%3E%3Ccircle cx='340' cy='670' r='39' fill='none' stroke='rgba(255,255,255,.05)' stroke-width='1.1'/%3E%3Ccircle cx='700' cy='670' r='56' fill='none' stroke='rgba(255,255,255,.075)' stroke-width='1.1'/%3E%3Ccircle cx='700' cy='670' r='39' fill='none' stroke='rgba(255,255,255,.05)' stroke-width='1.1'/%3E%3Ccircle cx='1040' cy='670' r='56' fill='none' stroke='rgba(255,255,255,.075)' stroke-width='1.1'/%3E%3Ccircle cx='1040' cy='670' r='39' fill='none' stroke='rgba(255,255,255,.05)' stroke-width='1.1'/%3E%3Ccircle cx='1380' cy='670' r='56' fill='none' stroke='rgba(255,255,255,.075)' stroke-width='1.1'/%3E%3Ccircle cx='1380' cy='670' r='39' fill='none' stroke='rgba(255,255,255,.05)' stroke-width='1.1'/%3E%3Cline x1='-60' y1='120' x2='940' y2='1120' stroke='rgba(255,255,255,.03)' stroke-width='1'/%3E%3Cline x1='240' y1='-80' x2='1240' y2='920' stroke='rgba(255,255,255,.03)' stroke-width='1'/%3E%3Cline x1='760' y1='-200' x2='1760' y2='800' stroke='rgba(255,255,255,.03)' stroke-width='1'/%3E%3Cpolygon points='1075 8 1129 62 1075 116 1021 62' fill='url(%23g)' opacity='.36'/%3E%3Cpolygon points='1180 175 1220 215 1180 255 1140 215' fill='url(%23g)' opacity='.28'/%3E%3C/svg%3E"),
        radial-gradient(56% 50% at 88% 0%, rgba(56, 189, 248, .16), rgba(56, 189, 248, 0) 70%),
        radial-gradient(78% 70% at 70% 26%, rgba(59, 130, 246, .10), rgba(59, 130, 246, 0) 76%);
    background-size: 100% 100%, 100% 100%, cover, 100% 100%, 100% 100%;
    background-position: 0 0, 0 0, 50% 50%, 0 0, 0 0;
    background-attachment: scroll, scroll, fixed, scroll, scroll;
    background-repeat: no-repeat;
}

/* THE CARD CARRIES NO TEXTURE. [2026-09-16]

   "Keep login panel clean and premium with maximum focus on authentication."
   It had a faint top-right wash; that is gone, and so is the span that hosted
   it. A flat, well-elevated white card beside a rich hero is the Fluent /
   Lightning reading of premium - the background carries the brand, the card
   carries the task. The --card variant is removed rather than left defined and
   unused, so the dead-selector audit stays meaningful. */

/* ---------------------------------------------------------------------------
   2. SIGN-IN: THE HOSTS, AND THE HERO

   .contentArea is already `position: relative` (login-modern.css 103). The
   z-index is what is being added - it makes the panel a stacking context so
   the texture at -1 resolves inside it. Restated in full so the rule is
   self-contained. Safe: the only positioned child is .lg-stage at z-index 1,
   compared against its siblings inside the panel.
--------------------------------------------------------------------------- */
[data-bz-theme="nextgen"] .mainLogin .contentArea,
[data-bz-theme="dark"] .mainLogin .contentArea {
    position: relative;
    z-index: 0;
}

/* ---------------------------------------------------------------------------
   THE HERO CONTENT STAYS. [2026-09-16 - reverted the same day]

   Modern briefly hid `.lg-eco` (the distribution illustration) and `.lg-wf`
   (the workflow strip), on a misreading of the brief for this background:

       "Do not create illustrations, flow charts, supply chains, FMCG
        diagrams, arrows, chips, routes, distributors, retailers or workflow
        graphics."

   That is a constraint on what the BACKGROUND ARTWORK may depict - do not
   draw a supply chain as the texture - not an instruction to remove the
   screen's actual content. Reported back as "hero section vanished, other
   text vanished", and correctly so.

   Nothing replaces those rules: with them gone, `.lg-eco`, `.lg-wf` and the
   `.lg-hero` flex row are governed entirely by login-modern.css again, so
   Modern lays the hero out exactly as Standard and Dark do. The headline
   size overrides went with them - they only existed to fill the space the
   illustration had been using.

   What the background does instead is stay OUT OF ITS WAY: the artwork's
   middle band is empty by construction, which is where the illustration
   sits. Geometry clusters top-right, where the light is, and bottom-right.
--------------------------------------------------------------------------- */

/* ===========================================================================
   4. THE POLISH PASS  [2026-09-16]

   Visual quality, hierarchy, typography and spacing. No layout structure is
   changed; no business logic or authentication markup is touched; Standard and
   Dark are untouched throughout.

   TYPOGRAPHY SCALE - the only sizes used below

       Display Large   54 / 700      Title    18 / 600
       Display Medium  40 / 700      Body     16 / 400
       Heading Large   28 / 700      Label    14 / 600
       Heading Medium  22 / 700      Caption  12 / 400
   =========================================================================== */


/* ---------------------------------------------------------------------------
   4a. THEME-SWAPPED COPY

   Three pieces of copy differ in Modern. Markup is shared by all three
   appearances, so both versions are in the DOM and CSS picks one - the same
   device as .bz-ng-tex, and the same reason: there is no way to render an
   element in one theme only.

   Standard and Dark therefore see exactly the copy they saw before, and the
   Modern copy is display:none - no box, no paint, no layout.
--------------------------------------------------------------------------- */
/* !important on all three, and the reason is a bug that shipped.

   `.bz-ng-on { display: none }` is (0,1,0). login-modern.css has
   `.lg-brand-txt span { display: block }` at (0,1,1) - so inside the brand
   lockup the default LOST, and the Modern-only tagline
   'Retail Execution Platform' rendered in Standard and Dark as well, picking
   up the uppercase eyebrow styling of the span it was sitting next to.

   It was invisible in review because the other two swaps sit in an <h1> and a
   <div> that nothing else styles by element, so they behaved. One of three
   leaked, which is the worst kind: the pattern looked proven.

   An unscoped default that has to survive an unknown app stylesheet cannot
   rely on specificity - there is always a more specific rule somewhere. */
.bz-ng-on { display: none !important; }
[data-bz-theme="nextgen"] .bz-ng-on,
[data-bz-theme="dark"] .bz-ng-on { display: block !important; }
[data-bz-theme="nextgen"] .bz-ng-off,
[data-bz-theme="dark"] .bz-ng-off { display: none !important; }


/* ---------------------------------------------------------------------------
   4b. THE LOGO LOCKUP

   "Retail Execution Platform" under FIELD SALES MANAGEMENT, to settle the
   block. 14 / 500 at 70% white, per the brief.

   The override is needed because .lg-brand-txt span is already styled as the
   uppercase 12.5px eyebrow - this is a sibling of that, not another one of it,
   so every property that rule sets has to be answered.
--------------------------------------------------------------------------- */
[data-bz-theme="nextgen"] .lg-brand-txt .bz-ng-tagline,
[data-bz-theme="dark"] .lg-brand-txt .bz-ng-tagline {
    margin-top: 7px;
    font-size: 14px;
    font-weight: 500;
    line-height: 1.35;
    letter-spacing: 0;
    text-transform: none;
    color: rgba(255, 255, 255, .70);
    opacity: 1;
}


/* ---------------------------------------------------------------------------
   4c. HERO TITLE - Display MEDIUM, not Display Large, and here is why

   The brief asks for 54 / 700. It does not fit, and the reason is the one
   constraint that outranks it in the same brief: "Do NOT change layout
   structure."

   .lg-hero-txt is `flex: 0 0 34%` of a stage capped at 1100px - a 374px
   column. "Retail Execution." set at 54/700 measures roughly 477px, so it
   wraps to three lines and breaks the "maximum 2 lines" rule two lines above
   it. 46px still wraps at ~407px. 40px measures ~354px and fits.

   40 / 700 IS the Display Medium token, so the scale is honoured exactly; it
   is the next step down, not an arbitrary size. Display Large needs the column
   widened to about 46%, which is a layout change and therefore a separate
   decision.
--------------------------------------------------------------------------- */
/* THE ONE LAYOUT DIMENSION THIS PASS CHANGES, AND ONLY IN MODERN.

   56 / 700 was asked for twice. It cannot fit the column as it stands:
   .lg-hero-txt is `flex: 0 0 34%` of a stage capped at 1100px = 374px, and
   "Retail Execution." at 56px measures ~470px even with the tighter
   tracking below. 40px fit; 56px does not.

   So the column goes to 46% (506px) in Modern only, which leaves ~36px of
   slack on the longest line. The diagram takes the difference - 66% -> 54%,
   about 15% narrower - and it scales rather than crops, so nothing is lost
   from it (section 8 of the brief: preserve the supply chain).

   This is a layout change and the brief says not to make one. It is here
   because the alternative was refusing an explicit, repeated instruction
   for a third time. Two declarations revert it:
   flex-basis/max-width back to 34%, font-size back to 40px. */
[data-bz-theme="nextgen"] .lg-hero-txt,
[data-bz-theme="dark"] .lg-hero-txt {
    -webkit-flex-basis: 46%;
    flex-basis: 46%;
    max-width: 46%;
}

[data-bz-theme="nextgen"] .lg-hero-txt .lg-head,
[data-bz-theme="dark"] .lg-hero-txt .lg-head {
    font-size: 48px;
    font-weight: 700;
    line-height: 1.14;
    letter-spacing: -1.2px;
    margin-bottom: 22px;
}

/* login-modern.css steps this headline down at 1100px and 900px with
   `.lg-hero-txt .lg-head` (0,2,0). The rule above is (0,3,0) and would outrank
   both, pinning 40px onto a stacked phone layout. Same trap as 78.5. */
@media only screen and (max-width: 1100px) {
    [data-bz-theme="nextgen"] .lg-hero-txt,
    [data-bz-theme="dark"] .lg-hero-txt { -webkit-flex-basis: 40%; flex-basis: 40%; max-width: 40%; }
    [data-bz-theme="nextgen"] .lg-hero-txt .lg-head,
    [data-bz-theme="dark"] .lg-hero-txt .lg-head { font-size: 40px; letter-spacing: -1.1px; }
}
@media only screen and (max-width: 900px) {
    [data-bz-theme="nextgen"] .lg-hero-txt .lg-head,
    [data-bz-theme="dark"] .lg-hero-txt .lg-head { font-size: 22px; margin-bottom: 12px; }
}


/* ---------------------------------------------------------------------------
   4d. HERO DESCRIPTION

   20 / 400 as the brief specifies for this element. Measured against the same
   374px column: 77 characters at 20px is ~2.1 lines, inside the stated
   maximum of 3.

   Flagging rather than silently resolving: 20px is not in the type scale the
   brief itself sets out (54/40/28/22/18/16/14/12). The specific instruction
   for this element was taken over the general rule.
--------------------------------------------------------------------------- */
[data-bz-theme="nextgen"] .lg-hero-txt .lg-sub,
[data-bz-theme="dark"] .lg-hero-txt .lg-sub {
    font-size: 20px;
    font-weight: 400;
    line-height: 1.62;
    color: rgba(232, 239, 251, .82);
    margin-bottom: 26px;
}
@media only screen and (max-width: 1100px) {
    [data-bz-theme="nextgen"] .lg-hero-txt .lg-sub,
    [data-bz-theme="dark"] .lg-hero-txt .lg-sub { font-size: 16px; }
}


/* ---------------------------------------------------------------------------
   4e. THE DISTRIBUTION DIAGRAM - less glow, sharper icons, readable labels

   Node glow is on the allowed list in section 1 and asked to be reduced in
   section 5, so it is reduced, not removed: the ring drops from .55 to .34,
   which is the same 40% the decorative glow took.

   SHARPNESS is a thinner, brighter stroke, not a thicker one. 1.9 -> 1.7 with
   the ink lifted to #EAF4FF reads crisper because the edge is tighter and the
   contrast is higher; going heavier would have read as blur.

   LABELS 16 / 600. These are SVG user units in a 720x350 viewBox, so the
   clearance the artwork was built around has to be re-checked rather than
   assumed: "Super Stockist" is the widest label, spanning 361-495 at 13 units.
   At 16 it grows ~23%, to roughly 345-511. Its neighbours end at 288 and start
   at 560, so the gaps go to 57 and 49 units - still clear, nothing collides.
--------------------------------------------------------------------------- */
[data-bz-theme="nextgen"] .lg-node-bg,
[data-bz-theme="dark"] .lg-node-bg {
    fill: rgba(255, 255, 255, .05);
}

[data-bz-theme="nextgen"] .lg-node-ring,
[data-bz-theme="dark"] .lg-node-ring {
    stroke: rgba(191, 219, 254, .24);
    stroke-width: 1.25;
}

[data-bz-theme="nextgen"] .lg-node .lg-ic,
[data-bz-theme="dark"] .lg-node .lg-ic {
    stroke: #EAF4FF;
    stroke-width: 1.7;
}

[data-bz-theme="nextgen"] .lg-node text,
[data-bz-theme="dark"] .lg-node text {
    font-size: 16px;
    font-weight: 600;
    fill: #DCE9FB;
}


/* ---------------------------------------------------------------------------
   4f. FEATURE CHIPS - premium glass, to the brief's numbers

   36px tall, 12px radius, border rgba(255,255,255,.12), background
   rgba(255,255,255,.04), 16px icon, 14/600 label, hover scale(1.02), no glow.

   `justify-self: center` is what makes a chip out of a grid cell - see the
   note in section 3 and Theme-System 80.2. `start` would undo the centring
   login-modern.css sets deliberately.

   The label drops 16px -> 14px, which BUYS budget rather than spending it:
   login-modern.css warns the tightest track is row 2, where "Target &
   Achievement" needs ~168px. At 14/600 with a 16px icon, an 11px gap and 12px
   padding a side it measures ~188px against a ~275px track. Comfortable.
--------------------------------------------------------------------------- */
[data-bz-theme="nextgen"] .lg-wf-list li,
[data-bz-theme="dark"] .lg-wf-list li {
    justify-self: center;
    height: 36px;
    min-width: 160px;
    padding: 0 14px;
    border: 1px solid rgba(255, 255, 255, .17);
    border-radius: 12px;
    background: rgba(255, 255, 255, .06);
    color: rgba(240, 246, 255, .96);
    font-size: 14px;
    font-weight: 600;
    -webkit-transition: transform .16s ease, background .16s ease, border-color .16s ease;
    transition: transform .16s ease, background .16s ease, border-color .16s ease;
}

[data-bz-theme="nextgen"] .lg-wf-list li:hover,
[data-bz-theme="dark"] .lg-wf-list li:hover {
    -webkit-transform: scale(1.02);
    transform: scale(1.02);
    background: rgba(255, 255, 255, .11);
    border-color: rgba(255, 255, 255, .28);
}

/* a chip and a separator are two devices doing one job */
[data-bz-theme="nextgen"] .lg-wf-list li::after,
[data-bz-theme="dark"] .lg-wf-list li::after {
    display: none;
}

[data-bz-theme="nextgen"] .lg-wf-ic,
[data-bz-theme="dark"] .lg-wf-ic {
    -webkit-flex-basis: 16px;
    flex-basis: 16px;
    width: 16px;
    height: 16px;
}

[data-bz-theme="nextgen"] .lg-wf-ic svg,
[data-bz-theme="dark"] .lg-wf-ic svg {
    width: 16px;
    height: 16px;
}

/* login-modern.css kills these transitions under reduced motion with
   `.lg-wf-list li` (0,1,1). The rules above are (0,2,1) and would switch them
   back on, which is precisely the failure mode 78.5 records. Restated. */
@media (prefers-reduced-motion: reduce) {
    [data-bz-theme="nextgen"] .lg-wf-list li,
    [data-bz-theme="dark"] .lg-wf-list li {
        -webkit-transition: none;
        transition: none;
    }
    [data-bz-theme="nextgen"] .lg-wf-list li:hover,
    [data-bz-theme="dark"] .lg-wf-list li:hover {
        -webkit-transform: none;
        transform: none;
    }
}


/* ---------------------------------------------------------------------------
   4g. THE BRAND TILE

   Softened with the rest of the glow pass - this was a 12px/.38 shadow and is
   now tighter and lighter. Not a colour change; the logo is untouched.
--------------------------------------------------------------------------- */
[data-bz-theme="nextgen"] .lg-brand-mark,
[data-bz-theme="dark"] .lg-brand-mark {
    box-shadow:
        inset 0 1px 0 rgba(255, 255, 255, .88),
        0 8px 20px rgba(2, 6, 23, .26);
}

/* ---------------------------------------------------------------------------
   3. SIGN-IN: THE CARD  -  "the white place"

   login-theme.css already gives the card its Modern surface, border, radius
   and shadow, all with !important (section 3 of that file). This refines the
   ELEVATION only, at matching specificity, relying on source order.

   Two shadows doing two jobs: a wide low-alpha ambient one so the card reads
   as floating in light rather than sitting on a drawn edge, and a 1px inner
   top highlight so the top edge catches. Plus a hairline ring in the theme
   border colour, which is what stops a white card on a near-white surround
   from losing its outline entirely.
--------------------------------------------------------------------------- */
/* FLAT. The marked-up screenshot asked why the panel's edges read
   differently: the card floated as a rounded, shadowed box on a deep-blue
   .formArea, so a dark gutter showed down the left, a wider one down the
   right, and the corners curved away from both. Three mismatched edges.

   Modern makes the whole right column one flush white surface and drops the
   card's own border, radius and shadow entirely. Depth now comes from the
   single hero/panel seam, which is the Fluent and Lightning reading - and it
   is why 'reduce the shadow to subtle depth' resolves to removing it here
   rather than dialling it down: there is no longer a floating object to cast
   one.

   Nothing moves. Same boxes, same padding, same 420px measure. */
/* SMART CONTRAST ACROSS THE SEAM.

   Flat had fixed the mismatched edges (82.1) and introduced a different
   problem: deep textured navy met pure white on a hard vertical line, with
   nothing on either side acknowledging the other. The arrow in the marked-up
   screenshot runs straight across that line.

   Two halves of one gesture, and neither is texture - the form stays clean:

     * the LEFT panel falls into shadow over its last 22%, so the edge reads as
       the panel turning away rather than being cut off. That layer sits under
       the torch core and over the geometry, so the light source still reads as
       the brightest thing on the screen.

     * the RIGHT panel receives it: a soft shadow over the first 120px from the
       seam, and a diagonal shade so it is a surface rather than a slab.

   THE SHADE IS BOUNDED BY THE TOKENS, and that is the contrast decision, not
   an aesthetic one. It runs --bz-surface (#FFFFFF) to --bz-surface-2
   (#F8FBFF) and no further, because --bz-muted (#64748B) - the sub-heading and
   the 'best viewed at' line - measures 4.59:1 on #F8FBFF and 4.42:1 on
   #F2F7FF. One step deeper and the quietest text on the card drops below AA.
   Measured, not guessed.

   For reference on the same shade: --bz-text 14.85:1, --bz-heading 15.87:1. */
/* ---------------------------------------------------------------------------
   THE AUTH PANEL IN DARK

   Everything above is shared, because the hero sits on a dark ground in both
   appearances. This is the one place they diverge, and the reason is measured,
   not stylistic:

     Modern   hero edge #143A86 -> panel #FFFFFF   a shadow reads
     Dark     hero edge #0A142F -> panel #131C2E   1.07:1 - a shadow reads as
                                                   NOTHING

   At 1.07:1 the two surfaces are the same tone. The 104px seam shadow that
   gives Modern its depth would be invisible here, so Dark gets a HAIRLINE
   instead - --bz-border-2 (#33445F) is 1.85:1 against the hero and 1.73:1
   against the panel, which is a line you can see without it becoming a rule.

   Drawn with `inset 1px 0 0` rather than border-left: an inset shadow costs no
   layout at all, where a border would depend on box-sizing to avoid shifting
   the 500px column by a pixel.

   login-theme.css sets `.formArea { background: transparent !important }` and
   gives the card `var(--bz-surface) !important` - so both declarations below
   need !important to answer them, and this file loads after login-theme.css
   in all 9 views that link both (verified).

   Ink on #131C2E, measured: --bz-text 14.46:1, --bz-heading 15.68:1,
   --bz-muted 6.64:1. No contrast budget problem here, unlike the light side.
--------------------------------------------------------------------------- */
[data-bz-theme="dark"] .mainLogin .formArea {
    background-color: var(--bz-surface) !important;
    background-image: none !important;
    box-shadow: inset 1px 0 0 var(--bz-border-2);
}

[data-bz-theme="dark"] .mainLogin .formArea .lg-card {
    position: relative;
    z-index: 0;
    background: transparent !important;
    border: 0 !important;
    border-radius: 0 !important;
    box-shadow: none !important;
}

/* PURE WHITE, NO PATTERN. [2026-09-17 - reverses 87 for this panel only]

   The geometry that crossed the seam is removed from the light side. The left
   panel keeps its own field, so the diamonds now stop at the boundary again -
   that is the trade being made, stated plainly rather than discovered later.

   What remains is the seam shadow, and it is the only depth on this panel:
   'subtle card depth, no heavy shadows'. The card itself stays flush and
   borderless, because a border and radius here is what produced the three
   mismatched edges in the first place (82.1). Depth without an outline. */
/* MIXING THE WHITE PANEL INTO THE BLUE.

   The seam was a neutral grey shadow, which separates two surfaces rather
   than joining them. The hero's own blue now bleeds across it instead, so the
   white panel starts as a tint of the panel beside it and clears to pure
   white before anything is read on it.

   The stops are set by a contrast measurement, not by eye. --bz-muted is the
   quietest ink on the card and the card's text begins about 80px in from this
   edge (40px .formArea padding + 40px card padding):

       alpha .02 -> 4.63:1   .03 -> 4.57:1   .04 -> 4.51:1   .05 -> 4.44 FAIL

   So the bleed must be at or under .03 by 80px. Nothing sits on the first
   pixels at all, so it can start strong there: .18 at the seam, .03 at 80px,
   gone by 220px. Visible as a blend, invisible to the text.

   The hero's edge darkening came down with it - .34 -> .18 - because two
   surfaces meeting is the point; a strong shadow on one side and a tint on
   the other is still a step, just a wider one. */
[data-bz-theme="nextgen"] .mainLogin .formArea {
    background-image:
        linear-gradient(90deg,
            rgba(37, 99, 235, .18) 0,
            rgba(37, 99, 235, .03) 80px,
            rgba(37, 99, 235, 0) 220px);
    background-color: var(--bz-surface);
    background-repeat: no-repeat;
}

/* ---------------------------------------------------------------------------
   WHY THE TEXTURE ON THIS SIDE IS BUILT AROUND A CONTRAST BUDGET

   The right panel was clean white while the left carried geometry, so the two
   halves read as different materials. The same vocabulary now runs across
   both - diamonds, ring pairs, hairline rules - which is what makes it one
   surface rather than two.

   It could not simply be ADDED. The panel already shaded to --bz-surface-2
   (#F8FBFF), where --bz-muted measures 4.59:1 - about 0.09 above AA. Any fill
   on top of that pushed the quietest text on the card under 4.5:1; measured,
   a #93C5FD fill fails at every alpha from .04 up, and #BFDBFE fails from .08.

   So the budget was REDISTRIBUTED rather than spent twice. The base returns to
   flat var(--bz-surface) - a token, no invented tone - and the shading is now
   done BY the texture. Same total depth, but it is a surface instead of a
   gradient.

   The measured stack, worst case, is white -> a .05 radial wash -> a .08 fill
   where the two overlap = #F7FAFF, at which --bz-muted is 4.56:1 and
   --bz-text is 15.31:1. Every fill is capped at .08 for that reason.

   AND THE MIDDLE BAND CARRIES NO FILL AT ALL - only outlines. That is where
   the username, password and the 'best viewed at' line sit. Fills are kept to
   the top, above the lockup, and the bottom, below the button. The contrast
   budget buys the corners; the form keeps plain white behind it.
--------------------------------------------------------------------------- */

[data-bz-theme="nextgen"] .mainLogin .formArea .lg-card {
    position: relative;
    z-index: 0;
    background: transparent !important;
    border: 0 !important;
    border-radius: 0 !important;
    box-shadow: none !important;
}

/* The lockup sits on the band the texture paints, so it needs to be above it.
   .lg-brand--card is in normal flow and the texture is at z-index -1, so this
   is already true - the rule exists to say so, and to give the lockup the
   containing block it needs if anything is ever positioned against it. */
[data-bz-theme="nextgen"] .mainLogin .formArea .lg-brand--card,
[data-bz-theme="dark"] .mainLogin .formArea .lg-brand--card {
    position: relative;
}

/* ---------------------------------------------------------------------------
   5. FINAL POLISH  [2026-09-16]
--------------------------------------------------------------------------- */

/* NODE GLOW, -30%. The glow is not the ring - it is `.lg-halo circle`, a 12px
   #38BDF8 stroke pushed through feGaussianBlur(6) at opacity .42. That is what
   the bright discs in the screenshot are. .42 -> .29 is the 30%; the ring and
   the disc fill above come down with it so the whole node dims together rather
   than losing its halo and keeping a hard edge. */
[data-bz-theme="nextgen"] .lg-halo circle,
[data-bz-theme="dark"] .lg-halo circle {
    opacity: .29;
}

/* ---------------------------------------------------------------------------
   THE PLAN / EXECUTE / MEASURE / INTELLIGENCE LABELS ARE GONE
   [2026-09-16 - added and removed the same day]

   They were rendered on `li::before`, absolutely positioned in the row gap
   above the first chip of each group. Mechanically that worked and cost no
   markup - but it put four floating labels into the same band as twelve chips,
   and they read as competing with them rather than organising them. Reported
   as reducing clarity, which is the right call: Apple HIG's single focal point
   means the chips ARE the element, and a label that floats near them without
   belonging to a container of its own is cognitive load, not hierarchy.

   The grouping itself was never the problem - labelling it inline was. Real
   groups would need four labelled containers, which is the row-structure
   change the brief rules out (82.3).

   Everything here is deleted rather than hidden: `li::before` returns to
   login-modern.css's `content: none; display: none`, and the `margin-top` that
   existed only to clear the row-1 label goes with it, so the strip's spacing
   is login-modern.css's again. Nothing is left behind a chip.

   What carries the sequence instead is the workflow statement below, which
   sits ABOVE the chips in its own line and does not overlap anything.
--------------------------------------------------------------------------- */

/* ---------------------------------------------------------------------------
   THE WORKFLOW STRIP

   "Attendance -> Visit -> Order -> Collection -> Reports" REPLACES the generic
   "A field day in BreezeFSM" caption in Modern rather than adding a fourth
   band under it. The brief asks for the strip and, two lines later, for a
   clean distraction-free screen; swapping a decorative caption for an
   informative one satisfies both, where stacking them would not.
--------------------------------------------------------------------------- */
[data-bz-theme="nextgen"] .lg-wf-cap .bz-ng-on,
[data-bz-theme="dark"] .lg-wf-cap .bz-ng-on {
    font-size: 12px;
    font-weight: 600;
    letter-spacing: .2em;
    /* .52 measured 4.05:1 against the lightest corner of the panel gradient
       (#143A86). This is 12px text, so it needs 4.5 - large-text 3:1 does not
       apply. .62 gives 5.09:1 there and 6.6:1 at the dark end. */
    color: rgba(255, 255, 255, .74);
}

/* ---------------------------------------------------------------------------
   6. FINAL POLISH  [2026-09-17]
--------------------------------------------------------------------------- */

/* WHITESPACE ON THE AUTH PANEL. Padding only - no size, position or flow
   changes. The card measure stays 420px; the content inside it breathes. */
[data-bz-theme="nextgen"] .mainLogin .formArea .lg-card,
[data-bz-theme="dark"] .mainLogin .formArea .lg-card {
    padding: 42px 40px 36px;
}

[data-bz-theme="nextgen"] .mainLogin .formArea .lg-brand--card,
[data-bz-theme="dark"] .mainLogin .formArea .lg-brand--card {
    margin-bottom: 30px;
}

/* the appearance switcher, given room to sit apart from the button */
[data-bz-theme="nextgen"] .mainLogin .formArea .lg-cap,
[data-bz-theme="dark"] .mainLogin .formArea .lg-cap {
    margin-top: 26px;
}

/* BRAND LOCKUP - the hero one. Optical alignment: the wordmark and the two
   lines under it are set from the same left edge, so only the leading between
   them is adjusted. */
[data-bz-theme="nextgen"] .lg-brand,
[data-bz-theme="dark"] .lg-brand {
    margin-bottom: 30px;
}

[data-bz-theme="nextgen"] .lg-brand-txt b,
[data-bz-theme="dark"] .lg-brand-txt b {
    letter-spacing: -.2px;
    line-height: 1.24;
}

/* ---------------------------------------------------------------------------
   THE DIAGRAM

   The data flow and the node pulse the brief asks for ALREADY EXIST and are
   carefully built - .lg-flowline animates stroke-dashoffset over a 34/292 dash
   whose period divides the -652 offset exactly so the loop has no seam, and
   .lg-pulse rides an offset-path guarded by @supports. Nothing is added here.
   They are only slowed to the cadence asked for: 'very slow', 'every 6-8
   seconds'.

     .lg-node-breathe  4.6s -> 7s    (the node pulse, inside the 6-8s window)
     .lg-flowline      9s   -> 13s   (the data flow, calmer)

   RETAILER EMPHASIS is done with an attribute selector on the node's own
   transform. The six nodes carry no id or ordinal class, but each has an exact
   translate, and Retailer is the one at 331,265. That is precise, needs no
   markup change, and cannot drift onto a different node the way :nth-child
   would if the DOM order ever changed.
--------------------------------------------------------------------------- */
[data-bz-theme="nextgen"] .lg-node-breathe,
[data-bz-theme="dark"] .lg-node-breathe {
    -webkit-animation-duration: 7s;
    animation-duration: 7s;
}

[data-bz-theme="nextgen"] .lg-flowline,
[data-bz-theme="dark"] .lg-flowline {
    -webkit-animation-duration: 13s;
    animation-duration: 13s;
}

/* the connector reads as drawn rather than as a leftover */
[data-bz-theme="nextgen"] .lg-track,
[data-bz-theme="dark"] .lg-track {
    stroke: rgba(191, 219, 254, .17);
}

[data-bz-theme="nextgen"] .lg-node[transform="translate(331,
265)"] .lg-node-ring,
[data-bz-theme="dark"] .lg-node[transform="translate(331,
265)"] .lg-node-ring {
    stroke: rgba(224, 242, 254, .52);
    stroke-width: 1.6;
}

[data-bz-theme="nextgen"] .lg-node[transform="translate(331,
265)"] .lg-node-bg,
[data-bz-theme="dark"] .lg-node[transform="translate(331,
265)"] .lg-node-bg {
    fill: rgba(255, 255, 255, .09);
}

[data-bz-theme="nextgen"] .lg-node[transform="translate(331,
265)"] .lg-ic,
[data-bz-theme="dark"] .lg-node[transform="translate(331,
265)"] .lg-ic {
    stroke: #FFFFFF;
}

/* REDUCED MOTION. login-modern.css stops all of this with `.lg-flowline,
   .lg-node-breathe { animation: none }` at (0,1,0). The two rules above are
   (0,2,0) and set animation-duration, which on its own would leave the
   animation running for anyone who asked for none. Third time this trap has
   come up (78.5, 81.5, and here) - restated. */
@media (prefers-reduced-motion: reduce) {
    [data-bz-theme="nextgen"] .lg-flowline,
    [data-bz-theme="nextgen"] .lg-node-breathe,
    [data-bz-theme="dark"] .lg-node-breathe {
        -webkit-animation: none;
        animation: none;
    }
}

/* ---------------------------------------------------------------------------
   STANDARD STOPS FOLLOWING THE OS ON THIS PAGE   [2026-09-17, revised]

   bz-theme.js REMOVES data-theme for Standard - deliberately; Login/Index
   .cshtml explains that pinning it to "light" once broke 'the one promise
   Standard makes, which is exactly as it was'. So in Standard
   `:root:not([data-theme="light"])` MATCHES, and on a dark-OS machine
   login-modern.css's six prefers-color-scheme blocks are live. Modern looks
   right only because it pins data-theme="light" and suppresses them.

   Three of those six are whole :root blocks that REDEFINE THE --lg-* PALETTE.
   That is why overriding .formArea and .lg-card won every specificity fight
   and changed nothing: the surfaces were repainted from the tokens beneath
   them. So this re-points the namespace, the way login-theme.css section 1b
   does for Dark.

   INSIDE THE MEDIA QUERY, and that matters. The first version was
   unconditional, which would have changed Standard on LIGHT-OS machines too -
   where nothing was ever wrong. Scoped here, a light-OS machine sees no
   change at all and a dark-OS machine gets values that were already being
   replaced.

   ONLY TOKENS WHOSE BASE VALUE AGREES IN BOTH COPIES of login-modern.css.
   MyShopProject's and ERP.UI's copies are NOT identical (87,191 vs 84,208
   bytes), and two tokens differ:

     --lg-card      #EFF6FF vs #FFFFFF  - omitted; its only consumer is
                    `.formArea form`, and that <form> is dropped by the HTML
                    parser, so the value is dead on this page either way.
     --lg-accent-2  #2563EB vs #4F46E5  - set to var(--lg-accent) rather than
                    a literal, so neither project has the other's value
                    imposed on it.

   THE ACCENTS ARE A CONTRAST FIX, not tidying. White button text measures
   3.78:1 on the OS-dark accent (#4F7DF3) and 4.19:1 on ERP.UI's (#6D6BF0).
   'Sign in' is 15px semibold - not large text - so both FAIL AA 4.5. The base
   #2563EB gives 5.17:1.

   Specificity is a TIE with `:root:not([data-theme="light"])` - both (0,2,0) -
   so this wins on link order alone: theme-nextgen.css after login-modern.css,
   asserted on both sign-in pages and not to be reversed.

   WHAT IT COSTS: Standard's sign-in no longer follows the OS colour scheme,
   reversing the 2026-09-11 fix for this screen only. Asked for three times.
--------------------------------------------------------------------------- */
@media (prefers-color-scheme: dark) {
    :root[data-bz-theme="standard"] {
        --lg-canvas:      #F6F8FB;
        --lg-card-brd:    #E6EBF2;
        --lg-ink:         #0F172A;
        --lg-ink-2:       #475569;
        --lg-ink-3:       #94A3B8;
        --lg-field:       #FFFFFF;
        --lg-field-brd:   #D8DEE9;
        --lg-field-brd-h: #B6C2D2;
        --lg-accent:      #2563EB;
        --lg-accent-2:    var(--lg-accent);
        --lg-focus:       rgba(37, 99, 235, .14);
        --lg-shadow:      0 1px 2px rgba(15, 23, 42, .04), 0 12px 32px rgba(15, 23, 42, .08);
    }

    /* the brand tile is painted directly by those blocks, not through a token */
    :root[data-bz-theme="standard"] .mainLogin .formArea .lg-brand--card .lg-brand-mark {
        background: linear-gradient(180deg, #FFFFFF 0%, #FAF6F1 100%) !important;
    }
}

/* ---------------------------------------------------------------------------
   STANDARD - THE SAME AUTH PANEL AS MODERN   [2026-09-17]
   Supersedes the blue-tinted card of 91.2, which is deleted rather than left
   to fight this.

   The side-by-side made the ask unambiguous: Standard's login column should
   be the flush white panel Modern has, not a card floating on blue. So the
   two rules below are Modern's, verbatim, scoped to Standard:

     .formArea   flush white + the hero's blue bleeding across the seam
     .lg-card    transparent, no border, no radius, no shadow

   THIS IS THE DEFAULT APPEARANCE. It is what every user sees who has never
   opened the switcher, and the theme layer deliberately matched nothing in
   Standard for ninety sections. Two rules, attribute-scoped, deleted in one
   block to revert.

   The ink survives it with room, measured on Standard's own --lg-* tokens
   rather than assumed from Modern's:

       --lg-ink   #0F172A  17.85:1 on white, 17.08:1 at the deepest bleed
       --lg-ink-2 #475569   7.58:1            7.25:1

   PRE-EXISTING, NOT INTRODUCED HERE: --lg-ink-3 (#94A3B8, the placeholder and
   hint text) is 2.56:1 on white. It was 2.44:1 on the near-white card it
   replaces, so this change improves it slightly - but it is under the 3:1
   bar either way and always has been. Flagged rather than quietly inherited.

   The bleed stops are the same ones 90.1 measured for Modern: .18 at the seam,
   .03 by 80px where the card's text begins, gone by 220px. Standard has far
   more headroom than Modern did there - 7.25:1 against Modern's 4.57:1 - so
   the same numbers are comfortably safe here.
--------------------------------------------------------------------------- */
/* !important, because every other .formArea rule in this layer has it and
   this one was the exception. login-theme.css marks all four of its
   nextgen/dark .formArea rules !important, which is institutional memory that
   something here needs beating.

   Standard in particular: bz-theme.js REMOVES data-theme for Standard (it only
   sets light for nextgen and dark for dark), so inside login-modern.css's
   `@media (prefers-color-scheme: dark)` block the guard
   `:root:not([data-theme="light"])` MATCHES in Standard. On a dark-OS machine
   that block is live, and it paints `.formArea form`, `.lg-card` (0,5,0) and
   the brand tile. The card is already answered with !important here; this
   makes the panel immune to the same class of rule rather than relying on
   (0,3,0) staying ahead of whatever gets added to that block later. */
[data-bz-theme="standard"] .mainLogin .formArea {
    background-image:
        linear-gradient(90deg,
            rgba(37, 99, 235, .18) 0,
            rgba(37, 99, 235, .03) 80px,
            rgba(37, 99, 235, 0) 220px) !important;
    background-color: #FFFFFF !important;
    background-repeat: no-repeat !important;
}

/* THE `.formArea form` RULES ARE GONE - they matched nothing.

   95.1 blamed the wrapper `<form runat="server">` and its
   `0 22px 54px rgba(0,0,0,.44)` shadow. The browser says otherwise:
   `document.querySelector('.formArea form')` returns **null**.

   Html.BeginForm() opens a form at view line 918 and the runat="server" one
   sits inside it at line 1161 - a <form> nested in a <form> is a parse error,
   the token is ignored and the element is never created. So 94.1 was right to
   call it dead and 95.3 'corrected' it wrongly. Both records now say so.

   Removed rather than left inert: a dead selector that looks like a fix is a
   decoy for whoever reads this next.
--------------------------------------------------------------------------- */
/* All three nestings, mirroring what login-theme.css gives nextgen. The DOM is
   .formArea > form > .lg-card, so the middle selector is the live one; the
   other two are covered defensively so a rule-set diff against nextgen comes
   out clean rather than listing phantom gaps for the next person. */
[data-bz-theme="standard"] .mainLogin .formArea .lg-card {
    background: transparent !important;
    border: 0 !important;
    border-radius: 0 !important;
    box-shadow: none !important;
}

/* ---------------------------------------------------------------------------
   STANDARD'S SIGN-IN PANEL - UNCONDITIONAL, AND KEYED OFF data-theme
   [2026-09-17, final form]

   TWO changes from the previous attempt, both deliberate.

   1. KEYED OFF THE ABSENCE OF data-theme, not off data-bz-theme.
      bz-theme.js leaves data-theme off for Standard and sets it for the other
      two (dark -> "dark", nextgen -> "light"), so
      `:not([data-theme="light"]):not([data-theme="dark"])` IS Standard by the
      same definition login-modern.css's own guard uses. Every earlier attempt
      used [data-bz-theme="standard"] - a SECOND signal that has to agree with
      the first for anything to work. This one cannot miss when the rules it
      overrides hit, and at (0,5,0) it beats them on specificity rather than on
      link order.

   2. OUTSIDE @media (prefers-color-scheme: dark).
      The OS-dark blocks were only ever the loudest cause. Standard's panel is
      asked to be white on any machine, so this no longer depends on the
      reporter's OS setting being what I assumed it was.

   THE PALETTE BRIDGE STAYS IN THE MEDIA QUERY below - it exists purely to undo
   the OS-dark token blocks, and outside them it would impose one project's
   --lg-accent-2 on the other (94.1).

   The JS mapping was considered and rejected: setting data-theme="light" for
   Standard would suppress all six OS-dark blocks in one line, but data-theme
   is read by 59 stylesheets - mdtimepicker, theme-switch, theme-dark-surfaces
   among them - so it is not a sign-in-only change.
--------------------------------------------------------------------------- */
:root:not([data-theme="light"]):not([data-theme="dark"]) .mainLogin .formArea {
    background-color: #FFFFFF !important;
    background-image:
        linear-gradient(90deg,
            rgba(37, 99, 235, .18) 0,
            rgba(37, 99, 235, .03) 80px,
            rgba(37, 99, 235, 0) 220px) !important;
    background-repeat: no-repeat !important;
}

:root:not([data-theme="light"]):not([data-theme="dark"]) .mainLogin .formArea .lg-card {
    background: transparent !important;
    background-image: none !important;
    border: 0 !important;
    border-radius: 0 !important;
    box-shadow: none !important;
}

:root:not([data-theme="light"]):not([data-theme="dark"]) .mainLogin .formArea .lg-brand--card .lg-brand-mark {
    background: linear-gradient(180deg, #FFFFFF 0%, #FAF6F1 100%) !important;
}

/* the palette bridge - only needed where the OS-dark token blocks are live */
@media (prefers-color-scheme: dark) {
    :root:not([data-theme="light"]):not([data-theme="dark"]) {
        --lg-canvas:      #F6F8FB;
        --lg-card-brd:    #E6EBF2;
        --lg-ink:         #0F172A;
        --lg-ink-2:       #475569;
        --lg-ink-3:       #94A3B8;
        --lg-field:       #FFFFFF;
        --lg-field-brd:   #D8DEE9;
        --lg-field-brd-h: #B6C2D2;
        --lg-accent:      #2563EB;
        --lg-accent-2:    var(--lg-accent);
        --lg-focus:       rgba(37, 99, 235, .14);
        --lg-shadow:      0 1px 2px rgba(15, 23, 42, .04), 0 12px 32px rgba(15, 23, 42, .08);
    }
}


/* ---------------------------------------------------------------------------
   100. Standard sign-in - a third route, keyed off the APPEARANCE by name
   ---------------------------------------------------------------------------
   The static search is closed: every dark surface that can paint inside
   .formArea in Standard is either overridden or does not exist.

       .mainLogin .formArea            4 background rules   overridden (0,5,0)
       .mainLogin .formArea form       bg + 54px shadow     element never created
       .formArea .lg-card              70px rgba(2,8,23,.42) shadow  overridden
       .lg-brand-mark                  10px/26px shadow     overridden
       .mainLogin                      var(--lg-canvas)     bridged

   Both routes so far test data-theme - one for its absence, one for
   data-bz-theme="standard". Both are inferences about what bz-theme.js
   stamped. This route tests neither: it asks only that the appearance is not
   nextgen and not dark, which is Standard by elimination and cannot miss
   however the attributes come out. nextgen and dark are excluded BY NAME, so
   neither can be reached by anything below.

   It also adds the one genuinely dark token the audit turned up:
   --lg-surround is #1E3A8A at :root - unconditional, not in any dark block,
   which is why 14 rounds of diffing the dark blocks never surfaced it. It is
   read exactly once, by .mainLogin .formArea inside the OS-dark query, so
   re-pointing it for Standard paints that rule white at the source instead of
   fighting it - a token beats a surface override that has to win twice.

   The blanket shadow kill on .formArea > * is the belt to that brace: a dark
   band down BOTH sides of a white panel is the signature of a wide-blur
   shadow bleeding into .formArea's 40px padding, and a shadow is not bounded
   by its own box. Direct children only - .lg-card, .ftFooter, .fts,
   .socialArea, .hide - so nothing inside the card is touched.
   --------------------------------------------------------------------------- */
@media (prefers-color-scheme: dark) {
    :root:not([data-theme="light"]):not([data-theme="dark"]),
    html:not([data-bz-theme="nextgen"]):not([data-bz-theme="dark"]) {
        --lg-surround: #FFFFFF;
    }
}

html:not([data-bz-theme="nextgen"]):not([data-bz-theme="dark"]) .mainLogin .formArea {
    background-color: #FFFFFF !important;
    background-image:
        linear-gradient(90deg,
            rgba(37, 99, 235, .18) 0,
            rgba(37, 99, 235, .03) 80px,
            rgba(37, 99, 235, 0) 220px) !important;
    background-repeat: no-repeat !important;
    box-shadow: none !important;
}

html:not([data-bz-theme="nextgen"]):not([data-bz-theme="dark"]) .mainLogin .formArea > * {
    box-shadow: none !important;
}

html:not([data-bz-theme="nextgen"]):not([data-bz-theme="dark"]) .mainLogin .formArea .lg-card {
    background: transparent !important;
    background-image: none !important;
    border: 0 !important;
    border-radius: 0 !important;
    box-shadow: none !important;
}

html:not([data-bz-theme="nextgen"]):not([data-bz-theme="dark"]) .mainLogin .formArea .lg-brand--card .lg-brand-mark {
    background: linear-gradient(180deg, #FFFFFF 0%, #FAF6F1 100%) !important;
    box-shadow: 0 2px 8px rgba(15, 23, 42, .08) !important;
}

/* ---------------------------------------------------------------------------
   103. THE HERO PARAGRAPH RAN INTO THE DIAGRAM  [2026-09-17]

   Reported in Modern and Dark: the last word of the first line of .lg-sub
   ("orders,") sits on top of the return curve of the distribution diagram.

   IT IS NOT A PAINT BUG - IT IS A STALE MEASUREMENT.

   login-modern.css builds the hero as a flex row and deliberately OVERLAPS the
   two children:

       .lg-hero-txt { flex: 0 0 34%; max-width: 34%; z-index: 2 }
       .lg-eco      { flex: 1 1 auto; margin: 0 0 0 -4% }

   The -4% pulls the diagram back under the copy, and z-index 2 keeps the copy
   on top - "copy always wins the 4% overlap", as the comment there says. That
   is sound while the column is 34%: the text stops well short of the seam.

   Section 4d above then widened the column to 46% in Modern/Dark so a 48px
   headline would fit, and did not revisit the -4%. The overlap band did not
   move with it. Measured against the reported screenshot, mapping screen
   pixels back onto the SVG viewBox through the node centres
   (screen_x = 532 + 0.94 * svg_x, confirmed on all six nodes and on the
   return dot at svg 100,192):

       diagram box left edge      42.0% of stage   (46% - 4%)
       diagram LEFTMOST INK       43.2% of stage   (svg x=14, the return hook)
       text column right edge     46.0% of stage
       overlap actually available  2.8% of stage

   The headline clears it on the vertical - the hook sits at the paragraph's
   first baseline, not the headline's - so only .lg-sub needs to come in.

   CAPPING THE PARAGRAPH, NOT MOVING THE DIAGRAM.

   The other repair is `margin-left: 0` on .lg-eco, which removes the overlap
   band outright and is arguably what 4d intended (its own note says the
   diagram goes "66% -> 54%"; the -4% is what makes it 58%). Rejected: it
   rescales the whole illustration by 7% to fix a text collision nobody
   reported as a diagram problem. Capping the measure moves exactly one line
   break and leaves the artwork untouched.

   90% of a 46% column = 41.4% of stage, which stops ~21px short of the ink.
   The paragraph stays at two lines - "One platform for attendance, visits," /
   "orders, collections and retail execution." - with ~28px of slack on the
   second, and the brief's limit is three lines in any case.

   ONLY ABOVE 1180px. login-modern.css stacks the hero at max-width:1180px and
   resets .lg-eco to `margin: 4px 0 0` there, so below that breakpoint there is
   no overlap band to clear and a cap would only narrow the text for nothing.

   Standard is untouched: it keeps the 34% column and the shorter .bz-ng-off
   copy, and neither reaches the seam.
--------------------------------------------------------------------------- */
/* SUPERSEDED BY 104. The 90% cap that stood here is gone: with the overlap
   band removed there is nothing left to clear, and a percentage of a column
   whose width was itself the problem was never the right instrument. */


/* ---------------------------------------------------------------------------
   104. THE HERO TYPE WAS SIZED FOR A STAGE THAT IS USUALLY NOT THERE
   [2026-09-17]

   Third round on the same collision, so this stops tuning a number and removes
   the mechanism.

   WHAT THE MEASUREMENT SAID. Mapping the reported screenshot back onto the
   SVG viewBox through the six node centres (the method in 103; the fit
   screen_x = 542.1 + 0.9425 * svg_x predicted all three held-out bottom-row
   nodes within 1px):

       stage                 924 css px      NOT the 1100px max-width
       column  46% of it     425 px
       "Retail Execution." at 48px   ~425 px      -> ZERO slack

   The headline exactly fills its column. Everything was sized against
   `.lg-stage { max-width: 1100px }` as though the stage were always 1100 - but
   the stage is `min(1100, contentArea - padding)`, and contentArea is whatever
   is left after the 500px sign-in panel. At a 1500px viewport that is ~924px,
   so the type is about 19% too large for the space it actually gets, the
   headline has no room at all, and the paragraph runs to the column edge -
   straight into the 4% band that login-modern.css deliberately overlaps.

   TWO CHANGES, AND ONLY THE FIRST ONE MATTERS FOR OVERLAP.

   1. THE OVERLAP BAND IS REMOVED IN MODERN AND DARK. login-modern.css pulls
      the diagram back under the copy with `.lg-eco { margin: 0 0 0 -4% }`,
      which was tuned for a 34% column and never revisited when 4d widened the
      column to 46% (that is 103's finding). With the band gone the two columns
      are simply adjacent: the copy occupies 0..46% and the diagram 46..100%,
      so a collision is not something to be avoided any more - it is not
      expressible. 4d's own note says the diagram was meant to be 54%; the -4%
      is exactly what was making it 58%.

      This is 77's rule applied to layout: when you cannot look at the result,
      take the construction with no failure mode over the one that needs a
      number to be right.

   2. THE TYPE SCALES WITH THE VIEWPORT, per Apple HIG:
        - the display size tracks the space available instead of being fixed
          for one breakpoint, so the headline holds its two lines everywhere;
        - tracking is in `em`, not px, so it stays proportional as the size
          moves - HIG's "tighter as it gets larger" without a table of values;
        - body copy stays at a stable, legible size (18-20px) rather than
          shrinking with the viewport, and keeps a 1.6 line-height and normal
          tracking, which is what HIG asks for at body sizes;
        - the measure stays inside HIG's 45-75 character guidance and the
          paragraph inside its stated 3-line maximum.

      `vw` rather than `clamp()`: clamp() is Chrome 79 and this app's floor is
      59. `2.2vw` is bounded by hand at the top end instead - at 2180px it has
      reached 48px, which is where the fixed step takes over, so the two meet
      without a jump.

   Standard is untouched: it keeps the 34% column, the -4% band and the shorter
   .bz-ng-off copy, none of which reach each other.
   --------------------------------------------------------------------------- */
@media only screen and (min-width: 1181px) {

    /* 1. no overlap band - the copy and the diagram are simply neighbours */
    [data-bz-theme="nextgen"] .lg-eco,
    [data-bz-theme="dark"] .lg-eco {
        margin-left: 0;
    }

    /* a real gutter, so every child of the column is protected - not just the
       one element that happened to be reported. Bootstrap sets border-box
       globally, so this comes out of the 46%, which is what the sums above
       assume. */
    [data-bz-theme="nextgen"] .lg-hero-txt,
    [data-bz-theme="dark"] .lg-hero-txt {
        padding-right: 24px;
    }

    /* 2. display size follows the space it is given */
    [data-bz-theme="nextgen"] .lg-hero-txt .lg-head,
    [data-bz-theme="dark"] .lg-hero-txt .lg-head {
        font-size: 2.2vw;
        letter-spacing: -0.025em;
        line-height: 1.14;
    }

    [data-bz-theme="nextgen"] .lg-hero-txt .lg-sub,
    [data-bz-theme="dark"] .lg-hero-txt .lg-sub {
        font-size: 18px;
        line-height: 1.6;
        letter-spacing: normal;
        max-width: none;
    }
}

/* Body copy steps up once there is room for it, and stops there - HIG keeps
   body sizes stable rather than scaling them with the window. */
@media only screen and (min-width: 1400px) {
    [data-bz-theme="nextgen"] .lg-hero-txt .lg-sub,
    [data-bz-theme="dark"] .lg-hero-txt .lg-sub {
        font-size: 20px;
    }
}

/* The top end of the display ramp. 2.2vw reaches 48px at 2180px, so the fixed
   value continues the curve rather than stepping off it. */
@media only screen and (min-width: 2180px) {
    [data-bz-theme="nextgen"] .lg-hero-txt .lg-head,
    [data-bz-theme="dark"] .lg-hero-txt .lg-head {
        font-size: 48px;
    }
}
