sbuilder-mcp 0.46.0 → 0.46.1

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.46.1] - 2026-09-14
+
+### Fixed
+- sb_remove's dry run now reports removing as an actual node count instead of the total patch count, which was off by one in the ordinary case because deleting a subtree also emits one extra patch to unlink it from its parent's child list; the raw patch count is still available under the new patches field.
+
 ## [0.46.0] - 2026-09-14
 
 ### Added

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.46.1] - 2026-09-14
+
+### Fixed
+- Dry run của sb_remove giờ báo removing là số node thực sự thay vì tổng số patch, vốn bị lệch một do việc xoá một subtree còn phát sinh thêm một patch để gỡ nó khỏi danh sách con của node cha; tổng số patch thô vẫn có sẵn qua trường patches mới.
+
 ## [0.46.0] - 2026-09-14
 
 ### Added

package/dist/tools/page.js

@@ -684,8 +684,26 @@ export function registerPageTools(server, ctx) {
     }, async ({ id, dry_run }) => {
         const d = session.current();
         const patches = removeNode(d, id);
+        // NODES, NOT PATCHES — this reported `patches.length` and the field is
+        // called `removing` on a tool whose description is "Remove a node and its
+        // whole subtree", so every caller reads it as a node count.
+        //
+        // It is off by one in the ORDINARY case and exact in the rare one, which
+        // is the worst arrangement available: `removeNode` emits one `unset` per
+        // doomed node PLUS one `remove` that takes the id out of its parent's
+        // child list — and that second patch exists only when the parent is still
+        // in the document. A childless section under ROOT therefore reported 2,
+        // and a four-node subtree whose parent had already been deleted reported
+        // 4 and was right. Both numbers were believed here: the 2 was read as
+        // evidence of a hidden node attached by `parent` alone, and a page-source
+        // dump then proved no such node exists.
+        //
+        // The doomed set is exactly the `unset` patches that name a node
+        // directly; the parent-list patch is an `insert`/`remove` four segments
+        // deep, so length is what separates them without re-deriving the walk.
+        const nodes = patches.filter((p) => p.op === 'unset' && p.path.length === 2).length;
         if (dry_run !== false)
-            return text({ dry_run: true, removing: patches.length });
+            return text({ dry_run: true, removing: nodes, patches: patches.length });
         await session.applyAndSave(patches);
         return text({ removed: id, rev: d.rev });
     });

package/package.json

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