@stalfh233/omc-cli 0.4.97 → 0.4.98

package/dist/capability-overview.js

@@ -231,7 +231,12 @@ export const CAPABILITY_CUES = Object.freeze({
     onlinejs: ["在线js", "脚本", "联动", "onload", "onvalidate"],
     bizservice: ["集成", "接口", "服务", "回调", "对接", "外部系统", "datasql", "restful"],
     report: ["报表", "图表", "看板", "bi", "dashboard"],
-    data: ["运行数据", "提交数据", "保存记录", "查记录"],
+    // r18 (2026-10-26): "造数据 / 造测试单据 / 录数据" is the RUN-DATA capability, but
+    // the goal usually also says 子表/明细 (field cues) — without these compound
+    // cues the router sent the probe to `field` in read mode (write:false), so it
+    // never reached data.submit. Compound (not bare 数据) to avoid stealing
+    // ordinary model/field asks that merely mention data.
+    data: ["运行数据", "提交数据", "保存记录", "查记录", "造数据", "测试数据", "测试单据", "造单据", "造单", "录数据", "填数据", "模拟数据", "业务数据", "造几条", "造两张", "造几张", "验数据"],
 });
 /**
  * Boundary cues — authored alongside CAPABILITY_CUES (same runtime authority).

package/dist/compute.js

@@ -212,8 +212,27 @@ export async function cmdCompute(args) {
     // data.save / data.submit / data.update never refresh the target field, no
     // matter how correct the formula is. Say so in the receipt instead of letting
     // the caller believe the write took effect (r12 believed it; r16 disproved it).
+    // r18: the dry-run receipt showed only an optionsSummary hash, so the probe
+    // could not tell whether `{items.qty} * {items.price}` means per-row or
+    // aggregate-after-multiply — a semantic difference that changes the answer.
+    // Echo the exact compiled formula (and its editor twin) on the dry-run face.
+    const compiled = !apply
+        ? (() => {
+            const stitch = createArgs.options?.shortTextStitch;
+            if (typeof stitch !== "string")
+                return undefined;
+            try {
+                const parsed = JSON.parse(stitch);
+                return { formula: parsed.formula ?? null, editorText: parsed.editorText ?? null, editorMark: parsed.editorMark ?? null };
+            }
+            catch {
+                return undefined;
+            }
+        })()
+        : undefined;
     const withWarning = apply && classified.status === "ok" ? { ...result, ...computeExecutionNotice() } : result;
-    writeEnvelope(envelope(classified.status, withWarning, request, classified.error));
+    const withCompiled = compiled ? { ...withWarning, compiledFormula: compiled } : withWarning;
+    writeEnvelope(envelope(classified.status, withCompiled, request, classified.error));
     return exitCode;
 }
 //# sourceMappingURL=compute.js.map

package/dist/field-families.js

@@ -954,6 +954,16 @@ export function assertFieldOptionsAllowed(type, options, schemaCode) {
                 const agg = parseOptionsObject(config.aggregation);
                 if (!agg || !isNonEmptyString(agg.schemaCode) || !isNonEmptyString(agg.dataItemCode) || !isNonEmptyString(agg.formula))
                     refuseFieldOptions("AGGREGATION aggregation is missing schemaCode/dataItemCode/formula", 'rejected: aggregation 形状 {schemaCode:"<目标模型schemaCode>", dataItemCode:"<目标字段code>", formula:"SUM({<目标模型>.<字段>})", calculateType:"SUM", queryConditions:[[…]]}（FormulaProcessor.executeMainAggregation + AggregationFormula）');
+                if (String(agg.dataItemCode).includes("."))
+                    throw new ToolRefusalError({
+                        status: "refused",
+                        blocker: "aggregation-data-item-not-scalar",
+                        schemaCode: schemaCode ?? null,
+                        dataItemCode: String(agg.dataItemCode),
+                        message: `聚合数据项 ${String(agg.dataItemCode)} 带点号：平台只接受**来源模型的主表标量列 code**（不带 schema 前缀）。` +
+                            `写成 <子表>.<子列> 会在 field.publish 回 309004「使用的聚合数据项不存在」（r18 真机）。` +
+                            `要汇总子表列：先在来源主模型上物化一个数值字段（门户计算规则或写入方维护），再聚合那个标量列。`,
+                    });
                 if (schemaCode !== undefined && aggregationTargetsOwnSchema(schemaCode, String(agg.schemaCode)))
                     throw new ToolRefusalError({
                         status: "refused",

package/dist/goal-routes.js

@@ -13,7 +13,7 @@ import { listSkills, readSkillSection } from "./skills.js";
 const SCOUT_CUES = ["能不能", "能不能够", "能否", "是否支持", "支持吗", "支持不支持", "可不可以", "有没有办法", "有没有可能", "怎么实现", "如何实现", "怎么写", "怎么配置"];
 const MODIFY_CUES = ["修改", "调整", "更新", "重命名", "改名", "编辑", "删除", "去掉", "移除", "改为", "改成"];
 const READ_CUES = ["查看", "读回", "盘点", "现状", "列出", "有哪些", "有没有", "检查", "审计", "导出", "只读", "看看", "看下", "查一下", "查询一下", "查一查", "梳理", "清点", "给我一份", "哪些", "是什么", "是否", "是否正确", "现有", "已有"];
-const BUILD_CUES = ["新建", "创建", "搭建", "从零", "从无到有", "做", "建", "加", "实现", "生成", "新增", "保存", "启用", "录入", "添加"];
+const BUILD_CUES = ["新建", "创建", "搭建", "从零", "从无到有", "做", "建", "加", "实现", "生成", "新增", "保存", "启用", "录入", "添加", "造", "填报", "打卡", "录"];
 /** Whole-application asks — a single-model atom is the wrong shape for these. */
 const WHOLE_APP_CUES = ["应用", "系统", "整套", "从零", "从无到有", "端到端", "一条龙", "一整套", "业务应用", "平台"];
 function looksWholePackage(goal, capabilityCount) {
@@ -122,6 +122,10 @@ function capabilityScores(registry, goal) {
 const DEFAULT_LADDER_RECIPES = {
     businessrule: { tool: "rule.save", recipe: "business-rule-branch-conditional" },
     datarule: { tool: "datarule.create", recipe: "field-compute-rule" },
+    // r18: a "造数据 / 录测试单据" ask reached the `data` capability but had no
+    // runnable shape — the probe had to fetch `describe data.submit --example`
+    // itself. These lane defaults give every ladder step a copyable command.
+    data: { tool: "data.submit", recipe: "plain-data-submit" },
 };
 function defaultRecipeFor(registry, capabilityId, lane) {
     const wanted = DEFAULT_LADDER_RECIPES[capabilityId];
@@ -609,6 +613,13 @@ export function goalRoute(registry, goal) {
             route: {
                 ...(whole ? { primary: "intent", atomicSupplement } : { ladder }),
                 ...routeReads(readSections),
+                // r18: when a step already carries a goal-matched recipe, the generic
+                // first section ("3. Draft template") is noise — the probe read it and
+                // got nothing. Say that the recipe command is the answer and the
+                // sections are only a fallback.
+                ...(ladder.some((step) => step.recipe)
+                    ? { readHint: "已命中配方：先跑 firstCommands 里的 `omc describe … --example …` 取形状；下面的 readSections 只是补充，不必先读（确实需要时用 `omc help <topic> --section \"<节>\"`，按 readMore 逐节补）。" }
+                    : {}),
                 // Each ladder step already carried a runnable recipe command, but it sat
                 // buried at `ladder[i].recipe.command` behind a readiness line — r14's
                 // probe reported "ladder 本身没给可直接跑的命令" and hand-built the rule

package/dist/lanes/field.js

@@ -141,6 +141,21 @@ function assertNameI18nArg(nameI18n) {
     if (typeof parsed !== "object" || parsed === null || Array.isArray(parsed))
         refuse("JSON 解析结果不是对象");
 }
+/**
+ * r18 (2026-10-26 live): aggregating a CHILD-TABLE schema (`schemaCode:"items"`)
+ * publishes fine but makes the TARGET model unwritable — every data.submit /
+ * data.update answers `40000 调用数据库发生异常` with no detail (the probe spent
+ * ~40 calls bisecting it). The child schema also has no parent-document column,
+ * so matching by the parent's document number can never work: even when the
+ * write goes through the value is always 0.
+ *
+ * Child schemas are recognizable from their field list: they alone carry the
+ * system columns `parentId`（子表业务对象父类ID）and `sortKey`（子表排序号）.
+ */
+function childSchemaCodes(rows) {
+    const codes = new Set(rows.map((row) => String(row.code ?? row.propertyCode ?? "")));
+    return codes.has("parentId") && codes.has("sortKey");
+}
 /**
  * r17 (2026-10-25, live + decompiled A/B): a FORMULA field CANNOT aggregate its
  * own model's child table. `BizPropertyManagerImpl.publishFormula` rewrites
@@ -184,6 +199,43 @@ function assertNoSelfSchemaAggregation(args, published) {
         message: aggregationSelfSchemaMessage(target, args.schemaCode),
     });
 }
+/**
+ * The async half of the aggregation gate: a FOREIGN child schema cannot be
+ * detected syntactically, so read the target's field list once (only for
+ * AGGREGATION) and refuse when it carries the child-schema system columns.
+ */
+async function assertNoChildSchemaAggregation(session, schemaCode, propertyType, options) {
+    const resolved = typeof propertyType === "number" ? propertyType : FIELD_PROPERTY_TYPES[String(propertyType)];
+    if (resolved !== FIELD_PROPERTY_TYPES.FORMULA)
+        return;
+    const config = decodeJsonObjectColumn(options.formulaConfig, { invalid: "undefined", array: "reject", object: "reject" });
+    if (!config || config.formulaType !== "AGGREGATION" || typeof config.aggregation !== "string")
+        return;
+    const agg = decodeJsonObjectColumn(config.aggregation, { invalid: "undefined", array: "reject", object: "reject" });
+    const target = typeof agg?.schemaCode === "string" ? agg.schemaCode.trim() : "";
+    if (!target)
+        return;
+    let rows;
+    try {
+        rows = wireRows((await wireCall(session, { path: ENDPOINTS.fieldList, query: { schemaCode: target, isPublish: "true" } })).data);
+    }
+    catch {
+        return;
+    }
+    if (!childSchemaCodes(rows))
+        return;
+    throw new ToolRefusalError({
+        status: "refused",
+        blocker: "aggregation-target-is-child-schema",
+        schemaCode,
+        aggregationSchemaCode: target,
+        message: `聚合目标 ${target} 是**子表 schema**（字段清单里带 parentId/sortKey 系统列）。` +
+            `平台允许发布，但目标模型从此**整个不可写**：data.submit/data.update 一律回 40000「调用数据库发生异常」且无明细（r18 真机，二分 40 次调用才定位）。` +
+            `而且子表 schema 没有父单单号列，按父单匹配恒为 0——即使不报错也算不出值。` +
+            `正确做法：聚合**来源模型的主表标量列**。需要子表合计时，先在来源主模型物化一个数值字段` +
+            `（门户计算规则 / 写入方维护），再用 AGGREGATION 聚合该标量。配方：omc describe field.create --example formula-aggregation-cross-model。`,
+    });
+}
 export function registerFieldLane(tools) {
     tools.push(defineTool({
         name: "field.list",
@@ -344,6 +396,7 @@ export function registerFieldLane(tools) {
         // One seam owns field-change normalization, every reproduced gate, and the
         // wire body (src/field-change.ts), so configure_model and intent share it.
         assertNoSelfSchemaAggregation(args, published);
+        await assertNoChildSchemaAggregation(session, args.schemaCode, args.propertyType, args.options ?? {});
         const prepared = prepareFieldChange(args);
         let performed;
         try {
@@ -437,6 +490,7 @@ async function runFieldUpdate(session, args) {
             .then((response) => wireRows(response.data))
             .catch(() => []);
         assertNoSelfSchemaAggregation({ schemaCode: args.schemaCode, propertyType: record.type ?? record.propertyType, options: args.options }, publishedRows);
+        await assertNoChildSchemaAggregation(session, args.schemaCode, record.type ?? record.propertyType, args.options);
     }
     const update = {
         schemaCode: args.schemaCode,

package/dist/lanes/runtime-data.js

@@ -598,6 +598,65 @@ export function assertRuntimeFieldValueShapes(meta, formData, childCodes, contex
         }
     }
 }
+/**
+ * r18 (2026-10-26 live): `errcode 40000 调用数据库发生异常` carries NO detail and
+ * `omc-refusals` had nothing for it. A probe burned ~40 calls bisecting it:
+ * the cause was an AGGREGATION field whose `schemaCode` pointed at a CHILD-TABLE
+ * schema — publish succeeds, then every write on that model 40000s. A FORMULA
+ * field whose config cannot serialize does the same.
+ *
+ * Metadata is read ONLY on failure (zero cost on the success path). The refusal
+ * names the model's FORMULA/AGGREGATION fields so the caller bisects the right
+ * thing instead of guessing at forms/permissions.
+ */
+async function diagnoseDbException(session, schemaCode, error) {
+    // Non-40000 errors fall through untouched (callers keep their own branches).
+    if (!(error instanceof WireError && error.kind === "business" && error.errcode === 40000))
+        return false;
+    let rows = [];
+    try {
+        rows = wireRows((await wireCall(session, { path: ENDPOINTS.fieldList, query: { schemaCode, isPublish: "true" } })).data);
+    }
+    catch {
+        // metadata unavailable: still explain what 40000 means
+    }
+    const formulaFields = [];
+    for (const row of rows) {
+        if (Number(row.propertyType ?? row.type) !== 100)
+            continue;
+        let formulaType;
+        let aggregationSchemaCode;
+        if (typeof row.options === "string" && row.options) {
+            try {
+                const options = JSON.parse(row.options);
+                const config = typeof options.formulaConfig === "string" ? JSON.parse(options.formulaConfig) : undefined;
+                if (typeof config?.formulaType === "string")
+                    formulaType = config.formulaType;
+                if (typeof config?.aggregation === "string") {
+                    const agg = JSON.parse(config.aggregation);
+                    if (typeof agg.schemaCode === "string")
+                        aggregationSchemaCode = agg.schemaCode;
+                }
+            }
+            catch {
+                formulaType = "unparsable-formulaConfig";
+            }
+        }
+        formulaFields.push({ code: String(row.code ?? row.propertyCode ?? ""), ...(formulaType ? { formulaType } : {}), ...(aggregationSchemaCode ? { aggregationSchemaCode } : {}) });
+    }
+    throw new ToolRefusalError({
+        status: "refused",
+        blocker: "runtime-write-db-exception",
+        schemaCode,
+        errcode: 40000,
+        formulaFields,
+        message: `平台回 40000「调用数据库发生异常」——这是**无明细的掩码**，不是表单/权限问题（r18 真机）。` +
+            `本模型上的公式字段：${formulaFields.length > 0 ? formulaFields.map((field) => `${field.code}(${field.formulaType ?? "?"}${field.aggregationSchemaCode ? `→${field.aggregationSchemaCode}` : ""})`).join("、") : "（读不到 field.list，或没有 FORMULA 字段）"}。` +
+            `最常见原因：**AGGREGATION 字段的 schemaCode 指向子表 schema** —— 平台允许发布，但该模型从此整个不可写。` +
+            `其次是 FORMULA 的 formulaConfig 无法序列化。` +
+            `定位：依次禁用/删除可疑公式字段再写一次（可逆）；形状见 omc describe field.create --example formula-aggregation-cross-model。`,
+    });
+}
 /** Runtime business-object data keyed by field code. */
 export function registerRuntimeDataLane(tools) {
     tools.push(defineTool({
@@ -949,15 +1008,22 @@ export function registerRuntimeDataLane(tools) {
             // isStartWf branch runs verifyReplay; the instance is DRAFT only when
             // data carries sequenceStatus DRAFT (an empty default builds PROCESSING).
             const replayToken = await getReplayToken(session);
-            const performed = await runtimeWriteWithAppMapping(session, args.schemaCode, 50000, "data.save 运行时写稳定失败（50000）", () => wireCall(session, {
-                path: ENDPOINTS.runtimeFormSave,
-                method: "POST",
-                body: {
-                    workflowCode: args.workflowCode,
-                    ...(replayToken ? { replayToken } : {}),
-                    bizObject: { schemaCode: args.schemaCode, sheetCode, data: { ...formData, id: objectId, sequenceStatus: "DRAFT" } },
-                },
-            }), formData, args.workflowCode);
+            let performed;
+            try {
+                performed = await runtimeWriteWithAppMapping(session, args.schemaCode, 50000, "data.save 运行时写稳定失败（50000）", () => wireCall(session, {
+                    path: ENDPOINTS.runtimeFormSave,
+                    method: "POST",
+                    body: {
+                        workflowCode: args.workflowCode,
+                        ...(replayToken ? { replayToken } : {}),
+                        bizObject: { schemaCode: args.schemaCode, sheetCode, data: { ...formData, id: objectId, sequenceStatus: "DRAFT" } },
+                    },
+                }), formData, args.workflowCode);
+            }
+            catch (error) {
+                await diagnoseDbException(session, args.schemaCode, error);
+                throw error;
+            }
             const vo = (performed.data ?? {});
             const returnedId = typeof vo.objectId === "string" && vo.objectId ? vo.objectId : typeof vo.bizObjectId === "string" && vo.bizObjectId ? vo.bizObjectId : objectId;
             const workflowInstanceId = typeof vo.workflowInstanceId === "string" ? vo.workflowInstanceId : null;
@@ -992,11 +1058,18 @@ export function registerRuntimeDataLane(tools) {
                 readback: { authoritative: projectReadbackRecord(normalizeLoadedRecord((readbackData ?? {})), args), sequenceStatus, expectedSequenceStatus: "DRAFT" },
             };
         }
-        const performed = await runtimeWriteWithAppMapping(session, args.schemaCode, 50000, "data.save 运行时写稳定失败（50000）", () => wireCall(session, {
-            path: ENDPOINTS.runtimeFormSave,
-            method: "POST",
-            body: { bizObject: { schemaCode: args.schemaCode, sheetCode, data: formData } },
-        }), formData);
+        let performed;
+        try {
+            performed = await runtimeWriteWithAppMapping(session, args.schemaCode, 50000, "data.save 运行时写稳定失败（50000）", () => wireCall(session, {
+                path: ENDPOINTS.runtimeFormSave,
+                method: "POST",
+                body: { bizObject: { schemaCode: args.schemaCode, sheetCode, data: formData } },
+            }), formData);
+        }
+        catch (error) {
+            await diagnoseDbException(session, args.schemaCode, error);
+            throw error;
+        }
         const bizObjectId = performed.data?.bizObjectId ?? performed.data?.objectId ?? performed.data;
         let readbackData = null;
         if (typeof bizObjectId === "string" && bizObjectId) {
@@ -1090,14 +1163,21 @@ export function registerRuntimeDataLane(tools) {
             });
         }
         const formData = (await prepareRuntimeFormData(session, args.schemaCode, args.formData, { isUpdate: true })).formData;
-        const performed = await wireCall(session, {
-            path: ENDPOINTS.runtimeFormSave,
-            method: "POST",
-            // Live-proven shape: BizObjectModel.getId() reads data["id"], so the
-            // target id MUST travel inside `data`; a top-level bizObject.id is
-            // ignored and the platform silently creates a new row.
-            body: { bizObject: { schemaCode: args.schemaCode, sheetCode, data: { ...formData, id: args.bizObjectId } } },
-        });
+        let performed;
+        try {
+            performed = await wireCall(session, {
+                path: ENDPOINTS.runtimeFormSave,
+                method: "POST",
+                // Live-proven shape: BizObjectModel.getId() reads data["id"], so the
+                // target id MUST travel inside `data`; a top-level bizObject.id is
+                // ignored and the platform silently creates a new row.
+                body: { bizObject: { schemaCode: args.schemaCode, sheetCode, data: { ...formData, id: args.bizObjectId } } },
+            });
+        }
+        catch (error) {
+            await diagnoseDbException(session, args.schemaCode, error);
+            throw error;
+        }
         const performedData = (performed.data ?? {});
         const returnedId = typeof performedData.objectId === "string" ? performedData.objectId : typeof performedData.bizObjectId === "string" ? performedData.bizObjectId : args.bizObjectId;
         const readbackData = await loadExistingBizObject(session, args.schemaCode, sheetCode, returnedId);
@@ -1424,6 +1504,7 @@ export function registerRuntimeDataLane(tools) {
             }), undefined, hasWorkflowCode ? explicitWorkflowCode : undefined);
         }
         catch (error) {
+            await diagnoseDbException(session, args.schemaCode, error);
             // r16 P4: 100005 is SYS_REPLAY_ERROR「频繁重复提交！」(ErrorCode.java:68 —
             // the same numeric code as TEST_CONNECTION_FAIL, so only the text
             // separates them). The platform rate-limits per WORK ITEM, so a different

package/dist/model-scaffold.js

@@ -108,11 +108,50 @@ export async function cmdModelScaffold(args) {
         ...(environment !== undefined ? { environment } : {}),
     };
     const plan = describeScaffoldPlan(options);
+    // r18: run the field-family preflight even in DRY-RUN. It is zero-wire
+    // (`field.create --dry-run` runs only the local capability gate), and the
+    // probe's first attempt — NUMERICAL without options.scale — passed the old
+    // plan-only dry-run and would have half-built a model on --apply.
+    const preflightProblems = [];
+    const preflightTargets = [
+        ...fields.filter((field) => scaffoldChildrenOf(field).length === 0),
+        ...fields.filter((field) => scaffoldChildrenOf(field).length > 0),
+    ];
+    {
+        for (const field of preflightTargets) {
+            const probe = await runToolCall("field.create", {
+                args: scaffoldFieldArgs(code, field),
+                requestId: request,
+                dryRun: true,
+                ...(environment !== undefined ? { environment } : {}),
+                print: () => undefined,
+            });
+            const status = String(probe.result.status ?? "ok");
+            if (probe.exitCode !== 0 || (status !== "dry-run" && status !== "ok")) {
+                preflightProblems.push({ code: field.code, message: refusalText(probe.result) });
+            }
+        }
+        if (preflightProblems.length > 0) {
+            writeEnvelope(envelope("error", {
+                status: "refused",
+                blocker: "scaffold-preflight-failed",
+                model: code,
+                written: false,
+                failed: preflightProblems.length,
+                preflightProblems,
+                message: `有 ${preflightProblems.length} 个字段的预检没过，**尚未写入任何东西**。` +
+                    `按 message 改 --fields 后重跑（常见：NUMERICAL 缺 options.scale、文本/数值字段用了自定义键名）。` +
+                    `--fields 的每一项就是 field.create 的参数（形状见 omc describe field.create），子表列用 subFields（childFields 是别名）。`,
+            }, request, { code: "policy-refused", message: "字段形状预检未通过（未写入）", retryable: false }));
+            return CLI_EXIT_CODES.policyRefused;
+        }
+    }
     if (!apply) {
         writeEnvelope(envelope("ok", {
             status: "dry-run",
             ...plan,
-            note: "dry-run 只列计划；--apply 依次执行 建模型 → 建字段 → 建子列 → 发布字段 → 发布表单。",
+            preflight: { checked: fields.length, passed: true },
+            note: "dry-run 只列计划；已对每个字段跑过本地形状预检（零 wire）。--apply 依次执行 建模型 → 建字段 → 建子列 → 发布字段 → 发布表单。",
         }, request));
         return CLI_EXIT_CODES.ok;
     }
@@ -138,43 +177,7 @@ export async function cmdModelScaffold(args) {
         return { ok: outcome.exitCode === 0, result };
     };
     const lastSummaries = [];
-    // 0) 前置校验：把每个字段先跑一次 dry-run（走完整字段族 preflight，不写库）。
-    // r13 真机：`NUMERICAL` 少 options.scale 时，前两个字段已经建好了才在第 3 个
-    // 报错，留下一个半成品模型要手工清。半成品比慢一点贵得多。
-    // 子列不在这里校验：它们的目标 schema（子表）此刻还不存在，dry-run 会误报。
-    const preflightTargets = [
-        ...fields.filter((field) => scaffoldChildrenOf(field).length === 0),
-        ...fields.filter((field) => scaffoldChildrenOf(field).length > 0),
-    ];
-    const preflightProblems = [];
-    for (const field of preflightTargets) {
-        const probe = await runToolCall("field.create", {
-            args: scaffoldFieldArgs(code, field),
-            requestId: request,
-            dryRun: true,
-            ...(environment !== undefined ? { environment } : {}),
-            print: () => undefined,
-        });
-        const status = String(probe.result.status ?? "ok");
-        if (probe.exitCode !== 0 || (status !== "dry-run" && status !== "ok")) {
-            preflightProblems.push({ code: field.code, message: refusalText(probe.result) });
-        }
-    }
-    if (preflightProblems.length > 0) {
-        const result = {
-            status: "refused",
-            blocker: "scaffold-preflight-failed",
-            model: code,
-            // Nothing was written — that is the point.
-            written: false,
-            failed: preflightProblems.length,
-            preflightProblems,
-            message: `有 ${preflightProblems.length} 个字段的 dry-run 预检没过，**尚未写入任何东西**。` +
-                `按下面的 message 改 --fields 后重跑（常见：NUMERICAL 缺 options.scale、SELECTION/RADIO 缺 choices、CHILD_TABLE 缺 subFields）。`,
-        };
-        writeEnvelope(envelope("refused", result, request, { code: "policy-refused", message: String(result.message), retryable: false }));
-        return CLI_EXIT_CODES.policyRefused;
-    }
+    // 0) 字段形状预检已在上面的 dry-run 分支前完成（零 wire）；这里只记录。
     steps.push({ step: "preflight", status: "ok", detail: { checked: preflightTargets.length, wrote: false } });
     // 1) 模型：已存在是常态（补建场景），不是失败。
     const created = await call("model.create", {

package/dist/recipes/field.js

@@ -253,7 +253,8 @@ const formulaAggregationCrossModel = Object.freeze({
     preconditions: [
         "**只能汇总「别的模型」**：同模型（含自己的子表）聚合在 field.publish 必抛 305003（平台 publishFormula 把相对码改写成子表父模型 = 本模型，checkCycleOfAggregation:1032 判成环）。工具已写前拒绝 `aggregation-self-schema-cycle`。",
         "目标字段用 FORMULA(100)（不是普通字段 + 计算规则——type2 计算规则在 REST 路径永不执行）。",
-        "`schemaCode` 是被汇总的**来源模型**；`dataItemCode` 是来源模型的列；`queryConditions` **不能为空**，否则反向过滤器为空、找不到要回算的目标行（真机：空条件时 recalc 日志照常打印但目标字段恒为 0）。",
+        "`schemaCode` 是被汇总的**来源模型**；`dataItemCode` 是来源模型的**主表标量列**（不带 schema 前缀）；`queryConditions` **不能为空**，否则反向过滤器为空、找不到要回算的目标行（真机：空条件时 recalc 日志照常打印但目标字段恒为 0）。",
+        "**不要指向子表 schema**（r18 2026-10-26 真机）：`schemaCode:\"<子表>\"` 能发布，但目标模型从此**整个不可写** —— `data.submit`/`data.update` 一律回 40000「调用数据库发生异常」且无明细；而且子表 schema 没有父单单号列，按父单匹配恒为 0。`dataItemCode` 写成 `<子表>.<子列>` 则在 publish 直接 309004「使用的聚合数据项不存在」。要汇总子表：先在来源**主模型**上物化一个数值字段（门户计算规则或写入方维护），再聚合该标量。OMC 已写前拒绝 `aggregation-target-is-child-schema` / `aggregation-data-item-not-scalar`。",
     ],
     conditionalRequirements: [
         "**DYNAMIC 条件的两个 code 分属两侧，写反了就静默 0**：`propertyCode` = **来源模型**的字段（这里是 r17_c.nm），`currentPropertyCode` = **目标模型**的字段（这里是 r17_d.srcNo）。语义 = 「来源行的 nm 等于本目标行的 srcNo」。",

package/package.json

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

package/skills/omc-business-configuration.md

@@ -154,6 +154,7 @@ rules:
 - **「聚合计算」是字段能力，不是规则节点**：FORMULA(计算公式)字段的 `options.formulaConfig.formulaType="AGGREGATION"` 就是 UI 里的「配置方式 → 聚合计算」。**只能汇总另一个模型**（跨模型），**同模型/自己的子表会 305003**（`field.publish` 时 `publishFormula` 把相对码改写成子表父模型 = 本模型，`checkCycleOfAggregation:1032` 判成环；工具已写前拒绝 `aggregation-self-schema-cycle`）。可直接抄 `omc describe field.create --example formula-aggregation-cross-model`。形状：
   `options = {persistent:true, formulaConfig: JSON字符串({resultType:2, formulaType:"AGGREGATION", aggregation: JSON字符串({schemaCode:"<来源模型>", dataItemCode:"<来源列>", calculateType:"SUM", formula:"SUM({<来源模型>.<列>})", queryConditions:[[{propertyCode:"<来源模型字段>", currentPropertyCode:"<目标模型字段>", operatorType:1, valueType:"DYNAMIC"}]]})})}`。
   - **`queryConditions` 不能为空**：它是反向过滤器的唯一输入，空数组时回算日志照打但目标字段恒 0（r17 实测）。
+  - **聚合目标必须是来源主表的标量列**（r18 2026-10-26 真机）：`aggregation.schemaCode` 指向**子表 schema** 时能发布，但目标模型从此整个不可写（`data.submit`/`data.update` 全回 40000 无明细），且子表无父单单号列、匹配恒 0；`dataItemCode` 写 `<子表>.<子列>` 则 publish 回 309004。要子表合计：先在来源主模型物化一个数值字段，再聚合该标量。
   - **DYNAMIC 条件的两个 code 分属两侧，写反了静默 0**：`propertyCode` = 来源模型字段，`currentPropertyCode` = 目标模型字段；语义「来源行的 X 等于本目标行的 Y」。
   - **`propertyType`/`currentPropertyType`（BizPropertyType）与 `operatorType`（OperatorType）必须写整数**——两者都是 `@JsonCreator get(int)`：propertyType 0=SHORT_TEXT 2=NUMERICAL 3=DATE 9=WORK_SHEET…；operatorType 1=EQ 2=NEQ 3=GT 4=IT（小于）5=GTEQ 6=ITEQ（小于等于）9=IS_NULL 10=IS_NOT_NULL…。写名字会被 `ObjectMapperUtils` 抛 json processing exception，再被死循环校验掩码成 305003（工具接受名字并自动转码）。`calculateType` 相反，是**字符串**（SUM/COUNT/COUNTIF/SUMIF/AVG/MAX/MIN/LARGE/SMALL/UNION）。
   - **回算时机（r17b 2026-10-26 完整行为图谱）**：① 目标行**自己 submit** 时镜像规则一定算（最可靠）；② 来源行 submit/update/**delete** 触发 `RollUpEventListener`→`FormulaPropertySupport` 事件回算（FIXED+DYNAMIC 混用、多组 OR、COUNTIF/MAX、子表行级条件都验过）；③ ⚠️ 事件回算**只在目标模型发布后几分钟内可靠**，之后静默停止（无报错）——`field.publish --force` 目标模型恢复。发布后平台自动生成 t100 `CALCULATE_RULE` 镜像行，别删。r17 真机：目标行 srcNo=C1、来源 C1 行 amt=100 → 读 100；再提交一条 C1/amt=5 → 读 105。

package/skills/omc-refusals.md

@@ -62,6 +62,14 @@ condition/expression/query shape is off. Compare against
 `omc describe <tool> --example …` and the node-graph prose, then re-save.
 Escalate to 二开 **only** for a real `capability-out-of-coverage` (§2).
 
+`40000 调用数据库发生异常` is the **most opaque** shape code — no detail at all.
+Line up the model's field-level config first: an `AGGREGATION` FORMULA field whose
+`aggregation.schemaCode` points at a **child-table schema** publishes fine and then
+makes every `data.submit`/`data.update` on that model 40000 (r18 2026-10-26 live;
+bisect by deleting/disabling the suspect formula field, which is reversible).
+`omc` now answers `runtime-write-db-exception` and lists the model's formula
+fields; the fix is to aggregate a MAIN-table scalar column instead.
+
 ## 4. Readback mismatch — the write landed but does not match
 
 `*-readback-failed`, `*-readback-mismatch`, `cleanup-absence-readback`,

package/skills/omc-write-hazards.md

@@ -112,6 +112,15 @@ omc call field.publish --env local --args '{"schemaCode":"expense"}'
   **回算可靠性（重要）**：① 目标行**自己 submit** 时镜像规则一定算（最可靠）；② 来源行 submit/update/delete 的事件回算**只在目标模型发布后几分钟内可靠**，之后静默停止（无报错，源变了目标不更新）——重新 `field.publish --force` 目标模型恢复。验收：发布后立刻改来源行并读目标字段；长期对账别依赖事件回算。
 - **同模型（含自己的子表）聚合不可用**：`field.publish` 必抛 305003 —— `publishFormula` 把相对码改写成子表父模型（= 本模型），
   `checkCycleOfAggregation:1032` 判成环。与 payload 无关，8.6.26 与 1.1.25 代码相同。OMC 已写前拒绝 `aggregation-self-schema-cycle`。
+- **聚合目标不能是任何子表 schema，数据项必须是来源主表的标量列**（r18 2026-10-26 真机，代价约 40 次调用）：
+  `aggregation.schemaCode` 指向子表时**能发布**，但目标模型从此整个不可写 —— `data.submit`/`data.update` 全部回
+  `40000 调用数据库发生异常`（无明细）；且子表 schema 无父单单号列，按父单匹配恒为 0。
+  `dataItemCode` 写成 `<子表>.<子列>` 则在 publish 回 309004「使用的聚合数据项不存在」。
+  正解：要子表合计，先在来源**主模型**物化一个数值字段（门户计算规则 / 写入方维护），再聚合该标量。
+  OMC 已写前拒绝 `aggregation-target-is-child-schema`（读一次来源字段清单识别 parentId+sortKey）与
+  `aggregation-data-item-not-scalar`（点号）。
+- **`40000` 的无明细掩码怎么查**：先怀疑字段级配置（上面的聚合/公式），用「删/禁一个公式字段再写一次」二分，
+  不要从表单/权限开始查。OMC 现在会把 40000 转成 `runtime-write-db-exception` 并列出该模型的公式字段。
 - **区别：`FORMULA`（计算公式，`propertyType:100`）字段的 EXPRESSION 模式仍只在前端算** —— API 写入不回填。
 
 ## 规则与业务集成