lan-low-code-cli 2.6.0 → 2.8.0

package/dist/generator/flow/layout.js

@@ -0,0 +1,136 @@
+"use strict";
+/**
+ * 动作流编排布局引擎
+ *
+ * 源码依据（均来自 action-flow-ide）：
+ * - 尺寸表 styleSheet.ts:339-347：BranchNode 56×56，其余 180×38；回显时宽高被强制覆盖
+ * - 种子 mxgraph/utils.tsx:93-135：N1 在 (C-90, 80)、N2 在 (C-90, 166)，L1 直连
+ * - 向下插入 R4（mxgraph/utils.tsx:422-465,1408-1428）：distance = h_prev + 52，
+ *   cy_new = cy_prev + distance，下游整体 y += distance
+ * - 左右插入 R5（mxgraph/utils.tsx:442-458,568-584）：与源节点同层中心线，
+ *   x = C - w/2 ± 2*distance
+ * - 无整图自动布局、无后端布局服务；坐标是持久化契约，IDE 回显原样使用
+ *
+ * 因此这里按「rank（逻辑层）+ lane（层内泳道）+ 中心线」复刻编排习惯：
+ * 主链居中，分支的直接后继与分支节点同层、左右对称，汇聚节点下移一层。
+ */
+Object.defineProperty(exports, "__esModule", { value: true });
+exports.DEFAULT_CENTER_X = exports.MIN_GAP = exports.RANK_PADDING = exports.START_Y = exports.NODE_SIZE = void 0;
+exports.nodeSize = nodeSize;
+exports.layoutGraph = layoutGraph;
+/** 与 styleSheet.ts nodeBounds 一致 */
+exports.NODE_SIZE = {
+    BranchNode: { width: 56, height: 56 },
+    general: { width: 180, height: 38 },
+};
+/** 主画布开始节点的 y（mxgraph/utils.tsx:130） */
+exports.START_Y = 80;
+/** R4 的层间距增量：distance = h_prev + 52 */
+exports.RANK_PADDING = 52;
+/**
+ * 最小边缘间隙，默认 40。
+ *
+ * IDE 常规编排的垂直间隙由 R4 推导：gap = 52 + (h_prev - h_new)/2；
+ * 38 高节点后紧跟 56 高 BranchNode 时最小为 52 - (56-38)/2 = 43px。
+ * 因此不能照搬 mxHierarchicalLayout 的 interRankCellSpacing=50（该值只在
+ * 折叠/展开时生效），否则正常分支流程会被误判为布局重叠。
+ */
+exports.MIN_GAP = 40;
+/** W=1920 时 (1920-562)/2；CLI 无浏览器宽度，可用 --center-x 覆盖 */
+exports.DEFAULT_CENTER_X = 679;
+function nodeSize(nodeType) {
+    return exports.NODE_SIZE[nodeType] ?? exports.NODE_SIZE.general;
+}
+const round = (v) => Math.round(v * 100) / 100;
+function layoutGraph(graph, options = {}) {
+    const mode = options.mode ?? 'ide';
+    const centerX = options.centerX ?? exports.DEFAULT_CENTER_X;
+    const padding = options.rankPadding ?? exports.RANK_PADDING;
+    const minGap = options.minGap ?? exports.MIN_GAP;
+    const diagnostics = [];
+    const bounds = {};
+    // passthrough：原样沿用已有坐标（P1 克隆 / UI 导出流程回写）
+    if (mode === 'passthrough') {
+        for (const node of graph.nodes) {
+            const size = nodeSize(node.type);
+            const given = node.bounds;
+            if (!given || typeof given.x !== 'number' || typeof given.y !== 'number') {
+                diagnostics.push({
+                    level: 'error',
+                    code: 'LAYOUT_MISSING_BOUNDS',
+                    message: `passthrough 模式要求节点提供 bounds.{x,y}：${node.id}`,
+                    nodeId: node.id,
+                });
+                continue;
+            }
+            bounds[node.id] = {
+                x: given.x,
+                y: given.y,
+                width: size.width,
+                height: size.height,
+                relative: given.relative ?? false,
+            };
+        }
+        return { bounds, rankCenters: [], diagnostics };
+    }
+    const maxRank = graph.nodes.reduce((max, n) => Math.max(max, n._rank), 0);
+    // 每层取最高节点，决定「该层到下一层」的间距：38→90、56→108
+    const rankHeight = [];
+    for (let r = 0; r <= maxRank; r++) {
+        const heights = graph.nodes.filter((n) => n._rank === r).map((n) => nodeSize(n.type).height);
+        rankHeight[r] = heights.length > 0 ? Math.max(...heights) : exports.NODE_SIZE.general.height;
+    }
+    const gapOf = (r) => (rankHeight[r] ?? exports.NODE_SIZE.general.height) + padding;
+    // 中心线：cy(0) = 80 + h_start/2 = 99；cy(r) = cy(r-1) + gap(r-1)
+    const rankCenters = [];
+    const startNode = graph.nodes.find((n) => n._isStart);
+    rankCenters[0] = exports.START_Y + (startNode ? nodeSize(startNode.type).height : exports.NODE_SIZE.general.height) / 2;
+    for (let r = 1; r <= maxRank; r++) {
+        rankCenters[r] = rankCenters[r - 1] + gapOf(r - 1);
+    }
+    for (const node of graph.nodes) {
+        const size = nodeSize(node.type);
+        const r = node._rank;
+        // R5 的 ±2*distance：distance 取当前层最高节点对应的层间距
+        const laneGap = options.laneGap ?? 2 * gapOf(r);
+        const x = centerX - size.width / 2 + node._lane * laneGap;
+        const y = (rankCenters[r] ?? rankCenters[rankCenters.length - 1]) - size.height / 2;
+        bounds[node.id] = {
+            x: round(x),
+            y: round(y),
+            width: size.width,
+            height: size.height,
+            relative: false,
+        };
+    }
+    // 矩形重叠检查（含最小间隙）
+    const placed = graph.nodes.filter((n) => bounds[n.id]);
+    for (let i = 0; i < placed.length; i++) {
+        for (let j = i + 1; j < placed.length; j++) {
+            const a = bounds[placed[i].id];
+            const b = bounds[placed[j].id];
+            const horizontal = a.x < b.x + b.width + minGap && b.x < a.x + a.width + minGap;
+            const vertical = a.y < b.y + b.height + minGap && b.y < a.y + a.height + minGap;
+            if (horizontal && vertical) {
+                diagnostics.push({
+                    level: 'error',
+                    code: 'LAYOUT_OVERLAP',
+                    message: `节点 ${placed[i].id} 与 ${placed[j].id} 的布局重叠或间距不足 ${minGap}px`,
+                    nodeId: placed[j].id,
+                });
+            }
+        }
+    }
+    for (const node of placed) {
+        const b = bounds[node.id];
+        if (b.x < 0 || b.y < 0) {
+            diagnostics.push({
+                level: 'warn',
+                code: 'LAYOUT_NEGATIVE',
+                message: `节点 ${node.id} 坐标为负 (${b.x}, ${b.y})，IDE 中可能显示不全；可增大 --center-x / --lane-gap`,
+                nodeId: node.id,
+            });
+        }
+    }
+    return { bounds, rankCenters, diagnostics };
+}

package/dist/generator/flow/schema-resolver.js

@@ -0,0 +1,133 @@
+"use strict";
+/**
+ * SchemaResolver：联网补齐动作流节点的运行时上下文（extraAttr.context_*）
+ *
+ * 真实环境实测结论（2026-11-10，mkylxt）：
+ * - `getSourceJsonSchema` / `getProcessDataOutJsonSchema` 的 entityId 必须带
+ *   `sys-modeling#` 前缀，裸 id 返回 HTTP 500；返回值即 JSON Schema。
+ * - `getSourceFields` / `getConditionFields` / `loadDataModel` 用裸 id 正常。
+ * - 平台保存的 `extraAttr.context_bindFormId` 形如 `sys-modeling#<fdId>`。
+ * - 前端 `edit/content.tsx:55-87` 的 tempFormatFn 也会在打开编辑器时自动补
+ *   extraAttr，因此这里采用 best-effort：调用失败只告警，不阻断发布。
+ *
+ * 不做的事：不臆造 `fields` 的公式映射。真实 fields 是
+ * `{ field:{name,label,tableName,tableType,type}, value:{format:'formula'|'fixed',valueJson:'...'} }`
+ * 数组，公式引用形如 `${data.node.N1.fd_xxx}`，必须由 spec 原样提供或从
+ * golden 模板复制；本模块只校验字段名是否在目标表 Schema 中存在。
+ */
+Object.defineProperty(exports, "__esModule", { value: true });
+exports.resolveFlowSchema = resolveFlowSchema;
+const flow_1 = require("../../api/flow");
+function diagnose(out, level, code, message, nodeId) {
+    out.push({ level, code, message, nodeId });
+}
+async function tryCall(fn, label, out, strict, nodeId) {
+    try {
+        return await fn();
+    }
+    catch (err) {
+        diagnose(out, strict ? 'error' : 'warn', 'SCHEMA_FETCH_FAILED', `${label} 调用失败：${err.message.split('\n')[0]}`, nodeId);
+        return undefined;
+    }
+}
+/** 从节点扁平字段里取出目标实体 id（真实结构见 startNodeDef / dataSourceVO / target） */
+function entityIdOf(node) {
+    const candidates = [
+        node.startNodeDef,
+        node.dataSourceVO,
+        node.target,
+    ];
+    for (const candidate of candidates) {
+        const value = candidate?.entityId;
+        if (typeof value === 'string' && value.trim())
+            return value.trim();
+    }
+    return undefined;
+}
+function parseInParam(raw, out, nodeId) {
+    if (typeof raw !== 'string')
+        return raw;
+    try {
+        return JSON.parse(raw);
+    }
+    catch {
+        diagnose(out, 'warn', 'SCHEMA_INPARAM_INVALID', 'startNodeDef.inParam 不是合法 JSON 字符串，已跳过注入', nodeId);
+        return undefined;
+    }
+}
+/** 校验 fields[].field.name 是否存在于目标表 Schema（不改写字段结构） */
+function validateFieldNames(node, schema, out, nodeId) {
+    if (!schema || !Array.isArray(node.fields))
+        return;
+    const properties = schema.properties;
+    if (!properties)
+        return;
+    for (const item of node.fields) {
+        const field = item?.field;
+        const name = field?.name;
+        if (typeof name === 'string' && !(name in properties)) {
+            diagnose(out, 'warn', 'SCHEMA_FIELD_MISSING', `字段 ${name} 不在目标表 Schema 中，请核对 fdName`, nodeId);
+        }
+    }
+}
+async function resolveFlowSchema(client, spec, result, options = {}) {
+    const strict = Boolean(options.strict);
+    const diagnostics = [...result.diagnostics];
+    const startWay = spec.startWay ?? 'StartActiveNode';
+    const resolveNode = async (node, isRootCanvas) => {
+        const nodeId = String(node.id ?? '?');
+        const extra = (node.extraAttr ?? {});
+        node.extraAttr = extra;
+        const entityId = entityIdOf(node);
+        const isStart = node.nodeType === 'StartNode' && isRootCanvas;
+        let schema;
+        if (entityId) {
+            const qualified = (0, flow_1.qualifyEntityId)(entityId);
+            if (isStart && startWay === 'StartDataNode') {
+                const fetched = await tryCall(() => flow_1.flowApi.getDataOutJsonSchema(client, entityId), 'getProcessDataOutJsonSchema', diagnostics, strict, nodeId);
+                schema = fetched;
+                if (fetched) {
+                    const sourceForm = fetched.properties?.sourceForm;
+                    if (extra.context_fdInParam === undefined)
+                        extra.context_fdInParam = fetched;
+                    if (extra.context_nodeParam === undefined)
+                        extra.context_nodeParam = sourceForm ?? null;
+                }
+            }
+            else if (!isStart) {
+                const fetched = await tryCall(() => flow_1.flowApi.getJsonSchema(client, entityId), 'getSourceJsonSchema', diagnostics, strict, nodeId);
+                schema = fetched;
+                if (fetched && extra.context_outputParam === undefined) {
+                    extra.context_outputParam = fetched;
+                }
+            }
+            if (extra.context_bindFormId === undefined)
+                extra.context_bindFormId = qualified;
+        }
+        if (isStart) {
+            const startDef = node.startNodeDef;
+            if (extra.context_fdInParam === undefined && startDef?.inParam !== undefined) {
+                const parsed = parseInParam(startDef.inParam, diagnostics, nodeId);
+                if (parsed !== undefined)
+                    extra.context_fdInParam = parsed;
+            }
+            if (extra.context_isMulti === undefined) {
+                extra.context_isMulti = startDef?.dataType === 2;
+            }
+        }
+        validateFieldNames(node, schema, diagnostics, nodeId);
+        const subProcess = node.subProcess;
+        if (subProcess && Array.isArray(subProcess.nodes)) {
+            for (const child of subProcess.nodes)
+                await resolveNode(child, false);
+        }
+    };
+    for (const node of result.design.nodes) {
+        await resolveNode(node, true);
+    }
+    return {
+        ...result,
+        fdDesign: JSON.stringify(result.design),
+        diagnostics,
+    };
+}

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,12 +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.6.0';
+const VERSION = '2.8.0';
 const program = new commander_1.Command();
 exports.program = program;
 program
@@ -38,6 +39,7 @@ program.hook('preAction', (thisCommand, actionCommand) => {
 (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);
 /**
@@ -114,6 +116,15 @@ ${logger_1.color.bold('常用查询')}
   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,6 +1,6 @@
 {
   "name": "lan-low-code-cli",
-  "version": "2.6.0",
+  "version": "2.8.0",
   "description": "lan-low-code cli：低代码表单引擎命令行工具（创建表单、获取可用字段、自动完善表单字段）",
   "keywords": [
     "low-code",

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

@@ -1,6 +1,6 @@
 ---
 name: lan-low-code-cli
-version: 2.6.0
+version: 2.8.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. |
 
@@ -93,8 +93,11 @@ Always run `llc <command> --help` before inventing flags — the CLI is the sour
 | `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; `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 operation list / get / create / update / delete / attach / detach` | form business operations (link, script, dialog); `--trigger-flow <flowId>` binds an action flow, `--inc-params` supplies its input |
 | `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 / run / enable / disable / delete` | **write** action-flow lifecycle; `apply` previews by default and needs `--yes` + `--app-code`; `run` executes a bound button via `sysModelingMain/other` |
 | `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 |
@@ -103,6 +106,13 @@ Always run `llc <command> --help` before inventing flags — the CLI is the sour
 >
 > 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
 

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

@@ -1,6 +1,6 @@
 ---
 name: lan-low-code-cli
-version: 2.6.0
+version: 2.8.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 降级。 |
 
@@ -90,8 +90,11 @@ 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` | 表单生命周期；`create --type category\|simpleCategory` 建分类表单（无业务字段，模板需在平台设计器创建） |
 | `llc field list / gen-key / library` | 可用字段 |
-| `llc operation list / get / create / update / delete / attach / detach` | 表单业务操作（链接、脚本、对话框），含挂载到列表/查看视图 |
+| `llc operation list / get / create / update / delete / attach / detach` | 表单业务操作（链接、脚本、对话框）；`--trigger-flow <动作流fdId>` 绑定动作流，`--inc-params` 传入参 |
 | `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 / run / enable / disable / delete` | **写入**动作流全生命周期；`apply` 默认预览，需 `--yes` + `--app-code`；`run` 通过 `sysModelingMain/other` 执行绑定按钮 |
 | `llc control list / show` | 环境已安装控件（`--add-field` 第三段的取值依据） |
 | `llc locale list` | 环境中有现成译文的语言（来自控件多语言资源） |
 | `llc config set / show / clear` | 全局凭据与默认值 |
@@ -100,6 +103,13 @@ llc config set --base-url http://<host>/data --token <X-AUTH-TOKEN>   # 一次
 >
 > 业务操作「脚本模式」的运行时 `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. 核心流程