/* Phone layout fixes for the Framer export (<= 809.98px).
 *
 * Same reasoning as nav.css: this has to be a stylesheet rather than a patch
 * to the exported markup, because Framer's runtime re-renders from its own
 * props and an edit to the HTML vanishes on hydration (see README, "What
 * patching can and cannot fix"). patch_export.py re-attaches this file to
 * every page after a re-export.
 *
 * SCOPING, AND WHY IT LOOKS LIKE THIS. Page-level layout in the export is
 * addressed by `framer-xxxxxxx` class hashes, which are regenerated on every
 * re-export -- a rule keyed on one of those would stop matching silently, and
 * the bug would come back with nothing to show for it. Framer does emit one
 * durable per-page identifier: the routeId inside `#main`'s
 * data-framer-hydrate-v2, which survives hydration. Rules here are scoped on
 * that plus a plain element selector, so the worst case if a route id ever
 * changes is that the rule stops applying -- never that it applies to the
 * wrong page.
 *
 * Verify a rule still bites after any re-export. There is no build-time check
 * for this.
 */

/* /for-experts -- the bottom of the page is unreachable on a phone.
 *
 * The export bakes `height: 5310px` onto <main> in the phone breakpoint (the
 * base rule is `height: min-content`), and <main> is `overflow: clip`. The
 * content is 5735px tall at 390px wide and 6525px at 320px, so 425px / 1215px
 * is cut off and cannot be scrolled to: two FAQ answers, the closing
 * "Interested?" heading and the "Get Started Here" button -- the page's only
 * bottom-of-funnel CTA -- at 390, and the entire FAQ block at 320.
 *
 * Restoring min-content is the same value every other breakpoint uses. It
 * cannot shrink the page: the content is taller than the baked height at both
 * widths, which is the whole bug.
 */
@media (max-width: 809.98px) {
  [data-framer-hydrate-v2*="c8Wf_UdAL"] main {
    height: min-content !important;
  }
}