bitboss-ui 3.0.0-beta.0 → 3.0.0-beta.2

package/dist/llms-medium.txt

@@ -5,16 +5,16 @@
 > how to choose a component, and the design language — plus a catalogue
 > of every public component.
 
-Canonical URL: https://cdn.jsdelivr.net/npm/bitboss-ui@alpha/dist/llms-medium.txt
+Canonical URL: https://cdn.jsdelivr.net/npm/bitboss-ui@beta/dist/llms-medium.txt
 
 Need more? Fetch the specific component contract you need — one hop, not
-the whole catalogue: https://cdn.jsdelivr.net/npm/bitboss-ui@alpha/dist/ai/<ComponentName>.md
-Machine-readable API surface: https://cdn.jsdelivr.net/npm/bitboss-ui@alpha/dist/ai/components.json
+the whole catalogue: https://cdn.jsdelivr.net/npm/bitboss-ui@beta/dist/ai/<ComponentName>.md
+Machine-readable API surface: https://cdn.jsdelivr.net/npm/bitboss-ui@beta/dist/ai/components.json
 
 ---
 
 <!-- dist/ai/guides/ai-router.md -->
-<!-- https://cdn.jsdelivr.net/npm/bitboss-ui@alpha/dist/ai/guides/ai-router.md -->
+<!-- https://cdn.jsdelivr.net/npm/bitboss-ui@beta/dist/ai/guides/ai-router.md -->
 
 # AI Router
 
@@ -28,9 +28,9 @@ Package export entry: `bitboss-ui/ai` → `dist/ai/index.md`.
 Subpaths: `bitboss-ui/ai/components.json`, `bitboss-ui/ai/guides/…`, etc.
 
 **Not installed, or can only fetch URLs?** The same files are served from the
-published package at `https://cdn.jsdelivr.net/npm/bitboss-ui@alpha/dist/ai/…`.
+published package at `https://cdn.jsdelivr.net/npm/bitboss-ui@beta/dist/ai/…`.
 If you can make only one request, fetch
-[`…@alpha/dist/llms-medium.txt`](https://cdn.jsdelivr.net/npm/bitboss-ui@alpha/dist/llms-medium.txt)
+[`…@beta/dist/llms-medium.txt`](https://cdn.jsdelivr.net/npm/bitboss-ui@beta/dist/llms-medium.txt)
 — this router plus the agent contract, setup, component picker, design language
 and the full component catalogue, in ~110 KB.
 
@@ -133,7 +133,7 @@ nothing else); the command names them if they are missing.
 ---
 
 <!-- dist/ai/guides/agent-contract.md -->
-<!-- https://cdn.jsdelivr.net/npm/bitboss-ui@alpha/dist/ai/guides/agent-contract.md -->
+<!-- https://cdn.jsdelivr.net/npm/bitboss-ui@beta/dist/ai/guides/agent-contract.md -->
 
 # Agent Contract
 
@@ -391,7 +391,7 @@ case is not decidable from markup and has no hint.
 ---
 
 <!-- dist/ai/guides/installation-and-plugin-setup.md -->
-<!-- https://cdn.jsdelivr.net/npm/bitboss-ui@alpha/dist/ai/guides/installation-and-plugin-setup.md -->
+<!-- https://cdn.jsdelivr.net/npm/bitboss-ui@beta/dist/ai/guides/installation-and-plugin-setup.md -->
 
 # Installation and Plugin Setup
 
@@ -403,16 +403,21 @@ Source of truth for integrating `bitboss-ui`. Two pieces are always required:
 ## 1) Install
 
 ```bash
-# v3 is a prerelease — the `@alpha` tag is REQUIRED.
+# v3 is a prerelease — a dist-tag is REQUIRED.
 # A bare `npm install bitboss-ui` still resolves to v2, which has no build
 # plugin and no `dist/ai` knowledge base, so everything below silently fails.
-npm install bitboss-ui@alpha
+npm install bitboss-ui@beta
 # recommended default icon set (any @iconify-json/* works)
 npm install -D @iconify-json/lucide
 ```
 
 Confirm you got v3 before continuing — `npm ls bitboss-ui` must report a
-`3.0.0-alpha.*` version. If it reports `2.x`, nothing in this guide applies.
+`3.0.0-*` version. If it reports `2.x`, nothing in this guide applies.
+
+**`@beta` is the current v3 channel.** `@alpha` still resolves, but it is
+frozen at the last alpha and does not receive fixes — it is not simply an older
+copy of the same line. `@latest` is the **v2** line and always will be until v3
+goes stable, so never reach for it here.
 
 Peer dependency: `vue ^3.5.12` — the only required one. `@inertiajs/vue3` is an **optional** peer, needed only in Inertia apps.
 
@@ -609,6 +614,48 @@ import 'bitboss-ui/styles.css';
 import 'bitboss-ui/reset.css';
 ```
 
+**Exception — an app that needs its own CSS to load _before_ the library.**
+Auto-injection is library-first and not configurable: the runtime plugin
+inserts its `<style>` **before the first** `style`/`link[rel="stylesheet"]`
+already in `<head>` (`src/utils/injectLibraryStyles.ts`), so the guaranteed
+order above is exactly what you get and every app stylesheet — your Tailwind
+entry included — lands after the library. There is no option to inject later.
+
+That is the order most apps want. It is the wrong order if you need library
+rules to beat Tailwind's Preflight **by source order**, which is the case on
+**Tailwind v3**: `@tailwind base` compiles to ordinary unlayered CSS, so under
+auto-injection Preflight sits after the library sheet and its element resets
+(`button`, `input`, `h1`, …) win every equal-specificity tie. `injectStyles:
+false` + `resetCss: false` (the default) disables injection entirely and hands
+you the order:
+
+```ts
+// vite.config.ts / the `bitboss` key in nuxt.config.ts
+bitbossUi({ iconDir: '…', injectStyles: false, resetCss: false });
+```
+
+```ts
+// app entry — order is yours now
+import './app.css'; // your Tailwind entry
+import 'bitboss-ui/styles.css'; // after Tailwind, so library rules win the ties
+```
+
+Leave `resetCss` at `false` here — Preflight already reset everything.
+Nothing else about the plugin changes; `injectStyles` controls only whether the
+library injects its own `<style>`.
+
+**Tailwind v4 apps do not need this** — source order does not decide their ties
+at all. `@import 'tailwindcss'` puts Preflight in a real `@layer base` and
+utilities in `@layer utilities`, and layered rules lose to unlayered rules of
+equal specificity **regardless of source order**. `dist/styles.css` declares no
+`@layer`, so the library wins those ties wherever it is injected: leave
+auto-injection on. The same mechanic bites the other way, and silently — a
+utility cannot re-size a Bb component either. `<BbButton class="h-12 px-6">`
+loses to the library's own `.bb-button { height: var(--h); padding-left:
+var(--px); padding-right: var(--px) }` (equal specificity, unlayered), with no
+warning from anything. Size Bb components through their props and tokens, never
+utilities. (Same trap as the scoped-`<style>` case above, one level up.)
+
 ## 6) Icons
 
 - `iconDir` (required) is scanned recursively for `.svg` files; each file becomes `local:<basename>`.
@@ -650,6 +697,15 @@ When `true`, the **dev server** adds `./node_modules/.bitboss-ui/local-icons.jso
 
 When `true`, the **dev server** registers the bitboss-ui MCP server in each project-scoped agent-harness config on boot — `.mcp.json` (Claude Code), `.cursor/mcp.json` (Cursor), and `.vscode/mcp.json` (VS Code / Copilot) — so agents can query the knowledge base with no manual setup. The write is merge-safe (leaves other servers alone) and idempotent (only logs when it actually changes a file). Windsurf is intentionally **not** written here: its config is global (`~/.codeium`), and silently editing a home-dir file that affects every project on the machine from a dev-server boot would be surprising — run `npx bitboss-ui ai-init --mcp` to register Windsurf too. This flag is the zero-command equivalent of that command's project-scoped writes. The MCP server's own runtime — `@modelcontextprotocol/sdk` and `zod` — ships as **optional peer dependencies** (~12 MB, more than every runtime dependency of the library combined, and loaded by nothing else), so install them with `npm i -D @modelcontextprotocol/sdk zod` before the harness first launches the server; both this flag and `ai-init --mcp` warn when they are missing.
 
+**MCP is a convenience, not a requirement, and skipping it costs no
+knowledge.** The server is a reader over files the install already put on disk
+— every tool `readFileSync`s out of `node_modules/bitboss-ui/dist/ai/` (plus
+`dist/styles.css` for the token lookup). An agent that opens that directory
+itself has the identical knowledge base, `npx bitboss-ui check` runs without the
+peers, and `ai-init` (no `--mcp`) still writes the harness pointers. If you are
+migrating under a "no new dependencies" constraint, leave `mcp` at `false`,
+skip `--mcp`, and point your agent at `dist/ai/guides/ai-router.md`.
+
 ### `inertiaLinkName?: string` (default: `'Link'`)
 
 Global component name used for Inertia links. **Optional** — when nothing is
@@ -828,7 +884,17 @@ than inventing hues.
 
 The package ships its agent docs in `node_modules/bitboss-ui/dist/ai/`. **Start at** `guides/ai-router.md`, then the catalogue `index.md`. Run `npx bitboss-ui ai-init` in the consumer project to inject harness-agnostic pointers (AGENTS.md, Cursor rules, Copilot instructions, Claude skill, Windsurf rules) so coding agents discover them without a vendor lock-in. After generating Bb\* markup, run `npx bitboss-ui check` (supports `--json`) so unknown props fail before review.
 
-Add `--mcp` to also register a live MCP server (`npx bitboss-ui@<installed version> mcp`, pinned so npx can never fetch a different version from the registry) the harness launches on demand — it merges the entry (never overwriting other servers) into `.mcp.json` (Claude Code), `.cursor/mcp.json` (Cursor), `.vscode/mcp.json` (VS Code / Copilot), and `~/.codeium/windsurf/mcp_config.json` (Windsurf). **Windsurf's config is global** — it has no per-project scope, so registering it affects every project on the machine; that is why only the explicit `ai-init --mcp` command writes it, while the plugin's `mcp: true` dev-server flag (§7) auto-registers the project-scoped harnesses only. Install the server's optional peers first — `npm i -D @modelcontextprotocol/sdk zod` — they are not dependencies of the library (~12 MB used only by the MCP server); the command warns if they are absent.
+**Three tiers ship under `dist/ai/`**, and the third one is easy to miss:
+`guides/` + `recipes/` are the authored prose; `<Name>.md` at the root is the
+generated typed contract for each component (props, slots, events, examples);
+`source/<Name>.md` is that same component's **complete implementation** —
+`.vue` template, `types.ts` and `index.css` in one file, one per component
+including the internal ones the package does not export. Read the source tier
+when the contract cannot answer the question — the usual case is rebuilding
+chrome around a control the library does not ship, since the class names such a
+template emits are already styled by the public `bitboss-ui/styles.css`.
+
+Add `--mcp` to also register a live MCP server (`npx bitboss-ui@<installed version> mcp`, pinned so npx can never fetch a different version from the registry) the harness launches on demand — it merges the entry (never overwriting other servers) into `.mcp.json` (Claude Code), `.cursor/mcp.json` (Cursor), `.vscode/mcp.json` (VS Code / Copilot), and `~/.codeium/windsurf/mcp_config.json` (Windsurf). **Windsurf's config is global** — it has no per-project scope, so registering it affects every project on the machine; that is why only the explicit `ai-init --mcp` command writes it, while the plugin's `mcp: true` dev-server flag (§7) auto-registers the project-scoped harnesses only. Install the server's optional peers first — `npm i -D @modelcontextprotocol/sdk zod` — they are not dependencies of the library (~12 MB used only by the MCP server); the command warns if they are absent. **`--mcp` is optional and skipping it loses you nothing but the transport** — the server only reads the `dist/ai/` files listed above, so run plain `ai-init` and let the agent read that directory if you cannot add the peers (see `mcp?: boolean` in §7).
 
 For a human-in-the-loop (and agent) safety net, add the `bitboss-ui/eslint-plugin` flat-config plugin (`...bitbossUi.configs.recommended`) so unknown/removed `Bb*` props surface as ESLint errors in the editor and CI — the same manifest checks as `bitboss-ui check`, reusing your `eslint-plugin-vue` parser. Real HTML attributes fall through untouched; escape hatches are the standard `<!-- eslint-disable-next-line bitboss-ui/no-unknown-attributes -->` and the rule's `allowAttributes` / `allowComponents` options. **`eslint --fix` also auto-migrates deprecated v2 props** (renames, boolean-polarity inversions like `allowWriting`→`disableWriting`, value remaps like BbToast `placement`→`position`, and deletion of inert removed props); structural migrations that need a slot/directive/CSS are reported but left by hand. **This library is TS-first (recipes ship `<script setup lang="ts">`, some with `generic="T"`), so wire `@typescript-eslint/parser` for both `.ts` and `.vue` files** — without it `vue-eslint-parser` throws a `Parsing error` on those files, which means no rule (including `no-unknown-attributes`) runs on them at all. See the README "ESLint plugin" section for the full config snippet (both parser blocks + the `npm i -D @typescript-eslint/parser` line) and the fix table. `recommended` also enables `bitboss-ui/no-active-class-on-root-link`: `active-class` on a link-capable `Bb*` component (`BbButton`/`BbBaseButton`/`BbBadgeButton`) matches by path PREFIX, so a link whose target is the literal root (`href="/"` / `to="/"`) reads as "active" on every URL — the rule flags that combination and points you at `exact-active-class` instead.
 
@@ -848,7 +914,7 @@ It also enables `bitboss-ui/require-partner-prop`: an opt-in prop set without it
 - [ ] build plugin configured: `bitboss-ui/vite` plugin or `bitboss-ui/nuxt` module (`bitboss` config key);
 - [ ] `iconDir` points at an existing SVG folder;
 - [ ] runtime plugin installed: `app.use(bitbossUiPlugin)` (automatic in Nuxt);
-- [ ] style strategy chosen: auto injection (default) or `injectStyles: false` + `import 'bitboss-ui/styles.css'`;
+- [ ] style strategy chosen: auto injection (default) or `injectStyles: false` + `import 'bitboss-ui/styles.css'` — auto injection is always library-first, so a Tailwind **v3** app that needs Preflight to load before the library must take the second option (§5);
 - [ ] if a reset is required: `resetCss: true` or `import 'bitboss-ui/reset.css'`;
 - [ ] Inertia apps: `@inertiajs/vue3` installed (no link registration needed; set `inertiaLinkName` only if you register your own link wrapper).
 - [ ] building the [Layout Scaffold](../recipes/vue/layout-scaffold.md)? `npm i @vueuse/core` — `usePageShellContext.ts` imports `injectLocal`/`provideLocal` from it. This library depends on it too, so it can resolve via hoisting without being declared — don't rely on that; declare it in your own `package.json` or a strict installer (pnpm, Yarn PnP) will fail to resolve it.
@@ -861,7 +927,7 @@ If one of the checks fails, fix setup before creating component examples.
 ---
 
 <!-- dist/ai/guides/component-picker.md -->
-<!-- https://cdn.jsdelivr.net/npm/bitboss-ui@alpha/dist/ai/guides/component-picker.md -->
+<!-- https://cdn.jsdelivr.net/npm/bitboss-ui@beta/dist/ai/guides/component-picker.md -->
 
 # Component Picker
 
@@ -1136,7 +1202,7 @@ See:
 ---
 
 <!-- dist/ai/guides/design-language.md -->
-<!-- https://cdn.jsdelivr.net/npm/bitboss-ui@alpha/dist/ai/guides/design-language.md -->
+<!-- https://cdn.jsdelivr.net/npm/bitboss-ui@beta/dist/ai/guides/design-language.md -->
 
 # Design Language
 
@@ -1721,7 +1787,7 @@ text, `--bb-label-weight`
 
 ## Component catalogue
 
-Every public component. Open one contract at `https://cdn.jsdelivr.net/npm/bitboss-ui@alpha/dist/ai/<Name>.md` before using it — never guess a prop name.
+Every public component. Open one contract at `https://cdn.jsdelivr.net/npm/bitboss-ui@beta/dist/ai/<Name>.md` before using it — never guess a prop name.
 
 - **BbAccordion** — Expands and collapses a content panel.
 - **BbAlert** — Shows contextual status messages.

package/dist/llms.txt

@@ -4,8 +4,8 @@
 
 ## AI Knowledge Base
 
-- [Core knowledge base](https://cdn.jsdelivr.net/npm/bitboss-ui@alpha/dist/llms-medium.txt): **Fetch this if you can only fetch one file** — hard rules, setup, component picker, design language, and the full component catalogue in ~70 KB.
-- [Complete knowledge base](https://cdn.jsdelivr.net/npm/bitboss-ui@alpha/dist/llms-full.txt): Everything concatenated (~2 MB). Bulk ingestion only — too large to prompt with.
+- [Core knowledge base](https://cdn.jsdelivr.net/npm/bitboss-ui@beta/dist/llms-medium.txt): **Fetch this if you can only fetch one file** — hard rules, setup, component picker, design language, and the full component catalogue in ~70 KB.
+- [Complete knowledge base](https://cdn.jsdelivr.net/npm/bitboss-ui@beta/dist/llms-full.txt): Everything concatenated (~2 MB). Bulk ingestion only — too large to prompt with.
 - [AI Router](ai/guides/ai-router.md): **Start here** — tiny hop map for any coding agent (which file to open next).
 - [Component index](ai/index.md): Full component catalogue with agent rules, grouped by category. Each entry links a typed contract (props/events/slots/v-model).
 - [Component manifest](ai/components.json): Machine-readable API surface of every component, for programmatic validation.
@@ -25,40 +25,40 @@
 - [Inertia Helpers](ai/guides/inertia-helpers.md): App-side toolkit for Laravel + Inertia apps — typed page props, lazy props, URL-driven filters, paginated/selection page contexts, promise forms, and navigation guards that pair with bitboss-ui pages.
 - [Migration v2 → v3](ai/guides/migration/v2-to-v3.md): Complete upgrade guide from bitboss-ui 2.x to 3.0 — plugin-based setup, token overhaul, variant registries, global behavioral changes, and the silent-failure audit playbook.
 - [Migration v2→v3: BbAlert](ai/guides/migration/components/bb-alert.md): showClose inverted to hideClose, theme replaced by typed variant.
-- [Migration v2→v3: BbAvatar](ai/guides/migration/components/bb-avatar.md): The color prop is removed — the initials fallback is always primary.
+- [Migration v2→v3: BbAvatar](ai/guides/migration/components/bb-avatar.md): The color prop is removed — retheme the fallback through the --bg-color / --text-color locals.
 - [Migration v2→v3: BbBadge (and where your v2 badges went)](ai/guides/migration/components/bb-badge.md): The v2 BbBadge (floating count/dot) is now BbIndicator; the v3 BbBadge is a new inline pill that also replaces BbChip.
 - [Migration v2→v3: BbBreadcrumbs](ai/guides/migration/components/bb-breadcrumbs.md): Item keys must be strings, the text divider prop is gone, per-item slot names are normalized.
 - [Migration v2→v3: BbButton](ai/guides/migration/components/bb-button.md): Async click handlers now auto-track loading (behavior flip), built-in tooltip props removed, variant locked to the registry.
 - [Migration v2→v3: BbCheckbox / BbRadio / BbSwitch](ai/guides/migration/components/bb-checkbox.md): reverse polarity inverted (explicit values flip, default layout unchanged), checked narrowed to boolean, color removed, BbRadio's name no longer required.
-- [Migration v2→v3: BbCheckboxGroup / BbRadioGroup / BbSwitchGroup](ai/guides/migration/components/bb-checkbox-group.md): labelPosition renamed legendPosition, per-item disabled is now inert (use selectable), color and the option affix slots removed, BbRadioGroup's name no longer required.
+- [Migration v2→v3: BbCheckboxGroup / BbRadioGroup / BbSwitchGroup](ai/guides/migration/components/bb-checkbox-group.md): labelPosition renamed legendPosition, per-item disabled is now inert (use selectable), color and the option affix slots removed, BbRadioGroup's name no longer required, and the shared bb-cr-container CSS block split into one per group.
 - [Migration v2→v3: BbChip (removed)](ai/guides/migration/components/bb-chip.md): BbChip is gone — BbBadge with clearable is the replacement; non-clearable chips were badges all along.
 - [Migration v2→v3: BbCollapsible](ai/guides/migration/components/bb-collapsible.md): The tag prop is removed; the root is always a div.
 - [Migration v2→v3: BbColorInput](ai/guides/migration/components/bb-color-input.md): picker renamed to eyeDropper.
 - [Migration v2→v3: BbColorPalette](ai/guides/migration/components/bb-color-palette.md): flip inverted to disableFlip, showArrow removed, picker renamed eyeDropper, update:open dropped, model updates never emit null.
 - [Migration v2→v3: BbDatePickerInput](ai/guides/migration/components/bb-date-picker-input.md): allowWriting inverted to disableWriting and hidePopover renamed to disableCalendar, both with a changed token set; the width prop is removed; adaptive mobile sheet by default; non-floating output carries the local offset instead of UTC `Z` (new `utc` prop restores v2 output).
-- [Migration v2→v3: BbDialog](ai/guides/migration/components/bb-dialog.md): showClose inverted to hideClose, several presentation props removed, default widths changed, adaptive bottom sheet on mobile by default.
+- [Migration v2→v3: BbDialog](ai/guides/migration/components/bb-dialog.md): showClose inverted to hideClose, several presentation props and the #close/#description slots removed, default widths changed, adaptive bottom sheet on mobile by default, --bb-dialog-* tokens replaced by --bb-panel-p plus locals.
 - [Migration v2→v3: BbDropdown](ai/guides/migration/components/bb-dropdown.md): Items now expect text as the label and can carry variants/submenus; arrowPadding removed; adaptive mobile sheet on by default.
 - [Migration v2→v3: BbDropdownButton](ai/guides/migration/components/bb-dropdown-button.md): autoLoading renamed to disableAutoLoading, disabledWhileLoading and theme removed.
 - [Migration v2→v3: BbDropzone](ai/guides/migration/components/bb-dropzone.md): modelValue is typed, accept no longer throws and takes bare tokens, and the hidden native-submit input only renders when name is set.
 - [Migration v2→v3: BbIcon](ai/guides/migration/components/bb-icon.md): The required prop is renamed type→icon, color is removed, and the xxl size key becomes 2xl.
 - [Migration v2→v3: BbIntersection](ai/guides/migration/components/bb-intersection.md): Removed with no replacement — it wrapped IntersectionObserver and carried no styling; use @vueuse/core's useIntersectionObserver.
-- [Migration v2→v3: BbOffCanvas](ai/guides/migration/components/bb-offcanvas.md): direction→side; showClose→hideClose; size defaults change; adaptive drawer configs unify on offCanvasProps.
+- [Migration v2→v3: BbOffCanvas](ai/guides/migration/components/bb-offcanvas.md): direction→side; showClose→hideClose; description and the #close/#description slots removed; size defaults change; adaptive drawer configs unify on offCanvasProps.
 - [Migration v2→v3: BbPagination](ai/guides/migration/components/bb-pagination.md): querykey renamed to queryKey; the loading prop is removed.
 - [Migration v2→v3: BbPopover](ai/guides/migration/components/bb-popover.md): Built-in close button, restoreFocus, theme, and the arrow are gone; close affordances move into your content.
-- [Migration v2→v3: BbRating](ai/guides/migration/components/bb-rating.md): color removed; name no longer required.
+- [Migration v2→v3: BbRating](ai/guides/migration/components/bb-rating.md): color removed; name no longer required; the star state modifier renamed --highlighted to --filled/--empty; --bb-rating-size demoted to a local --size; input-position finally works.
 - [Migration v2→v3: BbSelect](ai/guides/migration/components/bb-select.md): allowWriting inverted to disableWriting, filterBy narrowed to string[], prefill value renamed, chevron/options slots removed, and two behavior changes (second click, mount-time coherence).
 - [Migration v2→v3: BbSelectPopover](ai/guides/migration/components/bb-select-popover.md): flip and allowWriting inverted, arrow props removed, filterBy narrowed, options slots replaced by header/footer; shares BbSelect's behavior changes.
 - [Migration v2→v3: BbSlider](ai/guides/migration/components/bb-slider.md): thumbTranslate inverted to disableThumbTranslate; string model values and color removed.
 - [Migration v2→v3: BbSmoothHeight](ai/guides/migration/components/bb-smooth-height.md): The `tag` prop is narrowed to `div | span`, and the inner measuring element now mirrors it instead of always being a `<div>`.
 - [Migration v2→v3: BbSpinner](ai/guides/migration/components/bb-spinner.md): The color prop is removed; spinners follow currentColor.
-- [Migration v2→v3: BbTable](ai/guides/migration/components/bb-table.md): allowSelectAll inverted to disableSelectAll; loading no longer blanks populated tables and now inerts rows; #loading is first-load-only; #no-data fills a full-width table cell instead of replacing the row.
-- [Migration v2→v3: BbTabs (was BbTab)](ai/guides/migration/components/bb-tabs.md): Component renamed; querykey→queryKey; animations default on; label slots renamed and all dynamic names/URL slugs normalized.
+- [Migration v2→v3: BbTable](ai/guides/migration/components/bb-table.md): allowSelectAll inverted to disableSelectAll; loading no longer blanks populated tables and now inerts rows; #loading is first-load-only; #no-data fills a full-width table cell instead of replacing the row; columns gained sortable + rowClass, which collide with same-named consumer fields.
+- [Migration v2→v3: BbTabs (was BbTab)](ai/guides/migration/components/bb-tabs.md): Component renamed; querykey→queryKey; animations default on; label slots renamed and all dynamic names/URL slugs normalized; the entire .bb-tab BEM tree renamed to .bb-tabs / .bb-tabs-list / .bb-tabs-panes.
 - [Migration v2→v3: BbTag](ai/guides/migration/components/bb-tag.md): modelValue is strictly string[] now, multiple is removed, and duplicates are rejected case-insensitively by default.
-- [Migration v2→v3: BbTextInput](ai/guides/migration/components/bb-text-input.md): The type prop narrows to the text-like input types — number/date values must move to their dedicated components.
+- [Migration v2→v3: BbTextInput](ai/guides/migration/components/bb-text-input.md): The type prop narrows to the text-like input types — number/date values must move to their dedicated components; a bare `floating` attribute was never a prop, the spelling is label-mode="floating".
 - [Migration v2→v3: BbToast and toast()](ai/guides/migration/components/bb-toast.md): Host placement becomes position with a corner-based value set; toast() options rewritten (variant, duration, actions, portal).
 - [Migration v2→v3: BbTooltip](ai/guides/migration/components/bb-tooltip.md): timeout renamed to delay; theme replaced by typed variant; hideArrow is now a declared prop; block removed; modelValue is new.
 - [Migration v2→v3: BbTree](ai/guides/migration/components/bb-tree.md): Item model rewritten — payload moves under meta, open becomes expanded, identifier becomes itemValue, expansion is a v-model.
-- [Migration v2→v3: confirm() / useConfirm](ai/guides/migration/components/use-confirm.md): yesText/onYes/noText/onNo collapse into yes/no configs, actions becomes an array-or-false, labels are localized, footer buttons default md.
+- [Migration v2→v3: confirm() / useConfirm](ai/guides/migration/components/use-confirm.md): yesText/onYes/noText/onNo collapse into yes/no configs, actions becomes an array-or-false, theme→variant, timeout→duration, autoClose flips to default-true, labels are localized, footer buttons default md.
 - [Migration v2→v3: useBroadcastChannelInstance](ai/guides/migration/components/use-broadcast-channel-instance.md): Removed — cross-tab messaging is not a UI concern; use useBroadcastChannel from @vueuse/core.
 - [Page Shell](ai/guides/page-shell.md): App-side page layout — topbar, content, and a right details sidebar driven by a stack-based context (push a record to peek it, pop to go back). The implementation ships in the per-platform Layout Scaffold recipe; this guide covers when and how to use it.
 - [Validated Forms (vee-validate)](ai/guides/validated-forms.md): The `bitboss-ui/validated` entrypoint — form controls pre-wired to vee-validate. Global rules give an effort-free `rules="required|email"` string syntax; BbForm hosts the form; requiredAsterisk marks required fields.