/* SEO-1 (inner-page SEO handoff, 15 Oct 2026): every call to action that navigates is now a link styled as a button
   (<a class="fid-btn ...">, LinkButton in core.jsx) instead of the design system's <button>, so crawlers can follow it.
   A link meets rules a button never met: the design system's tokens/base.css `a:hover{color:var(--text-link-hover);
   text-decoration:underline}` and home/site.css `a:hover{color:...}` (0,1,1) outrank `.fid-btn` and its variant colour
   (0,1,0), so a hovered link was underlined and took --text-link-hover (2.6:1 on the orange CTA, below WCAG 2.1 AA).
   These rules restore what the button had. Each is `a:where(...)`, specificity 0,1,1 like `a:hover` itself: it wins
   only by coming later, and every rule the pages scope to a section (a dark band's white secondary button, 0,2,0 and
   above) still wins as it did for the button. Also the button's own centred text (a link inherits the start side).
   The Book a Demo pages' current-page pill (`a.fid-btn.hdr__cur`, a link in the source, demo/demo.css) is left out.
   Website-scoped; nothing is loaded and no design-system file or token changes. */
a:where(.fid-btn:not(.hdr__cur)){text-align:center}
a:where(.fid-btn:not(.hdr__cur)):hover{text-decoration:none}
a:where(.fid-btn--primary:not(.hdr__cur)):hover{color:var(--text-on-brand)}
a:where(.fid-btn--secondary:not(.hdr__cur),.fid-btn--ghost:not(.hdr__cur)):hover{color:var(--text-default)}
a:where(.fid-btn--exception:not(.hdr__cur)):hover{color:var(--text-on-orange)}
a:where(.fid-btn--critical:not(.hdr__cur)):hover{color:var(--sem-critical-text)}