openxiangda-skill-kit 2.0.0-alpha.105 → 2.0.0-alpha.107
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.
|
|
3
|
+
"version": "2.0.0-alpha.107",
|
|
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.
|
|
20
|
+
"openxiangda-devkit-core": "2.0.0-alpha.86"
|
|
21
21
|
},
|
|
22
22
|
"devDependencies": {
|
|
23
23
|
"tsx": "4.23.12",
|
|
@@ -126,6 +126,25 @@ Notification Hub recipient projection and deep-links to the platform-resolved
|
|
|
126
126
|
target. Do not query Notification Hub management endpoints or recreate a local
|
|
127
127
|
message state store.
|
|
128
128
|
|
|
129
|
+
The compiler also emits the required generated `routeManifest`. This is the
|
|
130
|
+
single desktop/mobile paired catalog for standard Workflow and Todo pages. Each
|
|
131
|
+
entry carries stable route codes, path parameters, access metadata and a
|
|
132
|
+
`requiresAuthentication: true` marker; the top-level digest binds the complete
|
|
133
|
+
catalog. Pass it directly to `OpenXiangdaApplication`. The runtime validates
|
|
134
|
+
pair surfaces, parameter names and shared access metadata before registering
|
|
135
|
+
the Router/Shell, and projects desktop `adminPages` from this same catalog.
|
|
136
|
+
Applications must not recreate standard `/admin/todos`, `/m/todos`, or
|
|
137
|
+
Workflow paths, add aliases/redirects, or maintain a second route state. The
|
|
138
|
+
compiler/platform preflight is the digest authority; the browser validates the
|
|
139
|
+
digest shape and fails closed on malformed or inconsistent entries.
|
|
140
|
+
|
|
141
|
+
For standard process submission, consume the typed browser helpers
|
|
142
|
+
`loadBusinessProcessReceipt(commandId)` and
|
|
143
|
+
`pollBusinessProcessCommand(commandId, afterRevision)` (or the matching Nest
|
|
144
|
+
`receipt`/`poll` methods). A first response may be `accepted`; follow
|
|
145
|
+
`nextPoll` until `terminal` instead of treating it as failure or issuing a
|
|
146
|
+
generic request to the platform endpoint.
|
|
147
|
+
|
|
129
148
|
For a small business action on a generated resource page, use the typed
|
|
130
149
|
`resources[resourceCode].toolbar`, `.row` or `.detail` slots accepted by
|
|
131
150
|
`defineApplicationContributions`. Declare a stable action code, label and
|