@aibranch/llm-meta-widget 0.8.0 → 0.8.1

package/README.md

@@ -124,7 +124,7 @@ that is not Rails needs no gem, no template engine and no asset pipeline — two
 lines of HTML:
 
 ```html
-<script type="module" src="https://cdn.jsdelivr.net/npm/@aibranch/llm-meta-widget@0.7"></script>
+<script type="module" src="https://cdn.jsdelivr.net/npm/@aibranch/llm-meta-widget@0.8"></script>
 <llm-meta-widget llm-url="https://your-meta-server.example"
                  model="qwen3-6-35b-fast"
                  greeting="Hi — ask me anything about this page."></llm-meta-widget>
@@ -135,6 +135,16 @@ instead of ERB. Both produce the same widget, so the advice in that section
 — CORS, a reachable `llm_url`, the hub's name for the model — applies here
 too.
 
+**`@0.8` is a range, and it stops at 0.8.x on purpose.** You get patches without
+touching your page, and you do not get a breaking release by surprise. The cost
+is that moving to 0.9 is a deliberate edit: read [CHANGELOG.md](CHANGELOG.md)
+first, because a major-or-minor bump here is where the page's own contract can
+change — 0.8.0 changed the shape of `window.aiState`, and a page that followed
+the new documentation while still loading `@0.7` would have had every state
+value silently replaced by an error string. Rails hosts are protected from that
+mismatch by the Gemfile constraint; a CDN embed has no such guard, so the
+version in that URL is the guard.
+
 Nothing else is needed: the stylesheets and the markdown renderer are bundled
 in, and the element injects its own styles. The host serves no CSS and no JS.
 

package/docs/custom-element-distribution.md

@@ -17,7 +17,7 @@ reduced to the element tag. The gem keeps its helper signature, so
 PubDictionaries needs no edit.
 
 Landed since: the npm package and the CDN URL. `@aibranch/llm-meta-widget` is on
-npm, and `https://cdn.jsdelivr.net/npm/@aibranch/llm-meta-widget@0.7` resolves to
+npm, and `https://cdn.jsdelivr.net/npm/@aibranch/llm-meta-widget@0.8` resolves to
 the bundle, so the two-line integration in the example below is now literally
 true — no gem, no Rails and no self-hosting required. The gem and the npm package
 ship the identical file, which is checked rather than assumed: both 0.7.2 copies
@@ -95,7 +95,7 @@ to npm and served from a CDN. Integration in any stack, or none:
 
 ```html
 <script type="module"
-        src="https://cdn.jsdelivr.net/npm/@aibranch/llm-meta-widget@0.7"></script>
+        src="https://cdn.jsdelivr.net/npm/@aibranch/llm-meta-widget@0.8"></script>
 <llm-meta-widget llm-url="https://hub.aibranch.org"
                  tool-hub-url="https://hub.aibranch.org"
                  model="qwen3-8-27b-fast"
@@ -195,7 +195,7 @@ adopter of it.
 The CDN URL has no path:
 
 ```
-https://cdn.jsdelivr.net/npm/@aibranch/llm-meta-widget@0.7
+https://cdn.jsdelivr.net/npm/@aibranch/llm-meta-widget@0.8
 ```
 
 `main` and `exports["."]` both point at the bundle, so jsdelivr resolves the

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@aibranch/llm-meta-widget",
-  "version": "0.8.0",
+  "version": "0.8.1",
   "//version": "Must stay in step with lib/llm_meta_widget/version.rb. Two independently versioned copies of the same client is the drift docs/custom-element-distribution.md warns about: bump both, release both.",
   "description": "Embeddable browser chat widget: a custom element that discovers tools at page, origin and hub scope and dispatches each tool call to the right one. Two lines of HTML on any host, Rails or not.",
   "keywords": [