sbuilder-mcp 0.56.0 → 0.57.0

package/CHANGELOG.md

@@ -6,6 +6,12 @@ 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.57.0] - 2026-09-15
+
+### Added
+- `sb_review` now reports a `categoryPage` readiness gap when a store has product categories but no published page of the `category` type, since `/collections/{slug}` falls back to that template and every collection link, including the ones in the site's own menu, 404s without it.
+- `sb_review` now reports an `articleTemplate` readiness gap when a site has written blog articles but no published page of the `post` type, since `/blog/{slug}` falls back to that template and every article link, including the ones a listing page carries, 404s without it.
+
 ## [0.56.0] - 2026-09-15
 
 ### Added

package/CHANGELOG.vi.md

@@ -6,6 +6,12 @@ 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.57.0] - 2026-09-15
+
+### Added
+- `sb_review` giờ báo lỗi sẵn sàng `categoryPage` khi store có danh mục sản phẩm nhưng chưa có trang loại `category` nào được publish, vì `/collections/{slug}` sẽ dùng template đó, và mọi liên kết danh mục — kể cả những liên kết trong menu của chính site — sẽ trả về 404 nếu thiếu.
+- `sb_review` giờ báo lỗi sẵn sàng `articleTemplate` khi site đã viết bài blog nhưng chưa có trang loại `post` nào được publish, vì `/blog/{slug}` sẽ dùng template đó, và mọi liên kết bài viết — kể cả những liên kết trong trang danh sách bài viết — sẽ trả về 404 nếu thiếu.
+
 ## [0.56.0] - 2026-09-15
 
 ### Added

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, categoryList, pageLinks, formList] = await Promise.all([
+    const [pageList, gateways, shipping, globals, productList, categoryList, pageLinks, formList, articleList] = await Promise.all([
         get(`/api/sites/${site}/pages`),
         get(`/api/sites/${site}/payment-gateways`),
         get(`/api/sites/${site}/shipping-methods`),
@@ -48,6 +48,10 @@ export async function gatherReadiness(ctx, siteId, pageNodes) {
         // blindness is what let one page quietly become the site's whole account
         // area, which is the shape `mergedAuthPage` reports.
         get(`/api/sites/${site}/forms`),
+        // THE ARTICLES, for the same reason the products are read: /blog/{slug}
+        // resolves to the site's `post` template, so a site that has written
+        // articles and has no template 404s every one of them.
+        get(`/api/sites/${site}/articles?limit=1`),
     ]);
     // 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:
@@ -94,5 +98,8 @@ export async function gatherReadiness(ctx, siteId, pageNodes) {
         categories,
         categoryPageLinks,
         forms: formList?.forms ?? null,
+        articles: Array.isArray(articleList?.articles)
+            ? (articleList?.total ?? articleList.articles.length)
+            : null,
     };
 }

package/dist/domains/site/readiness.js

@@ -178,6 +178,31 @@ export function readinessGaps(input) {
             });
         }
     }
+    // ARTICLES WRITTEN AND NOTHING TO RENDER THEM IN.
+    //
+    // `post` is the ARTICLE template: /blog/{slug} resolves to the site's
+    // published page of that type, so a site that has written articles and has
+    // none 404s every single one — including the links its own listing page
+    // carries, which is the page that makes the articles findable in the first
+    // place.
+    //
+    // ASKED OF EVERY SITE, above the store gate: a blog is not a commerce
+    // feature, and a brochure site with a news section has exactly this problem.
+    // Gated on having WRITTEN something, so a site with no blog hears nothing.
+    if (pages && (input.articles ?? 0) > 0 && !published(pages, 'post')) {
+        const draft = drafted(pages, 'post');
+        gaps.push({
+            id: 'articleTemplate',
+            draft,
+            problem: `This site has ${input.articles} article${input.articles === 1 ? '' : 's'} and no ` +
+                'published page of the "post" type. /blog/{slug} needs one, so every article 404s — ' +
+                'including the links a listing page carries.',
+            fix: draft
+                ? 'Publish the article template page that already exists.'
+                : 'Create a page of type "post" and publish it. It opens seeded with the cover, ' +
+                    'headline, date and body an article cannot be read without.',
+        });
+    }
     if (!isStore(input))
         return gaps;
     if (pages && !published(pages, 'checkout')) {
@@ -219,6 +244,36 @@ export function readinessGaps(input) {
                 : 'Create a page of type "product" and publish it.',
         });
     }
+    // AND THE SAME HOLE ON THE OTHER SIDE OF THE CATALOGUE.
+    //
+    // `/collections/{slug}` resolves the same way /products/{slug} does — through
+    // PublishedForEntity, to the category's own page or to the DEFAULT TEMPLATE
+    // for the `category` type — so a store with categories and no published one
+    // 404s every collection link, including the ones its own menu carries.
+    //
+    // `categoryScope` below is a different defect and assumes this page EXISTS:
+    // it reports a template SHARED across categories, which is the complaint you
+    // can only make once there is a template to share. With none, every URL fails
+    // outright and the scope question does not arise.
+    //
+    // GATED ON HAVING CATEGORIES, unlike productPage. A store can genuinely sell
+    // without collections — one shop, one flat catalogue — and telling it to build
+    // a template for a thing it does not use is the nag this file keeps warning
+    // about. Silent when the count could not be read, like everything else here.
+    if (pages && (input.categories ?? 0) > 0 && !published(pages, 'category')) {
+        const draft = drafted(pages, 'category');
+        gaps.push({
+            id: 'categoryPage',
+            draft,
+            problem: `This store has ${input.categories} categor${input.categories === 1 ? 'y' : 'ies'} and no ` +
+                'published page of the "category" type. /collections/{slug} needs one, so every ' +
+                'collection link 404s — including the ones in the site\'s own menu.',
+            fix: draft
+                ? 'Publish the category template page that already exists.'
+                : 'Create a page of type "category" and publish it. It opens seeded with the collection ' +
+                    'title and a product repeater.',
+        });
+    }
     // NOTHING TO SELL. Checked before the delivery option, because a shipping
     // method for an empty catalogue is furniture.
     if (input.products) {

package/package.json

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