/* ------------------------------------------------------------------
   Rapid Ready Ai — theme customisations
   Auto-loaded by includes/head.tpl when this file exists at
   core/styles/<style>/assets/css/theme-custom.css
   NOTE: lagom-cms.css loads AFTER this file, so anything it also sets
   needs to win on specificity, not source order.
   ------------------------------------------------------------------ */

/* Footer: "Platforms:" is a section label, not a link.
   Lagom's footerprimary.tpl renders every child menu item as <a>, and the
   footer menu offers no Divider / Header Collapse item type, so the label is
   a Custom Link pointing at #platforms and is neutralised here.
   Added 2026-09-15.
   2026-09-16: dropped `margin-top: 1.25rem` and `display: inline-block` so the
   label keeps the same vertical rhythm as every other footer link. The theme
   sets `.footer-nav>li>a{display:flex;padding:var(--main-footer-link-padding-v) ...}`
   and that padding is what spaces the column evenly; overriding display to
   inline-block replaced the flex box and the margin added a gap on top of it,
   so Live Chat -> Platforms: -> RRAi Chat sat wider apart than the neighbouring
   columns. Styling stays, spacing no longer differs. */
.footer-nav li a.nav-link[href="#platforms"] {
    pointer-events: none;
    cursor: default;
    font-weight: 600;
    opacity: 1;
    color: #fff;
}

.footer-nav li a.nav-link[href="#platforms"] span {
    font-weight: 600;
    letter-spacing: .02em;
}

.footer-nav li a.nav-link[href="#platforms"]:hover,
.footer-nav li a.nav-link[href="#platforms"]:focus {
    text-decoration: none;
    color: #fff;
}

/* Featured plan emphasis (AI Workforce Team on /ai).
   Written 2026-08-25 but saved to assets/css/vars/custom.css — one directory
   below either path head.tpl loads — so it never reached the browser. Moved
   here 2026-09-15, and strengthened: CMS package cards also carry .is-bordered,
   which lagom-cms.css paints via
   `.lagom-futuristic .site-section:not(.section-gray) .package.is-bordered`
   (0,5,0). The original `.package.package-featured` (0,2,0) lost to it, so the
   rule would not have worked from the correct path either. */
.lagom-futuristic .site-section:not(.section-gray) .package.is-bordered.package-featured,
.package.is-bordered.package-featured,
.package.package-featured {
    border-color: var(--brand-primary);
    box-shadow: 0 0 0 1px var(--brand-primary);
}