@stalfh233/omc-cli 0.4.64 → 0.4.65

package/dist/lanes/rule-graph.js

@@ -1664,7 +1664,7 @@ export function validateRuleNodeGraph(graph, ruleCode, schemaCode, options = {})
                     code: "rule-graph-cross-model-child-source-fanout",
                     nodeCode,
                     key: "filterCondition.mainConditions",
-                    message: `${nodeCode}: 跨模型 UPDATE 用子表字段做定位条件（${childSourcedLeaves.join("、")}）——1.1.25 把 "子表.字段" 解析成**集合**，目标主表仍只查询一次，不会按每条子表行各更新一次，运行结果是 0 行命中（r5-asset 2026-10-20 真机：保存/发布全绿、状态不变）。单行回写改用主表字段做 DYNAMIC 来源；一张单多行逐件回写需二开（BIZ_ACTION 自调接口一次处理多行）。`,
+                    message: `${nodeCode}: 跨模型 UPDATE 的定位条件用了点号来源（${childSourcedLeaves.join("、")}）——1.1.25 的 DatasetImpl 把 "x.y" 当作**子表路径**解析（parts[0] 找子表、收集该列所有行的值），既不是"关联字段.id"，也不会按每行各更新一次：目标主表仍只查询一次，结果 0 行命中（r5/r6 真机：保存发布全绿、字段不变）。单跳关联字段直接用字段 code（引擎会取关联对象的 id，真机 2026-10-21 已验证）；多跳（a.b）没有可用形状——把目标 id 用表单映射落到本模型的一个字段上再引用它，或走二开。`,
                 });
             if (!targetIsChild && Array.isArray(filterRecord.sheetConditions) && filterRecord.sheetConditions.length > 0)
                 blockers.push({

package/dist/lanes/workflow.js

@@ -85,6 +85,57 @@ const WORKFLOW_ROUTE_CONDITION_KEYS = ["text", "formula", "utilizeElse", "fixedP
  * and the line silently never fires (the same class of silent no-op that bit
  * checkType=2). Only caller-supplied `routes`/`rules` are checked.
  */
+/**
+ * AI-Platform 1.1.25 rejects a template whose first activity after START is not
+ * the originator fill node: WorkflowTemplateValidateUtility.validateStartActivity
+ * emits 401035 「发起节点的参与者只能是{Originator}」 and publish answers
+ * errcode 0 with a ValidateMessage[] (nothing is stored). Live 2026-10-21: a
+ * role-approval node placed directly after START failed publish with exactly
+ * that code, and the generic message did not name the cause.
+ */
+function assertFirstActivityIsOriginator(template, tool, merged) {
+    // Only gate AUTHORING intent: the caller must have sent both a START node and
+    // routes. A partial/stored-draft publish is left to the platform validator
+    // (401035), which the tool already surfaces faithfully.
+    const callerRows = callerActivities(template);
+    const callerRoutes = template.routes ?? template.rules ?? template.edges;
+    if (!Array.isArray(callerRows) || !Array.isArray(callerRoutes))
+        return;
+    if (!callerRows.some((activity) => String(activity.activityType ?? activity.type ?? "") === "START"))
+        return;
+    // Assert on the MERGED body: participant shorthands ({type:Originator,name:…})
+    // are normalized to "{Originator}" there.
+    const activities = callerActivities(merged ?? template);
+    const rawRoutes = merged ? (merged.routes ?? merged.rules ?? merged.edges) : callerRoutes;
+    if (!Array.isArray(activities) || !Array.isArray(rawRoutes))
+        return;
+    const start = activities.find((activity) => String(activity.activityType ?? activity.type ?? "") === "START");
+    if (!start)
+        return;
+    const startCode = activityCodeOf(start);
+    const first = rawRoutes
+        .map((entry) => (entry ?? {}))
+        .find((route) => String(route.preNode ?? route.preActivityCode ?? route.pre ?? route.from ?? "") === startCode);
+    if (!first)
+        return;
+    const nextCode = String(first.postNode ?? first.postActivityCode ?? first.post ?? first.to ?? "");
+    const next = activities.find((activity) => activityCodeOf(activity) === nextCode);
+    if (!next)
+        return;
+    const type = String(next.activityType ?? next.type ?? "");
+    const participant = String(next.participant ?? "").trim();
+    if (type === "PARTICIPANT" && /^\{Originator\}$/i.test(participant))
+        return;
+    throw new ToolRefusalError({
+        status: "refused",
+        blocker: "workflow-first-activity-not-originator",
+        workflowCode: String(template.workflowCode ?? template.code ?? ""),
+        activityCode: nextCode,
+        message: `${tool}: START 之后的第一个节点必须是参与者为 {Originator} 的填写节点（当前是 ${type || "?"}「${String(next.activityName ?? next.name ?? nextCode)}」${participant ? `，参与者 ${participant}` : ""}）。` +
+            `平台校验 WorkflowTemplateValidateUtility.validateStartActivity 对此报 401035「发起节点的参与者只能是{Originator}」，publish 回 errcode 0 但一个 ValidateMessage[] 就把模板挡在门外、不落库（真机 2026-10-21）。` +
+            `正确形状：Start → 填写({Originator}) → 审批/条件分支 … → End；审批节点不能直接接在 START 后。`,
+    });
+}
 function validateWorkflowRouteConditions(template, tool) {
     const raw = template.routes ?? template.rules ?? template.edges;
     if (!Array.isArray(raw))
@@ -1818,6 +1869,7 @@ export function registerWorkflowLane(tools) {
         const merge = args.merge === true || (args.merge !== false && activitiesLackBoundaries(template));
         const body = await mergedTemplateBody(session, args.schemaCode, args.code, template, merge);
         await backfillDesignerDefaults(session, args.schemaCode, body, template);
+        assertFirstActivityIsOriginator(template, "workflow.update", body);
         validateWorkflowRender(body, "workflow.update");
         // Live: workflow/update does NOT run the template validator — it stores a
         // refused participant silently and only /publish answers the
@@ -1868,6 +1920,7 @@ export function registerWorkflowLane(tools) {
         // boundaries is a partial edit → delta merge (see activitiesLackBoundaries).
         const body = await mergedTemplateBody(session, args.schemaCode, args.code, template, activitiesLackBoundaries(template));
         await backfillDesignerDefaults(session, args.schemaCode, body, template);
+        assertFirstActivityIsOriginator(template, "workflow.publish", body);
         const unregistered = unregisteredParticipantFunctions(body);
         if (unregistered.length > 0)
             throw new ToolRefusalError({

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@stalfh233/omc-cli",
-  "version": "0.4.64",
+  "version": "0.4.65",
   "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.64",
+    "@stalfh233/omc-fake-platform": "0.4.65",
     "commander": "14.0.3",
-    "omc-core": "0.4.64",
+    "omc-core": "0.4.65",
     "proper-lockfile": "4.1.2",
     "write-file-atomic": "6.0.0",
     "zod": "^3.23.8",

package/skills/omc-business-configuration.md

@@ -151,6 +151,8 @@ 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`，别整包内联进推理。
+- **流程第一个节点必须是 `{Originator}` 填写节点**：平台 `WorkflowTemplateValidateUtility.validateStartActivity` 对「START 后直接接审批」报 401035「发起节点的参与者只能是{Originator}」，publish 回 errcode 0 但一个 ValidateMessage[] 就把模板挡在门外、不落库（真机 2026-10-21）。OMC 0.4.65 起在 `workflow.update`/`publish` 出门前拒绝（`workflow-first-activity-not-originator`）。
+- **跨模型回写的目标行必须已提交（COMPLETED）**：DRAFT 行不参与目标查询，运行 0 行命中且日志只有「查找范围不存在数据」。单跳关联字段可直接作 DYNAMIC 来源（引擎取关联对象 id）；点号路径按子表解析，`关联字段.id` / 两跳路径都不支持。
 - **参与人解析失败分两种，别当成同一种（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

@@ -144,6 +144,8 @@ omc call field.publish --env local --args '{"schemaCode":"expense"}'
 
 对应源码：`UpdateServiceExecutor.getUpdatedMainBizObject()` 只把 `mainConditions` 交给目标主表查询；`sheetConditions` 只在 `doUpdateChildData()` 里被读取。
 
+两个前提（真机 2026-10-21）：① **目标行必须已提交**——DRAFT 行不参与目标查询，`data.save` 建的行永远改不到，日志只有「查找范围不存在数据」；② **单跳关联字段可直接作 DYNAMIC 来源**（引擎取关联对象 id），点号路径按子表解析，`关联字段.id` 与两跳都不支持——用表单映射把目标 id 落到本模型字段再引用。
+
 由此得到四条使用纪律：
 
 1. **主表目标上的 `sheetConditions` 是死配置**——不会生效（OMC 0.4.64 起给 warning）。