openxiangda-cli 2.0.0-alpha.69 → 2.0.0-alpha.70

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "openxiangda-cli",
-  "version": "2.0.0-alpha.69",
+  "version": "2.0.0-alpha.70",
   "description": "Thin application-level CLI for OpenXiangda 2.0.",
   "type": "module",
   "main": "./dist/index.js",
@@ -23,9 +23,9 @@
   ],
   "dependencies": {
     "@oclif/core": "4.13.3",
-    "openxiangda-contracts": "2.0.0-alpha.32",
-    "openxiangda-devkit-core": "2.0.0-alpha.42",
-    "openxiangda-mcp": "2.0.0-alpha.42"
+    "openxiangda-contracts": "2.0.0-alpha.33",
+    "openxiangda-devkit-core": "2.0.0-alpha.43",
+    "openxiangda-mcp": "2.0.0-alpha.43"
   },
   "devDependencies": {
     "tsx": "4.23.12",

package/template/AGENTS.md

@@ -9,5 +9,6 @@
 - Use the current logged-in user and the union of application roles. Do not select RoleSession, persist platform Token or implement a second authorization path.
 - Declare restricted field read, create and update permissions explicitly. There is no `write` fallback; generated update permission is denied unless explicitly granted.
 - Desktop and mobile pages share values, validation and authorization, but use separate renderers. Members, departments, resources and attachments use platform-owned selectors and stable IDs.
+- A single directory user reference uses a `string` field; a single department or same-app resource reference uses `uuid`; every `multiple: true` reference uses `json`. Roles that consume directory-backed fields explicitly include `app:<app-code>:directory:read`.
 - Do not add compatibility aliases, migration branches or silent fallbacks for an earlier 2.0 alpha contract. Replace an incorrect contract and regenerate the application.
 - Run `pnpm openxiangda check` after contract changes. Deploy with `pnpm openxiangda deploy`, inspect with `pnpm openxiangda status` and `pnpm openxiangda logs`, and use the platform rollback command rather than mutating K3s directly.

package/template/README.md

@@ -9,7 +9,7 @@ cd visitor-reservations
 pnpm openxiangda dev
 ```
 
-在 `platform/data` 中声明 `DataResource` 和字段即可生成标准后台列表、筛选、表单、详情、审计、文件上传和独立移动端页面。成员、部门和资源关系分别使用 `reference: { kind: 'directory-user' }`、`directory-department`、`resource`，只保存稳定 ID，不复制目录数据。
+在 `platform/data` 中声明 `DataResource` 和字段即可生成标准后台列表、筛选、表单、详情、审计、文件上传和独立移动端页面。成员、部门和资源关系分别使用 `reference: { kind: 'directory-user' }`、`directory-department`、`resource`，只保存稳定 ID，不复制目录数据。单选成员字段使用 `string`，单选部门和资源引用使用 `uuid`，多选引用统一使用 `json`。需要目录选择器的业务角色必须显式拥有 `app:<app-code>:directory:read` 能力。
 
 所有 CRUD 位于 `apps/web/src/platform-client.ts` 的 Data API adapter；Nest 只在需要复杂事务或外部集成时增加 App API。选择器显式携带当前环境、使用同源 Cookie，浏览器不读取 Token，也不发送 RoleSession header。
 

package/template/apps/server/package.json

@@ -15,7 +15,7 @@
     "@nestjs/common": "11.1.29",
     "@nestjs/core": "11.1.29",
     "@nestjs/platform-fastify": "11.1.29",
-    "openxiangda-nest": "2.0.0-alpha.38",
+    "openxiangda-nest": "2.0.0-alpha.39",
     "reflect-metadata": "0.2.2",
     "rxjs": "7.8.2"
   },

package/template/apps/web/package.json

@@ -16,7 +16,7 @@
     "antd": "6.4.3",
     "dayjs": "1.11.18",
     "docx-preview": "0.3.7",
-    "openxiangda-contracts": "2.0.0-alpha.32",
+    "openxiangda-contracts": "2.0.0-alpha.33",
     "react": "19.2.8",
     "react-dom": "19.2.8",
     "react-router-dom": "7.8.2",

package/template/package.json

@@ -22,9 +22,9 @@
     "build": "pnpm --recursive build"
   },
   "devDependencies": {
-    "openxiangda-cli": "2.0.0-alpha.69",
-    "openxiangda-contracts": "2.0.0-alpha.32",
-    "openxiangda-devkit-core": "2.0.0-alpha.42",
+    "openxiangda-cli": "2.0.0-alpha.70",
+    "openxiangda-contracts": "2.0.0-alpha.33",
+    "openxiangda-devkit-core": "2.0.0-alpha.43",
     "typescript": "5.9.3"
   }
 }