openxiangda-skill-kit 2.0.0-alpha.75 → 2.0.0-alpha.77

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "openxiangda-skill-kit",
-  "version": "2.0.0-alpha.75",
+  "version": "2.0.0-alpha.77",
   "description": "Validation and deterministic packaging for OpenXiangda 2.0 AI skills.",
   "type": "module",
   "main": "./dist/index.js",
@@ -17,7 +17,7 @@
     "README.md"
   ],
   "dependencies": {
-    "openxiangda-devkit-core": "2.0.0-alpha.57"
+    "openxiangda-devkit-core": "2.0.0-alpha.59"
   },
   "devDependencies": {
     "tsx": "4.23.12",

package/skills/openxiangda-v2/references/data-authz.md

@@ -39,7 +39,7 @@ const visitorReservations = {
     },
     {
       code: 'attachments', type: 'file', label: '附件',
-      file: { multiple: true, maxCount: 5, maxSizeMb: 20, accept: ['image/*', '.pdf'] },
+      file: { maxCount: 5, maxSizeMb: 20, accept: ['image/*', '.pdf'] },
     },
     {
       code: 'internalNote', type: 'text.long', label: '内部备注',
@@ -56,14 +56,16 @@ Put it in `data: { resources: [visitorReservations] }`. Resource CRUD
 capabilities are derived by `resourceCapabilityCodes`; grant the needed values
 to roles. Directory-backed roles also require
 `app:<app-code>:directory:read`. Explicit field `access` capability codes are
-also granted only to the intended roles.
+also granted only to the intended roles. They are owned and exported by the
+generated field policy, so do not repeat them in `authz.capabilities`.
+`authz.capabilities` contains only explicit `backend` or `ui` capabilities.
 
 `required: true` owns both storage nullability and form validation. A field
 without `access` inherits the resource read/create/update capability. Each
 access array is all-of; `false` is explicit deny. The same arrays drive the
 generated UI and platform field policies.
 
-Field types are semantic, not PostgreSQL storage aliases. Use the catalog in the generated `AGENTS.md`: for example `text.short`, `number.integer`, `user.single`, `department.multiple`, `resource-ref.single`, `file`, `address` and `subtable`. The compiler alone chooses storage columns and constraints. Reference fields store complete labeled snapshots; resource references additionally declare their source and snapshot fields. File limits exist only under `file` and use `maxSizeMb`.
+Field types are semantic, not PostgreSQL storage aliases. Use the catalog in the generated `AGENTS.md`: for example `text.short`, `number.integer`, `user.single`, `department.multiple`, `resource-ref.single`, `file`, `address` and `subtable`. The compiler alone chooses storage columns and constraints. Reference fields store complete labeled snapshots; resource references additionally declare their source and snapshot fields. File limits exist only under `file`; `maxCount` owns the single/multiple bound and `maxSizeMb` owns the per-file size bound. There is no `file.multiple` key.
 
 Do not author raw schema or storage words as field types. `string`, `text`,
 `integer`, `decimal`, `boolean`, `date`, `datetime`, `uuid`, `json` and `file`
@@ -80,7 +82,7 @@ currentUserDataPolicy({
   code: 'reservation-host',
   name: '接待人员仅查看本人预约',
   resourceCode: 'visitor-reservations',
-  field: 'hostUserId.value',
+  field: 'hostUserId',
   roleCodes: ['reception_staff'],
   unrestrictedRoleCodes: ['visitor_admin'],
 })
@@ -88,6 +90,8 @@ currentUserDataPolicy({
 
 Put that value in `authz.dataPolicies`, declare both roles, and set the
 resource `dataPolicyCode` to the same code. Do not invent `operator`, `value`,
-`current_user: true`, lowercase match modes, or policy-level `roleCodes`.
+`current_user: true`, lowercase match modes, a dotted value path, or
+policy-level `roleCodes`. The compiler and platform know that `user.*` fields
+compare their stable `value`; `field` remains the declared field root code.
 
 Run `pnpm openxiangda check` after every declaration or permission change.