@stalfh233/omc-cli 0.4.61 → 0.4.62

package/dist/lanes/runtime-data.js

@@ -570,6 +570,7 @@ export function registerRuntimeDataLane(tools) {
             schemaCode: z.string(),
             bizObjectId: z.string({ required_error: "bizObjectId 必填（参数名就是 bizObjectId——不是 id 也不是 objectId，r44 两个 agent 都猜了 objectId；取值来自 data.submit 读回的 objectId/sequenceNo 或 data.list 的 row.bizObjectId）" }),
             full: z.boolean().optional().describe("返回未裁剪的完整业务对象（含 owner/creater 等系统字段；默认返回业务字段+身份的精简记录）"),
+            fields: z.array(z.string().min(1)).optional().describe("只保留列出的字段——核验状态时传 [\"sequenceStatus\",\"<业务状态字段>\"]，别整条 data.load（r4-training 2026-10-20：同一对象被读 74 次）；缺失字段回在 missingFields"),
             capability: capabilityArg,
         },
         handler: async (ctx, args, self) => {
@@ -603,7 +604,27 @@ export function registerRuntimeDataLane(tools) {
                 }
                 if (includeSchema)
                     ctx.schemaCache.add(args.schemaCode);
-                return { schemaCode: args.schemaCode, bizObjectId: args.bizObjectId, exists: data != null, ...(includeSchema ? {} : { schemaCached: true }), data };
+                // r4-training 2026-10-20: most repeat loads only ask "did it move?".
+                // Trim on the CLI side so the caller pays for the state bits, not the
+                // whole record (74 reads of one object in the r4 session).
+                let missingFields;
+                if (Array.isArray(args.fields) && args.fields.length > 0) {
+                    if (data && typeof data === "object" && !Array.isArray(data)) {
+                        const source = data;
+                        const projected = {};
+                        const missing = [];
+                        for (const field of args.fields) {
+                            if (field in source)
+                                projected[field] = source[field];
+                            else
+                                missing.push(field);
+                        }
+                        data = projected;
+                        if (missing.length > 0)
+                            missingFields = missing;
+                    }
+                }
+                return { schemaCode: args.schemaCode, bizObjectId: args.bizObjectId, exists: data != null, ...(missingFields ? { missingFields, availableFields: data && typeof data === "object" ? Object.keys(data) : [] } : {}), ...(includeSchema ? {} : { schemaCached: true }), data };
             }, { full: args.full === true, target: `data.load:${args.schemaCode}:${args.bizObjectId}` });
         },
     }));

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@stalfh233/omc-cli",
-  "version": "0.4.61",
+  "version": "0.4.62",
   "description": "CloudPivot 8.6 configuration capability CLI — governed, fail-closed, coverage-manifest bounded.",
   "type": "module",
   "bin": {
@@ -50,9 +50,9 @@
     "access": "public"
   },
   "dependencies": {
-    "@stalfh233/omc-fake-platform": "0.4.61",
+    "@stalfh233/omc-fake-platform": "0.4.62",
     "commander": "14.0.3",
-    "omc-core": "0.4.61",
+    "omc-core": "0.4.62",
     "proper-lockfile": "4.1.2",
     "write-file-atomic": "6.0.0",
     "zod": "^3.23.8",

package/skills/omc-business-configuration.md

@@ -150,6 +150,7 @@ rules:
 
 - **两条路**：模型+表单+流程一揽子交付走**意图**（`intent` 的 `workflow` 能力，声明式一次 apply）；只动流程或想逐步控制走**低层链** `workflow.create → workflow.update（权限/节点）→ workflow.publish`，标准链配方见 `omc describe workflow.update`（含多级审批/participant 三形态/自动回填说明）。流程权限细节见下节。
 - 一个模型只能有一个流程；已有流程的模型直接 `workflow.update`，不要另建。
+- **核验状态用投影，别重复整条读**：`data.load --args '{"schemaCode":..,"bizObjectId":..,"fields":["sequenceStatus","<业务状态字段>"]}'` 只回指定字段（缺失项在 `missingFields`）——r4 实测同一对象被整条读 74 次；大结果先 `artifact get <id> --summary` → `--keys/--jq`，别整包内联进推理。
 - **参与人解析失败分两种，别当成同一种（1.1.25 实测）**：① **解析为空**（角色零成员、成员未挂部门、自由文本、角色码不存在）→ 引擎把任务**退回发起人**，流程继续，症状是「审批人显示成我自己」，`data.submit` 与 `workitem.list` 都正常；② **参与人函数未注册**（`FindUsersByRoleFunction` / `FindUsersSpecByRoleFunction`，1.1.25 未内置）→ `FunctionNotFoundException`、不生成待办、实例卡 PROCESSING 而接口仍回 `errCode 0`。区分用 `omc call workflow.instanceActivity --args '{"workflowInstanceId":"<id>"}'`：无 `status:1` 节点=卡住；`status:1` 且参与人全是发起人=`diagnosis.warnings` 给 `participant-fallback-to-originator`。不要从 `workflow.get_published` 的摘要回抄函数式参与人；内置写法只有 `FindUserByRole(org, roleCode[, order])`，跨部门/全局角色优先用参与者对象数组（角色 id）。
 
 ## 流程字段权限