arcane_lexicon

Fixed

• Example docs site failed to compile (and broke the GitHub Pages deploy): main.server.dart still constructed ShadcnKnowledgeBaseRenderers, NeonKnowledgeBaseRenderers, and NeubrutalismKnowledgeBaseRenderers, which moved to the arcane_jaspr_kb package. The example now depends on and imports arcane_jaspr_kb.
• Rounded callouts, active navigation, and top-bar groups no longer use one-sided borders, clipped hotspots, or asymmetric inset highlights. Status is expressed with complete perimeter borders, fills, icon tiles, and symmetric rings.
• Single-stylesheet knowledge bases (those passing only stylesheet: to KnowledgeBaseApp.create, with no stylesheetOptions) rendered a completely blank page. The style-slot system synthesizes one slot with id default, but the active-slot id resolved to '' on both the server (KBLayout) and the client runtime (_fallbackStylesheetId), so no slot ever matched and every slot stayed display:none/hidden. A single synthesized slot is now always active server-side, and the client fallback id is default, so single-theme docs render correctly. Multi-stylesheet sites are unaffected.
• DefaultKnowledgeBaseRenderers.showTopBarBranding returned a hardcoded false, so KBs using the default renderers (e.g. single-stylesheet apps) left the top bar's left side empty (only a desktop-hidden hamburger) and pushed the brand into the sidebar. It now returns data.showNavigationBar && data.useTopPosition (matching the shadcn/neon/neubrutalism renderers), so the brand renders top-left in the standard position when the nav bar is top-positioned.

Added

• Opt-in autoHide on the documentation top bar (KBTopBar and KnowledgeBaseRenderers.topBar), default false. When enabled, the top bar hides on scroll-down and reappears on scroll-up (via a data-kb-autohide marker, scoped CSS, and a throttled scroll-direction handler). The default (always-visible sticky bar) is unchanged.

Changed

• ArcaneJaspr typed classes compatibility. Updated for arcane_jaspr's wrapper widgets (ArcaneDiv/ArcaneSpan/ArcaneParagraph/ArcaneHeading/ArcaneLink/…) now taking classes: List<String>? instead of String?. Every internal classes: argument across the layout (kb_page_nav, kb_changelog, kb_related_pages, kb_rating, kb_layout) and rich-markdown components now passes a single-element list, so the rendered class="..." output is byte-identical. Requires the corresponding arcane_jaspr release; bump the arcane_jaspr constraint once it is published.
• NeonKnowledgeBaseRenderers simplified to use the standard DefaultKnowledgeBaseRenderers docs chrome (top bar / sidebar / content), matching ShadcnKnowledgeBaseRenderers. Removed the bespoke shell/neonMobileDock/rail/stage/command-drawer overrides (the neon-kb-nav-rail, neon-kb-stage, neon-kb-mobile-dock, etc. layout) whose styling had been retired, so the Neon docs no longer render an unstyled, collapsed chrome. The Neon theme now styles the standard kb-* chrome.

Removed

• Theme-specific KnowledgeBaseRenderers (ShadcnKnowledgeBaseRenderers, NeonKnowledgeBaseRenderers, NeubrutalismKnowledgeBaseRenderers, Win95KnowledgeBaseRenderers) moved out of lexicon into their respective arcane_jaspr theme packages, which now depend on arcane_lexicon and extend the exported DefaultKnowledgeBaseRenderers. Consumers pass them explicitly via KBStylesheetOption.knowledgeBaseRenderers. The internal _defaultRenderersFor id-switch (which auto-resolved shadcn/neon/neubrutalism) is gone; a stylesheet option without an explicit renderer now falls back to DefaultKnowledgeBaseRenderers.