/* Block: cnm-faq
 * Classes: glossary-terms, glossary-cat, interior-faq-item, is-open,
 *          interior-faq-question, label, toggle, interior-faq-answer, cnm-faq
 *
 * --- THIS FILE IS DELIBERATELY EMPTY -------------------------------------
 *
 * It carried a THIRD copy of the in-page nav component — `.toc-sidebar .label`,
 * `.toc-sidebar .toc-sidebar__subs .label` and `.toc-sidebar a.is-active` — in
 * the stylesheet of a block that does not render a nav at all. Because this file
 * is enqueued as its own <link>, it landed after the inlined theme CSS and won.
 *
 * That is not hypothetical: on 2026-08-17 the TOC label went to the comp's
 * Pacaembu 300 in assets/css/interior.css and the Glossary kept rendering it at
 * 400, on a fresh URL, with the served HTML visibly containing the 300 rule. The
 * stale `font-weight: 400` in THIS file was the winner. Understanding UTUC
 * updated correctly because its nav renders through cnm-toc, whose duplicate had
 * already been removed — so exactly one of the two pages sharing one component
 * moved, which is the drift signature to watch for.
 *
 * EMPTYING THIS WAS CHECKED, NOT ASSUMED. Every rule was compared declaration by
 * declaration against the theme first:
 *   - `.toc-sidebar .toc-sidebar__subs .label`, `.toc-sidebar a.is-active`,
 *     `.interior-faq-answer` and its reduced-motion pair: byte-identical to
 *     assets/css/interior.css
 *   - the `scroll-margin-top` group: byte-identical to interior.css (and to
 *     blocks/cnm-article-topics, which is a separate duplicate of its own)
 *   - `.toc-sidebar .label`: the ONLY divergence, and it was this copy being
 *     stale
 *   - nothing existed here and nowhere else
 * interior.css is enqueued on every non-home page (inc/enqueue.php picks
 * home.css vs interior.css), so both pages that render this block still get all
 * of it.
 *
 * The file is kept, not deleted, because cnm-faq.php enqueues it by name — an
 * empty stylesheet is a no-op, a missing one is a 404 on every page with an FAQ.
 * If this block ever needs styling that is genuinely its own, it belongs here;
 * anything the pages share does not.
 *
 * See blocks/cnm-toc/css/style.css for the same note about the same component.
 * ------------------------------------------------------------------------- */