sbuilder-mcp 0.9.1 → 0.9.2

package/CHANGELOG.md

@@ -6,6 +6,14 @@ 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.9.2] - 2026-09-09
+
+### Added
+- sb_look now reports `stuck_note` once per process when the page pins something (`position: sticky` or `fixed`), explaining that a screenshot cannot show whether the element is actually stuck and pointing at a browser server (Playwright MCP or Chrome DevTools MCP) to scroll and check for the `wb-stuck` class.
+
+### Internal
+- docs/tools.md and the sbuilder-site-design skill now document which of the other MCP servers (Figma, Google Stitch, Chrome DevTools, Playwright) answers which question, alongside sb_look, covering six cases a screenshot alone cannot settle: a sticky header actually engaging, a style that "did not apply", a cart drawer's click trigger, a checkout submission, an entity template previewed with a real record, and layout stability (CLS).
+
 ## [0.9.1] - 2026-09-09
 
 ### Fixed

package/CHANGELOG.vi.md

@@ -6,6 +6,14 @@ 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.9.2] - 2026-09-09
+
+### Added
+- sb_look giờ báo cáo `stuck_note` một lần mỗi tiến trình khi trang có ghim một phần tử (`position: sticky` hoặc `fixed`), giải thích rằng một ảnh chụp màn hình không thể cho biết phần tử đó có thực sự bị "stuck" hay không, và chỉ ra một trình duyệt server (Playwright MCP hoặc Chrome DevTools MCP) để cuộn trang và kiểm tra class `wb-stuck`.
+
+### Internal
+- docs/tools.md và skill sbuilder-site-design giờ ghi lại server MCP nào (Figma, Google Stitch, Chrome DevTools, Playwright) trả lời câu hỏi nào, bên cạnh sb_look, bao quát sáu trường hợp mà chỉ riêng ảnh chụp màn hình không thể trả lời: một header sticky có thực sự ghim hay không, một style "không được áp dụng", nút bấm mở giỏ hàng, việc submit checkout, xem trước một template entity với dữ liệu thật, và độ ổn định bố cục (CLS).
+
 ## [0.9.1] - 2026-09-09
 
 ### Fixed

package/dist/tools/live.js

@@ -7,6 +7,7 @@ import { uploadMedia } from '../transport/media.js';
 import { request } from '../transport/http.js';
 import { shoot, DEFAULT_WIDTHS } from '../vision/shoot.js';
 import { measure, MEASURE_NOTICE } from '../vision/measure.js';
+import { isPinnedNode } from '../domains/site/sticky.js';
 import { compactFindings } from '../domains/site/findings.js';
 import { reviewField } from './page.js';
 import { boxesForResponse, BOXES_FORMAT } from '../vision/boxes.js';
@@ -340,10 +341,30 @@ export function registerLiveTools(server, ctx, session) {
                 '("Color / Size", "Red / S") rather than the product\'s own. That is the preview, ' +
                 'not the page. Pass a published storefront URL as `url` to judge a template.')
             : undefined;
+        // A STILL PICTURE CANNOT SHOW A PINNED ELEMENT ENGAGING, and this is the
+        // one tool a caller would expect to. `position: sticky` looks identical at
+        // rest and while stuck — that is the whole reason the platform needs a
+        // runtime class for it — so a page carrying a pinned node has a look this
+        // tool is structurally unable to photograph, however many widths it shoots.
+        //
+        // Gated on the document actually carrying one, and said once, for the same
+        // reason `preview_note` is: a directive that fires on pages it cannot
+        // apply to is noise, and noise is what makes the real notes unread.
+        const pinned = Object.values(session.current().doc.nodes).some((n) => isPinnedNode(n));
+        const stuckNote = pinned
+            ? ctx.notices.once('stuck-scroll', 'This page pins something (position sticky/fixed). A screenshot is ONE scroll ' +
+                'position, so nothing here can show whether it engages or what it looks like ' +
+                'once it does — the platform styles that moment through a class a runtime island ' +
+                'toggles, "wb-stuck", and CSS alone cannot express it. To check: open the ' +
+                'PUBLISHED page in a browser server (Playwright or Chrome DevTools MCP), scroll, ' +
+                'and read classList for "wb-stuck". If it never appears, every stuck override on ' +
+                'the page is stored and never painted.')
+            : undefined;
         return images(shots.map((s) => ({ dataBase64: s.imageBase64, mimeType: s.mimeType })), {
             widths: shots.map((s) => s.width),
             ...(url ? { shot: url } : {}),
             ...(previewNote ? { preview_note: previewNote } : {}),
+            ...(stuckNote ? { stuck_note: stuckNote } : {}),
             ...(node_id ? { framed: node_id } : {}),
             ...(with_boxes === false
                 ? {}

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "sbuilder-mcp",
-  "version": "0.9.1",
+  "version": "0.9.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",