openxiangda-skill-kit 2.0.0-alpha.117 → 2.0.0-alpha.119

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "openxiangda-skill-kit",
-  "version": "2.0.0-alpha.117",
+  "version": "2.0.0-alpha.119",
   "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.95"
+    "openxiangda-devkit-core": "2.0.0-alpha.97"
   },
   "devDependencies": {
     "tsx": "4.23.12",

package/skills/openxiangda-v2/references/frontend.md

@@ -175,3 +175,20 @@ Generated contracts intentionally emit each resource Surface once in
 `resourceSurfaces`; `resourceDefinitions[code].surface` references that shared
 object. Import the generated runtime definitions normally. Do not serialize,
 inline or duplicate Surface literals in application code.
+
+The standard Workflow detail renderers consume only the authoritative Surface:
+`presentation.businessDetail`, `presentation.summary`, the typed timeline and
+operation descriptors. Continue to use `SurfaceFieldValue` for complete field
+semantics and the Workflow-scoped file client for attachments, rich-text images
+and signatures. Keep desktop and mobile renderers structurally independent;
+place decision actions in the fixed primary group, all low-frequency actions in
+the single more-actions entry, and collect comments in the action confirmation
+layer. The canonical desktop paths are `/tasks/:taskId` and
+`/workflows/:instanceId`; they render as standalone full-screen pages outside
+the admin Shell, while the platform alone replace-redirects historical admin
+detail URLs. Filter `system: true` and internal fields, omit empty sections,
+merge operation actor/action/reason/time into its vertical node, and never show
+UUIDs or revision/event diagnostics. Treat `stale` as metadata and show the
+friendly refresh prompt only after a real command token/CAS conflict. Do not
+copy the standard page into an application merely to show full business fields
+or rearrange platform-owned operations.

package/skills/openxiangda-v2/references/workflow-events.md

@@ -154,6 +154,40 @@ channel snapshots. Omitting `detailRouteCode` keeps the standard pages. A
 declared but missing or incompatible route fails closed rather than falling
 back silently.
 
+When `detailRouteCode` is omitted, use the platform standard detail page. Its
+Surface carries `presentation.businessDetail`, pinned to the instance Data
+logical revision, declaration digest and physical resource while re-reading the
+current values of the same Native Data record on every request. The start-time
+`requestedRevision` remains CAS metadata; `sourceRevision` and visible values
+must advance after a business-record update and must never become start-time
+value snapshots. The projection applies the current user's field policy and
+removes every `system: true` or internal field plus any empty group. Parent and subtable
+resources stay on that same logical revision and each subtable is bounded to
+200 rows. Render the provided summary, full field Surface, typed timeline and
+server-owned operation descriptors; do not infer labels, operation hierarchy
+or field semantics from codes in application code. Desktop and mobile have
+independent renderers, low-frequency operations live under one more-actions
+entry, and comments are collected only after an operation is selected. A
+`stale` detail status is metadata, not a persistent banner or an action block;
+show the friendly refresh prompt only when a command returns a real
+`freshSurface` token/CAS conflict and never auto-replay it. Merge operation
+actor/action/reason/time into the corresponding vertical node instead of
+rendering a second audit block. Never render UUIDs, revision/event diagnostics
+or a technical information section. Resolve the applicant from a directory or
+stable snapshot and use a friendly placeholder instead of exposing userId.
+
+The standard desktop task and instance pages use `/tasks/:taskId` and
+`/workflows/:instanceId` as standalone full-screen routes outside the admin
+Shell. Historical `/admin/tasks/:taskId` and `/admin/workflows/:instanceId`
+routes only replace-redirect while preserving query/hash. Mobile remains the
+independent `/m/tasks/:taskId` and `/m/workflows/:instanceId` surface.
+
+Files, rich-text images and signatures on this page use only the Workflow
+instance-scoped preview/content client. Every request is rebound to the current
+principal, authorized instance, projected resource/record/field and managed
+file id. Never substitute the ordinary Data API file route or put credentials
+in a file URL.
+
 Standard launch entry is also a platform Surface. Desktop uses
 `/admin/workflows/:workflowCode/new` and mobile uses
 `/m/workflows/:workflowCode/start`; both first load
@@ -204,4 +238,4 @@ Use Fake Channel before a real Adapter. Verify create, update, close, reconcile,
 
 ## Verification
 
-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.
+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.