openxiangda-skill-kit 2.0.0-alpha.116 → 2.0.0-alpha.118

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "openxiangda-skill-kit",
3
- "version": "2.0.0-alpha.116",
3
+ "version": "2.0.0-alpha.118",
4
4
  "description": "Validation and deterministic packaging for OpenXiangda 2.0 AI skills.",
5
5
  "type": "module",
6
6
  "main": "./dist/index.js",
@@ -17,7 +17,7 @@
17
17
  "README.md"
18
18
  ],
19
19
  "dependencies": {
20
- "openxiangda-devkit-core": "2.0.0-alpha.94"
20
+ "openxiangda-devkit-core": "2.0.0-alpha.96"
21
21
  },
22
22
  "devDependencies": {
23
23
  "tsx": "4.23.12",
@@ -175,3 +175,13 @@ Generated contracts intentionally emit each resource Surface once in
175
175
  `resourceSurfaces`; `resourceDefinitions[code].surface` references that shared
176
176
  object. Import the generated runtime definitions normally. Do not serialize,
177
177
  inline or duplicate Surface literals in application code.
178
+
179
+ The standard Workflow detail renderers consume only the authoritative Surface:
180
+ `presentation.businessDetail`, `presentation.summary`, the typed timeline and
181
+ operation descriptors. Continue to use `SurfaceFieldValue` for complete field
182
+ semantics and the Workflow-scoped file client for attachments, rich-text images
183
+ and signatures. Keep desktop and mobile renderers structurally independent;
184
+ place decision actions in the fixed primary group, all low-frequency actions in
185
+ the single more-actions entry, and collect comments in the action confirmation
186
+ layer. Do not copy the standard page into an application merely to show full
187
+ business fields or rearrange platform-owned operations.
@@ -154,6 +154,23 @@ channel snapshots. Omitting `detailRouteCode` keeps the standard pages. A
154
154
  declared but missing or incompatible route fails closed rather than falling
155
155
  back silently.
156
156
 
157
+ When `detailRouteCode` is omitted, use the platform standard detail page. Its
158
+ Surface carries `presentation.businessDetail`, pinned to the instance Data
159
+ logical revision, declaration digest, physical resource and requested record
160
+ revision, then filtered by the current user's field policy. Parent and subtable
161
+ resources stay on that same logical revision and each subtable is bounded to
162
+ 200 rows. Render the provided summary, full field Surface, typed timeline and
163
+ server-owned operation descriptors; do not infer labels, operation hierarchy
164
+ or field semantics from codes in application code. Desktop and mobile have
165
+ independent renderers, low-frequency operations live under one more-actions
166
+ entry, and comments are collected only after an operation is selected.
167
+
168
+ Files, rich-text images and signatures on this page use only the Workflow
169
+ instance-scoped preview/content client. Every request is rebound to the current
170
+ principal, authorized instance, projected resource/record/field and managed
171
+ file id. Never substitute the ordinary Data API file route or put credentials
172
+ in a file URL.
173
+
157
174
  Standard launch entry is also a platform Surface. Desktop uses
158
175
  `/admin/workflows/:workflowCode/new` and mobile uses
159
176
  `/m/workflows/:workflowCode/start`; both first load
@@ -204,4 +221,4 @@ Use Fake Channel before a real Adapter. Verify create, update, close, reconcile,
204
221
 
205
222
  ## Verification
206
223
 
207
- Run the workspace generate/check/test/build gates plus real current-user positive and negative role-union cases. Acceptance must include submit, approve, reject, return/resubmit, transfer, delegate, before/after add-sign, withdraw, terminate, duplicate commands, stale revisions, repeated callbacks, full terminal card updates, detail navigation and 1.x zero-touch evidence.
224
+ Run the workspace generate/check/test/build gates plus real current-user positive and negative role-union cases. Acceptance must include full business-detail projection, bounded parent/subtable reads, Workflow-scoped files, independent desktop/mobile renderers, submit, approve, reject, return/resubmit, transfer, delegate, before/after add-sign, withdraw, terminate, duplicate commands, stale revisions, repeated callbacks, full terminal card updates, detail navigation and 1.x zero-touch evidence.