/* ===========================================================================
   Relevance Exchange — auth pages, brand blue
   ===========================================================================
   The band across the top half of the sign-in / sign-up / sign-out pages was the
   Velzon template's own indigo: .auth-one-bg .bg-overlay paints
   linear-gradient(to right, var(--vz-primary-text-emphasis), var(--vz-primary)),
   which resolves to #364574 -> #405189. Next to the portal and the landing page
   that reads as a different product.

   THIS FILE IS THE ONLY THING THAT CHANGES IT, and it is opted into per page:

       auth-signin-basic.html   auth-signup-basic.html   auth-logout-basic.html

   linked after custom.min.css so it wins on order alone — no !important, and the
   theme's own files are left untouched. Reversible by dropping the three <link>
   tags.

   The palette is the landing page's hero navy, same values as
   frontend/index.html and the --rx-blue-* set in rx-sleek.css:
       #0d2240  navy-900   the base
       #173451  navy-800   the portal sidebar's navy
       #1d4269  navy-700   the light end, so the band is not flat
       #366ea5  blue-500   the mesh highlight
=========================================================================== */

/* There is no background image behind this band — the overlay IS the colour — so
   opacity can go to 1 and the gradient is exactly what shows. The template left it
   at .9 to let a cover pattern through, and no such pattern is in use here. */
.auth-one-bg .bg-overlay {
    background:
        /* One soft highlight up in the top-right, which is where the landing hero
           puts its brightest point. Without it the band is a flat wash; the page is
           380px tall and a flat wash at that size looks like a placeholder. */
        radial-gradient(58% 72% at 86% 6%, rgba(54, 110, 165, .50) 0%, transparent 62%),
        radial-gradient(46% 60% at 4% 96%, rgba(31, 131, 198, .22) 0%, transparent 66%),
        linear-gradient(118deg, #0d2240 0%, #173451 54%, #1d4269 100%);
    opacity: 1;
}

/* --- The primary buttons ---------------------------------------------------
   Sign In, Sign Up, "Send me a code", "Set new password", "Confirm and continue"
   and the logout page's Sign In link all carry .btn-success, which is the
   template's teal (#0ab39c). Against the navy above and the orange CTAs on the
   landing page it read as a third brand.

   OVERRIDDEN THROUGH THE VARIABLES, not by setting background-color. Bootstrap
   builds .btn entirely out of --vz-btn-* — hover, active, the focus ring and the
   disabled state each read their own one — so redefining the set covers every
   state at once. Setting background-color directly would fix the resting button
   and leave the teal to reappear the moment somebody hovered it, and the auth
   forms disable their submit button while the request is in flight, which is a
   state a page visitor actually sees.

   Colours are the landing page's: #C35418 resting, brightening to #f27127 on
   hover exactly as .btn--primary does there, and #a8460f while pressed.

   .btn-success is left alone everywhere else — this file is only linked from the
   three auth pages, and the wrapper scope makes that explicit rather than
   incidental. */
.auth-page-wrapper .btn-success {
    --vz-btn-color: #fff;
    --vz-btn-bg: #C35418;
    --vz-btn-border-color: #C35418;
    --vz-btn-hover-color: #fff;
    --vz-btn-hover-bg: #f27127;
    --vz-btn-hover-border-color: #f27127;
    --vz-btn-focus-shadow-rgb: 195, 84, 24;
    --vz-btn-active-color: #fff;
    --vz-btn-active-bg: #a8460f;
    --vz-btn-active-border-color: #a8460f;
    --vz-btn-disabled-color: #fff;
    --vz-btn-disabled-bg: #C35418;
    --vz-btn-disabled-border-color: #C35418;
}