@stalfh233/omc-cli 0.4.99 → 0.4.101

package/dist/lanes/workflow.js

@@ -1686,6 +1686,34 @@ function sanitizeWorkflowSnapshotForReplay(row) {
         }),
     };
 }
+/**
+ * 2026-10-27 用户需求：创建流程时流程名默认与表单名一致。
+ *
+ * 解析链（全部真实读回，不捏造）：
+ *   ① 显式 name → "args"
+ *   ② 该模型默认表单的名字（bizsheet/get 的 name 字段）→ "form-name"
+ *   ③ 模型名（bizmodels/list_schema 行的 name）→ "model-name"
+ *   ④ 都读不到（模型不存在/无名字段）→ 拒绝：让调用方显式给 name，
+ *      绝不拿 schemaCode 冒充流程名（占位符冒充合法值是形状红线）。
+ */
+async function resolveWorkflowName(session, explicitName, schemaCode) {
+    if (typeof explicitName === "string" && explicitName.trim().length > 0)
+        return { name: explicitName, resolvedFrom: "args" };
+    const sheet = await wireCall(session, { path: ENDPOINTS.sheetGet, query: { schemaCode, sheetCode: schemaCode } }).catch(() => null);
+    const sheetName = sheet?.data?.name;
+    if (typeof sheetName === "string" && sheetName.trim().length > 0)
+        return { name: sheetName, resolvedFrom: "form-name" };
+    const listed = await wireCall(session, { path: ENDPOINTS.modelList, method: "POST", body: { schemaCodes: [schemaCode] } }).catch(() => null);
+    const rows = wireRows(listed?.data);
+    const modelName = rows.find((row) => String(row.schemaCode ?? "") === schemaCode)?.name;
+    if (typeof modelName === "string" && modelName.trim().length > 0)
+        return { name: modelName, resolvedFrom: "model-name" };
+    throw new ToolRefusalError({
+        status: "refused",
+        blocker: "invalid-input",
+        message: `流程 name 缺省解析失败：模型 ${schemaCode} 读不到表单名或模型名（模型不存在？）。显式传 name，或先确认模型存在（omc call model.list --args '{"filter":"<名或码>"}'）`,
+    });
+}
 function workflowRollbackSpec(toolName) {
     return {
         target: (args) => `workflow:${String(args.schemaCode ?? "")}/${String(args.code ?? args.workflowCode ?? "")}`,
@@ -2121,7 +2149,13 @@ export function registerWorkflowLane(tools) {
             return { workflowCode, valid: errors.length === 0, errorCount: errors.length, warningCount: warnings.length, errors, warnings };
         }, { target: `workflow.validate:${args.workflowCode ?? args.schemaCode}` }),
     }));
-    writeTool(tools, "workflow.create", WORKFLOW_LANE, WORKFLOW_TOOLS["workflow.create"].scope, WORKFLOW_TOOLS["workflow.create"].description, { schemaCode: z.string().min(1), name: z.string().min(1), code: z.string().min(1) }, async (session, args) => {
+    writeTool(tools, "workflow.create", WORKFLOW_LANE, WORKFLOW_TOOLS["workflow.create"].scope, WORKFLOW_TOOLS["workflow.create"].description, {
+        schemaCode: z.string().min(1),
+        // 2026-10-27 用户需求：流程名默认与表单名一致。省略时的解析链见
+        // resolveWorkflowName——表单名 → 模型名 → 拒绝（不拿 schemaCode 冒充）。
+        name: z.string().min(1).optional().describe("流程名称；省略时默认 = 该模型默认表单的名字（无表单草稿时用模型名），与设计器行为一致"),
+        code: z.string().min(1),
+    }, async (session, args) => {
         // Ticket 76 idempotent retry: get_header FIRST — a post-timeout
         // re-create of the same code short-circuits with the existing header
         // and ZERO create wires. On the happy path this read REPLACES the
@@ -2131,12 +2165,13 @@ export function registerWorkflowLane(tools) {
         if (existingHeader != null) {
             return { performed: { skipped: "already-present" }, readback: { alreadyPresent: true, header: existingHeader } };
         }
+        const { name: workflowName, resolvedFrom } = await resolveWorkflowName(session, args.name, args.schemaCode);
         let performed;
         try {
             performed = await wireCall(session, {
                 path: ENDPOINTS.workflowCreate,
                 method: "POST",
-                body: { workflowCode: args.code, workflowName: args.name, schemaCode: args.schemaCode, icon: "h-icon-all-logic" },
+                body: { workflowCode: args.code, workflowName, schemaCode: args.schemaCode, icon: "h-icon-all-logic" },
             });
         }
         catch (error) {
@@ -2163,7 +2198,7 @@ export function registerWorkflowLane(tools) {
         const draft = await getWorkflowDraftOrNull(session, args.code);
         return {
             performed: { errcode: performed.errcode },
-            readback: { workflowCode: args.code, headerPresent: true, draftPresent: draft != null, templateId: draft?.id ?? null },
+            readback: { workflowCode: args.code, name: workflowName, nameResolvedFrom: resolvedFrom, headerPresent: true, draftPresent: draft != null, templateId: draft?.id ?? null },
         };
     }, undefined, undefined, workflowRollbackSpec("workflow.create"));
     writeTool(tools, "workflow.update", WORKFLOW_LANE, WORKFLOW_TOOLS["workflow.update"].scope, WORKFLOW_TOOLS["workflow.update"].description, { schemaCode: z.string().min(1), code: z.string().min(1), template: workflowTemplateArg, merge: z.boolean().optional().describe("增量：只发改动/新增的活动与路由，工具按 activityCode 合并到草稿（草稿为基；新增节点自动接链），不必先读回整模板再重发。默认自动：模板缺 START 或 END 时按增量 merge（部分模板），给了完整 START..END 才整模板替换；显式 true 强制增量、false 强制替换。merge 是并集、绝不删边：结果比草稿少边会被拒（workflow-merge-would-drop-routes）；--dry-run 会返回 routesBefore/routesAfter/routesAdded/routesDropped") }, async (session, args) => {

package/dist/recipes/b2-registration.js

@@ -16,14 +16,15 @@ const restfulQueryService = Object.freeze({
         },
         methodName: "querySupplier",
         methodConfig: { httpType: "Post", requestBodyType: "JSON", url: "/supplier/query", frontEndExtensionEnable: true },
-        methodInputParameters: [{ code: "keyword", name: "关键字", required: true, configJson: { position: "REQUEST_BODY" } }],
-        methodOutputParameters: [{ code: "name", name: "供应商名称", configJson: { position: "REQUEST_BODY" } }],
+        methodInputParameters: [{ code: "keyword", name: "关键字", required: true, bizPropertyType: "SHORT_TEXT", configJson: { position: "REQUEST_BODY" } }],
+        methodOutputParameters: [{ code: "name", name: "供应商名称", bizPropertyType: "SHORT_TEXT", configJson: { position: "REQUEST_BODY" } }],
     },
     preconditions: ["serviceCategoryId 由 service.category.list 解析（「全部」是空 id 虚拟项不可用）；RESTFUL 服务 configJson 需要 auth 与 commonlist[url]；带 methodName 时必须有 methodConfig"],
     conditionalRequirements: [
         "RESTFUL auth.code ∈ customer(parameterlist=[]) / basic(client… username/password) / oauth_password / oauth_client；parameterlist 每项 {code,value} 且必须与 auth.code 期望参数完全一致",
         "RESTFUL 方法 configJson 必需键：httpType(Post/Get/Put/Patch/Delete)、requestBodyType(Form-urlencoded/JSON/Text)、url、frontEndExtensionEnable(布尔)",
         "RESTFUL 每个输入/输出参数必须带 configJson.position ∈ QUERY_PARAMS/REQUEST_HEADER/REQUEST_BODY/PATH_PARAMS（URL_VARIABLE 被运行时拒 501007）",
+        "每个输入/输出参数必须带 bizPropertyType（如 SHORT_TEXT/NUMERICAL）——缺它提交即被 bizservice-parameter-face-invalid 拒（r19-p7 首拒根因，2026-10-26 修正本配方）",
         "一次写只建一个方法；给既有服务加方法走 method.create（escape hatch）",
     ],
     priorToolReferences: [
@@ -92,10 +93,10 @@ const methodCreateRestfulGet = Object.freeze({
         name: "供应商查询",
         methodConfig: { httpType: "Get", requestBodyType: "JSON", url: "/openapi/supplier/query", frontEndExtensionEnable: true },
         methodInputParameters: [
-            { code: "keyword", name: "关键字", required: true, configJson: { position: "QUERY_PARAMS" } },
-            { code: "x-lowcode-corpId", name: "企业ID（平台注入常量）", required: false, codeType: 0, bizCode: "<corpId>", configJson: { position: "REQUEST_HEADER" } },
+            { code: "keyword", name: "关键字", required: true, bizPropertyType: "SHORT_TEXT", configJson: { position: "QUERY_PARAMS" } },
+            { code: "x-lowcode-corpId", name: "企业ID（平台注入常量）", required: false, bizPropertyType: "SHORT_TEXT", codeType: 0, bizCode: "<corpId>", configJson: { position: "REQUEST_HEADER" } },
         ],
-        methodOutputParameters: [{ code: "name", name: "供应商名称", configJson: { position: "REQUEST_BODY" } }],
+        methodOutputParameters: [{ code: "name", name: "供应商名称", bizPropertyType: "SHORT_TEXT", configJson: { position: "REQUEST_BODY" } }],
     },
     preconditions: ["服务已存在（method.create 只加方法）；methodCode 未存在；RESTFUL 每个入参与出参都带 configJson.position"],
     conditionalRequirements: [
@@ -127,8 +128,8 @@ const methodCreateRestfulPost = Object.freeze({
         methodCode: "saveSupplier",
         name: "供应商保存",
         methodConfig: { httpType: "Post", requestBodyType: "JSON", url: "/openapi/supplier/save", frontEndExtensionEnable: true },
-        methodInputParameters: [{ code: "body", name: "供应商对象", required: true, configJson: { position: "REQUEST_BODY" } }],
-        methodOutputParameters: [{ code: "id", name: "主键", configJson: { position: "REQUEST_BODY" } }],
+        methodInputParameters: [{ code: "body", name: "供应商对象", required: true, bizPropertyType: "SHORT_TEXT", configJson: { position: "REQUEST_BODY" } }],
+        methodOutputParameters: [{ code: "id", name: "主键", bizPropertyType: "SHORT_TEXT", configJson: { position: "REQUEST_BODY" } }],
     },
     preconditions: ["服务已存在；methodCode 未存在；POST 入参 position=REQUEST_BODY，requestBodyType=JSON"],
     conditionalRequirements: [

package/dist/recipes/businessrule.js

@@ -255,6 +255,7 @@ const ruleCrossModelCreate = Object.freeze({
         "上游是 QUERY 时 `inputParam=\"_<QUERY节点code>_output\"`（QUERY 查 N 行→CREATE 逐条生成即 N→N 扇出，真机验证支持，同/跨模型均可）；否则 `\"_input\"`。",
         "`QUERY` 节点只能查**主模型行**：查子表 schema（`parent.child` 或子 schema 名）空条件返回 0 行、带条件 550018（真机 2026-10-08）——逐子表明细扇出才需要二开。",
         "跨模型 CREATE/UPDATE 真机验证支持（2026-09-28 / 2026-10-08）；承载规则的触发时机要对（Create 在提交时触发、Update 只在 data.update 触发、TIMING 定时触发）。",
+        "**CREATE 目标是已发布流程的模型时**（2026-10-27 真机四格矩阵）：不传 startWorkflow → 建行**不发起流程**；要发起必须 startWorkflow:true + targetWorkflowCode:<该流程> + originatorValue 用户对象数组 [{\"id\":\"<userId>\",\"name\":\"<名>\"}]（传对象 {} → 触发提交 50000 expect '['；无效 id → 50000 发起人不存在）；设计器手工编辑可打开该开关，API 与设计器配置会漂移，rule.get 回读核对。",
     ],
     priorToolReferences: [
         { tool: "field.list", args: { environment, schemaCode: "<targetModel>", published: true }, purpose: "确认目标模型/字段已发布" },
@@ -269,7 +270,63 @@ const ruleCrossModelCreate = Object.freeze({
     ],
     requiresEnvironmentDerivedIds: false,
 });
+/**
+ * r19 p7（2026-10-26）：「Create 规则调用二开服务回写」在真机上全链路走通，但
+ * agent 为 methodMapping 形状 describe 了 rule.save 4 次（最大 16.8KB）——五条
+ * 既有配方里只有 data-duplicate-flag 带单向 inputMappings。本配方以 p7 的真实
+ * 成功参数为模板（输入 cname→来源字段、输出 level→目标字段，codeType:1），
+ * 双向映射一步可抄。
+ */
+const ruleBizactionInvokeService = Object.freeze({
+    id: "rule-bizaction-invoke-service",
+    title: "Create 规则调用服务方法并映射回写（BIZ_ACTION 双向）",
+    aliases: ["服务方法", "调用服务", "BIZ_ACTION", "回写服务", "查服务回写"],
+    status: "requires-prior-readback",
+    tool: "rule.save",
+    args: {
+        environment,
+        schemaCode: model,
+        ruleCode: "Create",
+        name: "数据新增",
+        nodeGraph: {
+            nodes: [
+                { nodeCode: "Start", nodeName: "开始", nodeType: "START" },
+                { nodeCode: "A1", nodeName: "调用服务并回写", nodeType: "BIZ_ACTION", inputParam: "_input", methodMapping: { schemaCode: model, serviceCode: "<svc>", serviceMethodCode: "<method>", inputMappings: [{ serviceMethodParameterCode: "<in_code>", codeType: 1, bizCode: "<src_field>", required: true }], outputMappings: [{ serviceMethodParameterCode: "<out_code>", codeType: 1, bizCode: "<dst_field>" }] } },
+                { nodeCode: "Create", nodeName: "新增数据", nodeType: "SYSTEM_CREATE", isSystemNode: true },
+                { nodeCode: "End", nodeName: "结束", nodeType: "END" },
+            ],
+            routes: [
+                { preNode: "Start", postNode: "A1", routeCondition: true },
+                { preNode: "A1", postNode: "Create", routeCondition: true },
+                { preNode: "Create", postNode: "End", routeCondition: true },
+            ],
+        },
+        publish: true,
+    },
+    preconditions: [
+        "模型与来源/目标字段已发布；服务与方法已注册（service.register 的 readback.method 直接给参数 code）",
+        "方法出参类型（bizPropertyType）与目标字段类型匹配",
+    ],
+    conditionalRequirements: [
+        "codeType:1 = 映射模型字段（bizCode=字段 code）；codeType:0 = 常量（bizCode=常量值）；serviceMethodParameterCode 必须与方法声明的参数 code 逐字一致",
+        "**接口响应必须在 JSON 根级**返回与出参 code 同名的键——嵌套在信封里（如 {data:{level}}）会静默映射不上（p7 实测）",
+        "**平台自调自己（127.0.0.1）会被运行时鉴权拦**：errcode 500012「绑定的API需要提供正确的身份验证或凭据」——需要带出站凭据的真实外部服务，或服务端配置鉴权放行；这不是 BIZ_ACTION 不支持（p7 定案）",
+        "BIZ_ACTION 放在 SYSTEM_CREATE **之前**（与自更新 UPDATE 相反：ASSIGN/BIZ_ACTION 在系统节点前，UPDATE 在系统节点后）",
+    ],
+    priorToolReferences: [
+        { tool: "service.register", args: { environment }, purpose: "注册服务+方法；readback.method 内联参数面（code/bizPropertyType），不必再 service.get" },
+    ],
+    dryRun: { supported: true, command: `omc call rule.save --env ${environment} --dry-run --args '<recipe.args>'`, notes: "dry-run 跑图 lint + 映射键校验（schemaCode/serviceCode/serviceMethodCode 非空、codeType 枚举）；服务参数面一致性真机 save 才核" },
+    expectedReadback: { readback: { published: true, enabled: false, next: "rule.enable → data.submit 触发 → data.load 读回目标字段" } },
+    refusalRecovery: [
+        { code: "rule-graph-bizmethod-unresolved", action: "serviceCode/serviceMethodCode 必须是已注册服务（service.list）；方法级详情 service.get" },
+        { code: "rule-graph-bizaction-mapping-field-missing", action: "inputMappings 的 bizCode 必须是本模型已发布字段 code（field.list 核对）" },
+        ...commonRecovery,
+    ],
+    notes: "p7 实测链（sandbox-r19/.scratch/report-p7.md §4）：注册查询服务 → 本配方建 Create 规则 → rule.enable → 提交触发。运行期若 500012 见 conditionalRequirements 第 3 条（出站凭据边界）",
+    requiresEnvironmentDerivedIds: true,
+});
 export const BUSINESSRULE_METADATA = Object.freeze({
-    "rule.save": Object.freeze({ recipes: [ruleGraph, ruleBranchGraph, ruleTimingTask, dataDuplicateFlag, ruleCrossModelCreate], relatedTools: ["field.list", "rule.get", "rule.enable"] }),
+    "rule.save": Object.freeze({ recipes: [ruleGraph, ruleBranchGraph, ruleTimingTask, dataDuplicateFlag, ruleCrossModelCreate, ruleBizactionInvokeService], relatedTools: ["field.list", "rule.get", "rule.enable", "service.get"] }),
 });
 //# sourceMappingURL=businessrule.js.map

package/dist/refusal-guidance.js

@@ -0,0 +1,207 @@
+/**
+ * Shape-family refusals: the payload was malformed in a way the CLI can see
+ * offline. Each cites the recipe that carries the correct shape.
+ */
+const SHAPE_GATES = Object.freeze({
+    "relation-single-array-shape": {
+        whatWentWrong: "单选关联字段（propertyType 9）传了数组",
+        correctShape: "单选关联只接受 id 字符串或 {id} 对象：{\"字段\":\"<关联行id>\"} 或 {\"字段\":{\"id\":\"<id>\"}}；多选关联（11）/人员（50）/组织（51）才用数组",
+        recipeCommand: { tool: "data.submit", recipe: "plain-data-submit" },
+        doNot: "不要对单选关联继续传数组重试——平台稳定回 50000，不是偶发",
+    },
+    "submit-date-shape": {
+        whatWentWrong: "日期字段的值形状不对（毫秒时间戳会落库 NULL）",
+        correctShape: "字符串且匹配字段 format：日期字段 \"YYYY-MM-DD\"；日期时间字段 ISO8601 带时区 \"2026-01-01T10:00:00+08:00\"",
+        recipeCommand: { tool: "data.submit", recipe: "plain-data-submit" },
+        doNot: "不要传毫秒数（如 1790000000000）——不报错但落库 NULL，读回才发现",
+    },
+    "submit-child-rows-missing-id": {
+        whatWentWrong: "更新已有记录时，子表行没带 id",
+        correctShape: "更新时子表行必须带平台 id（新增行才省略）；无 id 的行会被当**新增**插入，不判重",
+        command: undefined,
+        recipeCommand: { tool: "data.update", recipe: "plain-data-submit" },
+        doNot: "不要用同一批无 id 子行重试 update——每次都会再插一遍（r17 实测 2 行变 8 行）",
+    },
+    "submit-approval-agree-misplaced": {
+        whatWentWrong: "agree 放在了 approval 对象里，平台只读顶层 agree",
+        correctShape: "通过/驳回用顶层参数：{\"agree\": true|false, \"approvalNote\": \"意见\"}；approval 对象只是评论载体（content/relUsers）",
+        recipeCommand: { tool: "data.submit", recipe: "workflow-backed-data-submit" },
+        doNot: "approval.agree 会被静默忽略且仍按通过处理（r18b 真机：agree:false 照样 APPROVE）——原地重试必然得到同样的错误结果",
+    },
+    "submit-approval-opinion-misplaced": {
+        whatWentWrong: "opinion 放在了 approval 对象里，平台不读它",
+        correctShape: "审批意见用顶层 approvalNote；approval.content 是评论内容，不是审批意见",
+        recipeCommand: { tool: "data.submit", recipe: "workflow-backed-data-submit" },
+        doNot: "改 approval.opinion 重试无意义——字段被静默忽略",
+    },
+    "aggregation-self-schema-cycle": {
+        whatWentWrong: "聚合目标是自己的子表——平台 publishFormula 必然判环（checkCycleOfAggregation:1032），无条件 305003",
+        correctShape: "聚合 schemaCode 指向**另一个模型**的主表标量列；要子表合计先物化到来源主表再聚合",
+        recipeCommand: { tool: "field.create", recipe: "formula-aggregation-cross-model" },
+        doNot: "同模型子表聚合是平台死路（8.6.26 与 1.1.25 逐行相同），改 payload 无用；也不要删平台自动生成的 t100 CALCULATE_RULE 镜像行",
+    },
+    "aggregation-target-is-child-schema": {
+        whatWentWrong: "聚合指向了子表 schema",
+        correctShape: "aggregation.schemaCode 必须是来源模型主表；数据项只能是来源主表的标量列",
+        recipeCommand: { tool: "field.create", recipe: "formula-aggregation-cross-model" },
+        doNot: "聚合指向子表会让目标模型整个不可写（40000 无明细）且匹配恒 0——先删这个字段配置再继续",
+    },
+    "aggregation-data-item-not-scalar": {
+        whatWentWrong: "聚合数据项不是来源主表的标量列",
+        correctShape: "跨模型汇总的数据项只能是来源主表标量列；子表列先在来源模型物化成主表字段",
+        recipeCommand: { tool: "field.create", recipe: "formula-aggregation-cross-model" },
+        doNot: "直接把子表列写进数据项不会报配置错误——回算静默恒 0，先回来源模型物化",
+    },
+    "aggregation-large-missing-k": {
+        whatWentWrong: "LARGE/SMALL 聚合缺 k（前 N 名的 N）",
+        correctShape: "algorithmOptions 里带 k（正整数）；LARGE=前 k 大，SMALL=前 k 小",
+        recipeCommand: { tool: "field.create", recipe: "formula-aggregation-cross-model" },
+        doNot: "缺 k 时平台抛 NumberFormatException 掩码成 50000——重试同参数无用",
+    },
+    "aggregation-union-result-type": {
+        whatWentWrong: "UNION（文本拼接）的 resultType 越界",
+        correctShape: "UNION 的 resultType 只能 0 或 1（拼接分隔行为），不是数值型枚举",
+        recipeCommand: { tool: "field.create", recipe: "formula-aggregation-cross-model" },
+        doNot: "写 2 及以上平台直接 50000——改回 0/1 再发布",
+    },
+    "rule-graph-validation-failed": {
+        whatWentWrong: "规则图形状没过写前校验",
+        correctShape: "nodeGraph：nodes（Start/动作/End，系统节点标 isSystemNode）+ routes（preNode→postNode）；条件分支用 BRANCH 节点",
+        recipeCommand: { tool: "rule.save", recipe: "business-rule-branch-conditional" },
+    },
+    "rule-graph-routes-empty": {
+        whatWentWrong: "规则图缺 routes（节点连线）",
+        correctShape: "每条 route {preNode, postNode, routeCondition:true}；Start→首节点→…→End 必须连通",
+        recipeCommand: { tool: "rule.save", recipe: "business-rule-branch-conditional" },
+    },
+    "rule-graph-bizaction-mapping-field-missing": {
+        whatWentWrong: "BIZ_ACTION 节点的输入映射缺 serviceMethodParameterCode 或 bizCode",
+        correctShape: "inputMappings 每条：serviceMethodParameterCode（服务方法参数）↔ bizCode（模型字段 code），codeType 按类型",
+        recipeCommand: { tool: "rule.save", recipe: "rule-cross-model-create" },
+        missingInputs: [
+            { name: "serviceCode/serviceMethodCode", source: "omc call bizservice.list --args '{}'（已注册的二开服务）" },
+            { name: "bizCode（模型字段）", source: "omc call field.list --args '{\"schemaCode\":\"<模型>\",\"all\":true}'" },
+        ],
+    },
+    "rule-graph-bizmethod-unresolved": {
+        whatWentWrong: "规则图引用的二开服务方法不存在或未注册",
+        correctShape: "methodMapping.schemaCode/serviceCode/serviceMethodCode 必须是已注册服务的真实 code",
+        recipeCommand: { tool: "rule.save", recipe: "rule-cross-model-create" },
+        missingInputs: [
+            { name: "serviceCode/serviceMethodCode", source: "omc call bizservice.list --args '{}'；方法级详情用 bizservice.get" },
+        ],
+        doNot: "不要凭记忆拼写服务 code——静默不匹配时规则保存成功但运行为空",
+    },
+    "field-relation-target-missing": {
+        whatWentWrong: "关联字段的目标模型缺失或不可解析",
+        correctShape: "关联字段 options 里目标模型 schemaCode 必须已存在且已发布",
+        missingInputs: [
+            { name: "目标模型 schemaCode", source: "omc call model.list --args '{}'" },
+        ],
+    },
+});
+/**
+ * Platform/permission/environment families: honest "fix this first" with NO
+ * retry command — a command that would fail again is worse than none.
+ */
+const FIX_FIRST_GATES = Object.freeze({
+    "workflow-start-permission-denied": "40009 有三个独立同码原因：① 发起人角色没挂该流程的发起权限（ouScope ∩ 发起人部门链，全空会静默回退发起人）；② 流程未启用/未发布；③ 模型未绑定流程。先 omc call workflow.get_published 核对 ②，再查角色 ouScope——不要反复换参数重试 data.submit",
+    "environment-write-disabled": "当前环境 profile 不可写：换可写环境，或让维护者在配置里开 writable——CLI 侧没有绕过开关",
+    "production-confirmation-required": "生产环境的写需要显式 confirmProduction:true——确认这次写入真的要落生产再加该参数，不要靠重试",
+    "app-not-published": "目标应用未发布：先 workflow/form/field 各面发布（或 app 级发布），再重试运行面操作",
+    "submit-workitem-not-mine": "该 workItem 不在当前登录人的待办里：用 omc call workitem.list --args '{\"status\":\"PENDING\"}' 拿**自己的** workItemId，不要用别人的 id 提交",
+    "capability-out-of-coverage": "需求不在覆盖面内：这份拒绝就是答案——用 omc capabilities 核对运行时清单，不要换相近工具伪造实现",
+    "version-family-evidence-missing": "平台版本证据缺失，写被关闭：先 omc doctor / discover_environment 取版本证据，非 8.6/1.1.25 家族按边界处理",
+});
+/** `tool-input-invalid` and friends: point at the refused tool's own describe. */
+function inputInvalidGuidance(toolName) {
+    if (!toolName)
+        return undefined;
+    return {
+        whatWentWrong: "入参没过工具的 schema 校验（缺必填或类型不对）",
+        correctShape: "必填参数与类型见 command 指向的 describe（firstCall 自带最小可跑形状）",
+        command: `omc describe ${toolName}`,
+        doNot: "不要盲目重试——同参数必然同拒绝",
+    };
+}
+/**
+ * r19 p14 — the report BI boundary (`/dashboard/v1/*`). A deployment without
+ * the report service answers every BI call with a gateway 502 (live p9
+ * evidence); that is an ENVIRONMENT boundary, not a transient failure, so the
+ * teaching says which faces still work and to stop retrying. Matched from the
+ * message/detail text so both the refused and the frozen (uncertain) envelope
+ * paths can carry it.
+ */
+function dashboardBoundaryGuidance() {
+    return {
+        whatWentWrong: "报表 BI 通道（/dashboard/v1/*）不可达——报表服务未启动（本机有此服务；网关 502，p9 实证）",
+        fixFirst: "报表能力暂不优先支持（维护者裁决，先隐藏）：不要重试同一子面。平台层仍可用：report.tree / report.update / report.get 存在性判定；确需 BI 详情/数据源/图表/配置时，先启动本机报表服务再深进",
+    };
+}
+function mentionsDashboardChannel(payload) {
+    return JSON.stringify({ m: payload.message, d: payload.detail, r: payload.reason }).includes("/dashboard/v1/");
+}
+/**
+ * Resolve the authored recipe command against the registry: the guidance must
+ * never cite a recipe the registry does not ship (that would be a second,
+ * contradictory shape source). Falls back to the tool's describe; if even the
+ * tool is unknown, the command is omitted.
+ */
+function resolveCommand(authored, registry) {
+    if (!authored.recipeCommand || !registry)
+        return undefined;
+    const tool = registry.find((entry) => entry.name === authored.recipeCommand.tool);
+    const recipe = tool?.executionMetadata?.recipes.find((entry) => entry.id === authored.recipeCommand.recipe);
+    if (tool && recipe)
+        return `omc describe ${tool.name} --example ${recipe.id}`;
+    if (tool)
+        return `omc describe ${tool.name}`;
+    return undefined;
+}
+export function refusalRecovery(blocker, payload, options = {}) {
+    // A refusal that already teaches (write-lock-held carries lock recovery) is
+    // not overwritten — single owner per envelope.
+    if (payload.recovery !== undefined)
+        return payload.recovery;
+    // r19 p14: the report BI boundary is matched from the wire path in the
+    // message/detail, so both refused and frozen (uncertain) envelopes teach it.
+    if (mentionsDashboardChannel(payload))
+        return dashboardBoundaryGuidance();
+    const shape = SHAPE_GATES[blocker];
+    if (shape) {
+        const command = resolveCommand(shape, options.registry);
+        const { recipeCommand: _drop, ...rest } = shape;
+        return { ...rest, ...(command !== undefined ? { command } : {}) };
+    }
+    const fixFirst = FIX_FIRST_GATES[blocker];
+    if (fixFirst)
+        return { whatWentWrong: String(payload.message ?? blocker).slice(0, 160), fixFirst };
+    if (blocker === "tool-input-invalid")
+        return inputInvalidGuidance(options.toolName);
+    return undefined;
+}
+/**
+ * Attach guidance to a refused result at the `runToolCall` choke point.
+ * Idempotent, refuses to overwrite, and leaves non-refused results untouched.
+ */
+export function attachRefusalRecovery(result, toolName, registry) {
+    // r19 p14: `/dashboard/v1/*` failures surface as UNCERTAIN (frozen) — the
+    // http-status wire kind is classified "uncertain" by design, and frozen
+    // envelopes carry `reason`/`detail` but NO `blocker` field. The dashboard
+    // boundary is definitive (gateway 502, report service not started), so those
+    // frozen envelopes get the teaching too; every other uncertain result stays
+    // untouched (never relabel network jitter as an environment boundary).
+    const frozenWithBoundary = result.status === "uncertain" && mentionsDashboardChannel(result);
+    if (result.status !== "refused" && !frozenWithBoundary)
+        return result;
+    if (result.recovery !== undefined)
+        return result;
+    const blocker = typeof result.blocker === "string" ? result.blocker : "";
+    if (!blocker && !frozenWithBoundary)
+        return result;
+    const recovery = refusalRecovery(blocker, result, { registry, toolName });
+    if (!recovery)
+        return result;
+    return { ...result, recovery };
+}
+//# sourceMappingURL=refusal-guidance.js.map

package/dist/rule-support.js

@@ -446,6 +446,100 @@ export function isModernAssignVersion(version) {
  * supported alternatives (BRANCH, or two rules).
  */
 const CHOICE_CONDITION_TYPES = new Set([12, 13, 14, 15]);
+/**
+ * 2026-10-27 用户反馈 + r24 沙盒四格矩阵（1.1.25 真机实测）：
+ * CREATE（新增数据）节点打到**已发布流程的模型**时的流程发起开关语义——
+ *
+ *   不传 startWorkflow          → 行落库、不发起流程（API 默认，实测）
+ *   true + originatorValue "{}" → 触发表单提交 50000（fastjson expect '[', but {）
+ *   true + 数组但 id 无效        → 50000「业务规则发起人不存在」
+ *   true + [{id,name}] 真实用户 + targetWorkflowCode → 行落库并自动发起流程
+ *
+ * 契约：目标有已发布流程而未声明开关 → warning 教学显式做法（合法的两种选择
+ * 都要写明）；开了开关但 originatorValue/targetWorkflowCode 不合法 → error
+ * 写前拒绝——那两种形状会把**触发表单的提交**整个打挂，正是 fail-closed 该拦的。
+ */
+async function createNodeFlowStartWarnings(session, nodes) {
+    const creates = nodes.filter((node) => String(node.nodeType ?? "") === "CREATE" && String(node.targetObjectCode ?? "") !== "");
+    if (creates.length === 0)
+        return [];
+    const flowByTarget = new Map();
+    for (const target of [...new Set(creates.map((node) => String(node.targetObjectCode)))]) {
+        try {
+            const isWorkflow = (await wireCall(session, { path: ENDPOINTS.workflowIsWorkflow, query: { schemaCode: target } })).data === true;
+            if (!isWorkflow)
+                continue;
+            const row = (await wireCall(session, { path: ENDPOINTS.workflowGetBySchema, query: { schemaCode: target } })).data;
+            const code = row && typeof row.workflowCode === "string" && row.workflowCode ? row.workflowCode : null;
+            if (!code)
+                continue;
+            // get_published 原样回模板（fake 保真：未发布也回 DRAFT 形状——Ticket 77，
+            // 发布证据是 templateType:PUBLISH 标记，不是有数据）；流程码用已解析的 code。
+            const published = (await wireCall(session, { path: ENDPOINTS.workflowGetPublished, query: { workflowCode: code } })).data;
+            const publishMarker = published !== null && published !== undefined ? String(published.templateType ?? "").toUpperCase() : "ABSENT";
+            if (published && (publishMarker === "" || publishMarker === "PUBLISH"))
+                flowByTarget.set(target, code);
+        }
+        catch {
+            // 读面失败不阻塞写面（与 radioConditionWarnings 同策略：读不到就不评）
+        }
+    }
+    const findings = [];
+    for (const node of creates) {
+        const target = String(node.targetObjectCode);
+        const flowCode = flowByTarget.get(target);
+        if (flowCode === undefined)
+            continue;
+        const nodeCode = String(node.nodeCode ?? "");
+        if (node.startWorkflow === undefined || node.startWorkflow === false) {
+            findings.push({
+                code: "rule-create-target-has-flow",
+                nodeCode,
+                key: "startWorkflow",
+                severity: "warning",
+                message: `CREATE 目标模型 ${target} 已发布流程 ${flowCode}：不传 startWorkflow 时规则建行**不发起流程**（实测 2026-10-27，行落库即止）。` +
+                    `要让规则新建的行直接进流程：显式 startWorkflow:true + targetWorkflowCode:"${flowCode}"，且 originatorValue 必须是用户对象数组 [{"id":"<userId>","name":"<名>"}]（id 用 org.user.search 取；传对象 {} 或无效 id 会让**触发表单的提交**直接 50000，实测）。` +
+                    `注意：设计器里手工编辑该节点可打开此开关——API 与设计器两侧配置可能漂移，改完用 rule.get 回读核对 startWorkflow/targetWorkflowCode。`,
+            });
+            continue;
+        }
+        const raw = typeof node.originatorValue === "string" ? node.originatorValue.trim() : node.originatorValue;
+        let parsed = raw;
+        if (typeof raw === "string" && raw.length > 0) {
+            try {
+                parsed = JSON.parse(raw);
+            }
+            catch {
+                parsed = null;
+            }
+        }
+        const originatorValid = Array.isArray(parsed)
+            && parsed.length > 0
+            && parsed.every((entry) => entry && typeof entry === "object" && typeof entry.id === "string" && entry.id.length > 0);
+        if (!originatorValid) {
+            findings.push({
+                code: "rule-create-startworkflow-originator-shape",
+                nodeCode,
+                key: "originatorValue",
+                message: `CREATE "${nodeCode}" 开了 startWorkflow 但 originatorValue 不是用户对象数组：期望 [{"id":"<userId>","name":"<名>"}]。` +
+                    `实测（2026-10-27，1.1.25）：传对象 {} → 触发表单提交 50000（fastjson "expect '[', but {"）；数组里 id 无效 → 50000「业务规则发起人不存在」。` +
+                    `id 用 org.user.search 取真实用户后再写。`,
+            });
+        }
+        // 「startWorkflow:true 必须带 targetWorkflowCode」由既有的离线同步检查
+        // rule-graph-create-workflow-code 负责（rule-graph.ts:2055），这里不重复——
+        // 但流程码要能对上：给了但不是该模型的已发布流程时补一条 error。
+        if (typeof node.targetWorkflowCode === "string" && node.targetWorkflowCode.length > 0 && node.targetWorkflowCode !== flowCode) {
+            findings.push({
+                code: "rule-create-startworkflow-target-mismatch",
+                nodeCode,
+                key: "targetWorkflowCode",
+                message: `CREATE "${nodeCode}" 的 targetWorkflowCode="${node.targetWorkflowCode}" 不是目标模型 ${target} 的已发布流程（应为 "${flowCode}"）——发到不匹配的流程会运行期失败。`,
+            });
+        }
+    }
+    return findings;
+}
 async function radioConditionWarnings(session, schemaCode, nodes) {
     const sources = new Set();
     const collect = (condition) => {
@@ -659,6 +753,8 @@ export async function executeRuleSaveWrite(session, args) {
     const blockers = [...prepared.warnings, ...validateRuleNodeGraph(preparedGraph, args.ruleCode, typeof args.schemaCode === "string" ? args.schemaCode : undefined, carriedNodeCodes ? { carriedNodeCodes } : {})];
     // 1.2: needs the published field types (pure lint cannot see them).
     blockers.push(...(await radioConditionWarnings(session, args.schemaCode, Array.isArray(preparedGraph.nodes) ? preparedGraph.nodes : [])));
+    // r24 反馈（2026-10-27 真机四格矩阵）：CREATE 目标带已发布流程时的发起开关教学/拦截。
+    blockers.push(...(await createNodeFlowStartWarnings(session, Array.isArray(preparedGraph.nodes) ? preparedGraph.nodes : [])));
     // Ticket 113: warning-severity findings (e.g. unknown mapping keys) do not
     // gate the write; they surface in the readback as lintWarnings.
     const warningFindings = blockers.filter((blocker) => blocker.severity === "warning");