@stalfh233/omc-cli 0.5.10 → 0.5.12

package/dist/cli-contract.js

@@ -256,7 +256,7 @@ export function classifyResult(result) {
         const suffix = candidates.length > 0 ? `；did you mean: ${candidates.join("、")}` : "；用 `omc commands --json --compact --lane <lane>` 或 `omc next` 定位工具";
         return { status: "error", error: withNext({ code: "invalid-input", message: `unknown tool ${String(result.tool ?? "")}${suffix}`, retryable: false }), exitCode: CLI_EXIT_CODES.invalidInput };
     }
-    if (result.blocker === "tool-input-invalid")
+    if (result.blocker === "tool-input-invalid" || result.blocker === "tool-input-unknown-keys")
         return {
             status: "error",
             error: { ...withNext({ code: "invalid-input", message: String(result.message ?? "tool input is invalid"), retryable: false }), nextCommand: `omc describe ${String(result.tool ?? "<tool>")}` },

package/dist/cli.js

@@ -42,7 +42,7 @@ import { absencePointer } from "./capability-absences.js";
 import { intentConfigRoot, readIntentFile, validateIntentText } from "./intent/cli.js";
 import { intentSchemaBlock, intentExample, intentExampleIds } from "./intent/schema.js";
 import { planIntent, readbackIntent, applyIntent, intentWarnings } from "./intent/plan-apply.js";
-import { listSkills, readSkill, readSkillOutline, readSkillSection, searchSkills } from "./skills.js";
+import { listSkills, readSkill, readSkillOutline, readSkillSection, searchSkills, suggestHelpTopics } from "./skills.js";
 import { parseToolInput, ToolInputError } from "./tool-types.js";
 import { WireError, wireCall } from "./wire.js";
 import { DEFAULT_PULL_CONCURRENCY, GraphIndexAbsentError, GraphPullLockHeldError, MAX_PULL_CONCURRENCY, impactGraph, publishGraphPull, queryGraphReferences, readGraphStatus, searchGraphRules, } from "./graph.js";
@@ -204,7 +204,7 @@ async function cmdDoctor(store, environment, serviceCode) {
             const errcode = error instanceof WireError ? error.errcode : undefined;
             if (errcode === 109001 || /许可证|license/i.test(error.message)) {
                 ok = false;
-                steps.push(`许可证    FAIL 已过期（平台拒绝 apppackage/list：${String(errcode ?? "")}）——续期或更换环境；否则几乎全部读面与所有写面都会被 109001 拒绝`);
+                steps.push(`许可证    FAIL 已过期（平台拒绝 apppackage/list：${String(errcode ?? "")}）——续期或更换环境。注意：109001 是**分面拦截**不是全环境不可用（r40 实证：报表/集成/部分读面被拒，模型/字段/数据面仍可交付）——不要因本项 FAIL 一刀切停步，按需逐面探测并用最小写验证`);
             }
             else {
                 ok = false;
@@ -1361,7 +1361,8 @@ function cmdHelpSearch(topic, query, transport, searchMode, limit) {
     if (singleSection !== undefined) {
         const sliced = readSkillSection(topic, singleSection);
         if (sliced === undefined) {
-            const message = `未知 topic "${topic}"；可用 topic：${topics.map((entry) => entry.name).join("、")}（命令清单见 omc help commands）${commandPointer}`;
+            const suggestions = suggestHelpTopics(topic);
+            const message = `未知 topic "${topic}"；可用 topic：${topics.map((entry) => entry.name).join("、")}（命令清单见 omc help commands）${commandPointer}${suggestions.length > 0 ? `；你可能要找：${suggestions.join("、")}` : ""}`;
             console.error(`help: ${message}`);
             return emitInvalid(transport, { message });
         }
@@ -1382,7 +1383,8 @@ function cmdHelpSearch(topic, query, transport, searchMode, limit) {
     }
     const document = readSkill(topic);
     if (document === undefined) {
-        const message = `未知 topic "${topic}"；可用 topic：${topics.map((entry) => entry.name).join("、")}（命令清单见 omc help commands）${commandPointer}`;
+        const suggestions = suggestHelpTopics(topic);
+        const message = `未知 topic "${topic}"；可用 topic：${topics.map((entry) => entry.name).join("、")}（命令清单见 omc help commands）${commandPointer}${suggestions.length > 0 ? `；你可能要找：${suggestions.join("、")}` : ""}`;
         console.error(`help: ${message}`);
         return emitInvalid(transport, { message });
     }

package/dist/lanes/rule-graph.js

@@ -1491,6 +1491,32 @@ export function validateRuleNodeGraph(graph, ruleCode, schemaCode, options = {})
     const relaxEnums = options.relaxEnums === true;
     if (nodeRecords.length !== nodes.length)
         blockers.push({ code: "rule-graph-node-not-object", message: "nodes 中存在非对象元素" });
+    // r42 头号返工根因（维护者同踩）：filterCondition 的目标查找条件键是
+    // mainConditions（FilterCondition 模型，List<List<TableCondition>>），不是
+    // 触发条件/BRANCH 出口的 conditionGroups——错键被平台静默反序列化为空，
+    // 引擎零循环恒报「查找范围不存在数据」，形似"跨模型 UPDATE 不可用"（曾据
+    // 此误判平台边界，反编译 FilterCondition.mainConditions + mainConditions 正形
+    // 真机回写成功双重实证后纠正）。fail closed：错键当场拒绝。
+    for (const node of nodeRecords) {
+        const nodeType = String(node.nodeType ?? "");
+        if (nodeType !== "UPDATE" && nodeType !== "DELETE" && nodeType !== "CREATE" && nodeType !== "ASSIGN" && nodeType !== "QUERY")
+            continue;
+        const fc = node.filterCondition;
+        if (fc === undefined || fc === null || typeof fc !== "object" || Array.isArray(fc))
+            continue;
+        const record = fc;
+        if ("mainConditions" in record)
+            continue;
+        const wrongKeys = ["conditionGroups", "conditions", "mainTableConditions", "filterGroups", "targetConditionGroups"].filter((key) => key in record);
+        if (wrongKeys.length > 0 || Object.keys(record).length === 0) {
+            blockers.push({
+                code: "rule-graph-filter-condition-wrong-key",
+                nodeCode: String(node.nodeCode ?? ""),
+                key: "filterCondition",
+                message: `${nodeType} "${String(node.nodeCode ?? "")}" 的 filterCondition 键写错（${wrongKeys.join("、") || "空对象"}）——目标查找条件用 mainConditions: [[{targetSchemaDataItem, ruleConditionType, ruleValueType, value|currentSchemaDataItem}]]；conditionGroups 是触发条件/BRANCH 出口的键，放这里会被平台静默忽略 → 引擎恒报「查找范围不存在数据」（形似跨模型回写不可用）。形状见 omc describe rule.save --example business-rule-branch-conditional`,
+            });
+        }
+    }
     // Cross-model write-back: SUPPORTED (verified live 2026-09-28). An UPDATE whose
     // `targetObjectCode` is a DIFFERENT model than the rule's own model writes back
     // correctly once TWO prerequisites hold — a 2026-09-27 probe that reported

package/dist/lanes/workflow.js

@@ -1423,6 +1423,23 @@ async function refuseRequiredOnChildTableFields(session, schemaCode, template, t
  * same edge). This is the "read back, then send the delta" path — without it a
  * subset silently REPLACED the whole activity list and dropped nodes.
  */
+function refusePartialBtnConfigList(activities) {
+    // r32 实证（backlog 清算批）：btnConfigList 局部行=整行替换——只传 {code, remark}
+    // 会把 enabled 静默置 false、commentPermission 置 null（驳回意见必填丢失）。
+    // fail-closed：按钮行不带显式 enabled 一律拒绝，指路 hazards 的整行回写法。
+    for (const activity of activities) {
+        const rows = activity.btnConfigList;
+        if (!Array.isArray(rows))
+            continue;
+        const partial = rows.filter((row) => row !== null && typeof row === "object" && !("enabled" in row));
+        if (partial.length > 0)
+            throw new ToolRefusalError({
+                status: "refused",
+                blocker: "workflow-btnconfig-partial-row",
+                message: `workflow.update: 节点 ${String(activity.activityCode ?? activity.id ?? "")} 的 btnConfigList 存在不带 enabled 的按钮行（${partial.map((row) => String(row.code ?? "?")).join("、")}）——该平台按**整行替换**处理，缺省键会被静默重置（enabled→false、commentPermission→null）。先 workflow.get_published/get_draft 取该按钮整行，改目标属性后整条回写（见 omc help omc-write-hazards --section 按钮）。`,
+            });
+    }
+}
 function mergeCallerDelta(template, draft, options = {}) {
     const { routes: routesRaw, rules: rulesRaw, activities: _raw, edges: edgesRaw, ...rest } = template;
     // `routes` and `edges` are the recipe spellings; `rules` is the platform DTO
@@ -1486,6 +1503,7 @@ function mergeCallerDelta(template, draft, options = {}) {
         return { ...activity, ...override };
     });
     const newActivities = [...callerByOriginal.values()];
+    refusePartialBtnConfigList([...mergedActivities, ...newActivities]);
     // A caller-only code that arrived WITHOUT a type has no draft row to inherit
     // from — refuse it here (the lint allows type-less permission-shape rows
     // precisely because they are expected to match an existing node).
@@ -1595,6 +1613,8 @@ function normalizeWorkflowTemplate(template, draft, options = {}) {
     // comment); give every changed/new node a fresh code, and remap caller routes
     // so they follow.
     const reconciled = rawCaller ? reconcileCallerActivityCodes(rawCaller, draftActivities, options) : undefined;
+    if (rawCaller !== undefined)
+        refusePartialBtnConfigList(rawCaller);
     const activities = reconciled?.activities;
     const codeMap = reconciled?.codeMap ?? new Map();
     const remapCode = (value) => codeMap.get(String(value ?? "")) ?? value;

package/dist/skills.js

@@ -48,6 +48,57 @@ export function listSkills() {
         return { name, description };
     });
 }
+/**
+ * r43 后 backlog：`omc help 编号` 曾零命中（高频中文业务词不是 topic 名）。
+ * 双路建议：①精选同义词表（高频业务词→topic，r24–r43 探针实测检索失败样本）
+ * ②全 topic 节标题子串扫描（自维护——节名改了建议跟着变）。
+ */
+const HELP_TOPIC_SYNONYMS = Object.freeze({
+    编号: ["omc-capabilities"],
+    序列号: ["omc-capabilities"],
+    单号: ["omc-capabilities"],
+    流水号: ["omc-capabilities"],
+    自动编号: ["omc-capabilities"],
+    审批: ["omc-five-piece-flow"],
+    流程: ["omc-five-piece-flow"],
+    回写: ["omc-business-configuration"],
+    跨模型: ["omc-business-configuration"],
+    规则: ["omc-business-configuration"],
+    字典: ["omc-business-configuration"],
+    权限: ["omc-business-configuration"],
+    视图: ["omc-write-hazards"],
+    过滤: ["omc-write-hazards"],
+    条件: ["omc-write-hazards"],
+    删除: ["omc-write-hazards"],
+    清理: ["omc-write-hazards"],
+    子表: ["omc-write-hazards"],
+    表单: ["omc-write-hazards"],
+    验收: ["omc-acceptance-criteria"],
+    入门: ["omc-start-here"],
+    拒绝: ["omc-refusals"],
+});
+export function suggestHelpTopics(query) {
+    if (query === undefined || query.length === 0)
+        return [];
+    const hits = new Set(HELP_TOPIC_SYNONYMS[query] ?? []);
+    for (const skill of listSkills()) {
+        if (skill.name.includes(query) || (skill.description ?? "").includes(query))
+            hits.add(skill.name);
+    }
+    // 节标题扫描：`omc help <topic> --section "<heading>"` 直达
+    for (const name of listSkills().map((skill) => skill.name)) {
+        const outline = readSkillOutline(name);
+        if (outline === undefined)
+            continue;
+        for (const section of outline.sections) {
+            if (section.heading.includes(query)) {
+                hits.add(`omc help ${name} --section "${section.heading}"`);
+                break;
+            }
+        }
+    }
+    return [...hits].slice(0, 5);
+}
 /** Read one methodology topic for `omc help <topic>`. */
 export function readSkill(name) {
     if (!/^[a-z0-9-]+$/.test(name))

package/dist/tool-types.js

@@ -91,6 +91,9 @@ function applyInputAliases(tool, input) {
             continue;
         normalized ??= { ...input };
         normalized[canonical] = input[hit];
+        // 同义词键就地删除：归一后的输入只留规范键——写面未知键 fail-closed
+        // （r43 后）不把已消费的同义词误报成未知键。
+        delete normalized[hit];
     }
     return normalized ?? input;
 }
@@ -111,8 +114,53 @@ function keyRenameHint(issuePath, input, tool) {
     // "你传的是 schemaCode", which pointed at the wrong key.
     return `（该对象在本工具里的键是 ${key}，你传的是 ${synonyms.join("/")}；键名对照见 omc-tool-selection 的 Key-name table）`;
 }
+/** Cheap closest-key suggestion: exact→prefix→shared-start bigrams, threshold keeps it honest. */
+function closestSchemaKey(key, schemaKeys) {
+    if (schemaKeys.has(key))
+        return key;
+    let best;
+    let bestScore = 0;
+    for (const candidate of schemaKeys) {
+        const lower = key.toLowerCase();
+        const candLower = candidate.toLowerCase();
+        let score = 0;
+        if (candLower.startsWith(lower) || lower.startsWith(candLower))
+            score = 0.9;
+        else if (candLower.includes(lower) || lower.includes(candLower))
+            score = 0.7;
+        else {
+            let shared = 0;
+            for (let i = 0; i + 2 <= lower.length; i++)
+                if (candLower.includes(lower.slice(i, i + 2)))
+                    shared++;
+            score = lower.length > 2 ? shared / (lower.length - 1) : 0;
+        }
+        if (score > bestScore) {
+            bestScore = score;
+            best = candidate;
+        }
+    }
+    return bestScore >= 0.4 ? best : undefined;
+}
 export function parseToolInput(tool, input) {
     const normalized = applyInputAliases(tool, input);
+    // r30 引出、r42/r43 再证：静默丢弃错键是头号返工源（dictionary.save items
+    // 未知键、跨模型 filterCondition 错键同族）。写面 fail-closed——未知顶层键
+    // 当场拒绝并给最接近的合法键提示；读面保持宽松（探查性调用常见无害附加）。
+    if (tool.kind === "write") {
+        const schemaKeys = new Set(Object.keys(tool.inputSchema));
+        const unknown = Object.keys(normalized).filter((key) => !schemaKeys.has(key));
+        if (unknown.length > 0) {
+            const suggestions = unknown.map((key) => `${key}→${closestSchemaKey(key, schemaKeys) ?? "（无相近键，omc describe <tool> 看参数表）"}`);
+            throw new ToolInputError({
+                status: "error",
+                blocker: "tool-input-unknown-keys",
+                tool: tool.name,
+                message: `写面工具不接受未知键（会被静默丢弃）：${unknown.join("、")}。最接近的合法键：${suggestions.join("；")}。参数表：omc describe ${tool.name}`,
+                issues: unknown.map((key) => ({ path: [key], code: "unrecognized_key", message: `unknown key; closest: ${closestSchemaKey(key, schemaKeys) ?? "none"}` })),
+            });
+        }
+    }
     const result = z.object(tool.inputSchema).safeParse(normalized);
     if (result.success)
         return result.data;

package/package.json

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

package/skills/omc-business-configuration.md

@@ -122,6 +122,7 @@ rules:
 
 - **每个 filter 项必须有且只有一个条件来源**：`from`（动态 EQ）或一个比较键（`equals`/`notEquals`/`gt`/`gte`/`lt`/`lte` + 标量）。缺来源 `intent-rule-leaf-source-missing` 拒绝；**绝不**静默成 `EQ null`。
 - 动作节点的条件分「定位数据」与「执行门」两类，**别混**（详见下「规则图的触发条件」）。
+- **跨模型 UPDATE 目标查找键=`filterCondition.mainConditions`**（`[[{targetSchemaDataItem, ruleConditionType, ruleValueType, value|currentSchemaDataItem}]]`，非触发条件的 conditionGroups——错键静默反序列化为空，引擎恒报「查找范围不存在数据」形似跨模型不可用，r42 曾误判；校验 `rule-graph-filter-condition-wrong-key` 已拦）。连坑：叶取值键 `value` 非 fixedValue；`rule.node.update` 只写 DRAFT，改完须 `rule.enable`/`--publish` 重发布才生效。
 - **跨模型写（`targetObjectCode`≠规则模型）平台支持、可运行时生效**（2026-09-28 真机复核）。两个前提：① 承载它的规则必须真的触发——`Create` 规则在提交时触发；`Update` 规则只在 `data.update` 触发，**submit 不执行它**（放进 `Update` 是典型静默空转，lint 警告 `rule-graph-cross-model-update-trigger-inert`；也可绑定流程事件如 `end`）。② 目标行必须已提交——目标查询不匹配 DRAFT 行，`data.save` 未 submit 的行不回写。
 - 关联字段：`type: WORK_SHEET` + `relativeCode: <目标模型>` + `options.displayField`，与 `field.create` 行形状一致。（键名是 `relativeCode`，wire 键 `relativeSchemaCode`，别混。）
 - 节点显示名用 activity 级的 `name`（`participant.name` 只作参与者说明，平台不认作节点名；`{type: Originator, name: 部门负责人}` 会被工具提升为节点名）。

package/skills/omc-write-hazards.md

@@ -55,7 +55,7 @@ omc help omc-write-hazards
 - **BIZ_ACTION 判成功只看传输**：REST 适配器解析响应后直接返回，**不校验 `errcode`**。扩展接口回 `{"errcode":50000}` + HTTP 200 会被当成节点成功（日志 `biz action node execute successful`）。要阻断必须走表单 `onValidate` 或数据规则，不能靠业务返回码。
 - **`rule.run`/自定义规则不回写出参**（r26 实证 2 轮）：出参合并只发生在预置 Update 规则的执行上下文；`rule.run` 手动触发与自定义规则不把服务出参写回本模型——出参落表要走「BIZ_ACTION 节点 outputMappings + 数据事件触发」，验收用 data.load 看字段而非 rule.run 回执。
 - **出参回写三前提（r28b 8 组实验定案，单点总纲）**：① 响应 JSON 根级平铺出参键 ② 预置 Create/Update 规则上下文 ③ data.submit/data.update 触发（data.save 不触发）。三者缺一出参恒 null 且节点日志仍 successful——外部接口回信封的（`{code,message,data:[...]}`），先落平铺整形端点（平台扩展）再配 outputMappings，不要反复换规则形状试。
-- **布尔出参映射到文本字段 → ClassCastException 50000**（r28b 实证）：服务出参 `bizPropertyType:LOGICAL` 的值映射到 SHORT_TEXT 字段会让规则执行炸 50000——布尔出参只能映射 LOGICAL 字段；要落文本先在扩展侧转字符串。
+- **布尔出参映射到文本字段 → ClassCastException 50000**（r28b）：LOGICAL 出参映射 SHORT_TEXT 即炸——布尔只映射 LOGICAL 字段，落文本先在扩展侧转字符串。
 - **审批提交的 formData 带子表数组 = 追加行**（r28b 实证）：approval submit 的 formData 里带子表数组会被平台当「追加行」处理，审批回执只回传主表字段——审批链路里要改子表行，用 data.update 单独写，不要塞进 formData。
 - **workItemId 不在 instanceActivity 里**（r28b 实证）：流程实例活动查询不返回 workItemId；办理待办要的 workItemId 从 `search_workitems?state=PENDING` 的 `content[].id` 取。
 - **模型创建/删除非原子，会有半态残留**（r28b 实证 ~20min）：model.create 在表单层撞错（如「表单已存在」）时 schema 可能已半落库——refused 后换名重试前先 model.list 核对半态并清理；同理模型删除后平台读面不可见但库里可能留僵尸行（引擎报 `appFunction not exist` 就是它在作祟），迁移/复用编码前先核对。
@@ -193,13 +193,15 @@ omc call field.publish --env local --args '{"schemaCode":"expense"}'
 - **`transferDepartment` 迁人不迁作用域**（r33 真机）：换部门后 `role.userScope` 仍指旧部门——迁移后复核成员作用域。
 - **`user.delete` 是软删**（r33 真机）：回 `deleted:true` 但 `user.info` 仍 `exists:true`（DISABLE）——验证口径用列表/状态，别称物理清除。
 - **「名称重复 200001」≠ 失败**（r33 真机）：多为首次已建成、重发才撞重复——先读回确认首建结果再决定。
-- **删了的东西≠删干净（孤儿三连，1101 三例）**：①删模型留收藏+h_biz_* 行→日志刷 `appFunction not exist`；②规则死服务 A1→submit 500015；③流程模板删后绑定残留（h_workflow_relative_object/header 指死 code）→getWorkflow 50000。都是删上游留下游引用、报错在别处——先查孤儿引用，维护者按表清。
-- **两套条件 DSL（r38/r39）**：listview.configure `conditions`={propertyCode, filterType, **defaultValue**}（值键叫 defaultValue）；data.list `filter`={op, field, value}。互抄必错——形状各查 `--param conditions`/`--param filter`。
-- **表单读回以控件清单为准，不看布尔位（r40）**：form.get 的 `published` 布尔会 false→true 抖动；draftViewJson 可含已删字段悬空引用（rebuild 自清）。判定布局依据=`publishedControlCodes` 内容；configure_form 回执已点名 `missingFieldCodes`。
-- **submit 被拒仍可能已落草稿（r40）**：`data.save --submit:true` 遇许可证/权限拒绝时平台可能在拒答前已写草稿——拒后 data.list 对账 total，残留 data.delete 单清。
-- **空聚合≠模型存在（r40）**：rule.list/datarule.list 对不存在模型静默回空——「0 条规则」≠模型在（mcc_contract 从不存在却一路答空）。rule.list 已修（空时探真身标 `modelPresent:false`）；datarule.list 同陷阱——判存在性一律 model.inspect。
-- **form.publish(rebuild) 后立即 submit 可能丢字段（r41 疑似竞态）**：链内演示行 `order_no` 落 null，同形状延迟复现正常。落演示行后 `data.load` 抽验非选项字段，缺值 data.save 单补，不重跑整链。
+- **删了的东西≠删干净（孤儿三连，1101 三例）**：①删模型留收藏/h_biz_* 行→日志 appFunction not exist；②规则死服务 A1→submit 500015；③流程模板删后绑定残留→getWorkflow 50000。都是报错在别处——先查孤儿引用。
+- **两套条件 DSL（r38/r39）**：listview `conditions`={propertyCode, filterType, defaultValue}；data.list `filter`={op, field, value}。互抄必错。
+- **表单读回以控件清单为准（r40）**：`published` 布尔会抖动、draftViewJson 可含悬空引用（rebuild 自清）——判定依据=publishedControlCodes 内容；configure_form 回执已点名 missingFieldCodes。
+- **submit 被拒仍可能已落草稿（r40）**：许可证/权限拒绝可能拒答前已写草稿——拒后对账 total，残留单清。
+- **空聚合≠模型存在（r40）**：rule.list 对不存在模型静默回空（已修，空时标 modelPresent:false）；datarule.list 响亮拒 601003。判存在性用 model.inspect。
+- **form.publish(rebuild) 后立即 submit 可能丢字段（r41 疑似竞态）**：链内演示行 order_no 落 null，延迟复现正常。落行后 data.load 抽验，缺值单补。
 - **data.list 选项列投影可为 null（r40/r41）**：`all:true`/queryCode 下 RADIO 读 null，`data.load`/`filter` 才有值——验证选项字段以 data.load 为权威。
+- **流程绑定行不可 data.save 直改（r42）**：COMPLETED 行直改打回 PROCESSING、值不落、可能岔行——走提交流程。连续 submit 撞限流 100005——批量先 workitem.list 取 workItemId。
+- **带流程模型 data.submit 必停审批位（r43）**：批量初始化滞留待办——流程加条件分支按单据类型直达结束。SEQNO 不回收。
 - **读回形状≠可写形状**（r38）：`listview.get` 读回条件带 `null` 字段，原样回写被拒——读回是输出形态，可写面有自己的契约；null 归一（false/省略）或只回写要改的键。
 - **data.list 的 columns 收窄可能静默空**（r38）：非视图列字段投影 null；甚至 columns+分页 total>0 而 items 0——判"无数据"先去 columns 复查或用 data.load。