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

package/package.json

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

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

@@ -183,5 +183,12 @@ 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. Do not copy the standard page into an application merely to show full
-business fields or rearrange platform-owned operations.
+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

@@ -156,14 +156,31 @@ 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, physical resource and requested record
-revision, then filtered by the current user's field policy. Parent and subtable
+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.
+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