@oneentry/mcp-platform-server 0.1.11 → 0.1.12

package/dist/api/operation-notes.js

@@ -190,38 +190,63 @@ export const OPERATION_NOTES = {
     },
     AdminMenusController_updatePosition: {
         example: {
-            position: { leftObjectId: null, rightObjectId: null },
+            position: {
+                leftObjectId: 459,
+                leftObjectType: 'menu-custom-item',
+                rightObjectId: 4,
+                rightObjectType: 'menu-page',
+            },
             newParentId: 12,
             newParentType: 'custom',
         },
         note: '"position" is required even when the order does not matter, and it must be an object: a ' +
             'body without it answers 400 naming the field, and an empty object is not enough — send ' +
             '{ leftObjectId: null, rightObjectId: null }. Both re-parenting and sibling order apply, ' +
-            'and a public read returns the items in that order. Neighbours are addressed by the id of ' +
-            'the item, not of its position, and page items and custom items are numbered separately: ' +
-            'in a mixed row name each neighbour with "leftObjectType" and "rightObjectType", or a ' +
-            'neighbour of the other kind is not found and the item lands at the edge of the list. ' +
-            '"newParentType" says which kind the new parent is; omit it and the number is looked up ' +
-            'among pages first, which is not necessarily the parent you meant.',
+            'and a public read returns the items in that order — the order is reproducible, for a row ' +
+            'of pages and for a mixed row alike. Neighbours are addressed by the id of the item, not ' +
+            'of its position, and page items and custom items are numbered separately, so in a mixed ' +
+            'row each neighbour is named with its kind. The body then carries TWO different ' +
+            'vocabularies for "kind", and that is where this operation is lost: ' +
+            '"leftObjectType" / "rightObjectType" take the object type of the position record — ' +
+            '"menu-page" or "menu-custom-item" — while "newParentType" takes "page" or "custom". ' +
+            'Sending "page" or "custom" as a neighbour kind is not refused: the neighbour is not ' +
+            'resolved, the moved item\'s rank is reset to the middle of the range and the answer is ' +
+            'still 200, so the resulting order can look intended and be arbitrary. Omit the neighbour ' +
+            'kinds only in a row of one kind — then each neighbour is read as the kind of the item ' +
+            'being moved. Omit "newParentType" and the number is looked up among pages first, which ' +
+            'is not necessarily the parent you meant. Omitting "position" while changing the parent ' +
+            'leaves the order alone.',
         verifyWith: {
             opId: 'AdminMenusController_findOne',
-            check: 'the parent of the item you moved, its parentType, and the order of its siblings',
-            why: 'a neighbour or parent resolved to the other kind answers success and moves it elsewhere',
+            check: 'the lexorank of the item you moved against its two neighbours\', and its parent ' +
+                'and parentType',
+            why: 'an unresolved neighbour answers 200 and resets the rank to the middle of the range, ' +
+                'which the order alone can still show as the one you asked for',
         },
     },
     AdminMenusController_updateCustomItemPosition: {
         example: {
-            position: { leftObjectId: null, rightObjectId: null },
+            position: {
+                leftObjectId: 3,
+                leftObjectType: 'menu-page',
+                rightObjectId: 4,
+                rightObjectType: 'menu-page',
+            },
             newParentId: 12,
             newParentType: 'custom',
         },
         note: 'Same body as AdminMenusController_updatePosition: "position" is required and must be an ' +
             'object — { leftObjectId: null, rightObjectId: null } when the order does not matter — and ' +
-            'the kind of every neighbour and of the new parent is named alongside its number.',
+            'the kind of every neighbour and of the new parent is named alongside its number, in the ' +
+            'two vocabularies that body uses: "menu-page" / "menu-custom-item" for a neighbour, ' +
+            '"page" / "custom" for the new parent. A custom item does move in among pages this way; ' +
+            'a neighbour kind the instance does not know is not refused but resets the rank.',
         verifyWith: {
             opId: 'AdminMenusController_findOne',
-            check: 'the parent of the item you moved, its parentType, and the order of its siblings',
-            why: 'a neighbour or parent resolved to the other kind answers success and moves it elsewhere',
+            check: 'the lexorank of the item you moved against its two neighbours\', and its parent ' +
+                'and parentType',
+            why: 'an unresolved neighbour answers 200 and resets the rank to the middle of the range, ' +
+                'which the order alone can still show as the one you asked for',
         },
     },
     AdminFormsController_create: {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@oneentry/mcp-platform-server",
-  "version": "0.1.11",
+  "version": "0.1.12",
   "description": "MCP server that lets an AI agent operate the OneEntry Admin API, grounded in the project's own rules",
   "license": "MIT",
   "type": "module",