/* ========================================================================== Wiki / Aide — visual system. Mirrors public/css/dashboard-new.css: same token block, same component recipes (card, dashed dividers, ink-black primary button, ghost button, pill, styled scrollbars), same Manrope type stack. The wiki is a reading surface rather than a data grid, so the spacing is looser and the prose measure is capped around 70ch. Five scope roots, deliberately separate so nothing leaks into — or gets leaked into by — the rest of the app: .wiki-app — the /aide pages (index + single guide) .wiki-overlay — the help-button backdrop (teleported to ) .wiki-panel — the help-button slide-over, child of .wiki-overlay .wiki-content — rendered markdown, owns its own typography .wiki-help-trigger — the inline "?" button, which lives on host pages SPECIFICITY POLICY — every rule below is prefixed with its scope root, the way dashboard-new.css writes `.menage-dash .card` and never a bare `.card`. This is not cosmetic. The app loads several global resets whose selectors tie with a single class at (0,1,0), and on a tie source order decides: [type=text],[type=email],… { padding:.5rem .75rem; border-radius:0; border-color:#6b7280; font-size:1rem } [type=text]:focus,… { border-color:#2563eb; box-shadow: } shipped by BOTH public/vendor/bladewind/css/bladewind-ui.min.css and the Tailwind/flowbite build output. A bare `.wiki-search-input` tied with the first and lost, putting the magnifier on top of the placeholder; a bare `.wiki-search-input:focus` tied with the second and could paint a blue focus ring. Scoping takes them to (0,2,0)/(0,3,0), which wins outright with no !important needed. Bootstrap (via resources/sass/app.scss) and Tailwind preflight also reset p / ol / ul / pre / code / hr / table / th / button at (0,0,1); those lose to any class, but the rules below are scoped anyway for consistency, and the properties they touch are re-declared explicitly. Loaded globally from layouts/app.blade.php because the slide-over can be opened from any page in the app. !important POLICY: 13 declarations, and every one of them exists solely to beat resources/css/app.css's global a { color: inherit !important; text-decoration: none !important; } Specificity cannot beat !important, so link `color` (6 rules) and .wiki-content's `text-decoration: underline` / `text-decoration-color` keep theirs, as does the prefers-reduced-motion kill switch. Note the `text-decoration: none` on .wiki-result / .wiki-gcard / .wiki-btn-dark / .btn-ghost / .wiki-back is deliberately NOT important: the global reset already forces `none`, so these are belt-and-braces for the day that reset goes away, and they must not outrank it in the meantime. Ditto .wiki-btn-dark's `background` — nothing in the app sets an important background on or