/* In-page navigation — Shell-owned, split out of shared.css (Sprint 9.5 Story 22, architecture/SHARED-CSS-LAYER-SPLIT.md). Segmented filters, in-page tab strips and their panels. Linked once in App.razor's , reaching every Blick's DOM the same way shared.css already did. Navigation icons are Font Awesome - do not add a second icon set. */ /* ── Segmented filter (.btn-group[role="radiogroup"]) ────────────────────────────────────────────────────── DESIGN-SYSTEM-GRIDS-AND-DIALOGS.md §11. Brian, 2026-09-02: the above-grid single-select filter control. NO NEW CLASS NAME: Bootstrap 5.3.3's own .btn-group + .btn-check + .btn, scoped by the standard ARIA role, per the class-naming ruling ("try to overwrite standard classes and elements"). role="radiogroup" is both the scope and the meaning -- Bootstrap's docs put role="group" on an ordinary button group, so an ordinary group can never match this. Reframed 2026-09-02 (Arthur's Part 2 review, §3): a .btn-group[role="radiogroup"] IS the segmented control and always renders as the track. If you need Bootstrap radio-toggle buttons that look different, you need a different control, not a different role -- a styling hook must never dictate ARIA, and role="radiogroup" is the CORRECT role for any single-select button-group toggle, not something to withhold to dodge this rule. SharedUIContractTests' segmented-filter sweep enforces the one real constraint this leaves: a role="radiogroup" copy must be the COMPLETE §11.2 pattern (radios + labels sharing one name, aria-label, no tabindex, a narrow-width