@stalfh233/omc-cli 0.6.11 → 0.6.13

package/dist/lanes/form.js

@@ -290,9 +290,13 @@ export function registerFormLane(tools) {
             draftViewJson: z.string().optional().describe("行分组：JSON 二维字符串数组 `[[\"codeA\",\"codeB\"],[\"codeC\"]]`——**一行几个 code 就是几列**（不是改 span 来改列数）；末行只放一个 code 即整宽。每个 code 必须同时出现在 draftAttributesJson 里。现成样例：`omc describe form.draft --example two-column-layout`"),
             draftAttributesJson: z.string().optional().describe("控件表：JSON 对象 `{ \"codeA\": { key:\"codeA\", type: <控件类型号>, options:{ name:\"显示名\", span: 12 } } }`。`span` 是 24 栅格宽度：两列各 span:12、整宽 span:24（必须与 draftViewJson 的行分组一致，否则 layout_coverage_mismatch）。现成样例：`omc describe form.draft --example two-column-layout`"),
             draftHtmlJson: z.string().optional(),
-            fieldCodes: z.array(z.string().min(1)).optional().describe("脚手架绑定的已发布字段（按此顺序）；由 configure_form/intent 显式传入"),
+            fieldCodes: z.array(z.string().min(1)).optional().describe("脚手架绑定的已发布字段（按此顺序）；由 configure_form/intent 显式传入。子表列写「父字段.子列」等价于 childColumns"),
+            childColumns: z
+                .array(z.object({ parent: z.string().min(1), fieldCodes: z.array(z.string().min(1)) }))
+                .optional()
+                .describe("把子表列绑进**已有** Sheet201 控件的 columns（issue #24）：[{parent:\"items\",fieldCodes:[\"category\"]}]。只追加列，不动其它控件/布局行；无已存布局时退回 scaffold"),
             rebuild: z.boolean().optional().describe("true 时丢弃现有草稿布局，按已发布字段重新生成（新增字段/子表要用它；默认保留现有草稿）"),
-            fromReadback: z.boolean().optional().describe("true = 本次 draftViewJson/draftAttributesJson 来自 form.get 的原样读回（平台自身布局可能含子表列行/系统行超宽）；工具会与已存面逐字比对，只有确实一致才放行，被改动过的面照常拒绝"),
+            fromReadback: z.boolean().optional().describe("true = 本次 draftViewJson/draftAttributesJson 来自 form.get 的**逐字未改动**原文（平台自身布局可能含子表列行/系统行超宽，逐字回写放行）。语义是「回写」不是「我读过」：读过之后改过一个字符就不再是回读，会被拒（去掉本参数按普通写面校验）。只加子表列请用 configure_form 的 childColumns"),
             allowEmptyLayout: z.boolean().optional().describe("显式放行空布局（\"[]\"/\"{}\"）写入；默认拒绝（form-empty-layout），防设计器 Save 清空后照写丢控件"),
             buttons: z
                 .array(z.record(z.unknown()))
@@ -365,14 +369,18 @@ export function registerFormLane(tools) {
             fieldCodes: z
                 .array(z.string().min(1))
                 .optional()
-                .describe("表单要绑定的已发布字段（按此顺序）；省略则脚手架绑定全部已发布字段；未知 code 拒绝（form-fieldcodes-unknown）"),
-            rebuild: z.boolean().optional().describe("true 时丢弃现有草稿布局，按已发布字段重新生成（新增字段/子表要用它；默认保留现有草稿）"),
+                .describe("表单要绑定的已发布字段（按此顺序）；省略则脚手架绑定全部已发布字段；子表列写「父字段.子列」（如 items.category），等价于 childColumns；未知 code 拒绝（form-fieldcodes-unknown）"),
+            childColumns: z
+                .array(z.object({ parent: z.string().min(1), fieldCodes: z.array(z.string().min(1)) }))
+                .optional()
+                .describe("把子表列绑进已有 Sheet201 控件的 columns（不动其它控件/布局）：[{parent:\"items\",fieldCodes:[\"category\"]}]。给已有表单加子表列时用它——rebuild:true 会丢弃手工布局与控件表达式"),
+            rebuild: z.boolean().optional().describe("true 时丢弃现有草稿布局，按已发布字段重新生成（新增字段/子表要用它；默认保留现有草稿，只增量处理 fieldCodes/childColumns）"),
             draftHtmlJson: z.string().optional(),
         },
         plan: (args) => ({
             summary: writeSummary("configure_form", args, undefined, "plan"),
             actions: [
-                { tool: "form.draft", args: { schemaCode: args.schemaCode, sheetCode: resolveSheetCode(args.schemaCode, args.sheetCode), ...(args.fieldCodes ? { fieldCodes: args.fieldCodes } : {}), ...(args.rebuild === true ? { rebuild: true } : {}), ...(typeof args.draftHtmlJson === "string" ? { draftHtmlJson: args.draftHtmlJson } : {}) } },
+                { tool: "form.draft", args: { schemaCode: args.schemaCode, sheetCode: resolveSheetCode(args.schemaCode, args.sheetCode), ...(args.fieldCodes ? { fieldCodes: args.fieldCodes } : {}), ...(args.childColumns ? { childColumns: args.childColumns } : {}), ...(args.rebuild === true ? { rebuild: true } : {}), ...(typeof args.draftHtmlJson === "string" ? { draftHtmlJson: args.draftHtmlJson } : {}) } },
                 { tool: "form.publish", args: { schemaCode: args.schemaCode, sheetCode: resolveSheetCode(args.schemaCode, args.sheetCode) } },
             ],
         }),
@@ -386,6 +394,7 @@ export function registerFormLane(tools) {
                 schemaCode: args.schemaCode,
                 sheetCode,
                 ...(args.fieldCodes ? { fieldCodes: args.fieldCodes } : {}),
+                ...(args.childColumns ? { childColumns: args.childColumns } : {}),
                 ...(args.rebuild === true ? { rebuild: true } : {}),
                 ...(typeof args.draftHtmlJson === "string" ? { draftHtmlJson: args.draftHtmlJson } : {}),
             });
@@ -401,13 +410,50 @@ export function registerFormLane(tools) {
             // r40 F4：published=true ≠ 请求的字段进了布局——模型已有手工布局时，非 rebuild
             // 草稿保留原控件，新字段不会出现，而 formPublished 仍是 true（假成功）。
             // readback 必须核「请求面是否真的落进 published 控件」，缺了就点名+给重建路。
-            const missing = (args.fieldCodes ?? []).filter((code) => !publishedControlCodes.includes(code));
+            const missing = (args.fieldCodes ?? []).filter((code) => !code.includes(".") && !publishedControlCodes.includes(code));
+            // issue #24：子表列不进 viewJson / 顶层 control codes——它们的权威面是父
+            // Sheet201 控件的 columns。请求了却没落进 columns 就是「页面仍不可见」，
+            // 必须逐条点名，不能报 formPublished:true 了事。
+            const requestedChild = [
+                ...(args.childColumns ?? []),
+                ...(args.fieldCodes ?? []).filter((code) => code.includes(".")).map((entry) => {
+                    const [parent, ...rest] = entry.split(".");
+                    return { parent, fieldCodes: [rest.join(".")] };
+                }),
+            ];
+            let childColumnReadback = {};
+            if (requestedChild.length > 0) {
+                const publishedAttributes = (() => {
+                    try {
+                        return JSON.parse(String(pub.publishedAttributesJson ?? "{}"));
+                    }
+                    catch {
+                        return {};
+                    }
+                })();
+                const missingChildColumns = [];
+                for (const request of requestedChild) {
+                    const columns = publishedAttributes[request.parent]?.columns;
+                    const bound = new Set(Array.isArray(columns) ? columns.map((column) => String(column.key ?? "")) : []);
+                    for (const code of request.fieldCodes)
+                        if (!bound.has(code))
+                            missingChildColumns.push({ parent: request.parent, code });
+                }
+                childColumnReadback = {
+                    childColumnsRequested: requestedChild,
+                    childColumnsPresent: missingChildColumns.length === 0,
+                    ...(missingChildColumns.length > 0
+                        ? { missingChildColumns, warning: `子表列 ${missingChildColumns.map((entry) => `${entry.parent}.${entry.code}`).join("、")} 未落进已发布表单的 Sheet201 columns——页面仍看不到；用 childColumns 绑定后重跑 form.publish` }
+                        : {}),
+                };
+            }
             return {
                 steps: results,
                 readback: {
                     formPublished: pub.published === true,
                     publishedHtmlJsonPresent: typeof pub.publishedHtmlJson === "string",
                     publishedControlCodes,
+                    ...childColumnReadback,
                     ...(missing.length > 0
                         ? { missingFieldCodes: missing, warning: `表单已发布，但请求的 ${missing.join("、")} 不在 published 控件里（既有手工布局未带上新字段）——重跑 configure_form 带 rebuild:true（或 form.draft {rebuild:true} → form.publish）后重验本字段` }
                         : {}),

package/dist/lanes/list-view-contract.js

@@ -122,7 +122,7 @@ export const LIST_VIEW_LANE_CONTRACT = Object.freeze({
         }),
         "listview.create": Object.freeze({
             scope: LIST_VIEW_SCOPE,
-            description: "创建自定义列表视图（query/create，强制 LIST/showOnPc/unpublished 默认）。**业务展示的默认入口就是自定义视图**：平台在 model.create 时自动生成的默认视图（code = schemaCode，系统自带）**不作为业务展示用**——列别在默认视图上堆、也别带系统字段；按需求建自定义视图（listview.create 命名业务视图），列**只用业务字段**，筛选条件**按需求选少数几个**（不要照搬全部字段/默认条件）。readback 见 get_header。",
+            description: "创建自定义列表视图（query/create，强制 LIST/showOnPc/unpublished 默认）。本工具只收 schemaCode/name/code——**列配置不在这里**：建完后用 `listview.configure` 的 fieldCodes 配列（不要把 fieldCodes 传给 create）。**业务展示的默认入口就是自定义视图**：平台在 model.create 时自动生成的默认视图（code = schemaCode，系统自带）**不作为业务展示用**——列别在默认视图上堆、也别带系统字段；按需求建自定义视图（listview.create 命名业务视图），列**只用业务字段**，筛选条件**按需求选少数几个**（不要照搬全部字段/默认条件）。readback 见 get_header。",
         }),
         "listview.configure": Object.freeze({
             scope: LIST_VIEW_SCOPE,
@@ -166,7 +166,7 @@ export function assertListViewContract() {
         throw new Error("list-view contract must pin queryLayer");
     if (!LIST_VIEW_WIRE.deleteBody.includes("query/delete"))
         throw new Error("list-view contract must pin the delete endpoint");
-    assertDescriptionCarries(LIST_VIEW_LANE_CONTRACT, "listview.create", ["query/create", "LIST", "get_header"]);
+    assertDescriptionCarries(LIST_VIEW_LANE_CONTRACT, "listview.create", ["query/create", "LIST", "get_header", "listview.configure"]);
     // Button scripts are stored in h_biz_button.actionConfig.scriptData (a JSON
     // STRING); listview.get/--buttons and form.get/--buttonScripts surface them
     // without a round trip through the artifact.

package/dist/lanes/list-view.js

@@ -5,7 +5,7 @@ import { capabilityArg, environmentArg } from "../args.js";
 import { governedRead } from "../read.js";
 import { writeTool } from "../write.js";
 import { encodeJsonColumn } from "../json-column.js";
-import { defineTool, ToolRefusalError } from "../tool-types.js";
+import { defineTool, ToolInputError, ToolRefusalError } from "../tool-types.js";
 import { wireCall, wireRows, WireError } from "../wire.js";
 import { QUERY_ACTION_TYPE } from "omc-core/list-view-wire";
 import { resolveModelTreeNode } from "./model.js";
@@ -454,13 +454,44 @@ export function registerListViewLane(tools) {
         lane: LIST_VIEW_LANE,
         scope: LIST_VIEW_TOOLS["listview.create"].scope,
         description: LIST_VIEW_TOOLS["listview.create"].description,
-        inputSchema: { schemaCode: z.string().min(1), name: z.string().min(1), code: z.string().optional().describe("视图 code；省略时**默认取 schemaCode**（与 listview.get / listview.list / rollback 的默认视图口径一致）。平台侧 code 必填，本工具会替你填，不要再依赖不回执的猜测（r26 真机：不传直接被 errcode 10005「编码不能为空」拒绝，白跑一轮线上往返）") },
+        inputSchema: {
+            schemaCode: z.string().min(1),
+            name: z.string().min(1),
+            code: z.string().optional().describe("视图 code；省略时**默认取 schemaCode**（与 listview.get / listview.list / rollback 的默认视图口径一致）。平台侧 code 必填，本工具会替你填，不要再依赖不回执的猜测（r26 真机：不传直接被 errcode 10005「编码不能为空」拒绝，白跑一轮线上往返）"),
+            // r29b F5a: create 没有列参数。接受 fieldCodes 只是为了给可执行 nextCommand，
+            // 避免未知键算法给出「fieldCodes→code」这种南辕北辙的建议。
+            fieldCodes: z.array(z.string()).optional().describe("本工具不配列——若传了会拒绝并指引 listview.configure"),
+        },
+        // dry-run 不跑 execute——fieldCodes 必须在 preflight 拦，否则 dry-run 仍会放行。
+        preflight: (args) => {
+            if (Array.isArray(args.fieldCodes) && args.fieldCodes.length > 0) {
+                const code = args.code ?? args.schemaCode;
+                throw new ToolInputError({
+                    status: "error",
+                    blocker: "tool-input-invalid",
+                    tool: "listview.create",
+                    message: "listview.create 不接受列参数：先 create（schemaCode/name/code），再 listview.configure 配 fieldCodes。" +
+                        "不要把 fieldCodes 当成 create 的拼写错误去改成 code。",
+                    nextCommand: `omc call listview.configure --args '${JSON.stringify({ schemaCode: args.schemaCode, code, fieldCodes: args.fieldCodes })}'`,
+                });
+            }
+        },
         execute: async (session, args) => {
             // r26 真机：`code` 在 schema 里可选，但三处读面/rollback 都用
             // `args.code ?? schemaCode`，唯独 create 把 undefined 原样发给平台 →
             // `errcode 10005 编码不能为空`，探针白跑一轮。默认视图 code 就是
             // schemaCode（listview.list 的 hint 也这么写），这里对齐。
             const code = args.code ?? args.schemaCode;
+            if (Array.isArray(args.fieldCodes) && args.fieldCodes.length > 0) {
+                throw new ToolInputError({
+                    status: "error",
+                    blocker: "tool-input-invalid",
+                    tool: "listview.create",
+                    message: "listview.create 不接受列参数：先 create（schemaCode/name/code），再 listview.configure 配 fieldCodes。" +
+                        "不要把 fieldCodes 当成 create 的拼写错误去改成 code。",
+                    nextCommand: `omc call listview.configure --args '${JSON.stringify({ schemaCode: args.schemaCode, code, fieldCodes: args.fieldCodes })}'`,
+                });
+            }
             // Ticket 81: read the header FIRST — a same-code retry short-circuits
             // with the existing view and sends ZERO create wires (the live
             // post-timeout retry otherwise answers 303002 编码重复).
@@ -545,6 +576,37 @@ export function registerListViewLane(tools) {
                     unknown: unknownRefs,
                     message: `fieldCodes 引用了模型 ${args.schemaCode} 发布面上不存在的字段（可给 propertyCode 或字段名）：${unknownRefs.join("、")}；先 field.create + field.publish，或修正引用`,
                 });
+            // r29b F5b: 列表视图不支持整列展示子表——平台会 50000「服务异常」，dry-run
+            // 以前也不拦。写前按 propertyType=CHILD_TABLE(8) 拒绝并给替代。
+            const childTableRefs = args.fieldCodes
+                .map((ref) => {
+                const resolved = resolveFieldRef(fieldRows, ref);
+                if (!resolved)
+                    return null;
+                const field = fieldRows.find((row) => (row.code ?? row.propertyCode) === resolved.code);
+                const type = Number(field.type ?? field.propertyType);
+                return type === 8 ? resolved.code : null;
+            })
+                .filter((code) => typeof code === "string");
+            if (childTableRefs.length > 0) {
+                const alternatives = args.fieldCodes.filter((ref) => {
+                    const resolved = resolveFieldRef(fieldRows, ref);
+                    if (!resolved)
+                        return false;
+                    const field = fieldRows.find((row) => (row.code ?? row.propertyCode) === resolved.code);
+                    return Number(field.type ?? field.propertyType) !== 8;
+                });
+                throw new ToolInputError({
+                    status: "error",
+                    blocker: "tool-input-invalid",
+                    tool: "listview.configure",
+                    message: `列表视图不支持整列展示子表（propertyType=CHILD_TABLE）：${childTableRefs.join("、")}。` +
+                        "平台会回 50000 服务异常。请改用子表首列/展开列，或在详情页（form）看子表；列表只放主表标量列。",
+                    nextCommand: alternatives.length > 0
+                        ? `omc call listview.configure --args '${JSON.stringify({ schemaCode: args.schemaCode, code, fieldCodes: alternatives })}'`
+                        : `omc call field.list --args '${JSON.stringify({ schemaCode: args.schemaCode, published: true })}'`,
+                });
+            }
             // replaceColumns: the caller's fieldCodes ARE the view. Start from an
             // empty set so system columns fall away unless listed — a system field
             // can still be shown by naming its code in fieldCodes (createdTime etc.
@@ -818,6 +880,40 @@ export function registerListViewLane(tools) {
             return { performed: { errcode: performed.errcode }, readback };
         },
         preflight: assertListViewConfigureShape,
+        // r29b F5b: dry-run 也必须拦 CHILD_TABLE 列，否则「计划能过、真写 50000」。
+        dryRunPayload: async (session, args) => {
+            const code = args.code ?? args.schemaCode;
+            const fieldRows = wireRows((await wireCall(session, { path: ENDPOINTS.fieldList, query: { schemaCode: args.schemaCode, isPublish: "true" } })).data);
+            const childTableRefs = args.fieldCodes
+                .map((ref) => {
+                const resolved = resolveFieldRef(fieldRows, ref);
+                if (!resolved)
+                    return null;
+                const field = fieldRows.find((row) => (row.code ?? row.propertyCode) === resolved.code);
+                return Number(field.type ?? field.propertyType) === 8 ? resolved.code : null;
+            })
+                .filter((value) => typeof value === "string");
+            if (childTableRefs.length > 0) {
+                const alternatives = args.fieldCodes.filter((ref) => {
+                    const resolved = resolveFieldRef(fieldRows, ref);
+                    if (!resolved)
+                        return false;
+                    const field = fieldRows.find((row) => (row.code ?? row.propertyCode) === resolved.code);
+                    return Number(field.type ?? field.propertyType) !== 8;
+                });
+                throw new ToolInputError({
+                    status: "error",
+                    blocker: "tool-input-invalid",
+                    tool: "listview.configure",
+                    message: `列表视图不支持整列展示子表（propertyType=CHILD_TABLE）：${childTableRefs.join("、")}。` +
+                        "平台会回 50000 服务异常。请改用子表首列/展开列，或在详情页（form）看子表；列表只放主表标量列。",
+                    nextCommand: alternatives.length > 0
+                        ? `omc call listview.configure --args '${JSON.stringify({ schemaCode: args.schemaCode, code, fieldCodes: alternatives })}'`
+                        : `omc call field.list --args '${JSON.stringify({ schemaCode: args.schemaCode, published: true })}'`,
+                });
+            }
+            return { wouldChange: true, summary: `即将配置列表视图 ${args.schemaCode}/${code} 的列` };
+        },
         rollback: listviewRollbackSpec("listview.configure"),
     });
     writeTool({

package/dist/lanes/meta.js

@@ -12,27 +12,47 @@ export function registerMetaLane(tools) {
         layer: "meta",
         kind: "meta",
         // r28k F5：manifest 是 lane 粒度，不是 capability id（放首句，避免 summary 截断吞掉）。
-        description: `Indexed by lane (not capability id, one lane may have multiple rows) — for "can X be used?" use omc capability <id>. ${META_TOOLS["coverage.manifest"].description}`,
+        // r30f F6：capability 参数同时接受能力描述名与 lane id（归一）；按能力 id 详查仍用 omc capability <id>（如 listview）。
+        description: `Indexed by lane — capability arg accepts lane id (W1-list-view); use omc capability listview for "can X?". ${META_TOOLS["coverage.manifest"].description}`,
         inputSchema: {
             full: z.boolean().optional().describe("返回完整覆盖投影；默认返回紧凑摘要"),
             // r28k F6（真机 2026-11-05）：探针传 `{"capability":"report"}` 想按能力过滤，
             // schema 只有 full，参数被**静默丢弃**，拿到 46 项还以为已过滤——多读 6.3KB。
             // 与其拒绝，不如真的过滤：manifest 行本身就有 capability 字段（免费）。
-            capability: z.string().optional().describe("按能力名过滤（大小写不敏感，子串匹配 capability 字段）；lane 请用 omc capability <id>"),
+            // r30f F6：同时接受 lane id（W1-list-view）——旧提示「按 id 查用 omc capability」对 lane id 是错的。
+            capability: z.string().optional().describe("能力描述名或 lane id（子串匹配 capability/lane）；详查用 omc capability listview"),
             lane: z.string().optional().describe("按 lane 名过滤（子串匹配）"),
         },
         handler: async (ctx, args) => {
             const full = args.full === true;
             const capabilityFilter = typeof args.capability === "string" && args.capability.trim() !== "" ? args.capability.trim().toLowerCase() : undefined;
             const laneFilter = typeof args.lane === "string" && args.lane.trim() !== "" ? args.lane.trim().toLowerCase() : undefined;
-            // r28k F6：过滤后为空要当成**没命中**说出来，别回一个看起来正常的空清单。
-            const matched = ctx.manifest.items.filter((item) => (capabilityFilter === undefined || String(item.capability ?? "").toLowerCase().includes(capabilityFilter)) &&
-                (laneFilter === undefined || String(item.lane ?? "").toLowerCase().includes(laneFilter)));
+            // r30f F6：capability 参数归一匹配 capability 描述名 **或** lane id。
+            const matched = ctx.manifest.items.filter((item) => {
+                const lane = String(item.lane ?? "").toLowerCase();
+                const capability = String(item.capability ?? "").toLowerCase();
+                const capabilityOk = capabilityFilter === undefined
+                    || capability.includes(capabilityFilter)
+                    || lane.includes(capabilityFilter);
+                const laneOk = laneFilter === undefined || lane.includes(laneFilter);
+                return capabilityOk && laneOk;
+            });
+            const totalBeforeFilter = ctx.manifest.items.length;
             const filterNote = capabilityFilter === undefined && laneFilter === undefined
                 ? undefined
                 : matched.length === 0
-                    ? { filtered: { capability: capabilityFilter ?? null, lane: laneFilter ?? null }, matched: 0, hint: `没有 capability/lane 命中「${capabilityFilter ?? laneFilter}」。manifest 的 capability 是**能力描述名**（如 "Report builder"），不是能力 id；按 id 查用 omc capability <id>` }
-                    : { filtered: { capability: capabilityFilter ?? null, lane: laneFilter ?? null }, matched: matched.length, total: ctx.manifest.items.length };
+                    ? {
+                        filtered: { capability: capabilityFilter ?? null, lane: laneFilter ?? null },
+                        matched: 0,
+                        totalBeforeFilter,
+                        hint: `没有 capability/lane 命中「${capabilityFilter ?? laneFilter}」。capability 参数可传能力描述名（如 Report）或 lane id（如 W1-list-view）；按能力 id 详查用 omc capability listview / omc capabilities`,
+                    }
+                    : {
+                        filtered: { capability: capabilityFilter ?? null, lane: laneFilter ?? null },
+                        matched: matched.length,
+                        totalBeforeFilter,
+                        totalScope: "filtered",
+                    };
             const items = matched.map((item) => full
                 ? {
                     lane: item.lane,
@@ -59,7 +79,8 @@ export function registerMetaLane(tools) {
                     },
                 };
             }
-            const byStatus = ctx.manifest.items.reduce((acc, item) => {
+            // r30f F6：byStatus 与 total 同口径（过滤后）；另给 totalBeforeFilter，避免 total:0 与 byStatus 46 并列。
+            const byStatus = matched.reduce((acc, item) => {
                 acc[item.status] = (acc[item.status] ?? 0) + 1;
                 return acc;
             }, {});
@@ -68,10 +89,15 @@ export function registerMetaLane(tools) {
                 manifest: {
                     version_family: ctx.manifest.version_family,
                     anchor_version: ctx.manifest.anchor_version,
-                    counts: { total: items.length, byStatus },
+                    counts: {
+                        total: items.length,
+                        totalScope: filterNote !== undefined ? "filtered" : "all",
+                        ...(filterNote !== undefined ? { totalBeforeFilter } : {}),
+                        byStatus,
+                    },
                     items,
                     ...(filterNote !== undefined ? { filter: filterNote } : {}),
-                    hint: "manifest 按 lane 索引（同一 lane 可有多行细项，status 不统一），不是 capability id；答「X 能力能不能用」请用 omc capability <id> / omc capabilities。full:true 取完整投影（scope/reason/tools）；工具清单用 commands --json --compact",
+                    hint: "manifest 按 lane 索引（同一 lane 可有多行细项，status 不统一）。capability 参数可传能力描述名或 lane id（如 W1-list-view）；答「X 能力能不能用」请用 omc capability listview / omc capabilities。full:true 取完整投影（scope/reason/tools）；工具清单用 commands --json --compact",
                 },
             };
         },

package/dist/lanes/model-contract.js

@@ -100,7 +100,7 @@ export const MODEL_LANE_CONTRACT = Object.freeze({
     tools: Object.freeze({
         "model.list": Object.freeze({
             scope: MODEL_SCOPE,
-            description: "List the models in an application (apppackage/trees, type==='BizModel') as a compact { code, name } inventory. Fills the gap where enumerating models otherwise required discover_environment + an artifact read. `applicationCode` optional (configured/default app); `filter` is a substring match on code/name.",
+            description: "List the models in an application (apppackage/trees, type==='BizModel') as a stable `{code,schemaCode,name[,legacyString]}` inventory (never a bare `code｜name` string — diet 也保对象形). Fills the gap where enumerating models otherwise required discover_environment + an artifact read. `applicationCode` optional (configured/default app; unknown → app-not-found); `filter`/`search`/`query` are interchangeable substring matches on code/name."
         }),
         "model.inspect": Object.freeze({
             scope: MODEL_SCOPE,
@@ -112,7 +112,7 @@ export const MODEL_LANE_CONTRACT = Object.freeze({
         }),
         "model.delete": Object.freeze({
             scope: MODEL_SCOPE,
-            description: "Physically delete a model (apppackage/physically_delete with the proven [{id,code,type:BizModel}] body) with exact-absence readback. The row id MUST be the app-tree node id (AppFunction id) — a biz-model record id is refused by the platform with 601003 业务模型不存在; without `applicationCode` the tool resolves the node across every application (default app first, then applicationList per-app trees) and refuses fail-closed (`model-application-unresolved`) when the record exists but no tree node does, never guessing an id. Inbound references are prechecked: relation fields (relativeCode / options.schemaCode) on same-app models refuse with blocker `model-referenced-by` plus the referencingModels list — clean up dependency-inverted (delete referencing models first, then the referenced one). The async per-column cascade takes 40-60s: absent:false with treeNodePending:true means wait ~60s and re-run (idempotent; already-absent short-circuits; nextAction guidance is returned) rather than judging failure. Accepts an explicit `applicationCode` (priority over the configured default) for cross-application model management.",
+            description: "物理删除模型（apppackage/physically_delete [{id,code,type:BizModel}]）；exact-absence 读回在 `readback.absent`/`readback.treeNodePending`（顶层无这两键——用 `--jq readback.absent`）。id 必须是应用树 AppFunction id（业务模型记录 id → 601003）。无 `applicationCode` 时跨应用解析节点，记录在但树节点缺 → `model-application-unresolved`。同应用入站引用预检 → `model-referenced-by`（dependency-inverted：先删引用方再删被引用方）。列级联 40–60s：`absent:false`+`treeNodePending:true` 等约 60s 再跑（幂等）。可显式传 `applicationCode`。",
         }),
         configure_model: Object.freeze({
             scope: MODEL_SCOPE,
@@ -120,15 +120,15 @@ export const MODEL_LANE_CONTRACT = Object.freeze({
         }),
         "model.deleteMany": Object.freeze({
             scope: MODEL_SCOPE,
-            description: "Physically delete several models in ONE request: apppackage/physically_delete is list-shaped (@RequestBody List<AppDeleteParamVO>, AppPackageController.java:1424), so schemaCodes[] is sent as one [{id,code,type:BizModel}] batch. Each row id is the app-tree node id (AppFunction id) resolved across applications; a target whose record exists but has no tree node refuses the whole batch fail-closed (`model-application-unresolved`) rather than sending a record id. Every target's inbound references are prechecked first — a referenced model refuses the whole batch with per-target blockedTargets evidence and zero side effects (batch members themselves never block each other; put referencing models INTO the list for dependency-inverted cleanup). Already-absent codes short-circuit; per-model absence is polled with the same wait-and-recheck guidance as model.delete.",
+            description: "批量物理删除：apppackage/physically_delete 收 List<AppDeleteParamVO>，schemaCodes[] 一次发 [{id,code,type:BizModel}]。id=跨应用解析的 AppFunction 节点；记录在树节点缺 → 整批 `model-application-unresolved`。入站引用预检：命中则整批拒并给 blockedTargets（零副作用；引用方需一并列入）。已缺席短路；缺席轮询同 model.delete（wait-and-recheck）。",
         }),
         "model.setSummary": Object.freeze({
             scope: MODEL_SCOPE,
-            description: "Set the model's data title / 数据标题 (POST bizmodels/update_summary {schemaCode, summary}) — the fallback display of relation fields and the portal list title. The platform stores `Summary[]` JSON and runtime resolution runs JsonUtility.toList(summaryExpression, Summary.class) (BizObjectTitleSetter :140-160); Summary is {int isDataItem (1=表单字段, 2=查询字段), String code, String param}. The tool normalizes: canonical Summary[] JSON is validated/re-serialized, a PURE {field} placeholder template is converted to [{isDataItem:1,code}], and anything else (literal text, malformed JSON) refuses `model-summary-invalid` — a raw template stored verbatim poisoned the model so ALL later data.save/data.submit answered a bare 50000 (live-verified). Readback is the sibling GET bizmodels/get_summary face; it warns when the STORED value is not a valid Summary[]. Empty summary refuses `model-summary-empty`; a missing schema answers 300014 数据模型未发布.",
+            description: "设数据标题（POST bizmodels/update_summary {schemaCode,summary}）。平台存 Summary[]：{isDataItem:1|2,code,param}。工具归一：合法 Summary[] 校验重序列化；纯 `{field}` 模板 → [{isDataItem:1,code}]；其余拒 `model-summary-invalid`（原文模板会毒化模型，后续 data.save/submit 裸 50000）。读回 GET get_summary；空 summary → `model-summary-empty`；缺 schema → 300014。",
         }),
         "model.move": Object.freeze({
             scope: "move a model's app-tree node to another folder (bizmodels/update parentId)",
-            description: "把模型移动到指定应用目录（分组）：复用 `POST bizmodels/update`，只把 `parentId` 换成目标目录节点 id（AppFunctionController 补丁语义：bizSchemaCode/id/name/parentId 全量必填，工具从应用树解析）。`folderId` 必须是 `folder.tree` 里 type=Folder 的 **id**，给目录名会 `folder-not-found` 并列出可用目录。移动只改菜单节点归属：schema/字段/表单/视图/发布状态不动。回读用应用树按 `parentId` 核对（`moved:true`）。",
+            description: "把模型在**同一应用内**移动到指定目录（分组）：复用 `POST bizmodels/update`，只把 `parentId` 换成目标目录节点 id（AppFunctionController 补丁语义：bizSchemaCode/id/name/parentId 全量必填，工具从应用树解析）。`folderId` 必须是 `folder.tree` 里 type=Folder 的 **id**，给目录名会 `folder-not-found` 并列出可用目录。**模型不能跨应用移动**（`folder-other-application`）：要在目标应用得到同名模型，请 `model.create --applicationCode <目标>`（换 code，或先 `model.delete` 源再同 code 重建）。移动只改菜单节点归属：schema/字段/表单/视图/发布状态不动。回读用应用树按 `parentId` 核对（`moved:true`）。",
         }),
         "model.update": Object.freeze({
             scope: MODEL_SCOPE,
@@ -149,7 +149,8 @@ export function assertModelContract() {
         throw new Error("model contract must require per-step authoritative readbacks");
     assertDescriptionCarries(MODEL_LANE_CONTRACT, "model.deleteMany", ["physically_delete", "List<AppDeleteParamVO>", "blockedTargets", "wait-and-recheck"]);
     assertDescriptionCarries(MODEL_LANE_CONTRACT, "model.setSummary", ["update_summary", "get_summary", "数据标题", "300014", "model-summary-empty", "model-summary-invalid", "Summary[]"]);
-    assertDescriptionCarries(MODEL_LANE_CONTRACT, "model.move", ["bizmodels/update", "parentId", "folder.tree", "folder-not-found", "moved"]);
+    assertDescriptionCarries(MODEL_LANE_CONTRACT, "model.move", ["bizmodels/update", "parentId", "folder.tree", "folder-not-found", "moved", "不能跨应用", "model.create"]);
+    assertDescriptionCarries(MODEL_LANE_CONTRACT, "model.list", ["code", "name", "filter", "query", "legacyString"]);
     assertDescriptionCarries(MODEL_LANE_CONTRACT, "model.update", ["bizmodels/update", "get_all", "model-type-immutable", "model-update-target-absent", "model-update-empty-patch"]);
     if (!MODEL_WIRE.summaryWire.includes("validateNotEmpty"))
         throw new Error("model contract must carry the update_summary validateNotEmpty fact");