sbuilder-mcp 0.11.1 → 0.11.2

package/CHANGELOG.md

@@ -6,6 +6,11 @@ All notable changes to this project are documented in this file.
 The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/),
 and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
+## [0.11.2] - 2026-09-09
+
+### Fixed
+- sb_set's routing of a hover write to an element's legacy home (a `button`, for instance) now also clears any leftover values in the unread `states.hover` slot in the same call, instead of leaving them behind for `sb_review` to keep reporting as `hover_dead`; the finding's own message previously named `unset` as the way to remove them, which could not reach the legacy home either, so the documented fix was unreachable.
+
 ## [0.11.1] - 2026-09-09
 
 ### Added

package/CHANGELOG.vi.md

@@ -6,6 +6,11 @@ Mọi thay đổi đáng chú ý của dự án được ghi lại trong file n
 Định dạng dựa trên [Keep a Changelog](https://keepachangelog.com/en/1.1.0/),
 và dự án tuân theo [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
+## [0.11.2] - 2026-09-09
+
+### Fixed
+- Khi sb_set định tuyến một lần ghi hover tới nơi lưu cũ của element (ví dụ `button`), giờ nó cũng xoá luôn mọi giá trị còn sót trong slot `states.hover` không ai đọc, ngay trong cùng một lệnh — thay vì để lại chúng cho sb_review tiếp tục báo là `hover_dead`; thông báo của chính finding này trước đây nêu `unset` là cách xoá, nhưng `unset` cũng không thể chạm tới nơi lưu cũ đó, khiến cách sửa được ghi ra là không thể thực hiện được.
+
 ## [0.11.1] - 2026-09-09
 
 ### Added

package/dist/domains/site/builder.js

@@ -264,6 +264,29 @@ export function setKeys(doc, id, keys, opts) {
         // compiler reads. Routed rather than refused: the caller asked for a hover
         // and there is a home that works; `hoverRoutingNote` says where it went.
         if (opts.state === HOVER_STATE && namespace === 'style' && hoverHome(doc.node(id).data.type) === 'legacy') {
+            // …AND CLEAR THE SLOT NOBODY READS, in the same call.
+            //
+            // On an element with this home, `states.hover` has no legitimate use: the
+            // universal compiler stands aside for it and its own renderer looks in the
+            // flat map. Leaving values there is the exact defect `sb_review` reports as
+            // `hover_dead`, so a rewrite that repaired the look and left the dead copy
+            // behind would fix the page and keep the finding — and the fix that
+            // finding names would still be unreachable, which is the shape this repo
+            // has now closed twice.
+            //
+            // Safe against the platform changing its mind: if a button ever keeps its
+            // hover in the node, its meta's `storage` becomes 'node', HOVER_HOMES says
+            // 'state', and this branch does not run at all.
+            const node = doc.node(id);
+            const dead = [];
+            if (node.states?.[HOVER_STATE] !== undefined) {
+                dead.push({ op: 'unset', path: ['nodes', id, 'states', HOVER_STATE] });
+            }
+            for (const [bp, slot] of Object.entries(node.responsive ?? {})) {
+                if (slot?.states?.[HOVER_STATE] !== undefined) {
+                    dead.push({ op: 'unset', path: ['nodes', id, 'responsive', bp, 'states', HOVER_STATE] });
+                }
+            }
             return [
                 ...Object.entries(keys).map(([k, v]) => ({
                     op: 'set',
@@ -271,6 +294,7 @@ export function setKeys(doc, id, keys, opts) {
                     value: v,
                 })),
                 ...(opts.unset ?? []).map((k) => ({ op: 'unset', path: legacyHoverPath(id, k) })),
+                ...dead,
             ];
         }
         // Base state and per-breakpoint state are DIFFERENT PLACES in the document,

package/dist/domains/site/findings.js

@@ -60,10 +60,9 @@ export const FIX = {
         '{ "overflowX": "visible", "overflowY": "visible" } — or move the pinned node outside it. ' +
         'Sticky resolves against its nearest SCROLLING ancestor, so a clipping one becomes that ' +
         'ancestor and the node pins inside a box that never scrolls.',
-    hover_dead: 'Rewrite it: sb_set id "<id>", namespace style, state "hover", keys { … } — sb_set now ' +
-        'routes a hover to the home its element declares, and reports where it went. The values ' +
-        'currently in states.hover are read by nobody; remove them with the same call\'s `unset` ' +
-        'once the working copy is in place.',
+    hover_dead: 'Rewrite it with the same values: sb_set id "<id>", namespace style, state "hover", ' +
+        'keys { … } — read them off the node first, because that one call both writes them where ' +
+        'the renderer looks AND clears the slot nobody reads. Nothing else to do afterwards.',
     stuck_no_host: 'Pin something: sb_set id "<id>" (or the section it lives in), namespace style, keys ' +
         '{ "position": "sticky" } — sb_set seeds the offset and the layer order with it. Until ' +
         'then the platform compiles no rule for this state at all, so the override is stored, ' +

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "sbuilder-mcp",
-  "version": "0.11.1",
+  "version": "0.11.2",
   "description": "MCP server that designs and operates a Store Builder site — pages, data, theme and publish — through the platform's own API and live-edit protocol.",
   "mcpName": "io.github.vuluu2k/sbuilder-mcp",
   "type": "module",