openxiangda-skill-kit 2.0.0-alpha.136 → 2.0.0-alpha.138

package/package.json

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

package/skills/manifest.json

@@ -4,7 +4,7 @@
     {
       "name": "openxiangda-v2",
       "description": "Use when researching, designing, building, testing, or delivering an OpenXiangda 2.0 application, including anonymous public forms and other no-account external-user pages.",
-      "sha256": "ad7e89a4cfeba1b730cdd9504609872e1355bf5d79101c439cdf7350a4bc9678"
+      "sha256": "f84c530b0b34766de941ca513961099a4a1f14444c3ecf6586b982dfd99d7bf7"
     }
   ]
 }

package/skills/openxiangda-v2/SKILL.md

@@ -32,6 +32,7 @@ Use this order:
 7. Read [Frontend](references/frontend.md) for pages or fields and [Backend actions](references/backend.md) only for a real business action.
    When the request customizes the application Todo center or the common PC/mobile frame around standard user pages, use only `standardUserSurfaces` from that reference. The platform must keep ownership of the Router, `RuntimeBoundary`, current user, Notification Hub and Workflow controllers.
 8. When the application explicitly enables standard approval, application events or notifications, read [Workflow, Events and Notification Hub](references/workflow-events.md). Keep them optional and out of ordinary CRUD.
+   Before changing a deployed workflow, inspect effective administrator parameters with `pnpm openxiangda admin workflow <workflowCode> --json`; current tasks stay frozen and subsequent node entries adopt current runtime settings. Never assume local defaults are the effective approvers.
 9. Run the connected loop with `pnpm openxiangda dev`, then follow [Testing](references/testing.md) and `pnpm openxiangda check`; check performs the target platform's read-only Native compatibility preflight before application checks or builds.
 10. Follow [Delivery](references/delivery.md): deploy preproduction first, inspect status/logs, then promote the exact successful version to production.
 

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

@@ -4,6 +4,7 @@
 
 | Command | Risk | Purpose |
 | --- | --- | --- |
+| `pnpm openxiangda admin` | read | 只读查看应用管理能力和流程节点运行配置 |
 | `pnpm openxiangda create` | deploy | 创建、绑定并初始化应用 |
 | `pnpm openxiangda dev` | write-local | 连接平台测试数据启动本地 Web，按需启动 Nest |
 | `pnpm openxiangda check` | write-local | 生成契约并在目标平台预检后执行检查、测试和构建 |

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

@@ -17,6 +17,21 @@ Use these optional modules only when the application has a real standard approva
 
 ## Workflow declaration
 
+Before changing an already deployed workflow, run `pnpm openxiangda admin workflow <workflowCode> --json`
+to read code defaults, administrator overrides, effective node parameters and revision history.
+The default is the test environment; read production explicitly with `--environment production`.
+`pnpm openxiangda admin context --json` reports the application's available management capabilities.
+Both commands use the logged-in developer and current workspace and are read-only.
+An unavailable response is not proof that no overrides exist.
+
+The platform owns runtime overrides for node title/description and fixed-user or role selection.
+New instances and future node entries in existing instances use the latest configuration;
+current tasks retain their frozen participants and binding, including assignment retries.
+Do not copy overrides back into a definition or mutate topology through management APIs.
+Publication retains compatible overrides and rejects removed/reused nodes, changed providers,
+or removed selected roles. Resolve the reported configuration in the application management
+console before retrying an incompatible publication or rollback. Test and production overrides are isolated.
+
 Declare workflow topology and bindings once in `openxiangda.config.ts`. Use only approval, condition and end nodes for the standard module. Every definition `inputSchema` is a closed root object (`type: 'object'`, `additionalProperties: false`). Keep business data in Data API/App API and pass the exact `{ resourceCode, id }` `dataRef`, a separate positive `dataRevision`, and bounded schema-valid facts into prepare/start. Undeclared facts and answers fail closed.
 
 `workflows.activations` is the complete desired set for the deployed version,

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

@@ -53,6 +53,8 @@ revisions and draft CAS; successful submission consumes the draft atomically.
 
 ## Optional application backend
 
+For an already deployed standard workflow, first inspect `pnpm openxiangda admin workflow <workflowCode> --json` (add `--environment production` only for production inspection). The platform owns administrator node parameters; local definitions own topology. Do not overwrite runtime overrides during code authoring. Existing tasks retain their frozen parameters and future node entries use the latest configuration.
+
 The default scaffold contains Web and shared contracts only. Declare
 `backend: { enabled: true }` or application server capabilities, then use the
 existing `pnpm openxiangda check` / `pnpm dev` loop. The tool initializes Nest