lan-low-code-cli 2.5.0 → 2.7.0

package/dist/generator/flow/schema.js

@@ -0,0 +1,96 @@
+"use strict";
+/**
+ * 动作流节点元数据表
+ *
+ * 逐 case 翻译 `action-flow-ide/enter.tsx:217-336` 的 generateNodeData：
+ * IDE 保存时只挑每种 nodeType 的专属字段，其余字段丢弃。
+ * 必填规则来自 `configuration/nodes/utils.tsx:37-288` 与 `validate.ts:13-17`。
+ */
+Object.defineProperty(exports, "__esModule", { value: true });
+exports.CONTEXT_KEYS = exports.FLOW_CODE_PATTERN = exports.NODE_ID_PATTERN = exports.KNOWN_START_WAYS = exports.MULTI_OUT_NODE_TYPES = exports.NODE_REQUIRED = exports.NODE_DEFAULTS = exports.NODE_FIELD_WHITELIST = void 0;
+/** 节点专属字段白名单；未列出的 nodeType 视为未知类型（透传 config 并告警） */
+exports.NODE_FIELD_WHITELIST = {
+    StartNode: ['startNodeDef'],
+    EndNode: ['outParamType', 'outParam', 'outputParamMapping'],
+    BranchNode: ['conditionType', 'flowWay', 'defaultTargetRef', 'ruleConfig', 'formulaConfig'],
+    LoopNode: ['loopDefine', 'subProcess'],
+    QueryLoopNode: [
+        'target', 'conditions', 'sortType', 'containsDeleted', 'executeTime',
+        'loopDefine', 'context_outputParam', 'limitTime',
+    ],
+    FilterDataNode: ['bindNode', 'formula'],
+    MessageNode: [
+        'bindNode', 'subject', 'notifyType', 'todoType', 'messageTarget', 'messageLink',
+        'eventCode', 'codeValue', 'notifyCategoryCode', 'subjectType', 'templateCode',
+        'templateFields', 'grantPermission',
+    ],
+    AddDataNode: ['bindNode', 'dataSourceVO', 'flow', 'commitType', 'fields', 'autoMatchField', 'fastExecute'],
+    DeleteDataNode: ['bindNode'],
+    QueryDataNode: ['target', 'conditions', 'sorts', 'resultType', 'maxSize', 'containsDeleted'],
+    UpdateDataNode: ['bindNode', 'fields', 'fastExecute'],
+    CreateKmReviewNode: ['bindNode', 'kmReviewTemplate', 'fdCreator', 'fdSubject', 'commitType', 'fields'],
+    AddOrUpdateNode: [
+        'bindNode', 'dataSourceVO', 'flow', 'commitType', 'fields', 'condition',
+        'autoMatchField', 'fastExecute',
+    ],
+    AssignValueNode: ['assignValueRuleConfigs'],
+    TransformNode: ['outParamType', 'outParam', 'outputParamMapping'],
+    ExecuteNode: ['outParamType', 'executeCode', 'inputParamMapping'],
+    FlowBotsNode: ['outParamType', 'flowBotsCode', 'inputParamMapping'],
+    InterfaceNode: ['apiType', 'apiMethodPath', 'inputParamMapping'],
+    SubActionNode: ['outParam', 'outParamType', 'actionFlowCode', 'inputParamMapping'],
+    MessageEliminateNode: ['eliminateRange', 'eliminateType', 'eventCode', 'bindNode'],
+    QueryStatisticsNode: [
+        'nativeNodeType', 'resultType', 'target', 'conditions', 'sorts',
+        'columns', 'statisticsDimensions', 'statisticsItems',
+    ],
+    DispatchNode: [],
+};
+/** 与 IDE 一致的缺省值（styleSheet.ts:404-445） */
+exports.NODE_DEFAULTS = {
+    BranchNode: { conditionType: 'formula', flowWay: 'singleBranch' },
+    QueryDataNode: { resultType: 'single' },
+    LoopNode: { loopDefine: { type: 'LoopArray' } },
+    MessageNode: { grantPermission: true },
+};
+/** 发布前 IDE 强校验的必填字段（configuration/nodes/utils.tsx:37-288） */
+exports.NODE_REQUIRED = {
+    AddDataNode: ['dataSourceVO', 'flow', 'fields'],
+    QueryDataNode: ['target'],
+    UpdateDataNode: ['bindNode'],
+    DeleteDataNode: ['bindNode'],
+    FilterDataNode: ['bindNode'],
+    BranchNode: ['conditionType', 'flowWay'],
+    SubActionNode: ['actionFlowCode'],
+    InterfaceNode: ['apiType', 'apiMethodPath'],
+    ExecuteNode: ['executeCode'],
+    QueryStatisticsNode: ['target'],
+    AddOrUpdateNode: ['dataSourceVO', 'flow', 'fields'],
+    LoopNode: ['loopDefine'],
+    AssignValueNode: ['assignValueRuleConfigs'],
+    CreateKmReviewNode: ['kmReviewTemplate', 'fdSubject'],
+    FlowBotsNode: ['flowBotsCode'],
+    MessageNode: ['subject', 'messageTarget'],
+    MessageEliminateNode: ['eliminateRange', 'eliminateType'],
+};
+/** 允许多条出边的节点（validateCommonVertex 的 getwayMap，另有 StartNode） */
+exports.MULTI_OUT_NODE_TYPES = new Set(['BranchNode', 'parallelGateway', 'StartNode']);
+exports.KNOWN_START_WAYS = [
+    'StartScheduledNode',
+    'StartDataNode',
+    'StartEventNode',
+    'StartActiveNode',
+];
+/** 节点编码 /^[0-9a-zA-Z_]{2,32}$/（configuration/nodes/utils.tsx:12-30） */
+exports.NODE_ID_PATTERN = /^[0-9a-zA-Z_]{2,32}$/;
+/** 动作流编码 /^[a-zA-Z0-9_]{1,30}$/（topbar/index.tsx:262-279） */
+exports.FLOW_CODE_PATTERN = /^[a-zA-Z0-9_]{1,30}$/;
+/** extraAttr 六个上下文键（enter.tsx:383-390） */
+exports.CONTEXT_KEYS = [
+    'context_bindFormId',
+    'context_bindNode',
+    'context_nodeParam',
+    'context_isMulti',
+    'context_fdInParam',
+    'context_outputParam',
+];

package/dist/generator/flow/types.js

@@ -0,0 +1,10 @@
+"use strict";
+/**
+ * 动作流编译内核 · 类型定义
+ *
+ * 依据 `sys-modeling/src/components/action-flow-ide/enter.tsx:339-428`：
+ * `fdDesign` 是 JSON 字符串，顶层 `{ nodes, lines, processVar? }`；
+ * 节点为扁平结构：`drawAttr.bounds` + `extraAttr.context_*` + 各 nodeType 专属字段。
+ * IDE 回显时原样使用 x/y，不重算坐标，因此坐标必须由本内核生成。
+ */
+Object.defineProperty(exports, "__esModule", { value: true });

package/dist/generator/flow/validate.js

@@ -0,0 +1,129 @@
+"use strict";
+/**
+ * 动作流离线校验器
+ *
+ * 移植 IDE 发布前的 validate(true)：连线数量、必填、编码格式、无环
+ * （enter.tsx:468-529、validate.ts:150-327、mxgraph/utils.tsx:1206-1258）。
+ * 目的是在发包之前把错误挡住——CLI 直接调 addPublish 会绕过 IDE 校验。
+ */
+Object.defineProperty(exports, "__esModule", { value: true });
+exports.validateSpec = validateSpec;
+exports.validateGraph = validateGraph;
+exports.hasErrors = hasErrors;
+const schema_1 = require("./schema");
+const err = (code, message, nodeId) => ({
+    level: 'error', code, message, nodeId,
+});
+const warn = (code, message, nodeId) => ({
+    level: 'warn', code, message, nodeId,
+});
+/** 基础信息校验 */
+function validateSpec(spec) {
+    const out = [];
+    if (!spec.name || !String(spec.name).trim())
+        out.push(err('SPEC_NAME_REQUIRED', '缺少流程名称 name'));
+    if (!spec.code || !schema_1.FLOW_CODE_PATTERN.test(spec.code)) {
+        out.push(err('SPEC_CODE_INVALID', `流程编码 code 必须匹配 /^[a-zA-Z0-9_]{1,30}$/：${spec.code ?? '(空)'}`));
+    }
+    const startWay = spec.startWay ?? 'StartActiveNode';
+    if (!schema_1.KNOWN_START_WAYS.includes(startWay)) {
+        out.push(err('SPEC_START_WAY_INVALID', `未知启动方式：${startWay}`));
+    }
+    if (!Array.isArray(spec.nodes))
+        out.push(err('SPEC_NODES_REQUIRED', '缺少 nodes 数组'));
+    if (!Array.isArray(spec.edges))
+        out.push(err('SPEC_EDGES_REQUIRED', '缺少 edges 数组'));
+    return out;
+}
+/** 开始节点按启动方式的必填项（configuration/nodes/utils.tsx:40-61、validate.ts:13-17） */
+function validateStartNode(graph, spec, startWay) {
+    const out = [];
+    const start = graph.nodes.find((n) => n._isStart);
+    if (!start)
+        return out;
+    const provided = start.config?.startNodeDef;
+    const def = provided ?? spec.trigger ?? {};
+    const has = (k) => def[k] !== undefined && def[k] !== null && def[k] !== '';
+    if (startWay === 'StartScheduledNode' && !has('scheduledDef')) {
+        out.push(err('START_SCHEDULE_REQUIRED', '定时触发必须在 trigger 中提供 scheduledDef', start.id));
+    }
+    if (startWay === 'StartDataNode' && !has('target')) {
+        out.push(err('START_DATA_TARGET_REQUIRED', '数据监听必须在 trigger 中提供 target（触发表单）', start.id));
+    }
+    if (startWay === 'StartEventNode' && !has('eventCode')) {
+        out.push(err('START_EVENT_REQUIRED', '事件监听必须在 trigger 中提供 eventCode', start.id));
+    }
+    if (startWay === 'StartActiveNode') {
+        const runTypes = def.fdRunType;
+        const byFlags = def.operateTrigger === true || def.bpmTrigger === true || def.apiTrigger === true;
+        const byList = Array.isArray(runTypes) && runTypes.length > 0;
+        if (!byFlags && !byList) {
+            out.push(err('START_ACTIVE_TRIGGER_REQUIRED', '主动触发必须提供 trigger.fdRunType（operate / bpm / api 至少一项）或对应布尔开关', start.id));
+        }
+    }
+    return out;
+}
+/** 图结构 + 节点必填校验 */
+function validateGraph(graph, spec, startWay = 'StartActiveNode') {
+    const out = [];
+    const ids = new Set();
+    const byId = new Map(graph.nodes.map((n) => [n.id, n]));
+    for (const node of graph.nodes) {
+        if (!schema_1.NODE_ID_PATTERN.test(node.id)) {
+            out.push(err('NODE_ID_INVALID', `节点 id 必须匹配 /^[0-9a-zA-Z_]{2,32}$/：${node.id}`, node.id));
+        }
+        if (ids.has(node.id))
+            out.push(err('NODE_ID_DUPLICATE', `节点 id 重复：${node.id}`, node.id));
+        ids.add(node.id);
+        if (!schema_1.NODE_FIELD_WHITELIST[node.type]) {
+            out.push(warn('NODE_TYPE_UNKNOWN', `未知节点类型 ${node.type}，config 将原样透传；请用 llc flow templates list 核对环境支持的节点`, node.id));
+        }
+        // 与编译器一致：默认值（如 BranchNode.conditionType / flowWay）也算已填
+        const config = { ...(schema_1.NODE_DEFAULTS[node.type] ?? {}), ...(node.config ?? {}) };
+        for (const field of schema_1.NODE_REQUIRED[node.type] ?? []) {
+            if (config[field] === undefined || config[field] === null || config[field] === '') {
+                out.push(err('NODE_FIELD_REQUIRED', `节点 ${node.id}（${node.type}）缺少必填字段 ${field}`, node.id));
+            }
+        }
+    }
+    const inCount = new Map();
+    const outCount = new Map();
+    const seenEdge = new Set();
+    for (const edge of graph.edges) {
+        const key = `${edge.from}->${edge.to}`;
+        if (seenEdge.has(key)) {
+            out.push(err('EDGE_DUPLICATE', `重复连线：${key}（IDE 设置 setMultigraph(false)）`));
+        }
+        seenEdge.add(key);
+        if (!byId.has(edge.from))
+            out.push(err('EDGE_SOURCE_MISSING', `连线起点不存在：${edge.from}`));
+        if (!byId.has(edge.to))
+            out.push(err('EDGE_TARGET_MISSING', `连线终点不存在：${edge.to}`));
+        if (edge.from === edge.to)
+            out.push(err('EDGE_SELF_LOOP', `禁止自连：${edge.from}`));
+        inCount.set(edge.to, (inCount.get(edge.to) ?? 0) + 1);
+        outCount.set(edge.from, (outCount.get(edge.from) ?? 0) + 1);
+    }
+    for (const node of graph.nodes) {
+        const incoming = inCount.get(node.id) ?? 0;
+        const outgoing = outCount.get(node.id) ?? 0;
+        if (node._isStart && incoming > 0)
+            out.push(err('START_HAS_IN_EDGE', '开始节点不能有入边', node.id));
+        if (node._isEnd && outgoing > 0)
+            out.push(err('END_HAS_OUT_EDGE', '结束节点不能有出边', node.id));
+        if (!node._isEnd && outgoing === 0) {
+            out.push(err('NODE_NO_OUT_EDGE', `节点 ${node.id} 没有出边`, node.id));
+        }
+        if (!node._isStart && incoming === 0) {
+            out.push(err('NODE_NO_IN_EDGE', `节点 ${node.id} 没有入边`, node.id));
+        }
+        if (outgoing > 1 && !schema_1.MULTI_OUT_NODE_TYPES.has(node.type)) {
+            out.push(err('NODE_MULTI_OUT_EDGE', `节点 ${node.id}（${node.type}）有 ${outgoing} 条出边；仅 BranchNode / StartNode / parallelGateway 允许多出边`, node.id));
+        }
+    }
+    out.push(...validateStartNode(graph, spec, startWay));
+    return out;
+}
+function hasErrors(diagnostics) {
+    return diagnostics.some((d) => d.level === 'error');
+}

package/dist/index.js

@@ -6,10 +6,13 @@ const app_1 = require("./commands/app");
 const config_1 = require("./commands/config");
 const control_1 = require("./commands/control");
 const field_1 = require("./commands/field");
+const flow_1 = require("./commands/flow");
 const form_1 = require("./commands/form");
 const locale_1 = require("./commands/locale");
+const operation_1 = require("./commands/operation");
+const template_1 = require("./commands/template");
 const logger_1 = require("./utils/logger");
-const VERSION = '2.5.0';
+const VERSION = '2.7.0';
 const program = new commander_1.Command();
 exports.program = program;
 program
@@ -34,6 +37,9 @@ program.hook('preAction', (thisCommand, actionCommand) => {
 (0, app_1.registerAppCommand)(program);
 (0, form_1.registerFormCommand)(program);
 (0, field_1.registerFieldCommand)(program);
+(0, operation_1.registerOperationCommand)(program);
+(0, template_1.registerTemplateCommand)(program);
+(0, flow_1.registerFlowCommand)(program);
 (0, locale_1.registerLocaleCommand)(program);
 (0, control_1.registerControlCommand)(program);
 /**
@@ -106,6 +112,19 @@ ${logger_1.color.bold('常用查询')}
   llc control list                              环境可用控件（含高级控件；明细/分页为容器类）
   llc locale list                               环境提供了哪些语言译文
   llc field library [--keyword 关键词]           字段库
+  llc operation list --form-id <fdId>           表单的业务操作（列表页/查看页按钮）
+  llc operation create --form-id <fdId> --name 打开帮助 --code openHelp --type link --url https://example.com
+  llc operation delete --id <operationId> --yes  删除业务操作（被引用时会拒绝）
+  llc operation attach --form-id <fdId> --operation-id <opId>  挂到列表视图（--target view 挂查看视图）
+  llc flow list --app-code <appCode>                 应用下的动作流（只读）
+  llc flow get --id <flowId> --with-design           查看动作流并解析 fdDesign
+  llc flow spec --out flow.json                      生成 Flow Spec 模板
+  llc flow validate --spec @flow.json                离线校验（图结构 / 必填 / 布局）
+  llc flow compile --spec @flow.json --json           编译出含编排布局的 fdDesign
+  llc flow apply --spec @flow.json --app-code <code>  预览提交体（追加 --yes 才写入）
+  llc flow diff --id <flowId> --spec @flow.json        对比本地与远端设计（忽略坐标）
+  llc flow script --id <flowId>                       生成 flow_{fdCode} 按钮脚本
+  llc flow enable/disable/delete --id <flowId>         生命周期管理
 
 ${logger_1.color.gray('高级控件（desc / tags / mdm / association / mechnumber …）与普通控件同样写法：')}
   llc form autofill --id <fdId> --apply --add-field "字段名:标题:控件类型"

package/package.json

@@ -1,49 +1,49 @@
-{
-  "name": "lan-low-code-cli",
-  "version": "2.5.0",
-  "description": "lan-low-code cli：低代码表单引擎命令行工具（创建表单、获取可用字段、自动完善表单字段）",
-  "keywords": [
-    "low-code",
-    "lan-low-code",
-    "llc",
-    "form",
-    "cli"
-  ],
-  "license": "MIT",
-  "packageManager": "pnpm@10.26.2",
-  "bin": {
-    "llc": "bin/llc.js"
-  },
-  "main": "dist/index.js",
-  "scripts": {
-    "build": "tsc -p tsconfig.json",
-    "clean": "rimraf dist",
-    "rebuild": "pnpm run clean && pnpm run build",
-    "start": "pnpm run build && node bin/llc.js",
-    "typecheck": "tsc -p tsconfig.json --noEmit",
-    "prepare": "pnpm run build",
-    "bump": "node scripts/bump-version.js",
-    "bump:check": "node scripts/bump-version.js --check",
-    "pack": "node scripts/pack.js",
-    "pack:cli": "node scripts/pack.js --target cli",
-    "pack:skill": "node scripts/pack.js --target skill"
-  },
-  "dependencies": {
-    "commander": "^11.1.0"
-  },
-  "devDependencies": {
-    "@types/node": "^20.11.30",
-    "rimraf": "^5.0.5",
-    "typescript": "^5.4.5"
-  },
-  "engines": {
-    "node": ">=18",
-    "pnpm": ">=8"
-  },
-  "files": [
-    "bin",
-    "dist",
-    "skills",
-    "README.md"
-  ]
-}
+{
+  "name": "lan-low-code-cli",
+  "version": "2.7.0",
+  "description": "lan-low-code cli：低代码表单引擎命令行工具（创建表单、获取可用字段、自动完善表单字段）",
+  "keywords": [
+    "low-code",
+    "lan-low-code",
+    "llc",
+    "form",
+    "cli"
+  ],
+  "license": "MIT",
+  "packageManager": "pnpm@10.26.2",
+  "bin": {
+    "llc": "bin/llc.js"
+  },
+  "main": "dist/index.js",
+  "scripts": {
+    "build": "tsc -p tsconfig.json",
+    "clean": "rimraf dist",
+    "rebuild": "pnpm run clean && pnpm run build",
+    "start": "pnpm run build && node bin/llc.js",
+    "typecheck": "tsc -p tsconfig.json --noEmit",
+    "prepare": "pnpm run build",
+    "bump": "node scripts/bump-version.js",
+    "bump:check": "node scripts/bump-version.js --check",
+    "pack": "node scripts/pack.js",
+    "pack:cli": "node scripts/pack.js --target cli",
+    "pack:skill": "node scripts/pack.js --target skill"
+  },
+  "dependencies": {
+    "commander": "^11.1.0"
+  },
+  "devDependencies": {
+    "@types/node": "^20.11.30",
+    "rimraf": "^5.0.5",
+    "typescript": "^5.4.5"
+  },
+  "engines": {
+    "node": ">=18",
+    "pnpm": ">=8"
+  },
+  "files": [
+    "bin",
+    "dist",
+    "skills",
+    "README.md"
+  ]
+}

package/skills/lan-low-code-cli/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: lan-low-code-cli
-version: 2.5.0
+version: 2.7.0
 author: Pig George
 description: Operate the Landray low-code form engine through the `llc` CLI. Use when the user asks to create, inspect, modify, publish, or delete low-code apps and forms; generate field configs; configure layouts (grid/tabs), field permissions, options, i18n, or control actions (onChange/onLoad); or run pre-publish validation. Also use for troubleshooting form loading/rendering errors.
 tags:
@@ -41,11 +41,11 @@ Verify: `llc -v` should print the version.
 ### Version check before upgrading
 
 Before upgrading (and whenever `llc -v` does not match this skill), compare the **major** version of the
-installed CLI with this skill's frontmatter `version:` (currently `2.4.1`):
+installed CLI with the `version:` in this skill's frontmatter:
 
 | CLI version vs skill | Action |
 |---|---|
-| Same major (`2.4.1` → e.g. `2.6.0`) | **Upgrade directly**: `npm i -g lan-low-code-cli@latest`. Non-major releases keep the flags in this skill valid. |
+| Same major (e.g. skill `2.x` → CLI `2.y`) | **Upgrade directly**: `npm i -g lan-low-code-cli@latest`. Non-major releases keep the flags in this skill valid. |
 | CLI major is higher (`2.x` skill vs `3.x` CLI) | A **major** version has been crossed: **this skill may be out of date**. Do not assume its flags/fields still exist — tell the user the skill may be stale and update it (see **Self-update** below) before running write operations. |
 | CLI major is lower | The CLI is older than the skill: upgrade the CLI first (`npm i -g lan-low-code-cli@latest`); never downgrade the skill. |
 
@@ -91,13 +91,28 @@ Always run `llc <command> --help` before inventing flags — the CLI is the sour
 | Command | Purpose |
 |---|---|
 | `llc app list / create / forms / delete / delete-data` | business apps (`--code` allows letters/digits/hyphen only, **no underscore**) |
-| `llc form create / list / get / publish / autofill / delete / delete-data` | form lifecycle |
+| `llc form create / list / get / publish / autofill / delete / delete-data` | form lifecycle; `create --type category\|simpleCategory` builds a category form (no business fields; templates are created in the platform designer) |
 | `llc field list / gen-key / library` | available fields |
+| `llc operation list / get / create / update / delete / attach / detach` | form business operations (link, script, dialog), including attaching to list/view pages |
+| `llc template list / create / add-fields / delete` | category-form templates: create/append/delete templates, porting fields/views/permissions from an existing form (auto category node, bypasses official init) |
+| `llc flow spec / compile / validate` | **offline**: generate a Flow Spec, compile it into `fdDesign` with IDE-style layout, run offline validation |
+| `llc flow list / get / category / logs / schema / templates` | **read-only** action-flow queries; `templates` extracts golden node skeletons (coordinates stripped) |
+| `llc flow apply / diff / script / enable / disable / delete` | **write** action-flow lifecycle; `apply` previews by default and needs `--yes` + `--app-code` |
 | `llc control list / show` | controls installed in the environment (basis for `--add-field` third segment) |
 | `llc locale list` | languages with translations available (from control i18n resources) |
 | `llc config set / show / clear` | global credentials and defaults |
 
 > Full per-command options, spec-string syntax and exit codes: **§7 CLI contract**. When in doubt, `llc <command> --help` is authoritative.
+>
+> Runtime `context` of operation scripts (selected rows, list refresh, query, navigation, event bus,
+> `window.MKXFORM`) is documented in [references/operation-script-context.md](references/operation-script-context.md) (Chinese).
+>
+> Action flows are **application-scoped** (`--app-code`, `fdAppCode`), not form-scoped. Always start with
+> `llc flow spec --out flow.json` → `llc flow validate --spec @flow.json` → `llc flow compile --spec @flow.json --json`.
+> `llc flow apply` **only previews** until `--yes` is added, and requires an explicit `--app-code`.
+> `--layout ide` (default) reproduces the platform's branch arrangement; never hand-write `drawAttr.bounds`.
+> Full Flow Spec syntax: **§10 of [references/cli-contract.md](references/cli-contract.md)**.
+> Add `--resolve-schema` when publishing nodes that reference a data model (`sys-modeling#<fdId>`).
 
 ## 2. Core workflow
 
@@ -181,7 +196,7 @@ llc form autofill --id <fdId> --apply --publish \
   is accepted), so an unsupported event saves fine but never fires. Confirm in this order: the designer's
   "控件动作" event dropdown (authoritative) → `llc control show --element <pkg> --json`, i.e. event
   declarations in `meta` if the package has any (not shown in human output) → the keys of
-  `controlAction.control['<table>.<uuid>']` on an existing form. See §7 of
+  `controlAction.control['<table>.<uuid>']` on an existing form. See §8 of
   [references/cli-contract.md](references/cli-contract.md).
 - `source` is function **source code** (evaluated via
   `new Function('MKXFORM', 'return (fn)')`); `@path` reads it from a file.

package/skills/lan-low-code-cli/SKILL.zh-CN.md

@@ -1,6 +1,6 @@
 ---
 name: lan-low-code-cli
-version: 2.5.0
+version: 2.7.0
 author: Pig George
 description: 通过 `llc` CLI 操作蓝凌低代码表单引擎。适用于：创建、查看、修改、发布或删除低代码应用与表单；生成字段配置；配置布局（栅格/页签）、字段权限、选项、多语言、控件动作（onChange/onLoad）；或执行发布前校验、排查表单加载/渲染报错。
 tags:
@@ -45,7 +45,7 @@ npm i -g lan-low-code-cli            # 全局安装，获得 `llc` 命令
 
 | CLI 版本 vs skill | 处理 |
 |---|---|
-| 同一大版本（`2.4.1` → 如 `2.6.0`） | **直接升级**：`npm i -g lan-low-code-cli@latest`。非大版本升级不影响本 skill 的参数与写法。 |
+| 同一大版本（如 skill `2.x` → CLI `2.y`） | **直接升级**：`npm i -g lan-low-code-cli@latest`。非大版本升级不影响本 skill 的参数与写法。 |
 | CLI 大版本更高（skill `2.x` vs CLI `3.x`） | 已**跨大版本**：**本 skill 可能已过期**。不要假设其中的参数/字段仍然有效——告知用户 skill 可能过期，按下方**自更新**更新后再执行写操作。 |
 | CLI 大版本更低 | CLI 比 skill 旧：先升级 CLI（`npm i -g lan-low-code-cli@latest`），不要把 skill 降级。 |
 
@@ -88,13 +88,28 @@ llc config set --base-url http://<host>/data --token <X-AUTH-TOKEN>   # 一次
 | 命令 | 用途 |
 |---|---|
 | `llc app list / create / forms / delete / delete-data` | 业务应用（`--code` 仅允许字母/数字/连字符，**不允许下划线**） |
-| `llc form create / list / get / publish / autofill / delete / delete-data` | 表单生命周期 |
+| `llc form create / list / get / publish / autofill / delete / delete-data` | 表单生命周期；`create --type category\|simpleCategory` 建分类表单（无业务字段，模板需在平台设计器创建） |
 | `llc field list / gen-key / library` | 可用字段 |
+| `llc operation list / get / create / update / delete / attach / detach` | 表单业务操作（链接、脚本、对话框），含挂载到列表/查看视图 |
+| `llc template list / create / add-fields / delete` | 分类表单模板：创建模板并把既有表单的字段/视图/权限移植进来，追加字段，或清理模板（自动建分类节点、跳过官方 init） |
+| `llc flow spec / compile / validate` | **纯离线**：生成 Flow Spec、编译出符合 IDE 编排布局的 `fdDesign`、离线校验 |
+| `llc flow list / get / category / logs / schema / templates` | **只读**查询动作流；`templates` 抽取 golden 节点骨架（已剥离坐标） |
+| `llc flow apply / diff / script / enable / disable / delete` | **写入**动作流全生命周期；`apply` 默认预览，需 `--yes` + `--app-code` 才提交 |
 | `llc control list / show` | 环境已安装控件（`--add-field` 第三段的取值依据） |
 | `llc locale list` | 环境中有现成译文的语言（来自控件多语言资源） |
 | `llc config set / show / clear` | 全局凭据与默认值 |
 
 > 每个命令的完整参数、规格字符串语法与退出码见**第 7 节 CLI 契约**；不确定时以 `llc <命令> --help` 为准。
+>
+> 业务操作「脚本模式」的运行时 `context`（选中数据、刷新列表、查询、跳转、事件总线、`window.MKXFORM`）
+> 见 [references/operation-script-context.md](references/operation-script-context.md)。
+>
+> 动作流是**应用级**对象（`--app-code` 即 `fdAppCode`），不是表单级。固定起手式：
+> `llc flow spec --out flow.json` → `llc flow validate --spec @flow.json` → `llc flow compile --spec @flow.json --json`。
+> `llc flow apply` **默认只预览**，必须追加 `--yes`，且必须显式给 `--app-code`。
+> `--layout ide`（默认）复刻平台分支编排，不要手写 `drawAttr.bounds`。
+> Flow Spec 完整语法见 [references/cli-contract.md](references/cli-contract.md) **第 10 节**。
+> 节点引用数据模型（`sys-modeling#<fdId>`）时，发布请加 `--resolve-schema`。
 
 ## 2. 核心流程
 
@@ -174,7 +189,7 @@ llc form autofill --id <fdId> --apply --publish \
 - **控件支持哪些事件**：CLI 不内置白名单、也不校验（只要求标识符），写错不会报错但不会触发。
   按序确认：设计器「控件动作」事件下拉（权威）→ `llc control show --element <pkg> --json` 的 `meta`
   （若包内声明了事件；人类可读输出不展示）→ 已有表单 `controlAction.control['<表名>.<uuid>']` 的键名。
-  详见 [references/cli-contract.zh-CN.md](references/cli-contract.zh-CN.md) 第 7 节。
+  详见 [references/cli-contract.zh-CN.md](references/cli-contract.zh-CN.md) 第 8 节。
 - `source` 是函数**源码**（运行时经 `new Function('MKXFORM', 'return (fn)')` 求值）；
   `@路径` 表示从文件读取。
 - 落库位置：`fdConfig.attribute.formAttr.controlAction.control['<表名>.<uuid>'][<事件>]`。