sbuilder-mcp 0.59.0 → 0.59.2

package/CHANGELOG.md

@@ -6,6 +6,23 @@ 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.59.2] - 2026-09-15
+
+### Fixed
+- The call sheet for creating or replacing a product now states, at the moment a price is written, that `priceCents`, `compareAtCents`, `costCents`, and a shipping method's `feeCents` are minor units divided by 100 on the storefront, instead of only as the fix for a readiness gap that clears the moment a product exists.
+- The call sheet now states that the variant picker renders from `product.attributes`, not from `variants[].options` alone, so a product with variants but no declared attributes no longer silently ships the element's seed options ("Color: Red / Green / Blue") on the published page.
+
+## [0.59.1] - 2026-09-15
+
+### Added
+- `sb_api_find` and `sb_api_call` now reach `POST /api/sites/{siteId}/ai/messages`, the editor's own AI assistant for a product, with its request shape (`question` plus a `history` of prior turns).
+- `sb_traits_for` now lists `articleSourceType` and `relationSlotKey` as controls on article-list repeaters, and both it and `sb_set` recognize `page_category` as a legal `articleSourceType` value and `page_collections` as a legal `collectionListType` value, so a single blog or collection template can render the category or collection the page itself names.
+- `list-dataset`'s generated empty-state table now seeds a `review` source ("No reviews yet"), so a review list repeater gets a styled empty state instead of none.
+
+### Changed
+- `sb_page_create` and `sb_template_use` now seed new collection-list pages with `collectionListType: "page_collections"` instead of `all_collections`, so a collection template's sub-collection grid follows the page it is on rather than listing every collection on the site.
+- The generated empty-state copy for collections, blog topics, and courses now reads "New … will show up here. Check back soon." instead of "… you create will show up here."
+
 ## [0.59.0] - 2026-09-15
 
 ### Added

package/CHANGELOG.vi.md

@@ -6,6 +6,23 @@ 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.59.2] - 2026-09-15
+
+### Fixed
+- Call sheet để tạo hoặc thay thế sản phẩm giờ nêu rõ, ngay tại thời điểm giá được ghi, rằng `priceCents`, `compareAtCents`, `costCents` và `feeCents` của một shipping method đều là đơn vị nhỏ nhất, được chia cho 100 trên storefront, thay vì chỉ xuất hiện như hướng khắc phục cho một lỗi sẵn sàng vốn biến mất ngay khi có sản phẩm.
+- Call sheet giờ nêu rõ bộ chọn variant hiển thị từ `product.attributes`, không phải chỉ từ `variants[].options`, nhờ đó một sản phẩm có variant nhưng chưa khai báo attributes sẽ không còn âm thầm hiển thị các tuỳ chọn gieo sẵn của phần tử ("Color: Red / Green / Blue") trên trang đã publish.
+
+## [0.59.1] - 2026-09-15
+
+### Added
+- `sb_api_find` và `sb_api_call` giờ với tới được `POST /api/sites/{siteId}/ai/messages`, trợ lý AI của chính editor dành cho một sản phẩm, cùng hình dạng request của nó (`question` và một `history` gồm các lượt hỏi đáp trước đó).
+- `sb_traits_for` giờ liệt kê `articleSourceType` và `relationSlotKey` là control trên các repeater danh sách bài viết, và cả nó lẫn `sb_set` đều nhận `page_category` là giá trị hợp lệ của `articleSourceType` và `page_collections` là giá trị hợp lệ của `collectionListType`, nhờ đó một template blog hoặc collection duy nhất có thể hiển thị đúng danh mục hoặc collection mà trang đó đại diện.
+- Bảng trạng thái rỗng sinh sẵn của `list-dataset` giờ gieo thêm nguồn `review` ("No reviews yet"), nên một repeater danh sách đánh giá có trạng thái rỗng được thiết kế riêng thay vì không có gì.
+
+### Changed
+- `sb_page_create` và `sb_template_use` giờ gieo các trang danh sách collection mới với `collectionListType: "page_collections"` thay vì `all_collections`, nên lưới sub-collection của một template collection sẽ theo đúng trang nó đang nằm trên đó thay vì liệt kê mọi collection của site.
+- Nội dung trạng thái rỗng sinh sẵn cho collection, chủ đề blog và khoá học giờ đọc là "New … will show up here. Check back soon." thay vì "… you create will show up here."
+
 ## [0.59.0] - 2026-09-15
 
 ### Added

package/README.md

@@ -112,7 +112,7 @@ in this client: one would put the very key the platform exists to hold back into
 | `sb_store` | Run a store flow that must happen in a fixed order — the four writes that make a working checkout, or any of the platform's 17 form templates (login, register, forgot, contact, subscribe …) with its own field document |
 | `sb_undo` | Put back what a PUT replaced. The SECOND answer for a page, not the only one: the platform has versions, history and restore (`sb_api_find` "page versions"), which outlive this process — reach for those first and use this for every other shaped PUT |
 
-Twenty-eight tools, **524 API operations** (175 of the 234 writes carrying a body shape read
+Twenty-eight tools, **525 API operations** (176 of the 235 writes carrying a body shape read
 off the handler), 113 elements, 79 binding sources. `sb_api_find`
 is an index rather than a tool per endpoint, so the tool list stays short while everything
 the platform can do stays reachable — and operations added to the platform arrive with the

package/README.vi.md

@@ -109,7 +109,7 @@ nhét ngược lại vào mọi bản cài.
 | `sb_store` | Chạy một luồng cửa hàng bắt buộc đúng thứ tự — bốn lệnh ghi tạo nên trang thanh toán, hoặc gieo bất kỳ template nào trong 17 form của nền tảng (login, register, forgot, contact, subscribe …) kèm field document của nó |
 | `sb_undo` | Trả lại thứ mà một lệnh PUT đã ghi đè. Với TRANG thì đây là đường về thứ hai chứ không phải duy nhất: nền tảng có version, history và restore (`sb_api_find` "page versions"), và chúng sống lâu hơn tiến trình này — hãy dùng chúng trước, còn tool này cho mọi PUT có hình dạng khác |
 
-Hai mươi tám tool, **524 operation API** (175 trong 234 lệnh ghi có hình dạng body đọc thẳng
+Hai mươi tám tool, **525 operation API** (176 trong 235 lệnh ghi có hình dạng body đọc thẳng
 từ handler), 113 element, 79 nguồn binding. `sb_api_find` là
 một chỉ mục chứ không phải mỗi endpoint một tool, nên danh sách tool vẫn ngắn trong khi mọi
 thứ nền tảng làm được vẫn với tới — và operation mới thêm bên nền tảng sẽ tự có sau lần

package/dist/catalog/api.generated.js

@@ -1,8 +1,8 @@
 export const SWAGGER_SOURCE = {
-    "operations": 524,
+    "operations": 525,
     "definitions": 107,
-    "bodyCarrying": 192,
-    "bodyUndescribed": 73,
+    "bodyCarrying": 193,
+    "bodyUndescribed": 74,
     "generatedFrom": "server/docs/swagger.json"
 };
 export const API_OPERATIONS = [
@@ -3321,6 +3321,41 @@ export const API_OPERATIONS = [
         "bodyRef": null,
         "credential": "siteScoped"
     },
+    {
+        "id": "post:/api/sites/{siteId}/ai/messages",
+        "method": "POST",
+        "path": "/api/sites/{siteId}/ai/messages",
+        "tags": [
+            "sites"
+        ],
+        "summary": "Ask the editor's AI assistant a question about this product",
+        "params": [
+            {
+                "name": "siteId",
+                "in": "path",
+                "required": true,
+                "type": "string",
+                "description": "Site ID"
+            },
+            {
+                "name": "Accept",
+                "in": "header",
+                "required": false,
+                "type": "string",
+                "description": "text/event-stream to receive the answer as it is written; anything else returns one JSON body"
+            },
+            {
+                "name": "message",
+                "in": "body",
+                "required": true,
+                "type": "object",
+                "description": "question (required) and history (prior turns: role user|assistant, text)"
+            }
+        ],
+        "bodyDescribed": false,
+        "bodyRef": null,
+        "credential": "siteScoped"
+    },
     {
         "id": "get:/api/sites/{siteId}/api-keys",
         "method": "GET",
@@ -18023,7 +18058,8 @@ export const API_DEFINITIONS = {
                 "description": "ZoneFees prices this method PER ZONE, keyed by zone id — the map behind\nFeeForZone. A zone with no entry falls back to FeeCents, so a merchant\nwho prices one method for one zone still has a working checkout for\nevery other combination.\n\nA MAP ON THE ROW rather than a method×zone table, and that is a\nconsidered exception to the normalise-everything rule: these fees are\nnever queried, sorted or aggregated on their own — every read wants them\nalongside the method they belong to — so a join table would buy a query\nnobody makes and cost one on every checkout.",
                 "type": "object",
                 "additionalProperties": {
-                    "type": "integer"
+                    "type": "integer",
+                    "format": "int64"
                 }
             }
         }

package/dist/catalog/deadkeys.generated.js

@@ -1,6 +1,6 @@
 export const DEAD_KEY_SOURCE = {
-    "files": 4247,
-    "identifiers": 77159,
+    "files": 4007,
+    "identifiers": 76941,
     "seededKeys": 384,
     "dead": 0
 };

package/dist/catalog/elements.generated.js

@@ -32181,7 +32181,7 @@ export const ELEMENTS = {
                 "collectionType": "all_products",
                 "collectionId": "all_products",
                 "articleCategoryId": "all_articles",
-                "collectionListType": "all_collections",
+                "collectionListType": "page_collections",
                 "listNavIcon": "ArrowLeftSLine",
                 "listNavPosition": "inside",
                 "listNavIconSize": 16,
@@ -33178,7 +33178,9 @@ export const ELEMENTS = {
                         "label": "Article",
                         "controls": [
                             "article_category",
-                            "articleCategoryId"
+                            "articleSourceType",
+                            "articleCategoryId",
+                            "relationSlotKey"
                         ]
                     },
                     {
@@ -33433,7 +33435,9 @@ export const ELEMENTS = {
             "paginationItemActiveBorderStyle",
             "paginationItemActiveBorderRadius",
             "article_category",
+            "articleSourceType",
             "articleCategoryId",
+            "relationSlotKey",
             "list_loading_mode",
             "list_load_more_label",
             "list_pager_style",
@@ -33513,8 +33517,9 @@ export const ELEMENTS = {
             "The dataset-block template — and every dataset node inside it — must carry the SAME config.datasetSource as this repeater. Each node reads its OWN key, so a collection list whose card omits it leaves that card on the product default: it binds product.url, no product context reaches a collection row, and the card publishes with no link, so clicking it does nothing",
             "config.datasetSource picks the ENTITY: \"product\" for a product list, \"category\" for a collection list. It is what derives the node's binding target (product::product_list / category::collection_list)",
             "Product lists: config.collectionType \"page_collection\" renders THE COLLECTION THE PAGE IS (the one /collections/{slug} named) so a single collection template serves every collection, \"all_products\" renders the whole catalog and narrows to the page collection on a collection template, \"collection\" renders the one named by config.collectionId, \"related\" renders the PAGE PRODUCT's neighbours — the products sharing one of its collections, minus itself",
+            "Article lists: config.articleSourceType \"page_category\" renders THE BLOG CATEGORY THE PAGE IS (the one /blog-categories/{slug} named) so a single blog template serves every category — off a blog template it shows every article; \"category\" filters by config.articleCategoryId (the \"all_articles\" sentinel means no filter, and on a blog template it narrows to the page category anyway); \"slot\" renders a curated shelf, the rows filed by hand under config.relationSlotKey",
             "Use \"related\" for a cross-sell shelf on a product page (\"Sản phẩm liên quan\" / \"You may also like\"). It reads no collectionId — its axis is whatever collections the page product is filed under — and it renders nothing on a page that names no product, so pair it with an emptyStateId if the section must never be blank",
-            "Collection lists: config.collectionListType \"all_collections\" renders every collection; \"custom_collections\" renders specials.collectionIds, in that order",
+            "Collection lists: config.collectionListType \"page_collections\" renders THE SUB-COLLECTIONS OF THE COLLECTION THE PAGE IS (the one /collections/{slug} named), so a single collection template draws every collection's browse grid — off a collection template it shows every collection instead; \"all_collections\" renders every collection; \"custom_collections\" renders specials.collectionIds, in that order",
             "config.quantity caps how many records render; config.itemsPerRow is the row size (grid columns / slide page size) and style.gap is the space between cards — both are per-breakpoint",
             "config.layout \"grid\" for a multi-row grid, \"slide\" for row-by-row carousel behaviour",
             "Navigation and pagination only matter when layout is \"slide\". The arrows exist while config.listNavIcon names an icon (clearing it turns them off); the dots exist while paginationItemWidth and paginationItemHeight are both above 0",
@@ -36419,7 +36424,7 @@ export const SATELLITE_RULES = {
                                 "textAlign": "center"
                             },
                             "specials": {
-                                "text": "Collections you create will show up here."
+                                "text": "New collections will show up here. Check back soon."
                             }
                         }
                     ]
@@ -36505,7 +36510,7 @@ export const SATELLITE_RULES = {
                                 "textAlign": "center"
                             },
                             "specials": {
-                                "text": "Topics you create will show up here."
+                                "text": "New topics will show up here. Check back soon."
                             }
                         }
                     ]
@@ -36548,7 +36553,50 @@ export const SATELLITE_RULES = {
                                 "textAlign": "center"
                             },
                             "specials": {
-                                "text": "Courses you publish will show up here."
+                                "text": "New courses will show up here. Check back soon."
+                            }
+                        }
+                    ]
+                },
+                "review": {
+                    "type": "list-empty",
+                    "children": [
+                        {
+                            "type": "icon",
+                            "style": {
+                                "color": "#d4d4d4"
+                            },
+                            "config": {
+                                "iconSize": 32
+                            },
+                            "specials": {
+                                "name": "ChatQuoteLine"
+                            }
+                        },
+                        {
+                            "type": "heading",
+                            "style": {
+                                "width": "auto",
+                                "fontSize": "20px",
+                                "fontWeight": "600",
+                                "color": "#171717",
+                                "textAlign": "center"
+                            },
+                            "specials": {
+                                "htmlTag": "h3",
+                                "text": "No reviews yet"
+                            }
+                        },
+                        {
+                            "type": "text",
+                            "style": {
+                                "width": "auto",
+                                "fontSize": "14px",
+                                "color": "#737373",
+                                "textAlign": "center"
+                            },
+                            "specials": {
+                                "text": "Reviews will show up here once customers leave them."
                             }
                         }
                     ]
@@ -36836,6 +36884,7 @@ export const CONFIG_VALUES = {
     "articleSourceType": {
         "values": [
             "category",
+            "page_category",
             "slot"
         ],
         "fallback": "category",
@@ -36845,7 +36894,8 @@ export const CONFIG_VALUES = {
     "collectionListType": {
         "values": [
             "all_collections",
-            "custom_collections"
+            "custom_collections",
+            "page_collections"
         ],
         "fallback": "all_collections",
         "aliases": {},

package/dist/catalog/search.js

@@ -352,7 +352,7 @@ export function describeOperation(op) {
                 '/apps/blocks again for what it contributed.',
         };
     }
-    // FILLING A CATALOGUE WAS REACHABLE AND THREE FACTS ABOUT IT WERE NOT, each
+    // FILLING A CATALOGUE WAS REACHABLE AND FIVE FACTS ABOUT IT WERE NOT, each
     // failing silently. Attached to the call sheet for the same reason the
     // translation table is: this is where the agent is when it decides what to
     // send, on both credential surfaces a product can be created or replaced on.
@@ -360,6 +360,37 @@ export function describeOperation(op) {
         out.product_traps = {
             price: 'Price lives on the VARIANT, not the product — variants[].priceCents. A product ' +
                 'posted with no variant renders a catalogue entry nobody can buy.',
+            // MINOR UNITS, SAID WHERE THE NUMBER IS BEING WRITTEN.
+            //
+            // The fact was already in the codebase — `readiness.ts` carries it twice —
+            // but only as the FIX on a store gap that fires when the catalogue is
+            // EMPTY or has no priced product. The moment an agent creates products the
+            // gap clears, so the sentence is on screen exactly while it cannot be
+            // acted on and gone the moment it could be.
+            //
+            // MEASURED: a whole storefront built with every price 100× low. Cherry at
+            // "8.500 ₫", a 3.2M gift basket at "32.000 ₫" — read back through the
+            // renderer, published, and only caught because the numbers looked absurd
+            // to a human. Nothing refused them: `priceCents` takes any integer, and a
+            // store whose every price is wrong by the same factor looks internally
+            // consistent.
+            units: 'priceCents is MINOR UNITS — the storefront divides by 100, so VND 280.000 is ' +
+                "28000000. Same for compareAtCents, costCents and a shipping method's feeCents. " +
+                'Nothing refuses a wrong one, and every price wrong by the same factor looks ' +
+                'deliberate. Write one, read the rendered price, then write the rest.',
+            // THE PICKER A PRODUCT GETS WHEN NOBODY DECLARED ITS OPTIONS.
+            //
+            // `variants[].options` alone is not enough: the buy box reads
+            // `attributes` for the control, and a product with variants but no
+            // attributes renders the ELEMENT'S SEED — "Color: Red / Green / Blue",
+            // "Size: S / M / L" — on a real product page, published.
+            //
+            // MEASURED on a fruit-gift store: every one of 19 products offered Color
+            // and Size until attributes were added.
+            attributes: 'The variant picker comes from product.attributes — [{ name, values[] }] — not ' +
+                "from variants[].options alone. Variants without attributes render the element's " +
+                'seed ("Color: Red / Green / Blue") on the published page. Declare attributes, and ' +
+                "match each variant's options keys to them.",
             slug: 'A colliding slug is RENAMED, not refused, and the write still answers 200/201. ' +
                 'Re-running an import does not error — it DOUBLES the catalogue in silence.',
             images: 'POST /api/media/{siteId}/from-url ingests a photo straight from its URL, one hop ' +

package/dist/catalog/shapes.generated.js

@@ -1,10 +1,10 @@
 export const SHAPE_SOURCE = {
-    "writeOperations": 234,
-    "shaped": 175,
-    "fromHandlers": 175,
+    "writeOperations": 235,
+    "shaped": 176,
+    "fromHandlers": 176,
     "fromSwaggerOnly": 0,
     "withReadOnly": 26,
-    "structsRead": 1671
+    "structsRead": 1678
 };
 export const REQUEST_SHAPES = {
     "post:/api/sites/{siteId}/api-keys": {
@@ -2998,6 +2998,21 @@ export const REQUEST_SHAPES = {
             "updatedAt"
         ]
     },
+    "post:/api/sites/{siteId}/ai/messages": {
+        "fields": [
+            {
+                "name": "question",
+                "type": "string"
+            },
+            {
+                "name": "history",
+                "type": "llm.Turn[]",
+                "note": "History is sent by the CLIENT, unlike the storefront chatbot's, which removed it as a security fix."
+            }
+        ],
+        "source": "go",
+        "goType": "(inline)"
+    },
     "post:/api/sites/{siteId}/fonts": {
         "fields": [
             {

package/dist/catalog/storepages.generated.js

@@ -675,7 +675,7 @@ export const PAGE_LAYOUT_SEEDS = {
                     "collectionType": "all_products",
                     "collectionId": "all_products",
                     "articleCategoryId": "all_articles",
-                    "collectionListType": "all_collections",
+                    "collectionListType": "page_collections",
                     "listNavIcon": "ArrowLeftSLine",
                     "listNavPosition": "inside",
                     "listNavIconSize": 16,
@@ -2411,7 +2411,7 @@ export const STORE_PAGE_SEEDS = {
                     "collectionType": "all_products",
                     "collectionId": "all_products",
                     "articleCategoryId": "all_articles",
-                    "collectionListType": "all_collections",
+                    "collectionListType": "page_collections",
                     "listNavIcon": "ArrowLeftSLine",
                     "listNavPosition": "inside",
                     "listNavIconSize": 16,
@@ -3109,7 +3109,7 @@ export const STORE_PAGE_SEEDS = {
                     "collectionType": "all_products",
                     "collectionId": "all_products",
                     "articleCategoryId": "all_articles",
-                    "collectionListType": "all_collections",
+                    "collectionListType": "page_collections",
                     "listNavIcon": "ArrowLeftSLine",
                     "listNavPosition": "inside",
                     "listNavIconSize": 16,
@@ -3813,7 +3813,7 @@ export const STORE_PAGE_SEEDS = {
                     "collectionType": "all_products",
                     "collectionId": "all_products",
                     "articleCategoryId": "all_articles",
-                    "collectionListType": "all_collections",
+                    "collectionListType": "page_collections",
                     "listNavIcon": "ArrowLeftSLine",
                     "listNavPosition": "inside",
                     "listNavIconSize": 16,

package/package.json

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