/* PE-CW-02 -03 — the only AUTHORED stylesheet in this wedge.
 *
 * Every other file in src/styles/hub/ is vendored byte-for-byte from the locked capture. This one
 * is written here, emitted last, and contains exactly one rule, for exactly one reason.
 *
 * THE DEFECT. The Financing section loads a third-party patient-financing widget from
 * files.withcherry.com. That widget sets `style="display: none"` on `#faq` — the page's own FAQ
 * section, 19 question/answer pairs and 1666 px of content at 1440x900 — almost certainly because
 * the widget renders an FAQ of its own and hides what it takes to be a duplicate. The id `faq` is
 * generic enough for a third party to claim it.
 *
 * On the LIVE page this is invisible, because the theme's `lxf-faq-accordion.js` installs a
 * MutationObserver per `.lxf-faq` section whose only job is to undo `display:none` the moment it
 * appears. PE-CW-02 first dropped that observer as a guard with nothing to guard against — the
 * reasoning being that nothing else runs on this page. That reasoning was wrong: the page loads a
 * third-party widget, and the pixel gate's per-section height comparison found the FAQ rendering
 * 0 px on the candidate against 1666 px on the live page, with all 23 other sections matching to
 * the pixel.
 *
 * WHY CSS AND NOT THE OBSERVER. An author `!important` declaration outranks a non-important inline
 * style, so one rule defeats the widget with no client JavaScript at all. It is also strictly
 * better than the live behaviour rather than equal to it: the observer necessarily runs AFTER the
 * widget hides the section, so the live page has a real flash of collapsed FAQ; this never hides.
 * And it removes a permanent observer whose purpose was to fight another script in a loop.
 *
 * WHY THIS IS A WORKAROUND AND NOT THE FIX. The actual defect is an id collision on a generic id.
 * The fix is to namespace the section (`#lxf-faq`), which cannot be done here: `headings` compares
 * the id of every heading's section and the anchor navigation links to `#faq`, so renaming it moves
 * both `headings` and `links` and needs an operator-approved deviation. Recorded in CONTRACT.md
 * § 5 S-12 and REPLACEMENT-PLAN.md.
 *
 * Scoped as tightly as the collision: this id, this class, this property.
 */
#faq.lxf-faq {
  display: block !important;
}
