openxiangda 1.0.12 → 1.0.13

package/lib/cli.js

@@ -1945,17 +1945,17 @@ function resolvePagePermissionMenuTargets(bound, flags = {}) {
 
 function resolveMenuPermissionTargets(bound, menuCode) {
   const menuEntry = bound.resources?.menus?.[menuCode];
-  const menuId = resolveMenuId(bound, menuCode);
   if (menuEntry?.formUuid) return [menuEntry.formUuid];
-  return [menuId];
+  if (menuEntry?.pageId) return [menuEntry.pageId];
+  return [resolveMenuId(bound, menuCode)];
 }
 
 function resolvePagePermissionTargets(bound, pageCode) {
   const menuEntry = findPagePermissionMenuEntry(bound, pageCode);
-  if (menuEntry?.menuId) {
-    return [menuEntry.menuId];
+  if (menuEntry?.pageId) {
+    return [menuEntry.pageId];
   }
-  fail(`页面 ${pageCode} 未找到已绑定菜单。请先发布/创建菜单，或直接传 --menu-codes/--menu-ids。`);
+  fail(`页面 ${pageCode} 未找到已绑定代码页菜单。请先发布/创建菜单，或直接传 --menu-form-uuids/--menu-ids。`);
 }
 
 function resolvePagePermissionRuntimeAliasTargets(bound, flags = {}) {
@@ -2001,9 +2001,11 @@ function resolveCodePagePermissionAliases(bound, menuEntry = {}, pageCode) {
   });
   return unique([
     pageCode,
+    menuEntry.menuId,
     menuEntry.pageCode,
     menuEntry.routeKey,
     menuEntry.legacyFormUuid,
+    pageEntry?.pageId,
     pageEntry?.pageCode,
     pageEntry?.routeKey,
     pageEntry?.legacyFormUuid,

package/openxiangda-skills/references/openxiangda-api.md

@@ -369,11 +369,11 @@ Body:
 {
   "name": "销售可见页面",
   "roles": ["sales"],
-  "menuFormUuids": ["FORM_XXX", "MENU_ID_FOR_CODE_PAGE"]
+  "menuFormUuids": ["FORM_XXX", "PAGE_ID_FOR_CODE_PAGE"]
 }
 ```
 
-An empty `menuFormUuids` array means all menus/pages are visible to the matched roles. For form menus this field can contain form UUIDs. For custom code page menus, the user-facing permission group should contain only the actual menu ID used by the platform admin tree. Because the current `/view` runtime guard also checks route keys and legacy `PAGE_...` aliases, OpenXiangda CLI `--page-codes` / `--menu-codes` creates a companion `（运行时别名）` page permission group for those aliases instead of mixing them into the editable menu group.
+An empty `menuFormUuids` array means all menus/pages are visible to the matched roles. For form menus this field can contain form UUIDs. For custom code page menus, the user-facing permission group should contain the code page `pageId`, which is what the platform permission editor uses for tree check state. Because the current `/view` runtime guard also checks menu IDs, route keys, and legacy `PAGE_...` aliases, OpenXiangda CLI `--page-codes` / `--menu-codes` creates a companion `（运行时别名）` page permission group for those aliases instead of mixing them into the editable menu group.
 
 ### GET `/apps/:appType/page-permission-groups/:groupId`
 

package/openxiangda-skills/references/permissions-settings.md

@@ -20,25 +20,25 @@ Role IDs are platform-specific. Store them only in `.openxiangda/state.json` und
 
 Page permission groups map role codes to visible menu targets. Form menus use their `FORM_...`
 form UUIDs. Custom code page/display menus need split targets because current platform
-surfaces check different identifiers: the admin edit tree expects menu IDs, while `/view`
-runtime checks route keys and legacy `PAGE_...` aliases.
+surfaces check different identifiers: the admin edit tree expects page IDs, while `/view`
+runtime checks menu IDs, route keys, and legacy `PAGE_...` aliases.
 
 ```json
 {
   "name": "销售页面",
   "roles": ["sales"],
-  "menuFormUuids": ["FORM_CUSTOMER", "FORM_ORDER", "MENU_ID_FOR_CODE_PAGE"]
+  "menuFormUuids": ["FORM_CUSTOMER", "FORM_ORDER", "PAGE_ID_FOR_CODE_PAGE"]
 }
 ```
 
-For custom code pages, keep the user-facing group editable by storing only menu IDs, then add a
+For custom code pages, keep the user-facing group editable by storing only page IDs, then add a
 companion runtime alias group with the same roles:
 
 ```json
 {
   "name": "销售页面（运行时别名）",
   "roles": ["sales"],
-  "menuFormUuids": ["CODE_PAGE_ROUTE_KEY", "PAGE_LEGACY_FORM_UUID"]
+  "menuFormUuids": ["MENU_ID_FOR_CODE_PAGE", "CODE_PAGE_ROUTE_KEY", "PAGE_LEGACY_FORM_UUID"]
 }
 ```
 
@@ -47,7 +47,7 @@ Rules:
 - `roles: []` means all roles can match.
 - `menuFormUuids: []` means all menus/pages are visible to matched roles.
 - Prefer `--form-codes` in CLI for form menus so each profile resolves its own form UUIDs.
-- Prefer `--page-codes` or `--menu-codes` in CLI for custom code page menus. The CLI writes menu IDs to the editable group and creates the companion `（运行时别名）` group automatically.
+- Prefer `--page-codes` or `--menu-codes` in CLI for custom code page menus. The CLI writes page IDs to the editable group and creates the companion `（运行时别名）` group automatically.
 
 ## Form Permission Groups
 

package/openxiangda-skills/skills/openxiangda-permission-settings/SKILL.md

@@ -43,7 +43,7 @@ openxiangda permission page-group-create sales_pages --name "销售页面" --rol
 openxiangda permission page-group-create portal_pages --name "门户页面" --page-codes portal_pc,portal_mobile --profile dev
 ```
 
-Use `--page-codes` or `--menu-codes` for custom code page menus; the CLI resolves code pages to the published menu ID plus the route key and legacy `PAGE_...` alias required by the platform's current admin tree, `/view` guard, and custom-page bootstrap checks. Use `--form-codes` for form menus; the CLI resolves forms to profile-local form UUIDs. Empty target lists mean all menus/pages are visible to matched roles.
+Use `--page-codes` or `--menu-codes` for custom code page menus; the CLI resolves the editable permission group to the published code page `pageId`, and creates a companion `（运行时别名）` group for the menu ID, route key, and legacy `PAGE_...` alias required by the platform's current `/view` guard and custom-page bootstrap checks. Use `--form-codes` for form menus; the CLI resolves forms to profile-local form UUIDs. Empty target lists mean all menus/pages are visible to matched roles.
 
 ## Form Permission Groups
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "openxiangda",
-  "version": "1.0.12",
+  "version": "1.0.13",
   "description": "OpenXiangda CLI, workspace build tools, runtime SDK, and form components.",
   "private": false,
   "bin": {