/**
 * Patriot University — touch target sizing (P1.12)
 *
 * `.pu-m1`-scoped, so inert until PU_MOBILE_FIRST is flipped.
 *
 * MEASURED ON THE HOMEPAGE AT 390px, where the KB category tree lives:
 *
 *     summary rows    15 items, 34-37px   ALL under 44
 *     leaf links      55 items, 34-37px   ALL under 44
 *     mobile toggle    1 item,  39px      under 44
 *
 * 70 rows a reader taps to navigate ~1,600 documents, every one of them below
 * the 44px `--pu-touch` target the design contract already declares.
 *
 * `pointer: coarse`, NOT a width breakpoint, and that distinction is the whole
 * design. 70 rows growing from ~35px to 44px adds 630px of height. On a phone
 * that is the fix; on a mouse-driven desktop it is half a screen of new
 * scrolling in a reference tree nobody is fat-fingering. §7.3 already uses
 * `pointer: coarse` for exactly this, and it is also more correct than width:
 * a touch laptop gets big targets, a narrow desktop window does not.
 *
 * The KB tree renders on the HOMEPAGE ONLY — checked across five surfaces
 * before writing, because §10.2 describes it as a shared component and it is
 * not one yet. That homepage is Surface B, so this cannot be scoped to Surface
 * A; `.pu-m1` is the correct gate and reaches it.
 *
 * `min-height` and never `height`: Android users routinely run 120-150% system
 * font, and a fixed height clips the label rather than growing the row (§7.3).
 */
@media (pointer: coarse) {
    .pu-m1 .pu-catnav__summary,
    .pu-m1 .pu-catnav__link,
    .pu-m1 .pu-catnav__toggle {
        min-height: var(--pu-touch);
        display: flex;
        align-items: center;
    }

    /*
     * The badge is INSIDE the row, so the row is already the hit target and the
     * badge needs no size of its own — growing it would only push the label.
     * It is listed here to record that the 18px measurement was considered and
     * deliberately left alone, rather than missed.
     */
}