bestax-mcp 1.18.35 → 1.18.37

package/data/bulma-classes.json

@@ -2248,7 +2248,7 @@
       "status": "mapped",
       "target": "Level",
       "tag": "nav",
-      "as": null,
+      "as": ["nav", "div", "header", "footer"],
       "sizeDrivesTag": false,
       "textColor": "textColor",
       "bgColor": "bgColor",

package/data/catalog.json

@@ -2,7 +2,7 @@
   "schemaVersion": 2,
   "generatedFrom": {
     "package": "@allxsmith/bestax-bulma",
-    "version": "5.66.1"
+    "version": "5.67.0"
   },
   "docsBase": "https://bestax.io/docs",
   "categories": [
@@ -875,7 +875,7 @@
       "slug": "layout/level",
       "import": "import { Level } from '@allxsmith/bestax-bulma';",
       "compound": true,
-      "propCount": 23,
+      "propCount": 24,
       "exampleCount": 5
     },
     {

package/data/components/AppFrame.json

@@ -38,7 +38,7 @@
       "code": "<AppFrame>\n  <AppFrameHeader>\n    <Navbar aria-label=\"Site\">\n      <Navbar.Brand>\n        <Navbar.Item href=\"#\">\n          <strong>Acme</strong>\n        </Navbar.Item>\n        <AppFrameBurger />\n      </Navbar.Brand>\n    </Navbar>\n  </AppFrameHeader>\n  <AppFrameNav>\n    <Menu>\n      <Menu.List>\n        <Menu.Item href=\"#\" active>\n          Dashboard\n        </Menu.Item>\n      </Menu.List>\n    </Menu>\n  </AppFrameNav>\n  <AppFrame.Main>\n    <Section>\n      <Paragraph>\n        AppFrameNav and AppFrame.Nav are the same component.\n      </Paragraph>\n    </Section>\n  </AppFrame.Main>\n</AppFrame>"
     }
   ],
-  "accessibility": "- **Landmarks:** the header, the nav, the page and the footer are the page's banner, navigation,\n  main and contentinfo landmarks, and the aside a complementary one, as long as the frame sits at\n  the top of the page. A development build warns when it sits inside a `main` or a sectioning\n  element, where the header and footer stop being landmarks.\n- **Names:** the nav is named \"Sections\" (`labels.nav`), since the `Navbar` in the header names\n  its own navigation. The name leaves out the word \"navigation\", which the role says. A `Menu`\n  in the nav keeps its `<aside>`, which inside a `<nav>` is a plain element unless it's named.\n- **Skip link:** the first thing on the page, hidden until it has focus, moves focus to the page's\n  `<main>` (WCAG 2.4.1).\n- **Sticky header:** `scroll-padding-top` on the document keeps an in-page link's target and a\n  focused element below the header (WCAG 2.4.11, technique C43).\n- **The burger** is a button named \"menu\" (`labels.burger`), with `aria-expanded` saying whether\n  the drawer is open, or from the breakpoint up whether the column is shown, and `aria-controls`\n  naming the nav. The server can't know the width, so until the page hydrates the burger has no\n  `aria-expanded` and shows its bars, and the first paint after hydration has both right.\n- **The drawer** is modal by default: focus moves to its close button, Tab and Shift+Tab stay\n  inside, the page doesn't scroll, the rest of the frame is inert, and Escape closes it while it's\n  the topmost overlay, so a `Modal` opened from it closes first. Escape, the close button and a\n  click on the backdrop hand focus back to the burger, and so does a press outside the drawer\n  without `overlay`, before the press moves it to what was pressed. The close button is there for\n  a touch screen reader user, who has no Escape key. It stays a navigation landmark rather than a\n  dialog: the inert frame is what keeps assistive technology inside it, so keep the page's content\n  inside the frame's parts.\n- **A closed drawer and a collapsed column** are `visibility: hidden`, so their links are out of\n  the Tab order and the accessibility tree before any script runs.\n- **Reflow:** at 320 pixels wide the nav is a drawer, so nothing scrolls sideways (WCAG 1.4.10).\n- **Motion:** the drawer's slide, the backdrop's fade and the column's collapse don't play under\n  `prefers-reduced-motion: reduce`.\n- **Forced colors:** the column keeps its divider, and the drawer gets a border on its open edge in\n  place of its shadow.\n- **Right to left:** the column sits on the right, and the drawer slides in from the right.",
+  "accessibility": "- **Landmarks:** the header, the nav, the page and the footer are the page's banner, navigation,\n  main and contentinfo landmarks, and the aside a complementary one, as long as the frame sits at\n  the top of the page. A development build warns when it sits inside a `main` or a sectioning\n  element, where the header and footer stop being landmarks.\n- **Names:** the nav is named \"Sections\" (`labels.nav`), since the `Navbar` in the header names\n  its own navigation. The name leaves out the word \"navigation\", which the role says. A `Menu`\n  in the nav keeps its `<aside>`, which inside a `<nav>` is a plain element unless it's named.\n- **Skip link:** the first thing on the page, hidden until it has focus, moves focus to the page's\n  `<main>` (WCAG 2.4.1).\n- **Sticky header:** `scroll-padding-top` on the document keeps an in-page link's target and a\n  focused element below the header (WCAG 2.4.11, technique C43).\n- **The burger** is a button named \"menu\" (`labels.burger`), with `aria-expanded` saying whether\n  the drawer is open, or from the breakpoint up whether the column is shown, and `aria-controls`\n  naming the nav. The server can't know the width, so until the page hydrates the burger has no\n  `aria-expanded` and shows its bars, and the first paint after hydration has both right.\n- **The drawer** is modal by default: focus moves to its close button, Tab and Shift+Tab stay\n  inside, the page doesn't scroll, the rest of the frame is inert, and Escape closes it while it's\n  the topmost overlay, so a `Modal` opened from it closes first. Escape, the close button and a\n  click on the backdrop hand focus back to the burger, and so does a press outside the drawer\n  without `overlay`, before the press moves it to what was pressed. The close button is there for\n  a touch screen reader user, who has no Escape key. It stays a navigation landmark rather than a\n  dialog: the inert frame is what keeps assistive technology inside it, so keep the page's content\n  inside the frame's parts.\n- **A closed drawer and a collapsed column** are `visibility: hidden`, so their links are out of\n  the Tab order and the accessibility tree before any script runs.\n- **Reflow:** at 320 pixels wide the nav is a drawer, so nothing scrolls sideways (WCAG 1.4.10).\n- **Motion:** the drawer's slide, the backdrop's fade and the column's collapse don't play under\n  `prefers-reduced-motion: reduce`.\n- **Forced colors:** the column keeps its divider, the drawer gets a border on its open edge in\n  place of its shadow, and the burger keeps its bars, as a [`Navbar`](https://bestax.io/docs/api/components/navbar)'s\n  does.\n- **Right to left:** the column sits on the right, and the drawer slides in from the right.",
   "related": [
     "Footer",
     "Menu",

package/data/components/DateInput.json

@@ -178,7 +178,7 @@
       "code": "function example() {\n  return (\n    <Field\n      horizontal\n      label=\"Date\"\n      labelProps={{ htmlFor: 'date-field-control' }}\n    >\n      <Field.Body>\n        <Field>\n          <Control iconLeftName=\"calendar-alt\">\n            <DateInput id=\"date-field-control\" placeholder=\"YYYY-MM-DD\" />\n          </Control>\n        </Field>\n      </Field.Body>\n    </Field>\n  );\n}"
     }
   ],
-  "accessibility": "- Trigger uses `role=\"combobox\"` with `aria-haspopup=\"dialog\"`, `aria-expanded`, and `aria-controls`.\n- Popover panel has `role=\"dialog\"` with an accessible name. Opening it puts focus on the focused date, month or year.\n- Closing the popover with `Escape` or a pick returns focus to the input, whether the input or the launcher opened it. Under `openOnFocus` that returning focus leaves the popover closed; focusing or clicking the input again opens it. Dismissing without a pick commits nothing: an empty field stays empty, and leaving afterwards commits only what you typed.\n- Calendar uses `role=\"grid\"` with cells as `role=\"gridcell\"`.\n- Cells expose `aria-selected`, `aria-disabled`, and `aria-current=\"date\"` for today.\n- Roving `tabindex` keeps a single grid cell focusable at a time, and focus moves with it, inline as in the popover. When the focused date is disabled, that cell is the nearest enabled day of the month.\n- The month grid is a `role=\"grid\"` of `role=\"row\"`s, labelled by the year in its header. Each month cell carries the full month name as its accessible name, `aria-current=\"date\"` for this month and `aria-disabled` for a month with no selectable day.\n- The year list is a `role=\"listbox\"` named by the `chooseYear` label. As the selection surface its options take `aria-selected` from the value's year rather than from focus, which roves through the list. When the focused year is disabled, the nearest enabled year takes the tab stop, so `Tab` still reaches the list.\n- The launcher and popover are named \"Choose month\" or \"Choose year\" to match the granularity; override them, and the month grid's \"Previous year\" / \"Next year\" buttons, through `labels` (`chooseMonth`, `chooseYear`, `prevYear`, `nextYear`).\n- Honors `prefers-reduced-motion` (skip popover fade-in).\n- On a right-to-left page the launcher sits at the end of the line and the calendar icon at the start, and the previous-month chevron points right. The month names follow the page.",
+  "accessibility": "- Trigger uses `role=\"combobox\"` with `aria-haspopup=\"dialog\"`, `aria-expanded`, and `aria-controls`.\n- Popover panel has `role=\"dialog\"` with an accessible name. Opening it puts focus on the focused date, month or year.\n- Closing the popover with `Escape` or a pick returns focus to the input, whether the input or the launcher opened it. Under `openOnFocus` that returning focus leaves the popover closed; focusing or clicking the input again opens it. Dismissing without a pick commits nothing: an empty field stays empty, and leaving afterwards commits only what you typed.\n- Calendar uses `role=\"grid\"` with cells as `role=\"gridcell\"`.\n- Cells expose `aria-selected`, `aria-disabled`, and `aria-current=\"date\"` for today. On a server-rendered page, today's day, month and year get it once the page hydrates, so the reader's clock decides which.\n- Roving `tabindex` keeps a single grid cell focusable at a time, and focus moves with it, inline as in the popover. When the focused date is disabled, that cell is the nearest enabled day of the month.\n- The month grid is a `role=\"grid\"` of `role=\"row\"`s, labelled by the year in its header. Each month cell carries the full month name as its accessible name, `aria-current=\"date\"` for this month and `aria-disabled` for a month with no selectable day.\n- The year list is a `role=\"listbox\"` named by the `chooseYear` label. As the selection surface its options take `aria-selected` from the value's year rather than from focus, which roves through the list. When the focused year is disabled, the nearest enabled year takes the tab stop, so `Tab` still reaches the list.\n- The launcher and popover are named \"Choose month\" or \"Choose year\" to match the granularity; override them, and the month grid's \"Previous year\" / \"Next year\" buttons, through `labels` (`chooseMonth`, `chooseYear`, `prevYear`, `nextYear`).\n- Honors `prefers-reduced-motion` (skip popover fade-in).\n- On a right-to-left page the launcher sits at the end of the line and the calendar icon at the start, and the previous-month chevron points right. The month names follow the page.",
   "related": ["DateTimeInput", "Input", "TimeInput"],
   "storybook": "https://bestax.io/storybook/?path=/story/form-dateinput",
   "summary": "The `DateInput` component is a form input that opens a popover calendar for date selection.",
@@ -492,7 +492,7 @@
           "name": "inline",
           "type": "boolean",
           "default": "false",
-          "description": "Render the calendar inline (no popover).",
+          "description": "Render the calendar inline (no popover). On a server-rendered page it marks today once the page hydrates, by the browser's clock rather than the server's. With no `value` or `defaultValue` it opens on the month the clock reads, and around the end of a month the server's clock and the browser's can read different months, so give it a date both render the same.",
           "required": false,
           "inherited": true,
           "deprecated": false
@@ -854,7 +854,7 @@
           "name": "inline",
           "type": "boolean",
           "default": "false",
-          "description": "Render the calendar inline (no popover).",
+          "description": "Render the calendar inline (no popover). On a server-rendered page it marks today once the page hydrates, by the browser's clock rather than the server's. With no `value` or `defaultValue` it opens on the month the clock reads, and around the end of a month the server's clock and the browser's can read different months, so give it a date both render the same.",
           "required": false,
           "inherited": false,
           "deprecated": false

package/data/components/DateRangeInput.json

@@ -351,7 +351,7 @@
           "name": "inline",
           "type": "boolean",
           "default": "false",
-          "description": "Render the calendar inline, with no inputs and no popover. The hidden form inputs still carry the range.",
+          "description": "Render the calendar inline, with no inputs and no popover. The hidden form inputs still carry the range. On a server-rendered page it marks today once the page hydrates, by the browser's clock rather than the server's. With no `value` or `defaultValue` it opens on the month the clock reads, and around the end of a month the server's clock and the browser's can read different months, so give it a date both render the same.",
           "required": false,
           "inherited": true,
           "deprecated": false
@@ -740,7 +740,7 @@
           "name": "inline",
           "type": "boolean",
           "default": "false",
-          "description": "Render the calendar inline, with no inputs and no popover. The hidden form inputs still carry the range.",
+          "description": "Render the calendar inline, with no inputs and no popover. The hidden form inputs still carry the range. On a server-rendered page it marks today once the page hydrates, by the browser's clock rather than the server's. With no `value` or `defaultValue` it opens on the month the clock reads, and around the end of a month the server's clock and the browser's can read different months, so give it a date both render the same.",
           "required": false,
           "inherited": false,
           "deprecated": false

package/data/components/DateTimeInput.json

@@ -170,7 +170,7 @@
       "code": "<DateTimeInput label=\"Input only\" popover={false} defaultValue={new Date()} />"
     }
   ],
-  "accessibility": "- Trigger uses `role=\"combobox\"` with `aria-haspopup=\"dialog\"`, `aria-expanded`, and `aria-controls`.\n- Popover panel has `role=\"dialog\"` with an accessible name. Opening it puts focus on the focused date.\n- Closing the popover with `Escape`, the ✓ button or `Enter` on a time wheel returns focus to the input, whether the input or the launcher opened it. Under `openOnFocus` that returning focus leaves the popover closed; focusing or clicking the input again opens it. Closing it commits nothing by itself: an empty field stays empty, and leaving afterwards commits only what you typed, so seconds the display leaves out are kept.\n- Calendar uses `role=\"grid\"`; cells expose `aria-selected`, `aria-disabled`, and `aria-current=\"date\"`.\n- Roving `tabindex` keeps a single day focusable at a time, and focus moves with it, inline as in the popover. When the focused date is disabled, that cell is the nearest enabled day of the month.\n- Each time wheel uses `role=\"spinbutton\"` with `aria-valuemin`, `aria-valuemax`, `aria-valuenow`, and `aria-valuetext`. The values drawn above and below are click targets hidden from assistive technology, which reads the value from the spinbutton.\n- In a 12-hour picker, AM/PM is one of those wheels, reading `AM` or `PM`. Its accessible name is `AM/PM` unless `labels.ampm` sets another.\n- The footer's confirm button exposes an accessible label (`Done`); the Reset button reverts your edits to the value the popover opened with.\n- Tab order walks from the calendar to the footer (Reset / ✓), and from the time wheels to the footer while they are open.\n- On a right-to-left page the launcher sits at the end of the line and the calendar icon at the start. The time wheels keep `dir=\"ltr\"`.",
+  "accessibility": "- Trigger uses `role=\"combobox\"` with `aria-haspopup=\"dialog\"`, `aria-expanded`, and `aria-controls`.\n- Popover panel has `role=\"dialog\"` with an accessible name. Opening it puts focus on the focused date.\n- Closing the popover with `Escape`, the ✓ button or `Enter` on a time wheel returns focus to the input, whether the input or the launcher opened it. Under `openOnFocus` that returning focus leaves the popover closed; focusing or clicking the input again opens it. Closing it commits nothing by itself: an empty field stays empty, and leaving afterwards commits only what you typed, so seconds the display leaves out are kept.\n- Calendar uses `role=\"grid\"`; cells expose `aria-selected`, `aria-disabled`, and `aria-current=\"date\"` for today. On a server-rendered page, today gets it once the page hydrates, so the reader's clock decides which day.\n- Roving `tabindex` keeps a single day focusable at a time, and focus moves with it, inline as in the popover. When the focused date is disabled, that cell is the nearest enabled day of the month.\n- Each time wheel uses `role=\"spinbutton\"` with `aria-valuemin`, `aria-valuemax`, `aria-valuenow`, and `aria-valuetext`. The values drawn above and below are click targets hidden from assistive technology, which reads the value from the spinbutton.\n- In a 12-hour picker, AM/PM is one of those wheels, reading `AM` or `PM`. Its accessible name is `AM/PM` unless `labels.ampm` sets another.\n- The footer's confirm button exposes an accessible label (`Done`); the Reset button reverts your edits to the value the popover opened with.\n- Tab order walks from the calendar to the footer (Reset / ✓), and from the time wheels to the footer while they are open.\n- On a right-to-left page the launcher sits at the end of the line and the calendar icon at the start. The time wheels keep `dir=\"ltr\"`.",
   "related": ["DateInput", "Input", "TimeInput"],
   "storybook": "https://bestax.io/storybook/?path=/story/form-datetimeinput",
   "summary": "The `DateTimeInput` combines a calendar and a time **wheel spinner** in a single popover — an iOS-style layout.",
@@ -475,7 +475,7 @@
           "name": "inline",
           "type": "boolean",
           "default": "false",
-          "description": "Render the panel inline (no popover).",
+          "description": "Render the panel inline (no popover). On a server-rendered page it marks today once the page hydrates, by the browser's clock rather than the server's. With no `value` or `defaultValue` it opens on the month the clock reads, and around the end of a month the server's clock and the browser's can read different months, so give it a date both render the same.",
           "required": false,
           "inherited": true,
           "deprecated": false
@@ -900,7 +900,7 @@
           "name": "inline",
           "type": "boolean",
           "default": "false",
-          "description": "Render the panel inline (no popover).",
+          "description": "Render the panel inline (no popover). On a server-rendered page it marks today once the page hydrates, by the browser's clock rather than the server's. With no `value` or `defaultValue` it opens on the month the clock reads, and around the end of a month the server's clock and the browser's can read different months, so give it a date both render the same.",
           "required": false,
           "inherited": false,
           "deprecated": false

package/data/components/Dialog.json

@@ -30,7 +30,7 @@
       "code": "function example() {\n  const [showDialog, setShowDialog] = useState(false);\n  return (\n    <Block>\n      <Button onClick={() => setShowDialog(true)}>Show Portaled Dialog</Button>\n      <Dialog\n        isOpen={showDialog}\n        title=\"Portaled Dialog\"\n        message=\"This dialog is portaled, so it escapes any ancestor with overflow: hidden.\"\n        onConfirm={() => setShowDialog(false)}\n        showCancel={false}\n        portal\n      />\n    </Block>\n  );\n}"
     }
   ],
-  "accessibility": "- Uses `role=\"alertdialog\"` for proper screen reader announcement\n- Has `aria-modal=\"true\"` to indicate modal behavior — note this does not make background content inert; no `inert` attribute is applied, so background content stays reachable by pointer\n- `title` is wired up as `aria-labelledby` and `message` as `aria-describedby`\n- Focus moves to the confirm (or cancel, with `focusCancel`) button when opened\n- Escape key closes the dialog (when `canCancel` is true). The underlying [`Modal`](https://bestax.io/docs/api/components/modal#accessibility) handles it, so one Escape closes the topmost overlay only: a dialog opened over a Modal or a [Sidebar](https://bestax.io/docs/api/components/sidebar) closes first, and the one under it on the next Escape\n- Tab and Shift+Tab cycle within the dialog while it is the topmost modal overlay, also from the underlying [`Modal`](https://bestax.io/docs/api/components/modal)\n- Body scroll is prevented when dialog is open, through the ref-counted lock shared with `Modal`, `Sidebar` and `Loading`\n- Confirm/cancel buttons are keyboard accessible",
+  "accessibility": "- Uses `role=\"alertdialog\"` for proper screen reader announcement\n- Has `aria-modal=\"true\"` to indicate modal behavior — note this does not make background content inert; no `inert` attribute is applied, so background content stays reachable by pointer\n- `title` is wired up as `aria-labelledby` and `message` as `aria-describedby`\n- Focus moves to the confirm (or cancel, with `focusCancel`) button when opened\n- Escape key closes the dialog (when `canCancel` is true). The underlying [`Modal`](https://bestax.io/docs/api/components/modal#accessibility) handles it, so one Escape closes the topmost overlay only: a dialog opened over a Modal or a [Sidebar](https://bestax.io/docs/api/components/sidebar) closes first, and the one under it on the next Escape\n- Tab and Shift+Tab cycle within the dialog while it is the topmost modal overlay, also from the underlying [`Modal`](https://bestax.io/docs/api/components/modal)\n- The page doesn't scroll while the dialog is open, through the [`Modal`](https://bestax.io/docs/api/components/modal#accessibility)'s ref-counted lock, shared with `Sidebar` and `Loading`\n- Confirm/cancel buttons are keyboard accessible",
   "related": ["Modal", "Toast"],
   "storybook": "https://bestax.io/storybook/?path=/story/components-dialog",
   "summary": "The `Dialog` component provides ready-made confirm and alert dialogs, so a destructive action stays one `await dialog.confirm()` call away.",

package/data/components/HoverCard.json

@@ -119,7 +119,7 @@
           "name": "appendToBody",
           "type": "boolean",
           "default": "false",
-          "description": "Render the card through `Portal`, into the `portalContainer` a `ConfigProvider` sets, `document.body` by default, fixed to the viewport, so an ancestor's `overflow`, `transform` or stacking context can't clip it. A trigger in running text needs it too, since the card's block content can't sit inside a `<p>`. The card then shows from the commit after hydration, never in server markup, and it sits in the Tab order where its container is. At the end of `<body>`, the default, Tab reaches it only after the rest of the page, and focus leaving the trigger on the way closes it, so keyboard users can open it, read it and close it with Escape, and whatever it links to has to be reachable from the page as well. It is measured against the trigger when it opens and on resize and scroll, so it doesn't follow content that changes size while it is open. Theming variables set on an ancestor of the trigger reach it only when its container is inside that ancestor.",
+          "description": "Render the card through `Portal`, into the `portalContainer` a `ConfigProvider` sets, `document.body` by default, fixed to the viewport, so an ancestor's `overflow`, `transform` or stacking context can't clip it. A trigger in running text needs it too, since the card's block content can't sit inside a `<p>`. The card then shows from the commit after hydration, never in server markup, and it sits in the Tab order where its container is. At the end of `<body>`, the default, Tab reaches it only after the rest of the page, and focus leaving the trigger on the way closes it, so keyboard users can open it, read it and close it with Escape, and whatever it links to has to be reachable from the page as well. Theming variables set on an ancestor of the trigger reach it only when its container is inside that ancestor.",
           "required": false,
           "inherited": false,
           "deprecated": false

package/data/components/Icon.json

@@ -77,7 +77,7 @@
       "props": [
         {
           "name": "name",
-          "type": "string | undefined",
+          "type": "string",
           "default": null,
           "description": "The icon name, with or without its library prefix (e.g. `'star'` or `'fa-star'`). Mutually exclusive with `children`.",
           "required": false,

package/data/components/IconText.json

@@ -140,7 +140,7 @@
       "props": [
         {
           "name": "name",
-          "type": "string | undefined",
+          "type": "string",
           "default": null,
           "description": "The icon name, with or without its library prefix (e.g. `'star'` or `'fa-star'`). Mutually exclusive with `children`.",
           "required": false,

package/data/components/Level.json

@@ -11,7 +11,7 @@
     },
     {
       "title": "Centered Level (Statistics)",
-      "code": "<Level>\n  <Level.Item hasTextCentered>\n    <Block>\n      <Paragraph\n        textSize=\"7\"\n        textTransform=\"uppercase\"\n        textWeight=\"semibold\"\n        mb=\"1\"\n      >\n        Posts\n      </Paragraph>\n      <Title as=\"p\">1,234</Title>\n    </Block>\n  </Level.Item>\n  <Level.Item hasTextCentered>\n    <Block>\n      <Paragraph\n        textSize=\"7\"\n        textTransform=\"uppercase\"\n        textWeight=\"semibold\"\n        mb=\"1\"\n      >\n        Following\n      </Paragraph>\n      <Title as=\"p\">6789</Title>\n    </Block>\n  </Level.Item>\n  <Level.Item hasTextCentered>\n    <Block>\n      <Paragraph\n        textSize=\"7\"\n        textTransform=\"uppercase\"\n        textWeight=\"semibold\"\n        mb=\"1\"\n      >\n        Followers\n      </Paragraph>\n      <Title as=\"p\">123K</Title>\n    </Block>\n  </Level.Item>\n  <Level.Item hasTextCentered>\n    <Block>\n      <Paragraph\n        textSize=\"7\"\n        textTransform=\"uppercase\"\n        textWeight=\"semibold\"\n        mb=\"1\"\n      >\n        Likes\n      </Paragraph>\n      <Title as=\"p\">9876</Title>\n    </Block>\n  </Level.Item>\n</Level>"
+      "code": "<Level as=\"div\">\n  <Level.Item hasTextCentered>\n    <Block>\n      <Paragraph\n        textSize=\"7\"\n        textTransform=\"uppercase\"\n        textWeight=\"semibold\"\n        mb=\"1\"\n      >\n        Posts\n      </Paragraph>\n      <Title as=\"p\">1,234</Title>\n    </Block>\n  </Level.Item>\n  <Level.Item hasTextCentered>\n    <Block>\n      <Paragraph\n        textSize=\"7\"\n        textTransform=\"uppercase\"\n        textWeight=\"semibold\"\n        mb=\"1\"\n      >\n        Following\n      </Paragraph>\n      <Title as=\"p\">6,789</Title>\n    </Block>\n  </Level.Item>\n  <Level.Item hasTextCentered>\n    <Block>\n      <Paragraph\n        textSize=\"7\"\n        textTransform=\"uppercase\"\n        textWeight=\"semibold\"\n        mb=\"1\"\n      >\n        Followers\n      </Paragraph>\n      <Title as=\"p\">123K</Title>\n    </Block>\n  </Level.Item>\n  <Level.Item hasTextCentered>\n    <Block>\n      <Paragraph\n        textSize=\"7\"\n        textTransform=\"uppercase\"\n        textWeight=\"semibold\"\n        mb=\"1\"\n      >\n        Likes\n      </Paragraph>\n      <Title as=\"p\">9,876</Title>\n    </Block>\n  </Level.Item>\n</Level>"
     },
     {
       "title": "Centered Level Menu",
@@ -19,14 +19,14 @@
     },
     {
       "title": "Mobile Level",
-      "code": "<Level isMobile>\n  <Level.Item hasTextCentered>\n    <Block>\n      <Paragraph\n        textSize=\"7\"\n        textTransform=\"uppercase\"\n        textWeight=\"semibold\"\n        mb=\"1\"\n      >\n        Posts\n      </Paragraph>\n      <Title as=\"p\">1,234</Title>\n    </Block>\n  </Level.Item>\n  <Level.Item hasTextCentered>\n    <Block>\n      <Paragraph\n        textSize=\"7\"\n        textTransform=\"uppercase\"\n        textWeight=\"semibold\"\n        mb=\"1\"\n      >\n        Following\n      </Paragraph>\n      <Title as=\"p\">4567</Title>\n    </Block>\n  </Level.Item>\n  <Level.Item hasTextCentered>\n    <Block>\n      <Paragraph\n        textSize=\"7\"\n        textTransform=\"uppercase\"\n        textWeight=\"semibold\"\n        mb=\"1\"\n      >\n        Followers\n      </Paragraph>\n      <Title as=\"p\">123K</Title>\n    </Block>\n  </Level.Item>\n  <Level.Item hasTextCentered>\n    <Block>\n      <Paragraph\n        textSize=\"7\"\n        textTransform=\"uppercase\"\n        textWeight=\"semibold\"\n        mb=\"1\"\n      >\n        Likes\n      </Paragraph>\n      <Title as=\"p\">9876</Title>\n    </Block>\n  </Level.Item>\n</Level>"
+      "code": "<Level as=\"div\" isMobile>\n  <Level.Item hasTextCentered>\n    <Block>\n      <Paragraph\n        textSize=\"7\"\n        textTransform=\"uppercase\"\n        textWeight=\"semibold\"\n        mb=\"1\"\n      >\n        Posts\n      </Paragraph>\n      <Title as=\"p\">1,234</Title>\n    </Block>\n  </Level.Item>\n  <Level.Item hasTextCentered>\n    <Block>\n      <Paragraph\n        textSize=\"7\"\n        textTransform=\"uppercase\"\n        textWeight=\"semibold\"\n        mb=\"1\"\n      >\n        Following\n      </Paragraph>\n      <Title as=\"p\">4,567</Title>\n    </Block>\n  </Level.Item>\n  <Level.Item hasTextCentered>\n    <Block>\n      <Paragraph\n        textSize=\"7\"\n        textTransform=\"uppercase\"\n        textWeight=\"semibold\"\n        mb=\"1\"\n      >\n        Followers\n      </Paragraph>\n      <Title as=\"p\">123K</Title>\n    </Block>\n  </Level.Item>\n  <Level.Item hasTextCentered>\n    <Block>\n      <Paragraph\n        textSize=\"7\"\n        textTransform=\"uppercase\"\n        textWeight=\"semibold\"\n        mb=\"1\"\n      >\n        Likes\n      </Paragraph>\n      <Title as=\"p\">9,876</Title>\n    </Block>\n  </Level.Item>\n</Level>"
     },
     {
       "title": "Compound (dot-notation) usage",
       "code": "<Level>\n  <Level.Left>\n    <Level.Item>\n      <Title as=\"p\" size=\"5\">\n        <strong>All Posts</strong>\n      </Title>\n    </Level.Item>\n  </Level.Left>\n  <Level.Right>\n    <Level.Item as=\"p\">\n      <a>Published</a>\n    </Level.Item>\n    <Level.Item as=\"p\">\n      <Button color=\"success\" as=\"a\">\n        New\n      </Button>\n    </Level.Item>\n  </Level.Right>\n</Level>"
     }
   ],
-  "accessibility": "- The root `Level` renders as a semantic `<nav>` for grouping and navigation.\n- Items can be rendered as `<div>`, `<p>`, or `<a>`. Use `as=\"a\"` for links, and provide clear text or accessible labels.\n- Use Bulma helper props for spacing and color to improve contrast and readability.\n\n:::note\nFor best accessibility, use semantic elements for headings/content within items, and ensure interactive elements (like `Button` or links) are focusable and labeled.\n:::",
+  "accessibility": "- `Level` renders a `<nav>` by default, as Bulma's markup does. A `nav` is a navigation landmark, which a screen reader user can list and jump to, so keep it for a row of links. A row that isn't navigation, such as the statistics above, takes `as=\"div\"`, which adds no landmark. `as=\"header\"` suits a level that opens a section and `as=\"footer\"` one that closes it.\n- Items can be rendered as `<div>`, `<p>`, or `<a>`. Use `as=\"a\"` for links, and provide clear text or accessible labels.\n- Use Bulma helper props for spacing and color to improve contrast and readability.\n\n:::note\nFor best accessibility, use semantic elements for headings/content within items, and ensure interactive elements (like `Button` or links) are focusable and labeled.\n:::",
   "related": ["Button", "Field", "Input", "Title", "useBulmaClasses"],
   "storybook": "https://bestax.io/storybook/?path=/story/layout-level--default",
   "summary": "The `Level` component provides a flexible horizontal layout for your Bulma React UI, perfect for aligning items on the left and right, distributing items evenly, or centering statistics and controls.",
@@ -39,6 +39,15 @@
       "summary": "The `Level` component provides a flexible horizontal layout for your Bulma React UI, perfect for aligning items on the left and right, distributing items evenly, or centering statistics and controls.",
       "component": null,
       "props": [
+        {
+          "name": "as",
+          "type": "'nav' | 'div' | 'header' | 'footer'",
+          "default": "'nav'",
+          "description": "HTML element to render (default: `nav`, as in Bulma's markup). A `nav` is a `navigation` landmark, so keep it for a row of links. A row that is not navigation, such as figures or a toolbar, takes `div`, which is no landmark. `header` suits a level that opens a section and `footer` one that closes it. A `header` is a `banner` landmark, and a `footer` a `contentinfo` one, only when no `section`, `article`, `aside`, `nav` or `main` is around it.",
+          "required": false,
+          "inherited": false,
+          "deprecated": false
+        },
         {
           "name": "isMobile",
           "type": "boolean",

package/data/components/Modal.json

@@ -46,7 +46,7 @@
       "code": "function example() {\n  const [open, setOpen] = useState(false);\n  const closeModal = () => setOpen(false);\n\n  return (\n    <>\n      <Button color=\"success\" onClick={() => setOpen(true)}>\n        Show Modal\n      </Button>\n      <Modal\n        isActive={open}\n        onClose={closeModal}\n        aria-labelledby=\"custom-content-title\"\n      >\n        <Modal.Background onClick={closeModal} />\n        <Modal.Content>\n          <Box>\n            <Title size=\"4\" id=\"custom-content-title\">\n              Custom Content\n            </Title>\n            <Paragraph>Using compound components for full control!</Paragraph>\n          </Box>\n        </Modal.Content>\n        <Modal.Close variant=\"floating\" />\n      </Modal>\n    </>\n  );\n}"
     }
   ],
-  "accessibility": "- The modal root gets `role=\"dialog\"` and `aria-modal=\"true\"` while active — pass an explicit `role` to override (e.g. `Dialog` passes `role=\"presentation\"` on the `Modal` it wraps so its own `role=\"alertdialog\"` is the only one announced).\n- **Give the dialog an accessible name.** With the legacy API, `modalCardTitle` is wired up as `aria-labelledby` for you. With the compound API, pass your own `aria-label` or `aria-labelledby` on `<Modal>` — a `role=\"dialog\"` with no name is announced as just \"dialog\". An explicit `aria-labelledby` always wins over the generated one.\n- Escape closes the modal (calls `onClose`) by default; opt out with `closeOnEscape={false}`. One Escape closes the topmost overlay only, whichever open Modal, [Dialog](https://bestax.io/docs/api/components/dialog), [Sidebar](https://bestax.io/docs/api/components/sidebar) or full-page [Loading](https://bestax.io/docs/api/components/loading) opened last, and the next Escape closes the one under it. A modal on top with `closeOnEscape={false}` still keeps Escape from the layers under it. A [Toast](https://bestax.io/docs/api/components/toast) waits until no overlay is open.\n- The modal calls `preventDefault()` on the Escape it closes on, so a listener of your own that runs after it can tell the key was used.\n- A popup inside the modal takes its own Escape first. With an Autocomplete list, a Dropdown menu, a Popover or a date picker's calendar open, the first Escape closes that and the next one closes the modal.\n- A popup of your own inside a modal should call `preventDefault()` on the Escape it closes on. The modal leaves an Escape that was prevented alone, whether your popup hears it in a React `onKeyDown` or in a listener on `document`. Call it only when the popup is open and the key was pressed in it, so an Escape with nothing to close still closes the modal, and so does one pressed in a modal opened over your popup.\n- Body scroll is locked while the modal is active; opt out with `lockScroll={false}`. The lock is ref-counted and shared with `Dialog`, `Sidebar` and `Loading`, so whichever overlay closes first doesn't unlock the page underneath one that is still open.\n- Focus moves to the first tab stop (or the modal itself) on open, and is restored to the previously focused element on close — unless another modal is still open on top, in which case that one keeps focus.\n- Tab and Shift+Tab cycle within the modal while it is the topmost modal overlay, so the keyboard order agrees with what `aria-modal=\"true\"` tells assistive technology. They wrap at the same tab stops [`useFocusTrap`](https://bestax.io/docs/api/helpers/usefocustrap) does, so disabled, hidden and `tabIndex={-1}` elements are skipped, and so is inert content, such as a closed [Sidebar](https://bestax.io/docs/api/components/sidebar) inside the modal, and the content of a closed `<details>`. A radio group counts once. A Tab from outside the modal brings focus back in, and so does a Tab the browser takes out anyway, as Safari does past links when its settings say to. With another Modal or Dialog, a [Sidebar](https://bestax.io/docs/api/components/sidebar) with an overlay or a full-page Loading opened over it, the modal leaves Tab alone until that one closes. A Sidebar without an overlay isn't modal: opened over the modal, it takes Escape first, but the modal keeps holding Tab and keeps focus, so the sidebar doesn't take focus when it opens, and a Tab from its controls comes back into the modal. A focus trap of your own inside it, such as a portaled panel's, keeps a Tab it calls `preventDefault()` on, and the modal leaves focus where your trap put it. Note that `aria-modal` does not by itself make background content inert, and no `inert` attribute is applied, so background content remains reachable by pointer and by browser UI such as find-in-page.\n- In the props form, the background closes the modal on click, and a close button is provided for both modal-card and modal-content variants (both call `onClose`, so pass it).\n- In the compound form, `Modal.Close` calls the modal's `onClose` unless you give it an `onClick` of your own, and `Modal.Background` closes the modal only when you pass it `onClick={onClose}`.\n\n:::note\nAlways provide an `onClose` handler for accessibility and to allow users to dismiss the modal.\n:::",
+  "accessibility": "- The modal root gets `role=\"dialog\"` and `aria-modal=\"true\"` while active — pass an explicit `role` to override (e.g. `Dialog` passes `role=\"presentation\"` on the `Modal` it wraps so its own `role=\"alertdialog\"` is the only one announced).\n- **Give the dialog an accessible name.** With the legacy API, `modalCardTitle` is wired up as `aria-labelledby` for you. With the compound API, pass your own `aria-label` or `aria-labelledby` on `<Modal>` — a `role=\"dialog\"` with no name is announced as just \"dialog\". An explicit `aria-labelledby` always wins over the generated one.\n- Escape closes the modal (calls `onClose`) by default; opt out with `closeOnEscape={false}`. One Escape closes the topmost overlay only, whichever open Modal, [Dialog](https://bestax.io/docs/api/components/dialog), [Sidebar](https://bestax.io/docs/api/components/sidebar) or full-page [Loading](https://bestax.io/docs/api/components/loading) opened last, and the next Escape closes the one under it. A modal on top with `closeOnEscape={false}` still keeps Escape from the layers under it. A [Toast](https://bestax.io/docs/api/components/toast) waits until no overlay is open.\n- The modal calls `preventDefault()` on the Escape it closes on, so a listener of your own that runs after it can tell the key was used.\n- A popup inside the modal takes its own Escape first. With an Autocomplete list, a Dropdown menu, a Popover or a date picker's calendar open, the first Escape closes that and the next one closes the modal.\n- A popup of your own inside a modal should call `preventDefault()` on the Escape it closes on. The modal leaves an Escape that was prevented alone, whether your popup hears it in a React `onKeyDown` or in a listener on `document`. Call it only when the popup is open and the key was pressed in it, so an Escape with nothing to close still closes the modal, and so does one pressed in a modal opened over your popup.\n- The page doesn't scroll under the modal while it's active; opt out with `lockScroll={false}`. The lock is ref-counted and shared with `Dialog`, `Sidebar` and `Loading`, so whichever overlay closes first doesn't unlock the page underneath one that is still open.\n- Focus moves to the first tab stop (or the modal itself) on open, and is restored to the previously focused element on close — unless another modal is still open on top, in which case that one keeps focus.\n- Tab and Shift+Tab cycle within the modal while it is the topmost modal overlay, so the keyboard order agrees with what `aria-modal=\"true\"` tells assistive technology. They wrap at the same tab stops [`useFocusTrap`](https://bestax.io/docs/api/helpers/usefocustrap) does, so disabled, hidden and `tabIndex={-1}` elements are skipped, and so is inert content, such as a closed [Sidebar](https://bestax.io/docs/api/components/sidebar) inside the modal, and the content of a closed `<details>`. A radio group counts once. A Tab from outside the modal brings focus back in, and so does a Tab the browser takes out anyway, as Safari does past links when its settings say to. With another Modal or Dialog, a [Sidebar](https://bestax.io/docs/api/components/sidebar) with an overlay or a full-page Loading opened over it, the modal leaves Tab alone until that one closes. A Sidebar without an overlay isn't modal: opened over the modal, it takes Escape first, but the modal keeps holding Tab and keeps focus, so the sidebar doesn't take focus when it opens, and a Tab from its controls comes back into the modal. A focus trap of your own inside it, such as a portaled panel's, keeps a Tab it calls `preventDefault()` on, and the modal leaves focus where your trap put it. Note that `aria-modal` does not by itself make background content inert, and no `inert` attribute is applied, so background content remains reachable by pointer and by browser UI such as find-in-page.\n- In the props form, the background closes the modal on click, and a close button is provided for both modal-card and modal-content variants (both call `onClose`, so pass it).\n- In the compound form, `Modal.Close` calls the modal's `onClose` unless you give it an `onClick` of your own, and `Modal.Background` closes the modal only when you pass it `onClick={onClose}`.\n\n:::note\nAlways provide an `onClose` handler for accessibility and to allow users to dismiss the modal.\n:::",
   "related": [
     "Button",
     "Dialog",
@@ -171,7 +171,7 @@
           "name": "lockScroll",
           "type": "boolean",
           "default": "true",
-          "description": "Lock body scroll while the modal is active. Ref-counted and shared with `Dialog`, `Sidebar` and `Loading`, so whichever overlay closes first does not unlock the page underneath one that is still open.",
+          "description": "Lock page scroll while the modal is active, padding the page by the room its scrollbar took so the content stays put. An element fixed to the window's right edge, such as a `fixed` Navbar, isn't padded, and moves by the scrollbar's width while the page is locked. Ref-counted and shared with `Dialog`, `Sidebar` and `Loading`, so whichever overlay closes first does not unlock the page underneath one that is still open.",
           "required": false,
           "inherited": false,
           "deprecated": false

package/data/components/Navbar.json

@@ -82,7 +82,7 @@
       "code": "<Navbar>\n  <Navbar.Brand>\n    <Navbar.Item href=\"#\">\n      <img src=\"/img/logo.svg\" alt=\"Logo\" width=\"28\" height=\"28\" />\n    </Navbar.Item>\n    <Navbar.Burger aria-label=\"menu\" />\n  </Navbar.Brand>\n  <Navbar.Menu active>\n    <Navbar.Start>\n      <Navbar.Item href=\"#\">Home</Navbar.Item>\n      <Navbar.Item href=\"#\">Docs</Navbar.Item>\n    </Navbar.Start>\n    <Navbar.End>\n      <Navbar.Item href=\"#\">Log in</Navbar.Item>\n    </Navbar.End>\n  </Navbar.Menu>\n</Navbar>"
     }
   ],
-  "accessibility": "- The root `Navbar` renders as `<nav role=\"navigation\" aria-label=\"main navigation\">`.\n  The default accessible name is `main navigation`. A screen reader announces it with\n  the role, and since the name holds the role word, \"navigation\" is heard twice.\n  Pass a name without the role word (`aria-label=\"Site\"`), and a different name\n  on each Navbar when a page has more than one. A passed `aria-label` replaces\n  the default.\n- `Navbar.Item active` sets `aria-current=\"page\"` on the element `as` renders, the link by\n  default, so the current item isn't only a color. An `aria-current` you pass wins: a navbar of\n  sections on one page can say `\"location\"`, and `aria-current={false}` turns it off.\n- Use semantic links (`<a>`) and buttons, and provide clear `aria-label` and `aria-expanded` for the burger toggle.\n- `Navbar.Link` inside a `Navbar.Dropdown` automatically gets `aria-haspopup=\"true\"` and\n  `aria-expanded` synced to the dropdown's open state — no manual wiring required.\n  <kbd>Enter</kbd>/<kbd>Space</kbd> toggle the dropdown open/closed, and <kbd>Escape</kbd>\n  closes it and keeps focus on the link. When the trigger isn't interactive on its own — no\n  `href`, not `as=\"button\"`, and not a custom component — it also gets `role=\"button\"` and\n  `tabIndex={0}` so it's reachable and operable by keyboard, and a mouse/touch click on it\n  toggles the dropdown too (a caller-supplied `onClick` still runs, and can\n  `preventDefault()` to opt out).\n- A custom component passed to `as` keeps its own semantics, because a router link takes `to`\n  rather than `href` and so can't be recognised from the props it's given. If yours renders\n  something non-interactive instead, pass `role=\"button\"` and it takes the fallback above —\n  `tabIndex` and click included. The keyboard path is wired either way.\n- `hoverable` dropdowns keep working with a mouse (hover-to-open); the keyboard path above\n  opens and closes them independently of hover.\n\n:::note\nThere's no arrow-key roving between navbar items and no outside-click handling for\n`Navbar.Dropdown` — Bulma navbar dropdowns are hover/click surfaces, so this is intentionally\nkept simple.\n:::",
+  "accessibility": "- The root `Navbar` renders as `<nav role=\"navigation\" aria-label=\"main navigation\">`.\n  The default accessible name is `main navigation`. A screen reader announces it with\n  the role, and since the name holds the role word, \"navigation\" is heard twice.\n  Pass a name without the role word (`aria-label=\"Site\"`), and a different name\n  on each Navbar when a page has more than one. A passed `aria-label` replaces\n  the default.\n- `Navbar.Item active` sets `aria-current=\"page\"` on the element `as` renders, the link by\n  default, so the current item isn't only a color. An `aria-current` you pass wins: a navbar of\n  sections on one page can say `\"location\"`, and `aria-current={false}` turns it off.\n- Use semantic links (`<a>`) and buttons, and provide clear `aria-label` and `aria-expanded` for the burger toggle.\n- `Navbar.Link` inside a `Navbar.Dropdown` automatically gets `aria-haspopup=\"true\"` and\n  `aria-expanded` synced to the dropdown's open state — no manual wiring required.\n  <kbd>Enter</kbd>/<kbd>Space</kbd> toggle the dropdown open/closed, and <kbd>Escape</kbd>\n  closes it and keeps focus on the link. When the trigger isn't interactive on its own — no\n  `href`, not `as=\"button\"`, and not a custom component — it also gets `role=\"button\"` and\n  `tabIndex={0}` so it's reachable and operable by keyboard, and a mouse/touch click on it\n  toggles the dropdown too (a caller-supplied `onClick` still runs, and can\n  `preventDefault()` to opt out).\n- A custom component passed to `as` keeps its own semantics, because a router link takes `to`\n  rather than `href` and so can't be recognised from the props it's given. If yours renders\n  something non-interactive instead, pass `role=\"button\"` and it takes the fallback above —\n  `tabIndex` and click included. The keyboard path is wired either way.\n- `hoverable` dropdowns keep working with a mouse (hover-to-open); the keyboard path above\n  opens and closes them independently of hover.\n- **Forced colors:** Bulma draws the burger's bars as a background color, which forced colors\n  (Windows' contrast themes) replaces, so the burger would vanish there while it still works and\n  takes focus. bestax's styles keep its bars visible in the system's button text color. That rule\n  ships in `bestax.css` and `extras.css`, not in Bulma's own stylesheet, and an\n  [`AppFrame`](https://bestax.io/docs/api/layout/appframe)'s burger gets it too.\n\n:::note\nThere's no arrow-key roving between navbar items and no outside-click handling for\n`Navbar.Dropdown` — Bulma navbar dropdowns are hover/click surfaces, so this is intentionally\nkept simple.\n:::",
   "related": ["Button", "Icon", "useBulmaClasses"],
   "storybook": "https://bestax.io/storybook/?path=/story/components-navbar--default",
   "summary": "The `Navbar` component implements Bulma's powerful, responsive navigation bar for your Bulma React UI.",

package/data/components/Panel.json

@@ -185,7 +185,7 @@
       "props": [
         {
           "name": "name",
-          "type": "string | undefined",
+          "type": "string",
           "default": null,
           "description": "The icon name, with or without its library prefix (e.g. `'star'` or `'fa-star'`). Mutually exclusive with `children`.",
           "required": false,

package/data/components/Popover.json

@@ -118,7 +118,7 @@
           "name": "appendToBody",
           "type": "boolean",
           "default": "false",
-          "description": "Render the panel through `Portal`, into the `portalContainer` a `ConfigProvider` sets, `document.body` by default, fixed to the viewport, so an ancestor's `overflow`, `transform` or stacking context can't clip it. The panel then shows from the commit after hydration, never in server markup. It is measured against the trigger when it opens and on resize and scroll, so it doesn't follow content that changes size while it is open. Theming variables set on an ancestor of the trigger reach it only when its container is inside that ancestor.",
+          "description": "Render the panel through `Portal`, into the `portalContainer` a `ConfigProvider` sets, `document.body` by default, fixed to the viewport, so an ancestor's `overflow`, `transform` or stacking context can't clip it. The panel then shows from the commit after hydration, never in server markup. Theming variables set on an ancestor of the trigger reach it only when its container is inside that ancestor.",
           "required": false,
           "inherited": false,
           "deprecated": false

package/data/components/Radio.json

@@ -142,7 +142,7 @@
     {
       "css": "--bulma-radio-dot-color",
       "sass": "$radio-dot-color",
-      "default": "var(--bulma-scheme-main)",
+      "default": "var(--bulma-radio-active-color)",
       "scope": "root"
     },
     {

package/data/components/Sidebar.json

@@ -38,7 +38,7 @@
       "code": "function example() {\n  const [isOpen, setIsOpen] = useState(false);\n  return (\n    <>\n      <Button color=\"primary\" onClick={() => setIsOpen(true)}>\n        Open Sidebar\n      </Button>\n      <Sidebar inline isOpen={isOpen} onClose={() => setIsOpen(false)}>\n        <Sidebar.Header>\n          <Sidebar.Title>Dot Notation</Sidebar.Title>\n          <Sidebar.Close onClick={() => setIsOpen(false)} />\n        </Sidebar.Header>\n        <Sidebar.Body>\n          <Paragraph>\n            Header, Title, Close, Body, and Footer are all available from the\n            single Sidebar import.\n          </Paragraph>\n        </Sidebar.Body>\n        <Sidebar.Footer>\n          <Button color=\"primary\" onClick={() => setIsOpen(false)}>\n            Done\n          </Button>\n        </Sidebar.Footer>\n      </Sidebar>\n    </>\n  );\n}"
     }
   ],
-  "accessibility": "- Uses `role=\"dialog\"` for proper screen reader announcement\n- Has `aria-modal=\"true\"` when overlay is shown\n- Focus moves into the sidebar when it opens, to its first tab stop or the sidebar itself, unless it has no overlay and a modal overlay is open under it (see below). That's decided as it opens, so changing `overlay` while it's open leaves focus where it is. When it closes, focus goes back to whatever had it when the sidebar opened, unless focus has already left the sidebar, say for an overlay that's still open on top\n- With an overlay, Tab and Shift+Tab stay inside the sidebar while it's the topmost modal overlay, so the keyboard order agrees with what `aria-modal=\"true\"` tells assistive technology. They wrap at the same tab stops [`useFocusTrap`](https://bestax.io/docs/api/helpers/usefocustrap) does, so hidden, disabled and `tabIndex={-1}` elements are skipped and a radio group counts once. A Tab from outside the sidebar brings focus back in, and so does a Tab the browser takes out anyway, as Safari does past links when its settings say to\n- A [Modal](https://bestax.io/docs/api/components/modal) or [Dialog](https://bestax.io/docs/api/components/dialog) opened over the sidebar, including one rendered inside it, holds Tab until it closes, and then the sidebar holds it again. A sidebar with an overlay opened over a Modal holds Tab until it closes, and then the Modal does\n- A focus trap of your own inside the sidebar, such as a portaled panel's, keeps a Tab it calls `preventDefault()` on, and the sidebar leaves focus where your trap put it\n- Without an overlay the sidebar isn't modal and holds no Tab. On the page, Tab moves in and out of it freely. Opened over a Modal, or over a sidebar with an overlay, it takes Escape first, but the one under it keeps holding Tab and keeps focus: the sidebar doesn't take focus when it opens, and a Tab from its controls, once a click puts focus there, goes back into that one\n- A closed sidebar stays in the page so it can slide out, and it's `inert` and `aria-hidden` while closed: Tab passes over its content and assistive technology doesn't read it\n- Escape key closes the sidebar by default. One Escape closes the topmost overlay only: a [Modal](https://bestax.io/docs/api/components/modal) or [Dialog](https://bestax.io/docs/api/components/dialog) opened over the sidebar closes first, and the sidebar on the next Escape. A sidebar opened over a Modal closes before it\n- A sidebar on top that can't close on Escape, with `escapeClose` or `canCancel` off, still keeps the key from the overlays under it. A [Toast](https://bestax.io/docs/api/components/toast) waits until no overlay is open\n- A popup open inside it, such as a Dropdown menu or a date picker's calendar, takes the first Escape, and the next one closes the sidebar. A popup of your own does the same by calling `preventDefault()` on the Escape it closes on, as the [Modal](https://bestax.io/docs/api/components/modal#accessibility) page explains.\n- Body scroll is prevented when the sidebar is open with an overlay, through the ref-counted lock shared with `Modal`, `Dialog` and `Loading` — so closing one overlay never unlocks the page underneath another that is still open",
+  "accessibility": "- Uses `role=\"dialog\"` for proper screen reader announcement\n- Has `aria-modal=\"true\"` when overlay is shown\n- Focus moves into the sidebar when it opens, to its first tab stop or the sidebar itself, unless it has no overlay and a modal overlay is open under it (see below). That's decided as it opens, so changing `overlay` while it's open leaves focus where it is. When it closes, focus goes back to whatever had it when the sidebar opened, unless focus has already left the sidebar, say for an overlay that's still open on top\n- With an overlay, Tab and Shift+Tab stay inside the sidebar while it's the topmost modal overlay, so the keyboard order agrees with what `aria-modal=\"true\"` tells assistive technology. They wrap at the same tab stops [`useFocusTrap`](https://bestax.io/docs/api/helpers/usefocustrap) does, so hidden, disabled and `tabIndex={-1}` elements are skipped and a radio group counts once. A Tab from outside the sidebar brings focus back in, and so does a Tab the browser takes out anyway, as Safari does past links when its settings say to\n- A [Modal](https://bestax.io/docs/api/components/modal) or [Dialog](https://bestax.io/docs/api/components/dialog) opened over the sidebar, including one rendered inside it, holds Tab until it closes, and then the sidebar holds it again. A sidebar with an overlay opened over a Modal holds Tab until it closes, and then the Modal does\n- A focus trap of your own inside the sidebar, such as a portaled panel's, keeps a Tab it calls `preventDefault()` on, and the sidebar leaves focus where your trap put it\n- Without an overlay the sidebar isn't modal and holds no Tab. On the page, Tab moves in and out of it freely. Opened over a Modal, or over a sidebar with an overlay, it takes Escape first, but the one under it keeps holding Tab and keeps focus: the sidebar doesn't take focus when it opens, and a Tab from its controls, once a click puts focus there, goes back into that one\n- A closed sidebar stays in the page so it can slide out, and it's `inert` and `aria-hidden` while closed: Tab passes over its content and assistive technology doesn't read it\n- Escape key closes the sidebar by default. One Escape closes the topmost overlay only: a [Modal](https://bestax.io/docs/api/components/modal) or [Dialog](https://bestax.io/docs/api/components/dialog) opened over the sidebar closes first, and the sidebar on the next Escape. A sidebar opened over a Modal closes before it\n- A sidebar on top that can't close on Escape, with `escapeClose` or `canCancel` off, still keeps the key from the overlays under it. A [Toast](https://bestax.io/docs/api/components/toast) waits until no overlay is open\n- A popup open inside it, such as a Dropdown menu or a date picker's calendar, takes the first Escape, and the next one closes the sidebar. A popup of your own does the same by calling `preventDefault()` on the Escape it closes on, as the [Modal](https://bestax.io/docs/api/components/modal#accessibility) page explains.\n- The page doesn't scroll while the sidebar is open with an overlay, through the ref-counted lock shared with [`Modal`](https://bestax.io/docs/api/components/modal#accessibility), `Dialog` and `Loading`, so closing one overlay never unlocks the page underneath another that is still open",
   "related": ["Menu", "Modal"],
   "storybook": "https://bestax.io/storybook/?path=/story/components-sidebar",
   "summary": "The `Sidebar` component provides a slide-out navigation panel that appears from the left or right side of the screen.",
@@ -110,7 +110,7 @@
           "name": "overlay",
           "type": "boolean",
           "default": "true",
-          "description": "Show an overlay behind the sidebar, which makes it modal: it gets `aria-modal=\"true\"`, locks body scroll, and keeps Tab and Shift+Tab inside it while it is the topmost modal overlay. A Modal or Dialog opened over it, even one rendered inside it, holds Tab until it closes. Without an overlay the sidebar isn't modal and holds no Tab: on the page, Tab moves in and out of it freely, and opened over a Modal, it leaves the Modal holding Tab, and focus, while still taking Escape first. Whether the sidebar takes focus is decided as it opens: changing this while it's open moves the Tab trap, not focus. Default: true.",
+          "description": "Show an overlay behind the sidebar, which makes it modal: it gets `aria-modal=\"true\"`, locks page scroll, and keeps Tab and Shift+Tab inside it while it is the topmost modal overlay. A Modal or Dialog opened over it, even one rendered inside it, holds Tab until it closes. Without an overlay the sidebar isn't modal and holds no Tab: on the page, Tab moves in and out of it freely, and opened over a Modal, it leaves the Modal holding Tab, and focus, while still taking Escape first. Whether the sidebar takes focus is decided as it opens: changing this while it's open moves the Tab trap, not focus. Default: true.",
           "required": false,
           "inherited": false,
           "deprecated": false
@@ -155,7 +155,7 @@
           "name": "inline",
           "type": "boolean",
           "default": "false",
-          "description": "Renders inline instead of using a portal.",
+          "description": "Renders inline instead of using a portal. Without it, the sidebar renders inline on the server and while hydrating, moving into the portal once the client takes over, so hydration matches.",
           "required": false,
           "inherited": false,
           "deprecated": false

package/data/components/Slider.json

@@ -108,19 +108,19 @@
           "deprecated": false
         },
         {
-          "name": "minDistance",
-          "type": "number",
-          "default": "0",
-          "description": "Minimum distance between thumbs in range mode.",
+          "name": "ariaLabel",
+          "type": "string | [string, string]",
+          "default": null,
+          "description": "ARIA label(s) for the slider thumb(s), which win over a label, the Slider's own or a surrounding `Field`'s. In range mode each entry is that thumb's whole name, and a thumb without one is named \"Minimum value\" or \"Maximum value\", after whatever names the Slider: a label, or in its place an `aria-label` or `aria-labelledby` given to the Slider, as in \"Budget Minimum value\" and \"Budget Maximum value\". An `aria-labelledby` set to `undefined` keeps every label out of both names.",
           "required": false,
           "inherited": true,
           "deprecated": false
         },
         {
-          "name": "ariaLabel",
-          "type": "string | [string, string]",
-          "default": null,
-          "description": "ARIA label(s) for the slider thumb(s), which win over a label, the Slider's own or a surrounding `Field`'s. In range mode each entry is that thumb's whole name, and a thumb without one is named \"Minimum value\" or \"Maximum value\", after whatever names the Slider: a label, or in its place an `aria-label` or `aria-labelledby` given to the Slider, as in \"Budget Minimum value\" and \"Budget Maximum value\". An `aria-labelledby` set to `undefined` keeps every label out of both names.",
+          "name": "minDistance",
+          "type": "number",
+          "default": "0",
+          "description": "Minimum distance between thumbs in range mode.",
           "required": false,
           "inherited": true,
           "deprecated": false

package/data/components/Toast.json

@@ -195,7 +195,7 @@
           "name": "inline",
           "type": "boolean",
           "default": "false",
-          "description": "Renders inline instead of using a portal. Through `toast.show()`, a toast already renders inline in `ToastContainer`'s stack for its position, and `inline` keeps one with a `container` in that stack too.",
+          "description": "Renders inline instead of using a portal. Without it, a toast renders inline on the server and while hydrating, moving into the portal once the client takes over, so hydration matches. Through `toast.show()`, a toast already renders inline in `ToastContainer`'s stack for its position, and `inline` keeps one with a `container` in that stack too.",
           "required": false,
           "inherited": false,
           "deprecated": false

package/data/skills/bestax-custom-component/references/patterns.md

@@ -122,7 +122,8 @@ Dialog also shows optional patterns you can borrow when relevant:
 - An **imperative API** (`dialog.alert`, `dialog.confirm`, `dialog.close`) plus a
   `DialogContainer` for programmatic mounting, exported from the same module.
 - **Accessibility**: `role="alertdialog"`, Escape-to-cancel, and focus management on open.
-- **Body scroll lock** via a module-level ref count so chained/overlapping dialogs behave.
+- **Page scroll lock** through the `Modal` it renders, whose lock is ref-counted so
+  chained/overlapping dialogs behave.
 
 These are not required for every component — start from the simple template in
 `library-contributor.md` and add only what your component needs.

package/data/skills/bestax-form/references/api.md

@@ -212,7 +212,9 @@ does a picker given its own `dayNames`, which it shows exactly as given: pass `f
 them and list them from that day. With
 server rendering, set a locale: without one, an `inline` calendar names its days in the server's
 language on the server and the reader's in the browser, and hydration fails to match whenever
-the two languages differ.
+the two languages differ. Give an `inline` picker a `value` or `defaultValue` there too: without
+one it opens on the month the clock reads, and the server's clock and the reader's can read
+different months.
 
 ```tsx
 <LocaleProvider locale="de">

package/data/skills/bestax-layout-scaffold/references/layout-components.md

@@ -128,11 +128,16 @@ back to. A header taller than Bulma's navbar sets
 `<Level>` is a horizontal toolbar (left/right groups). Subcomponents: `Level.Left`, `Level.Right`,
 `Level.Item`.
 
-| Prop                         | Type                                  |
-| ---------------------------- | ------------------------------------- |
-| `Level.isMobile`             | `boolean` (keep horizontal on mobile) |
-| `Level.Item.as`              | `'div' \| 'p' \| 'a'`                 |
-| `Level.Item.hasTextCentered` | `boolean`                             |
+| Prop                         | Type                                                     |
+| ---------------------------- | -------------------------------------------------------- |
+| `Level.as`                   | `'nav'` (default) \| `'div'` \| `'header'` \| `'footer'` |
+| `Level.isMobile`             | `boolean` (keep horizontal on mobile)                    |
+| `Level.Item.as`              | `'div' \| 'p' \| 'a'`                                    |
+| `Level.Item.hasTextCentered` | `boolean`                                                |
+
+A `nav` is a navigation landmark, so keep the default for a row of links. A row that isn't
+navigation takes `as="div"`, or `as="header"` when it opens a section and `as="footer"` when it
+closes one. A dashboard's row of key figures is `Stats`, not a `Level`.
 
 ## Stack / Group / Center / Flex
 

package/data/skills/bestax-migrate/references/bloomer/prop-map.md

@@ -118,7 +118,7 @@ bloomer put `tag` on nearly every component; bestax declares `as` on a subset, s
 narrowed to a literal union, so a value outside the union is a type error you can see rather
 than a silent rewrite. The components whose `tag` becomes `as`:
 
-`Button`, `Image`, `Title`, `Subtitle`, `Footer`, `Media`, `MediaLeft`, `LevelItem`, `Control`,
+`Button`, `Image`, `Title`, `Subtitle`, `Footer`, `Media`, `MediaLeft`, `Level`, `LevelItem`, `Control`,
 `DropdownItem`, `MenuLink`, `NavbarItem`, `NavbarLink`, `Container`, `Hero`, `HeroHeader`,
 `HeroFooter`, `Panel`.
 

package/data/skills/bestax-migrate/references/bulma-classes/component-map.md

@@ -60,7 +60,7 @@ a `tag:<Target>` TODO instead of a conversion. A component's own `as` can take m
 | `.hero-head`           | `Hero.Head`           | `<div>`, `<header>`, `<nav>` via `as`                                                            |
 | `.hero-body`           | `Hero.Body`           | `<div>` only                                                                                     |
 | `.hero-foot`           | `Hero.Foot`           | `<div>`, `<footer>`, `<nav>` via `as`                                                            |
-| `.level`               | `Level`               | `<nav>` only                                                                                     |
+| `.level`               | `Level`               | `<nav>`, `<div>`, `<header>`, `<footer>` via `as`                                                |
 | `.level-left`          | `Level.Left`          | `<div>` only                                                                                     |
 | `.level-right`         | `Level.Right`         | `<div>` only                                                                                     |
 | `.level-item`          | `Level.Item`          | `<div>`, `<p>`, `<a>` via `as`                                                                   |

package/data/skills/bestax-migrate/references/rbx/prop-map.md

@@ -96,6 +96,7 @@ everywhere else:
 | `Footer`                     | `'footer' \| 'div'`                                                                     |
 | `Media`                      | `'article' \| 'div'`                                                                    |
 | `Media.Left`                 | `'figure' \| 'div'`                                                                     |
+| `Level`                      | `'nav' \| 'div' \| 'header' \| 'footer'`                                                |
 | `Level.Item`                 | `'div' \| 'p' \| 'a'`                                                                   |
 | `Control`                    | `'div' \| 'p'`                                                                          |
 | `Menu.Item`                  | any element type                                                                        |

package/data/skills/bestax-migrate/references/react-bulma-components/prop-map.md

@@ -32,7 +32,7 @@ this automatically for literal values; dynamic values get TODOs.
 ## `renderAs` → `as`, and the props that follow it
 
 `renderAs` becomes `as` on the components bestax declares one on: `Button`, `Title` and
-`SubTitle` (from `Heading`), `Image`, `Form.Control`, `Footer`, `Level.Item`, `Media` and its
+`SubTitle` (from `Heading`), `Image`, `Form.Control`, `Footer`, `Level`, `Level.Item`, `Media` and its
 `Item`s, `Menu.Item`, `Navbar.Item`, `Navbar.Link`, `Dropdown.Item`, `Container`, `Hero`,
 `Hero.Header`, `Hero.Footer`, `Panel` and `Panel.Block`. Everywhere else it is flagged.
 

package/data/skills/bestax-optimize/SKILL.md

@@ -104,7 +104,7 @@ Create `src/styles.scss` — base + themes always come first:
 
 // One line per stock Bulma component the app imports…
 @use 'bulma/sass/elements/button';
-@use 'bulma/sass/components/navbar';
+@use 'bulma/sass/components/card';
 // …and per bestax extras component:
 @use '@allxsmith/bestax-bulma/scss/components/dialog';
 // …and bestax's partial for a stock component that has one:

package/data/skills/bestax-optimize/references/modular-build.md

@@ -46,7 +46,7 @@ publishes its SCSS sources (`src/scss` ships in the npm package, exposed via the
 
 **Rule:** stock Bulma components map to `bulma/sass/<category>/<lowercased-name>`; bestax
 extras map to `@allxsmith/bestax-bulma/scss/<category>/<lowercased-name>`. Components that
-are pure stock Bulma (Box, Card, Navbar, Modal, Hero, …) have **no** extras partial —
+are pure stock Bulma (Box, Card, Modal, Hero, …) have **no** extras partial —
 Bulma's own module is all they need.
 
 Bulma groups its form controls, so their modules don't follow the name: `Input` and `TextArea`
@@ -82,7 +82,7 @@ is **more complete** than the docs page's Option C example, which omits several)
 `loading`, `collapse`, `tooltip`, `popover`, `hovercard`, `contextmenu`, `steps`, `sidebar`,
 `toast`, `dialog`, `carousel`, `lightbox`, `tabs`, `menu`, `tableofcontents`, `reveal`, `avatar`, `avatars`,
 `badge`, `emptystate`, `timeline`, `treeview`, `scrollarea`, `command`, `datatable`,
-`pagination`, `affix`
+`pagination`, `affix`, `navbar`
 
 **Layout** (`@allxsmith/bestax-bulma/scss/layout/<name>`): `appframe`, `splitter`, `stack`
 
@@ -135,6 +135,16 @@ Notes:
   @use '@allxsmith/bestax-bulma/scss/components/pagination' as bestax-pagination;
   ```
 
+- The `navbar` partial **extends** stock Bulma navbar (it keeps the burger's bars in
+  ButtonText in forced colors, where Chromium paints them in the page's Canvas color), so an
+  app using `Navbar` needs both, in either order. `AppFrame.Burger` renders `Navbar.Burger`,
+  so a build with one wants this partial too:
+
+  ```scss
+  @use 'bulma/sass/components/navbar';
+  @use '@allxsmith/bestax-bulma/scss/components/navbar' as bestax-navbar;
+  ```
+
 - The `file` partial **extends** stock Bulma file (File's keyboard focus ring, and the rounded
   corners of a boxed `hasName` File with no name to show), so an app using `File` needs both, in
   either order:
@@ -213,12 +223,15 @@ Notes:
   so its text clears the button, so include it (`as bestax-notification`) next to the Bulma
   module in any build that shows a dismissible notification. It doesn't depend on the order of
   the two `@use` lines either.
-- `Delete` is stock Bulma too (`bulma/sass/elements/delete`), and it's the close button of
-  `Notification`, `Message`, `Toast`, a `Modal` card, `AppFrame`'s drawer and the tags of
-  `Taginput`, `Combobox` and `Dropzone`. Bulma draws its circle and cross as background colors, which forced colors
-  (Windows' contrast themes) replaces, so they vanish there. The `delete` extras partial keeps
-  them drawn in the system's button colors, and the `Modal`'s floating close
-  (`bulma/sass/components/modal`) and `Tag isDelete` (`bulma/sass/elements/tag`) with them, so
+- `Delete` is stock Bulma too, and it's the close button of `Notification`, `Message`, `Toast`, a
+  `Modal` card, `AppFrame`'s drawer and the tags of `Taginput`, `Combobox`, `Dropzone` and
+  `TreeSelect`. Bulma draws it in `bulma/sass/elements/delete`, and the modules of the components
+  it sits in don't, so a build that shows one needs that module next to theirs. Without it the
+  button doesn't show, though it still takes keyboard focus. The `Modal`'s floating close is the
+  exception, since `bulma/sass/components/modal` draws that one itself. Bulma draws the circle and
+  cross as background colors, which forced colors (Windows' contrast themes) replaces, so they
+  vanish there. The `delete` extras partial keeps them drawn in the system's button colors, and
+  the `Modal`'s floating close and `Tag isDelete` (`bulma/sass/elements/tag`) with them, so
   include it (`as bestax-delete`) in any build that shows a close button. Its rules win over
   Bulma's either way, so the order of the `@use` lines does not matter.
 - `Button` is stock Bulma too (`bulma/sass/elements/button`). Bulma shows a focused button with
@@ -245,9 +258,9 @@ Notes:
 
 - Stock-Bulma form controls still need their Bulma module (`bulma/sass/form/…`); the extras
   form partials above style only the bestax-specific behavior.
-- Bulma component modules pull their own internal sub-elements — e.g.
-  `elements/notification` styles its `delete` close button itself (verified). No extra
-  `@use` lines are needed for pieces rendered _inside_ a component you've already included.
+- Bulma's module for a component doesn't always style what bestax renders inside it. A close
+  button is the common case: it needs `bulma/sass/elements/delete` and the `delete` partial, as
+  the `Delete` note above says.
 
 ## Bulma helper categories
 

package/data/skills/bestax-theming/references/css-variables.md

@@ -820,7 +820,8 @@ As with Checkbox, set these on a class you pass through `className`, with both c
 selector (`.styled-radio.my-radio`): `style` goes to the hidden `<input>`. A `color` prop
 declares `--bulma-radio-active-color` again on `.styled-radio.is-<color>`, which ties that
 selector, so leave `color` unset when a class sets it. The unchecked ring, `--bulma-radio-border-color`, defaults to `text-weak` for the same 3:1 boundary
-contrast.
+contrast. The checked dot, `--bulma-radio-dot-color`, defaults to `--bulma-radio-active-color`,
+so it follows the ring and a `color` prop until a class gives it a color of its own.
 
 `--bulma-radio-size` (default `1.25em`) can't take the circle below 24px: the stylesheet gives the
 `.check` circle a `min-width` and `min-height` of 24px, WCAG 2.2's minimum target size, so with

package/data/skills.json

@@ -17,7 +17,7 @@
           "file": "references/library-contributor.md",
           "bytes": 23311
         },
-        { "id": "patterns", "file": "references/patterns.md", "bytes": 4601 }
+        { "id": "patterns", "file": "references/patterns.md", "bytes": 4632 }
       ],
       "examples": [
         { "id": "stat-card", "file": "examples/stat-card.tsx", "bytes": 3734 }
@@ -29,7 +29,7 @@
       "promptName": "form",
       "dir": "bestax-form",
       "references": [
-        { "id": "api", "file": "references/api.md", "bytes": 32997 },
+        { "id": "api", "file": "references/api.md", "bytes": 33178 },
         { "id": "patterns", "file": "references/patterns.md", "bytes": 10001 }
       ],
       "examples": []
@@ -64,7 +64,7 @@
         {
           "id": "layout-components",
           "file": "references/layout-components.md",
-          "bytes": 25314
+          "bytes": 25761
         }
       ],
       "examples": [
@@ -93,7 +93,7 @@
         {
           "id": "bloomer-prop-map",
           "file": "references/bloomer/prop-map.md",
-          "bytes": 27249
+          "bytes": 27258
         },
         {
           "id": "bloomer-unmappables",
@@ -128,7 +128,7 @@
         {
           "id": "rbx-prop-map",
           "file": "references/rbx/prop-map.md",
-          "bytes": 16090
+          "bytes": 16213
         },
         {
           "id": "rbx-unmappables",
@@ -143,7 +143,7 @@
         {
           "id": "react-bulma-components-prop-map",
           "file": "references/react-bulma-components/prop-map.md",
-          "bytes": 8367
+          "bytes": 8376
         },
         {
           "id": "react-bulma-components-unmappables",
@@ -162,7 +162,7 @@
         {
           "id": "modular-build",
           "file": "references/modular-build.md",
-          "bytes": 18954
+          "bytes": 19671
         }
       ],
       "examples": []
@@ -176,7 +176,7 @@
         {
           "id": "css-variables",
           "file": "references/css-variables.md",
-          "bytes": 71903
+          "bytes": 72074
         },
         {
           "id": "themeable-components",

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "bestax-mcp",
-  "version": "1.18.35",
+  "version": "1.18.37",
   "mcpName": "io.github.allxsmith/bestax-mcp",
   "description": "MCP server for @allxsmith/bestax-bulma — component props, examples, CSS variables and agent skills, served offline from a version-pinned index",
   "type": "module",
@@ -42,7 +42,7 @@
   "dependencies": {
     "@modelcontextprotocol/sdk": "^1.32.2",
     "zod": "^4.6.7",
-    "@allxsmith/bestax-bulma": "^5.66.1"
+    "@allxsmith/bestax-bulma": "^5.67.0"
   },
   "devDependencies": {
     "@types/node": "^26.6.6",