bestax-mcp 1.18.35 → 1.18.36

package/data/catalog.json

@@ -2,7 +2,7 @@
   "schemaVersion": 2,
   "generatedFrom": {
     "package": "@allxsmith/bestax-bulma",
-    "version": "5.66.1"
+    "version": "5.66.2"
   },
   "docsBase": "https://bestax.io/docs",
   "categories": [

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/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/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:

package/data/skills.json

@@ -162,7 +162,7 @@
         {
           "id": "modular-build",
           "file": "references/modular-build.md",
-          "bytes": 18954
+          "bytes": 19404
         }
       ],
       "examples": []

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "bestax-mcp",
-  "version": "1.18.35",
+  "version": "1.18.36",
   "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.66.2"
   },
   "devDependencies": {
     "@types/node": "^26.6.6",