sbuilder-mcp 0.13.1 → 0.14.0

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.14.0] - 2026-09-09
+
+### Added
+- sb_review now reports `categoryScope` when a store has more than one product category and none of them is linked to a page of its own, since `/collections/{slug}` then falls back to the category type's default template for every category, and nothing on that shared template narrows the product feed to the category in the URL, so a shopper sees the whole catalogue (or another category's products) no matter which one they open; the finding names the fix — a page per category with its repeater set to `{ "collectionType": "collection", "collectionId": "<category id>" }`, linked with `sb_api_call post:/api/sites/{siteId}/page-links/bulk`.
+
 ## [0.13.1] - 2026-09-09
 
 ### Fixed

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.14.0] - 2026-09-09
+
+### Added
+- sb_review giờ báo cáo `categoryScope` khi một store có nhiều hơn một product category mà không category nào được link tới một page riêng, vì khi đó `/collections/{slug}` sẽ rơi về default template của loại category cho mọi category, và không có gì trên template dùng chung đó thu hẹp product feed theo category trong URL, nên khách hàng sẽ thấy toàn bộ catalogue (hoặc sản phẩm của category khác) dù mở category nào; finding nêu rõ cách khắc phục — mỗi category một page riêng với repeater đặt `{ "collectionType": "collection", "collectionId": "<id category>" }`, liên kết bằng `sb_api_call post:/api/sites/{siteId}/page-links/bulk`.
+
 ## [0.13.1] - 2026-09-09
 
 ### Fixed

package/dist/domains/site/readiness-fetch.js

@@ -24,7 +24,7 @@ export async function gatherReadiness(ctx, siteId, pageNodes) {
         }
     };
     const site = encodeURIComponent(siteId);
-    const [pageList, gateways, shipping, globals, productList] = await Promise.all([
+    const [pageList, gateways, shipping, globals, productList, categoryList, pageLinks] = await Promise.all([
         get(`/api/sites/${site}/pages`),
         get(`/api/sites/${site}/payment-gateways`),
         get(`/api/sites/${site}/shipping-methods`),
@@ -34,6 +34,14 @@ export async function gatherReadiness(ctx, siteId, pageNodes) {
         // key-only one. A page is enough to tell empty from not; `total` carries the
         // real count when the platform sends it.
         get(`/api/sites/${site}/products?limit=200`),
+        // THE CATEGORIES, and the pages they point at. `/collections/{slug}` resolves
+        // through PublishedForEntity: the category's OWN page when a page-link names
+        // one, else the DEFAULT TEMPLATE for the `category` type — and nothing on
+        // that shared template narrows the product feed to the category in the URL.
+        // So two categories with no page-links means at most one of them can be
+        // right, and the rest list the whole catalogue.
+        get(`/api/sites/${site}/product-categories`),
+        get(`/api/sites/${site}/page-links`),
     ]);
     // A gateway counts only when it is BOTH enabled and configured — the editor's
     // `live` getter also filters by the store's currency, which is a narrowing:
@@ -44,6 +52,12 @@ export async function gatherReadiness(ctx, siteId, pageNodes) {
         : null;
     const methods = shipping?.shippingMethods ?? shipping?.methods;
     const shippingMethods = Array.isArray(methods) ? methods.length : null;
+    const cats = categoryList?.categories ?? categoryList?.productCategories;
+    const categories = Array.isArray(cats) ? (categoryList?.total ?? cats.length) : null;
+    const links = pageLinks?.links ?? pageLinks?.pageLinks;
+    const categoryPageLinks = Array.isArray(links)
+        ? links.filter((l) => l?.linkType === 'productCategory').length
+        : null;
     const globalNodes = globals?.globalSections
         ? globals.globalSections.flatMap((g) => Object.values(g.document?.nodes ?? {}))
         : null;
@@ -64,5 +78,7 @@ export async function gatherReadiness(ctx, siteId, pageNodes) {
         shippingMethods,
         pageNodes,
         globalNodes,
+        categories,
+        categoryPageLinks,
     };
 }

package/dist/domains/site/readiness.js

@@ -190,6 +190,39 @@ export function readinessGaps(input) {
             fix: 'Put a control with the open_cart event in the header global section.',
         });
     }
+    // EVERY CATEGORY SHOWS EVERY PRODUCT, which is what a shared template does.
+    //
+    // `/collections/{slug}` resolves through PublishedForEntity: the category's
+    // OWN page when a page-link names one, else the DEFAULT TEMPLATE for the
+    // `category` type. Nothing on that shared template narrows the product feed to
+    // the category in the URL — `entityScope` threads the entity into the article
+    // feed for a blogCategory and the review feed for a product, and into nothing
+    // at all for a productCategory — so a repeater on `all_products` repeats the
+    // whole catalogue, and one on `collection` names ONE fixed id. Either way at
+    // most one category can be right.
+    //
+    // Reported on the COUNTS rather than by reading the template's document: two
+    // categories and no page-links is already the defect, whatever the template
+    // says, and a document fetch per review to confirm it would cost every store
+    // that has this right. Silent when either count could not be read, like every
+    // other check here.
+    if ((input.categories ?? 0) > 1 && input.categoryPageLinks === 0) {
+        gaps.push({
+            id: 'categoryScope',
+            draft: false,
+            problem: `${input.categories} product categories share ONE page — none of them points at a page ` +
+                'of its own, so /collections/{slug} serves the default template for every one. Nothing ' +
+                'on that template narrows the product feed to the category in the URL (the blog twin ' +
+                'auto-scopes; this one does not), so a shopper who picks a category sees the whole ' +
+                'catalogue, or one other category, on all of them.',
+            fix: 'Give each category its own page and set its product repeater to config ' +
+                '{ "collectionType": "collection", "collectionId": "<that category id>" }, then link ' +
+                'them in one call: sb_api_call post:/api/sites/{siteId}/page-links/bulk with body ' +
+                '{ "linkType": "productCategory", "linkIds": ["<category ids>"], "pageId": "<page id>" } ' +
+                '— one call per page, since each page is one category. sb_duplicate the template you ' +
+                'already have rather than rebuilding it.',
+        });
+    }
     return gaps;
 }
 export const READINESS_NOTICE = 'These are STORE gaps, not page defects: each one survives publish without a warning and is ' +

package/package.json

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