@stalfh233/omc-cli 0.4.61 → 0.4.63

package/dist/lanes/runtime-data.js

@@ -300,10 +300,10 @@ async function stampChildRowStatuses(session, schemaCode, formData) {
         }
     }
     catch {
-        return formData;
+        return { formData, childCodes: [] };
     }
     if (childCodes.size === 0)
-        return formData;
+        return { formData, childCodes: [] };
     let changed = false;
     const next = { ...formData };
     for (const code of childCodes) {
@@ -321,7 +321,7 @@ async function stampChildRowStatuses(session, schemaCode, formData) {
             return { ...row, rowStatus: hasId ? "Modified" : "Added" };
         });
     }
-    return changed ? next : formData;
+    return { formData: changed ? next : formData, childCodes: [...childCodes] };
 }
 /** Runtime business-object data keyed by field code. */
 export function registerRuntimeDataLane(tools) {
@@ -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}` });
         },
     }));
@@ -625,7 +646,7 @@ export function registerRuntimeDataLane(tools) {
                 message: "submit:true 与 workflowCode 互斥——workflowCode 是流程草稿两段式的第一段（返回 workItemId 后用 data.submit 提交）；无流程模型的一调完成态用 submit:true 且不带 workflowCode",
             });
         const { sheetCode, resolvedFrom } = await resolveFormSheetCode(session, { schemaCode: args.schemaCode, sheetCode: args.sheetCode });
-        const formData = await stampChildRowStatuses(session, args.schemaCode, args.formData);
+        const formData = (await stampChildRowStatuses(session, args.schemaCode, args.formData)).formData;
         if (typeof args.workflowCode === "string" && args.workflowCode.trim()) {
             // Portal draft-save shape. The row id travels in data.id (the portal
             // form SDK receives a pre-generated id from form/load and echoes it);
@@ -787,7 +808,7 @@ export function registerRuntimeDataLane(tools) {
                 message: "no live business object with this id; refusing to update (the platform would otherwise insert a new row)",
             });
         }
-        const formData = await stampChildRowStatuses(session, args.schemaCode, args.formData);
+        const formData = (await stampChildRowStatuses(session, args.schemaCode, args.formData)).formData;
         const performed = await wireCall(session, {
             path: ENDPOINTS.runtimeFormSave,
             method: "POST",
@@ -886,6 +907,7 @@ export function registerRuntimeDataLane(tools) {
         workItemId: z.string().optional(),
         bizObjectId: z.string().optional().describe("existing record id; REQUIRED for workItem approval submits (formType=1 + workItemId) — the submit's bizObject must reference the in-flight record or the engine NPEs (DataChangeHandlerImpl.changeBizObject)"),
         agree: z.boolean().optional(),
+        allowChildRowAppend: z.boolean().optional().describe("默认 false：审批提交（带 workItemId/workflowInstanceId）时 formData 含子表数组会被拒——平台按追加插行，每次提交重复一份。确实要追加子行时才置 true。"),
         approval: z.record(z.string(), z.unknown()).optional(),
         runMode: z.string().optional(),
         isSimulative: z.boolean().optional(),
@@ -905,7 +927,27 @@ export function registerRuntimeDataLane(tools) {
             });
         }
         const { sheetCode, resolvedFrom } = await resolveFormSheetCode(session, { schemaCode: args.schemaCode, sheetCode: args.sheetCode });
-        const formData = await stampChildRowStatuses(session, args.schemaCode, args.formData);
+        const stampedSubmit = await stampChildRowStatuses(session, args.schemaCode, args.formData);
+        const formData = stampedSubmit.formData;
+        // r5-asset 2026-10-20: the platform APPENDS child rows carried in an
+        // approval submit's formData (no upsert by row id, no error). Live: an
+        // approval that echoed the whole form twice turned 2 detail rows into 6
+        // and 30000 into 90000 while every call answered errcode 0 — node-level
+        // `editable:false` does not stop it server-side. Refuse before the wire.
+        if ((hasWorkItem || hasInstance) && args.allowChildRowAppend !== true) {
+            const carried = stampedSubmit.childCodes.filter((code) => {
+                const value = args.formData[code];
+                return Array.isArray(value) && value.length > 0;
+            });
+            if (carried.length > 0)
+                throw new ToolRefusalError({
+                    status: "refused",
+                    blocker: "submit-approval-child-rows",
+                    schemaCode: args.schemaCode,
+                    childTables: carried,
+                    message: `审批提交（workItemId/workflowInstanceId）的 formData 不要带子表数组：${carried.join("、")}。平台按「追加行」处理——每提交一次就再插一份（真机：2 行 → 6 行，30000 → 90000），且不报错、审批节点的 editable:false 也拦不住。只传主表字段；确实要在审批中追加子行时显式传 allowChildRowAppend:true。`,
+                });
+        }
         // Portal required-field semantics: the REST submit does NOT enforce them,
         // so a missing required value must be REPORTED, not silently accepted as a
         // portal-valid submit (dogfood R3). Best-effort read; a failure never

package/dist/lanes/workflow.js

@@ -691,7 +691,7 @@ function validateWorkflowRender(template, tool) {
  * chain order" — reusing any edge whose endpoints survived. A draft whose
  * (possibly branching) graph is untouched passes the chain check verbatim.
  */
-function completeWorkflowChain(rules, activities) {
+export function completeWorkflowChain(rules, activities) {
     const codes = activities.map((activity) => String(activity.activityCode ?? "")).filter((code) => code.length > 0);
     if (codes.length < 2)
         return rules;
@@ -712,13 +712,24 @@ function completeWorkflowChain(rules, activities) {
     }
     for (const code of codes) {
         const type = typeOf(code);
-        if (type !== "START" && (inbound.get(code) ?? 0) !== 1)
+        if (type !== "START" && (inbound.get(code) ?? 0) < 1)
             valid = false;
-        if (type !== "END" && (outbound.get(code) ?? 0) !== 1)
+        if (type !== "END" && (outbound.get(code) ?? 0) < 1)
             valid = false;
     }
     if (valid)
         return rules;
+    // r5-asset 2026-10-20: a node with TWO outgoing edges is a conditional
+    // branch (condition edge + utilizeElse fallback), NOT an invalid chain. The
+    // old rule demanded outbound === 1, so every branched graph fell through to
+    // the linear rebuild below — which maps consecutive activity codes and
+    // silently DROPS the else edge. Live symptom: a workflow.update that sent
+    // activities without routes erased A3→A5, every low-amount instance stalled
+    // in PROCESSING with errcode 0, and the only trace was a missing edge in
+    // get_published. Never linearize a graph that already branches.
+    const branched = [...outbound.values()].some((count) => count > 1);
+    if (branched)
+        return rules;
     const byEdge = new Map(rules.map((rule) => [`${rule.preActivityCode}->${rule.postActivityCode}`, rule]));
     return codes.slice(0, -1).map((code, index) => byEdge.get(`${code}->${codes[index + 1]}`) ?? { preActivityCode: code, postActivityCode: codes[index + 1] });
 }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@stalfh233/omc-cli",
-  "version": "0.4.61",
+  "version": "0.4.63",
   "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.63",
     "commander": "14.0.3",
-    "omc-core": "0.4.61",
+    "omc-core": "0.4.63",
     "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）。
 
 ## 流程字段权限

package/skills/omc-write-hazards.md

@@ -125,3 +125,18 @@ omc call field.publish --env local --args '{"schemaCode":"expense"}'
 ## 固定验收顺序
 
 执行阶段以 `omc-five-piece-flow` 为准；写面安全只额外强调两点：写前先 `commands/describe/contract` + dry-run 静态校验，写后权威 readback，必要时再用 CLI 触发运行验证。
+
+## 审批提交回传子表 = 追加行（真机 2026-10-20）
+
+带 `workItemId` / `workflowInstanceId` 的 `data.submit` 里放子表数组，平台按**追加**处理，不按行 `id` upsert、也不报错：
+2 行明细回传两次 → 6 行，`totalValue` 30000 → 90000，审批节点的 `editable:false` 拦不住服务端写入。
+**只传主表字段**；确需追加行时显式 `allowChildRowAppend:true`（0.4.63 起默认拒绝，blocker `submit-approval-child-rows`）。
+收尾时前后各读一次子表行数确认未变。
+
+## 跨表回写只能取主表字段（真机 2026-10-20）
+
+- `id = {子表code}.asset` / `...asset.id`：保存发布全绿，**运行不命中**，无日志。
+- 请求体直接引用子表关联（CREATE 的 dataActions 等）：提交报 `550010 业务规则使用的数据项不存在`。
+- BRANCH 后接两个跨表 UPDATE：`50000`。
+- 固定 id / 主表字段条件：可运行。
+逐件联动（一张单多件资产）纯配置做不到，走二开 BIZ_ACTION 或人工。