bitboss-ui 3.0.0-beta.41 → 3.0.0-beta.43

package/README.md

@@ -127,7 +127,7 @@ magnitude, not a contract.
 
 - [Core knowledge base](https://llms-bitboss-ui.bitboss.it/dist/llms-medium.txt) (about 200 KB) — **start here if you can only fetch one file.** Hard rules, setup, component picker, design language, and the full component catalogue.
 - [Index](https://llms-bitboss-ui.bitboss.it/llms.txt) (about 20 KB) — link index into every document.
-- [components.json](https://llms-bitboss-ui.bitboss.it/dist/ai/components.json) — machine-readable API surface, for programmatic validation.
+- [Component API files](https://llms-bitboss-ui.bitboss.it/dist/ai/manifest/index.json) — machine-readable API, one file per component (`manifest/components/<Name>.json`), each one read. The same data in one file for tools: [components.json](https://llms-bitboss-ui.bitboss.it/dist/ai/components.json) (about 1.2 MB).
 - [Complete knowledge base](https://llms-bitboss-ui.bitboss.it/dist/llms-full.txt) (about 5 MB) — everything concatenated. Bulk ingestion only; too large to prompt with.
 
 Already installed? Prefer the local copy under `node_modules/bitboss-ui/dist/ai/`,
@@ -318,10 +318,12 @@ Restart your agent harness once after either path so it picks up the new server.
 
 The server's tools: `search_docs` (the section that answers a "how do I…"
 question, across every guide and component), `search_components` (empty query
-= the catalogue), `get_component` (compact: every prop, event, slot and pt
-part, plus guide sections on request; also answers for type names and for v2 /
-beta names that were renamed), `get_guide`, `get_composable`, `list_recipes` /
-`get_recipe`, `list_tokens`, `list_changes` and `validate`.
+= the catalogue), `get_component` (one line per prop, event and slot; whole
+rows with `members`, guide prose with `sections`; also answers for type names
+and for v2 / beta names that were renamed), `get_guide`, `get_composable`,
+`list_recipes` / `get_recipe`, `list_tokens`, `list_changes` (counts, then one
+line per change) and `validate`. Every answer is small by default: ask for the
+part you need.
 
 ### CLI commands
 
@@ -475,13 +477,59 @@ a `BbProgress` with no `label`: all three render with no accessible name. Put th
 still name the button:
 
 ```vue
-<BbButton icon="lucide:trash">Elimina</BbButton>
+<BbButton icon="lucide:trash">Delete</BbButton>
 <BbProgress label="Upload" :model-value="progress" />
 ```
 
 `BbSpinner` is not covered: without `label` it is decorative, which is correct.
 For raw HTML controls, use `eslint-plugin-vuejs-accessibility`.
 
+#### v-model on a const reactive(): `no-reactive-v-model`
+
+`bitboss-ui/no-reactive-v-model` flags a `v-model` (or `v-model:arg`) bound to
+a `<script setup>` `const x = reactive(…)`. Dev runs it fine; a production
+build compiles the write-back to `x = $event`, an assignment to a `const`, and
+the bundler stops. Hold the object in a `ref()` and read `.value` in script; the
+template does not change:
+
+```vue
+<script setup lang="ts">
+import { ref } from 'vue';
+const values = ref({ name: '' }); // not: const values = reactive({ name: '' })
+</script>
+
+<template>
+	<ProfileEditor v-model="values" />
+</template>
+```
+
+A `let`, a member expression (`v-model="form.name"`) and Inertia's
+`useForm()` are fine. `<BbForm>` is left to `form-model`: it takes its object
+one way, so `:model` is the fix there, not a `ref()`. `bitboss-ui check`
+reports the same as `reactive-v-model`.
+
+#### The object a form fills: `form-model`
+
+`<BbForm>` takes the object it fills one way, `:model="draft"`: any reactive
+object — `reactive()`, `ref`, Pinia state, Inertia `useForm()` — written in
+place. `bitboss-ui/form-model` fixes `v-model="…"` and `:model-value="…"` on
+`<BbForm>` to `:model="…"`, and reports an `@update:model-value` listener (the
+form emits none: watch the object deep) and a writable `computed` bound as the
+model (its setter is never called):
+
+```vue
+<script setup lang="ts">
+import { reactive } from 'vue';
+const draft = reactive({ name: '' });
+</script>
+
+<template>
+	<BbForm :model="draft">…</BbForm>
+</template>
+```
+
+`bitboss-ui check` reports the same as `form-v-model`.
+
 #### Rating star colours: `no-star-color`
 
 `bitboss-ui/no-star-color` flags any colour utility in `BbRating`'s `pt:item`,
@@ -569,7 +617,8 @@ A standard `llms.txt` discovery file is also published at:
 | ------------------------------------- | ------------------------------------------------------------------------------------ |
 | `dist/ai/guides/ai-router.md`         | **Start here** — which file to open next                                             |
 | `dist/ai/index.md`                    | Full catalogue + agent rules                                                         |
-| `dist/ai/components.json`             | Machine-readable API (props/events/slots)                                            |
+| `dist/ai/manifest/index.json`         | Machine-readable API for agents: the component list → `components/<Name>.json`       |
+| `dist/ai/components.json`             | The same API in one file, for tools (`check`, ESLint, MCP)                           |
 | `dist/ai/<ComponentName>.md`          | Guide-first contract per component                                                   |
 | `dist/ai/composables/<name>.md`       | Composable docs                                                                      |
 | `dist/ai/guides/agent-contract.md`    | Mandatory agent rules                                                                |
@@ -588,6 +637,7 @@ files directly:
 | ----------------------------------- | ------------------------------ |
 | `bitboss-ui/ai`                     | `dist/ai/index.md` (catalogue) |
 | `bitboss-ui/ai/components.json`     | `dist/ai/components.json`      |
+| `bitboss-ui/ai/manifest/index.json` | `dist/ai/manifest/index.json`  |
 | `bitboss-ui/ai/guides/ai-router.md` | `dist/ai/guides/ai-router.md`  |
 
 Agents can also read paths under `node_modules/bitboss-ui/dist/ai/` directly.