llm_meta_widget 0.13.1 → 0.14.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: b72c0af2bf75bb5a7d1b83b0048aac15dc0485d86448ca4ea99403737c7a95ec
-  data.tar.gz: 1c5dfb8782859c09727fde1f996a39055c0cbe8e75b6116258b9d547a4a7b7a4
+  metadata.gz: e67bd92aa30299ffd0f7d6e3a9291dc5c398800cf9276b04768101077e212880
+  data.tar.gz: 487c187c3d20631b38f72cc4b6b9241db285ae5a7e2e5e5ef50f814bcb8cee42
 SHA512:
-  metadata.gz: cf20127dce92b482a6c6a88a42e3a31fc2b80e127274c9cbae5e7d6f75d3043c9334e38459a7feddf90f0c985984f1a3cdced6550091953952ab44a9282fcf25
-  data.tar.gz: 5554707eda6744fdf8188c1c7d81765c27c068cb078a672d894825cb70f8f5c2c2e6ed4f3593f5a5432b7255bd7d0f01718c14804b1dcba9af661c0df7667a3c
+  metadata.gz: 39e08820f2551e2eccd15b71b7bba68e2342911cb7ec57de0b1f9ee8d26a720b8e36283f2c033a019fe206de3dc1d10b4337c5fedaee94a39c72ba9482c36bcc
+  data.tar.gz: e373ab9a30c2274817d7fae2da1bdea107d024c92f6204af3ae404debcbc22011b6de131bfaf6d25205d420f8f1b98ce8e9328220dcff81ae8142822dbec2a6e

data/CHANGELOG.md

@@ -3,6 +3,26 @@
 This file starts at 0.8.0, the first release with a breaking change worth
 calling out. Earlier releases are in the git history (`git log --oneline v0.7.6`).
 
+## 0.14.0
+
+### Breaking: a transport declared in top-level `remotes` is no longer read
+
+0.13.0 moved the declaration into
+`_meta["io.modelcontextprotocol/static-primitives"].transports` and kept reading
+the old top-level `remotes` list, with a warning, so that a page and a widget
+could be updated in either order. That transition is over.
+
+**If your page card still declares its transport in `remotes`, move it to
+`transports` before taking this release.** A card that still carries the old
+spelling gets no handlers from the card: the widget falls back to
+`window.aiActions`, `window.aiPrompts` and `window.aiResources`, which is
+nothing at all for a page that does not define them. The widget reports the
+situation in the browser console rather than leaving you to find it, but it
+cannot dispatch.
+
+Nothing else changed. If your card already declares `transports`, this release
+behaves exactly like 0.13.1.
+
 ## 0.13.1
 
 ### Documentation: the README caught up with 0.12.x and 0.13.0

data/README.md

@@ -61,7 +61,7 @@ Option 3 if it does not.
 
 ```ruby
 # Gemfile
-gem "llm_meta_widget", "~> 0.13.1"
+gem "llm_meta_widget", "~> 0.14.0"
 ```
 
 ```bash
@@ -152,26 +152,25 @@ The widget is a custom element in a single self-contained ES module, so the
 whole integration is two lines of HTML:
 
 ```html
-<script type="module" src="https://cdn.jsdelivr.net/npm/@aibranch/llm-meta-widget@0.13"></script>
+<script type="module" src="https://cdn.jsdelivr.net/npm/@aibranch/llm-meta-widget@0.14"></script>
 <llm-meta-widget llm-url="https://your-meta-server.example"
                  model="gpt-oss-120b"
                  greeting="Hi — ask me anything about this page."></llm-meta-widget>
 ```
 
-**`@0.13` is a version range, and it stops at 0.13.x on purpose.** You receive
+**`@0.14` is a version range, and it stops at 0.14.x on purpose.** You receive
 bug fixes without editing your page, and a release that breaks your page cannot
 arrive on its own.
 
-Moving to 0.14 is therefore a change you make yourself. Read
+Moving to 0.15 is therefore a change you make yourself. Read
 [CHANGELOG.md](CHANGELOG.md) before you do, because this is where what your page
 must provide can change. For example, 0.10.0 changed how the widget finds a page
 card: by media type rather than by element id. A page that declared its card the
 new way while still loading `@0.9` lost every tool, prompt and resource it had
 declared. Nothing failed, anywhere. The CHANGELOG entry for 0.10.0 describes it.
 
-0.13.0 moves where a page declares its transport. That one is safe to take
-first, because 0.13.x still reads the old spelling and warns; the page can move
-afterwards.
+0.13.0 moved where a page declares its transport, and 0.14.0 stopped reading
+the old spelling. Move your card to `transports` before taking 0.14.x.
 
 A Rails app is protected from that mismatch, because the `Gemfile` will not
 resolve a widget version the page cannot use. A page that loads the widget from
@@ -312,10 +311,10 @@ widget supports today. Leave `transports` out and the widget reads
 `window.aiActions`, `window.aiPrompts` and `window.aiResources` instead — see
 "Say where your handlers live".
 
-Widgets up to 0.12.2 read this declaration from a `remotes` list at the top
-level of the card instead. Version 0.13.0 still reads that, and warns, so a page
-and a widget can be updated in either order. Write `transports`; a page may
-declare both while a deployment is still catching up, and `transports` decides.
+Widgets from 0.11.1 to 0.12.2 read this declaration from a `remotes` list at the
+top level of the card, and 0.13.x read either spelling. From 0.14.0 the old one
+is not read at all: a card that still carries it gets no handlers, and the
+widget reports that in the browser console. Write `transports`.
 
 A page may declare `prompts` in the same block. See [The page card](#the-page-card)
 for prompts, for the size and volatility hints on a resource, and for what

data/app/assets/javascripts/llm_meta_widget/llm-meta-widget.js

@@ -701,12 +701,8 @@ function declaredPageGlobal(card, warn = console.warn) {
     warn("[llm-meta-widget] page card declares transports " + JSON.stringify(declared.map((t) => t && t.type)) + ", none of which this widget supports; not dispatching to the page");
     return null;
   }
-  for (const remote of card && card.remotes || []) {
-    if (!remote || remote.type !== PAGE_GLOBAL_TRANSPORT) continue;
-    if (typeof remote.global === "string" && remote.global.trim() !== "") {
-      warn(`[llm-meta-widget] page card declares its transport in top-level "remotes", which is deprecated; move it to _meta["${STATIC_PRIMITIVES_META}"].transports`);
-      return remote.global.trim();
-    }
+  if ((card && card.remotes || []).some((r) => r && r.type === PAGE_GLOBAL_TRANSPORT)) {
+    warn(`[llm-meta-widget] page card declares its transport in top-level "remotes", which is no longer read. Move it to _meta["${STATIC_PRIMITIVES_META}"].transports`);
   }
   return null;
 }

data/app/assets/javascripts/llm_meta_widget/orchestrator.js

@@ -1130,10 +1130,9 @@ export const PAGE_GLOBAL_TRANSPORT = "page-global"
 // `page-postmessage`, `page-jsonrpc` and `page-worker` are reserved, and a card
 // declaring only those gets no handlers rather than the wrong ones.
 //
-// Top-level `remotes` is the pre-d44bd25a shape that 0.11.1 and 0.12.2 read. It
-// is accepted for one release so a page and a widget can be updated in either
-// order without the page going dark in between, and it warns so the author
-// knows to move.
+// Top-level `remotes` is the pre-d44bd25a shape that 0.11.1 to 0.12.2 read and
+// 0.13.x accepted. It is no longer read, but a card still carrying it is
+// reported, because the alternative is a page that quietly stops working.
 export function declaredPageGlobal(card, warn = console.warn) {
   const declared = (card && card.transports) || []
   for (const transport of declared) {
@@ -1149,14 +1148,14 @@ export function declaredPageGlobal(card, warn = console.warn) {
     return null
   }
 
-  for (const remote of (card && card.remotes) || []) {
-    if (!remote || remote.type !== PAGE_GLOBAL_TRANSPORT) continue
-    if (typeof remote.global === "string" && remote.global.trim() !== "") {
-      warn('[llm-meta-widget] page card declares its transport in top-level ' +
-           '"remotes", which is deprecated; move it to ' +
-           `_meta["${STATIC_PRIMITIVES_META}"].transports`)
-      return remote.global.trim()
-    }
+  // No longer read. Reporting it is still worth a few lines: without this a
+  // card that declares its transport only in the old place gets no handlers,
+  // falls through to the legacy globals, and a page that deliberately defines
+  // none — as PubDictionaries does — simply stops working with nothing said.
+  if (((card && card.remotes) || []).some((r) => r && r.type === PAGE_GLOBAL_TRANSPORT)) {
+    warn('[llm-meta-widget] page card declares its transport in top-level ' +
+         '"remotes", which is no longer read. Move it to ' +
+         `_meta["${STATIC_PRIMITIVES_META}"].transports`)
   }
   return null
 }

data/lib/llm_meta_widget/version.rb

@@ -1,3 +1,3 @@
 module LlmMetaWidget
-  VERSION = "0.13.1"
+  VERSION = "0.14.0"
 end

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: llm_meta_widget
 version: !ruby/object:Gem::Version
-  version: 0.13.1
+  version: 0.14.0
 platform: ruby
 authors:
 - jdkim