sbuilder-mcp 0.36.0 → 0.36.1

package/CHANGELOG.md

@@ -6,6 +6,10 @@ 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.36.1] - 2026-09-11
+
+- fix(import,api): a capture waited on iframes, and a recovery list was unreadable
+
 ## [0.36.0] - 2026-09-11
 
 ### Added

package/dist/tools/api.js

@@ -45,6 +45,33 @@ function pickFields(item, fields) {
  * it would have been and how to narrow the call. A non-list answer is never
  * cut: there is no honest place to stop inside one object.
  */
+/**
+ * LIST OPERATIONS WHOSE EVERY ROW CARRIES A WHOLE PAGE DOCUMENT.
+ *
+ * The page recovery surface answers with the documents themselves — which is
+ * right, since a restore has to have something to restore from — and useless to
+ * read. MEASURED against a live server: one version of a TWO-NODE page is 1,690
+ * bytes, so a realistic 120-node page runs about 70 KB per version and a listing
+ * of twenty is **1.4 MB in one answer**. An agent choosing which version to
+ * restore would be handed a truncated blob and no reliable way to pick.
+ *
+ * `sb_publish` already had this exact problem and the same answer: a published
+ * row carries `document`, `html` and `css` for every page the cascade touched,
+ * so it PROJECTS the rows. This is that, applied where the caller cannot know to
+ * ask — and it is a DEFAULT rather than a rule: an explicit `pick` still wins,
+ * so the document is one argument away for a caller that wants to read one.
+ */
+const LIST_PROJECTIONS = {
+    'get:/api/sites/{siteId}/pages/{pageId}/versions': [
+        'id',
+        'versionNo',
+        'label',
+        'createdBy',
+        'createdAt',
+        'isLive',
+    ],
+    'get:/api/sites/{siteId}/pages/{pageId}/history': ['id', 'createdBy', 'createdAt'],
+};
 export function shapeResponse(raw, opts) {
     const asked = opts.pick !== undefined || opts.max_items !== undefined;
     const isObj = (v) => !!v && typeof v === 'object' && !Array.isArray(v);
@@ -271,7 +298,10 @@ export async function callOperation(ctx, args) {
     if (raw === null || raw === undefined) {
         return { ok: true, method: op.method, path, note: 'The platform answered with no content.' };
     }
-    return shapeResponse(raw, { pick: args.pick, max_items: args.max_items });
+    // The caller's own `pick` outranks the default: asking for `document` is how
+    // you read a version rather than merely choose one.
+    const projection = args.pick ?? LIST_PROJECTIONS[op.id];
+    return shapeResponse(raw, { pick: projection, max_items: args.max_items });
 }
 export function registerApiTools(server, ctx) {
     server.registerTool('sb_api_find', {

package/dist/vision/capture.js

@@ -1127,7 +1127,22 @@ async function readPage(browser, url, width, work) {
     let page;
     try {
         page = await browser.newPage({ viewport: { width, height: 900 } });
-        await page.goto(url, { waitUntil: 'load', timeout: 30_000 });
+        // `domcontentloaded`, NOT `load`, and `settleDom` does the rest.
+        //
+        // `load` waits for every SUBRESOURCE — including third-party iframes, which
+        // an import has no use for: this walk reads the iframe's `src` ATTRIBUTE and
+        // never needs the frame to render. So a page carrying an ad frame, a chat
+        // widget or a slow video embed stalled the whole capture for up to thirty
+        // seconds and then THREW, losing an import whose DOM had been ready the
+        // entire time. Caught by this repo's own test, whose fixture embeds real
+        // YouTube, Vimeo and Google Maps frames: it started failing at exactly 30s
+        // with nothing about the page having changed.
+        //
+        // The same lesson `sb_look` already paid for with `networkidle`, one wait
+        // earlier: the right question is "has the DOM stopped changing", and
+        // `settleDom` answers it directly and bounded. A page that genuinely needs
+        // its images is the SHOOT path's problem, and that one still waits.
+        await page.goto(url, { waitUntil: 'domcontentloaded', timeout: 30_000 });
         // THE SAME SETTLE `sb_look` USES, not a flat sleep. A fixed 600ms is wrong
         // at both ends: example.com is finished long before it, and a page that
         // builds itself with scripts is not finished after it — which is exactly the

package/package.json

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