@fieldwangai/agentflow 0.1.149 → 0.1.154

package/builtin/nodes/tool_display_share_link.md

@@ -1,5 +1,6 @@
 ---
 # Built-in node: create share link for Display nodes
+runtime: native
 description: Create a public share link for upstream Display nodes
 displayName: Display Share Link
 input:

package/builtin/nodes/tool_get_env.md

@@ -1,5 +1,7 @@
 ---
 # 内置节点：按 key 读取环境/配置
+runtime: none
+palette: hidden
 description: Get environment variable value
 displayName: GetEnv
 input:

package/builtin/nodes/tool_git_checkout.md

@@ -1,5 +1,6 @@
 ---
 # 内置节点：Git Checkout
+runtime: native
 description: |
   Clone or update a Git repository and expose it as a workspace context for downstream nodes.
 

package/builtin/nodes/tool_git_worktree_load.md

@@ -1,5 +1,6 @@
 ---
 # Built-in node: Git Worktree Load
+runtime: native
 description: |
   Create or reuse a Git worktree and expose it as the downstream workspace context.
 

package/builtin/nodes/tool_git_worktree_unload.md

@@ -1,5 +1,6 @@
 ---
 # Built-in node: Git Worktree Unload
+runtime: native
 description: |
   Remove a Git worktree.
 

package/builtin/nodes/tool_gitlab_create_mr.md

@@ -1,5 +1,6 @@
 ---
 # Built-in node: GitLab Create MR
+runtime: native
 description: |
   Create or reuse a GitLab merge request for the current branch.
 

package/builtin/nodes/tool_jenkins_build.md

@@ -1,5 +1,7 @@
 ---
 # Built-in node: durable Jenkins build
+runtime: none
+palette: hidden
 description: |
   Trigger one Jenkins job and durably monitor it until completion.
 

package/builtin/nodes/tool_load_key.md

@@ -1,5 +1,7 @@
 ---
 # 内置节点：按 key 读取
+runtime: none
+palette: hidden
 description: Load key-value from global storage
 displayName: LoadKey
 input:

package/builtin/nodes/tool_nodejs.md

@@ -1,30 +1,28 @@
 ---
 # 内置节点：执行 Node.js
+runtime: native
 description: |
-  Execute Node.js script via agentflow apply -ai run-tool-nodejs.
+  Execute a Node.js script. The Workspace runtime spawns the command directly — no agent involved.
 
-  **Success/Failure:** Determined by script process **exit code**—0 = success, non-0 = failed.
-  **Result Output:** Script stdout directly becomes result slot content (plain text, e.g., `console.log("hello")`).
-  When stdout is empty and exit code is non-0, stderr info will be written to failure message.
+  **Success/Failure:** Determined by the script process **exit code** — 0 = success, non-0 = failed.
+  **Result Output:** Script stdout becomes the `result` slot content (plain text, e.g. `console.log("hello")`).
+  When stdout is empty and the exit code is non-0, stderr is written to the failure message.
+  Do **not** wrap stdout in a JSON envelope.
 
-  **JSON Compatible (Optional):** If stdout is `{"err_code":0,"message":{"result":"..."}}` format, err_code will override exit code semantics, message.result writes to result slot. Only use when needing different success/failure semantics than exit code.
-
-  **Direct Execution Mode (Recommended):** Set `script` field in flow.yaml instance, pipeline will skip AI and execute directly.
-  `script` supports ${} placeholders (workspaceRoot, pipelineWorkspace, flowName, runDir, flowDir and all input/output slots), values are auto shell-quoted.
-  When a CD Workspace node is connected, `workspaceRoot` is the current execution workspace; `pipelineWorkspace` is the original pipeline workspace.
-  flowDir is absolute path of current pipeline flow.yaml directory, can be used to reference scripts in same directory.
+  **Script placeholders:** `script` (inline) or `scriptRef` (file) support `${}` placeholders —
+  `workspaceRoot` / `pipelineWorkspace` / `flowDir` (all three resolve to the scoped workspace root),
+  `cwd`, `nodeRunDir`, `nodeTmpDir`, `outputsDir`, `scriptRef`, plus every input and output slot name.
+  Values are auto shell-quoted, so do not add your own quotes.
   Example: `script: node ${flowDir}/scripts/my-check.mjs --root ${workspaceRoot} --input ${todo}`
 
-  **Pin Path Constraint (Important):** File paths read/written by script **must be passed via pins**, forbidden to construct output paths inside script.
-  - All input slots with type 'file' (e.g., `figma_tree`, `semantic_outline`) are parsed from upstream connections by pipeline, script receives via CLI args.
-  - All output slots with type 'file' (e.g., `restore_todolist`, `screenshot_map`) are generated by pipeline as absolute paths following `output/<instanceId>/node_<instanceId>_<slot>.md` convention, script receives via CLI args and writes directly.
-  - Use `${slotName}` in `script` field to get correct path, e.g., `--figma-tree ${figma_tree} --output ${restore_todolist}`.
-  - **Forbidden** to use `outDirForNode`, manually write `node_<instance>_xxx.json` etc. in script—this causes script output path mismatch with pipeline parser convention, downstream nodes cannot find files.
-
-  **AI Execution Mode (Legacy):** Without `script` field, AI agent reads body and manually executes commands.
+  **Pin Path Constraint (Important):** File paths read/written by the script **must be passed via pins**;
+  never construct output paths inside the script.
+  - Input slots of type `file` are resolved from upstream connections; the script receives them as CLI args.
+  - Output slots of type `file` are resolved to absolute paths by the runtime; the script writes to them directly.
+  - Reference them with `${slotName}` in `script`, e.g. `--figma-tree ${figma_tree} --output ${restore_todolist}`.
+  - **Forbidden** to invent output paths inside the script — downstream nodes will not find the files.
 
-  **Underlying Usage:**
-  agentflow apply -ai run-tool-nodejs <workspaceRoot> <flowName> <uuid> <instanceId> [execId] -- <scriptCmd> [args...]
+  **Scripts under `scripts/` must be referenced as `${flowDir}/scripts/xxx.mjs`.**
 displayName: NodeJs
 input:
   - type: node

package/builtin/nodes/tool_print.md

@@ -1,5 +1,7 @@
 ---
 # 内置节点：醒目输出
+runtime: none
+palette: hidden
 description: Output content to user with special font style
 displayName: Print
 input:

package/builtin/nodes/tool_save_key.md

@@ -1,5 +1,7 @@
 ---
 # 内置节点：按 key 写入
+runtime: none
+palette: hidden
 description: Save key-value pair to global storage
 displayName: SaveKey
 input:

package/builtin/nodes/tool_set_run_env.md

@@ -1,5 +1,6 @@
 ---
 # Built-in node: set environment variables for the current run only
+runtime: native
 description: Set environment variables for downstream nodes in the current workspace run
 displayName: Set Run Env
 input:

package/builtin/nodes/tool_user_ask.md

@@ -1,5 +1,7 @@
 ---
 # 内置节点：用户选择（Switch 分支）
+runtime: none
+palette: hidden
 description: 等待用户从多个选项中选择一个，流程暂停；按用户选择沿对应出边分支继续。每个 output 槽位对应一条分支，槽位的 description 作为选项文案。
 displayName: UserAsk
 input:

package/builtin/nodes/tool_user_check.md

@@ -1,5 +1,7 @@
 ---
 # 内置节点：用户确认
+runtime: none
+palette: hidden
 description: 等待用户确认，流程暂停。展示确认内容给用户，用户可编辑/AI修改后保存，回复 "继续" 后重启流程。
 displayName: UserCheck
 input:

package/builtin/nodes/tool_wecom_send_app_markdown.md

@@ -1,5 +1,6 @@
 ---
 # Built-in node: WeCom direct markdown message
+runtime: native
 description: Send Markdown message to WeCom users through an enterprise application
 displayName: WeCom Direct Markdown
 input:

package/builtin/nodes/tool_wecom_send_group_markdown.md

@@ -1,5 +1,6 @@
 ---
 # Built-in node: WeCom group robot markdown message
+runtime: native
 description: Send Markdown message to a WeCom group robot webhook
 displayName: WeCom Group Chat Markdown
 input:

package/builtin/nodes/workspace_one_click_task.md

@@ -0,0 +1,44 @@
+---
+# 内置节点：一键任务
+runtime: native
+type: agent
+description: 输入任务描述，选择 Skills、workspace 上下文和输出类型后直接运行；等价于「Load Skills + 子 Agent + Display」的合并节点。
+displayName: 一键任务
+input:
+  - type: node
+    name: prev
+    default: ""
+  - type: text
+    name: skillKeys
+    default: ""
+    showOnNode: false
+  - type: bool
+    name: includeWorkspaceContext
+    default: "true"
+    showOnNode: false
+  - type: text
+    name: displayType
+    default: "markdown"
+    showOnNode: false
+  - type: text
+    name: knowledgeContext
+    default: ""
+    showOnNode: false
+  - type: text
+    name: workspaceContext
+    default: ""
+    showOnNode: false
+output:
+  - type: node
+    name: next
+    default: ""
+  - type: text
+    name: content
+    default: ""
+    showOnNode: true
+  - type: text
+    name: displayType
+    default: "markdown"
+    showOnNode: false
+---
+输入任务，选择 Skills、workspace 上下文和输出类型后直接运行。

package/builtin/nodes/workspace_run.md

@@ -0,0 +1,16 @@
+---
+# 内置节点：Run
+runtime: native
+type: control
+description: Workspace 图的运行入口。点击运行时，从本节点出发沿控制边选出子图并执行；本节点自身不产生输出。
+displayName: Run
+input:
+  - type: node
+    name: prev
+    default: ""
+output:
+  - type: node
+    name: next
+    default: ""
+---
+Run the downstream workspace subgraph connected from this node.

package/builtin/nodes/workspace_scheduled_run.md

@@ -0,0 +1,16 @@
+---
+# 内置节点：Scheduled Run
+runtime: native
+type: control
+description: 定时运行入口。与 Run 相同的执行语义，区别是由调度器按节点 body 中的 JSON 排程配置触发。
+displayName: Scheduled Run
+input:
+  - type: node
+    name: prev
+    default: ""
+output:
+  - type: node
+    name: next
+    default: ""
+---
+Run the downstream workspace subgraph on a schedule.

package/builtin/pipelines/module-migrate/scripts/gate.mjs

@@ -0,0 +1,37 @@
+#!/usr/bin/env node
+/**
+ * 把「脚本判定」和「AI 判定」合成一个 bool，喂给 `control.if` 的 prediction。
+ *
+ * 用法（由 tool_nodejs 的 script 调用）：
+ *   node gate.mjs <scriptOk> <aiVerdict> <okPath> <reportPath>
+ *
+ * - `<scriptOk>`：上游脚本节点写的 `true` / `false`
+ * - `<aiVerdict>`：上游 agent 的回复正文，**第一行**必须是 true / false
+ *
+ * 为什么不用 `control.agentToBool`：那个节点没有任何东西约束模型输出，`parse-bool` 只认
+ * `true` / `1` / `yes` / `on`，模型回「是」或「true（因为…）」都会静默变成 false。判定能
+ * 用脚本做的时候就别交给模型。
+ */
+import fs from "node:fs";
+
+const [scriptOk, aiVerdict, okPath, reportPath] = process.argv.slice(2);
+
+if (!okPath || !reportPath) {
+  console.error("用法: node gate.mjs <scriptOk> <aiVerdict> <okPath> <reportPath>");
+  process.exit(1);
+}
+
+const scriptPassed = String(scriptOk || "").trim().toLowerCase() === "true";
+const firstLine = String(aiVerdict || "").trim().split("\n")[0].trim().toLowerCase();
+const aiPassed = firstLine === "true";
+const ok = scriptPassed && aiPassed;
+
+fs.writeFileSync(reportPath, [
+  `脚本检查：${scriptPassed ? "通过" : "未通过"}`,
+  `AI 检查：${aiPassed ? "通过" : `未通过（首行是 ${JSON.stringify(firstLine)}，期望 true）`}`,
+  "",
+  ok ? "两边都干净，进入编译。" : "有一边没过，进入修复。",
+].join("\n"), "utf-8");
+fs.writeFileSync(okPath, ok ? "true" : "false", "utf-8");
+
+console.log(`脚本=${scriptPassed} AI=${aiPassed} -> ${ok}`);

package/builtin/pipelines/module-migrate/scripts/static-check.mjs

@@ -0,0 +1,82 @@
+#!/usr/bin/env node
+/**
+ * 把 `check_imports.mjs` 接到 Workspace 运行时上。
+ *
+ * 用法（由 tool_nodejs 的 script 调用）：
+ *   node static-check.mjs <repoRoot> <beforeList> <afterList> <okPath> <reportPath>
+ *
+ * `<beforeList>` / `<afterList>` 是**清单正文**（每行一个仓库相对路径），不是文件路径——
+ * 上游 agent 的回复正文直接作为引脚值传进来。这里落成临时文件再喂给 check_imports。
+ *
+ * `check_imports.mjs` 是旧执行栈的产物，stdout 吐一行
+ * `{"err_code":0|1,"message":{"result":"…"}}`。Workspace 运行时不认这个信封，所以在这里
+ * 拆开：结果写 `<reportPath>`，通过与否写 `<okPath>`（`true` / `false`）。
+ *
+ * **总是 exit 0**：查出问题不是这一步失败，是下一步要修的事。真失败只有「脚本跑不起来」。
+ * 缺 tree-sitter 依赖时也走 `false` + 明确的报告，绝不静默跳过。
+ */
+import { spawnSync } from "node:child_process";
+import fs from "node:fs";
+import path from "node:path";
+import { fileURLToPath } from "node:url";
+
+const HERE = path.dirname(fileURLToPath(import.meta.url));
+const [repoRoot, beforeText, afterText, okPath, reportPath] = process.argv.slice(2);
+
+if (!repoRoot || !okPath || !reportPath) {
+  console.error("用法: node static-check.mjs <repoRoot> <beforeList> <afterList> <okPath> <reportPath>");
+  process.exit(1);
+}
+
+const finish = (ok, report) => {
+  fs.writeFileSync(reportPath, report, "utf-8");
+  fs.writeFileSync(okPath, ok ? "true" : "false", "utf-8");
+  console.log(ok ? "静态检查通过" : "静态检查有问题，交给下游修");
+  process.exit(0);
+};
+
+if (!fs.existsSync(path.join(HERE, "node_modules", "tree-sitter"))) {
+  finish(false, [
+    "# 静态检查未运行",
+    "",
+    "`check_imports.mjs` 依赖 tree-sitter，当前 `scripts/node_modules` 里没有。先执行：",
+    "",
+    "```bash",
+    `cd ${HERE} && npm install`,
+    "```",
+    "",
+    "装完重跑本节点。**这一轮的 false 不代表代码有问题，只代表没查。**",
+  ].join("\n"));
+}
+
+const tmpDir = fs.mkdtempSync(path.join(process.env.TMPDIR || "/tmp", "static-check-"));
+const beforeFile = path.join(tmpDir, "before.txt");
+const afterFile = path.join(tmpDir, "after.txt");
+fs.writeFileSync(beforeFile, String(beforeText || ""), "utf-8");
+fs.writeFileSync(afterFile, String(afterText || ""), "utf-8");
+
+const r = spawnSync("node", [
+  path.join(HERE, "check_imports.mjs"),
+  "--root", repoRoot,
+  "--before-list", beforeFile,
+  "--after-list", afterFile,
+], { encoding: "utf-8" });
+
+if (r.error) {
+  console.error(`执行 check_imports.mjs 失败：${r.error.message}`);
+  process.exit(1);
+}
+
+let payload = null;
+try {
+  payload = JSON.parse(String(r.stdout || "").trim().split("\n").pop() || "");
+} catch {
+  payload = null;
+}
+
+if (!payload) {
+  finish(false, `# 静态检查输出无法解析\n\n\`\`\`\n${(r.stdout || "") + (r.stderr || "")}\n\`\`\`\n`);
+}
+
+const detail = String(payload?.message?.result || "").trim();
+finish(payload.err_code === 0 && !detail, `# 静态引用检查\n\n${detail || "未发现主模块直接引用被迁类。"}\n`);

package/builtin/pipelines/module-migrate/workspace.flow.js

@@ -0,0 +1,172 @@
+import { agent, control, display, flow, provide, tool } from "agentflow/flow";
+
+// ── 输入：原来这些值硬编码在节点正文里，现在提到引脚上 ──────────────
+const repoRoot = provide.str("仓库根目录", {
+  value: ".",
+});
+const sourcePath = provide.str("待迁移的源码路径", {
+  value: "app/src/main/java/com/example/push/",
+});
+const moduleName = provide.str("新模块名", {
+  value: "module-push",
+});
+const rules = provide.str("模块规范文档", {
+  value: ".cursor/rules/android-module-structure.mdc、.cursor/rules/module-main-sub-dependency.mdc",
+});
+
+// ══ ① 定范围 ════════════════════════════════════════════════════════
+const scope = agent.subAgent("确定迁移范围", {}, `参照 ${rules.value}，确定 ${sourcePath.value} 的迁移范围。仓库根目录 ${repoRoot.value}。
+
+**只定范围，不动任何文件。**
+
+回复正文就是要迁的文件清单，每行一个仓库相对路径，不要标题、不要编号、不要别的话——下游脚本按行解析。`);
+
+const showScope = display.markdown("迁移范围（确认后点②）", { content: scope.result });
+
+export const scopeRun = flow("① 定范围", scope, showScope);
+
+// ══ ② 建模块并迁移 ══════════════════════════════════════════════════
+const newModule = agent.subAgent("新建模块", {}, `参照 ${rules.value}，在 ${repoRoot.value} 下新建模块 ${moduleName.value}，同时建出配套的 ${moduleName.value}_api。
+
+按规范补齐 build.gradle、settings.gradle 注册、包结构。`);
+
+const migrate = agent.subAgent("执行迁移", {}, `按清单迁移到 ${moduleName.value}：
+
+${scope.result}
+
+**只搬代码和资源，不改业务逻辑。** 可以并行分派多个 agent，但只做搬运，不做检查。
+
+回复正文是迁移后的文件清单，每行一个仓库相对路径，格式同上。`);
+
+// ── 静态检查：脚本查一遍，AI 再查一遍，两个判定用脚本合成一个 bool ──
+const staticCheck = tool.nodejs("静态引用检查", {
+  repoRoot: repoRoot.value,
+  before: scope.result,
+  after: migrate.result,
+}, `node ${flowDir}/scripts/static-check.mjs ${repoRoot} ${before} ${after} ${ok} ${report}`);
+const { ok: staticOk, report: staticReport } = staticCheck;
+
+const aiCheck = agent.subAgent("AI 交叉检查", {}, `迁移前清单：
+
+${scope.result}
+
+迁移后清单：
+
+${migrate.result}
+
+脚本侧的静态检查结果：
+
+${staticReport}
+
+参照 ${rules.value}，检查主模块是否还直接依赖被迁走的类。逐条列出需要改成 API 中转的位置（\`文件:行号 -> 全限定类名\`）。
+
+**回复正文第一行必须只有 \`true\` 或 \`false\`**：脚本和你自己都没查出问题写 true，任一有问题写 false。第二行起写明细。`);
+
+const verdict = tool.nodejs("合成静态检查结论", {
+  scriptOk: staticOk,
+  aiVerdict: aiCheck.result,
+}, `node ${flowDir}/scripts/gate.mjs ${scriptOk} ${aiVerdict} ${ok} ${report}`);
+const { ok: verdictOk, report: verdictReport } = verdict;
+
+// ── 静态一次过：直接编译 ────────────────────────────────────────────
+// 「逐个编译、失败就修、修完重编」是节点内部的迭代，不是图上的环——图不支持环，
+// 而 agent 本来就能在一个节点里循环。原来那圈 anyOne + toBool + if 就是在图上
+// 表达本该在节点里表达的东西。
+const buildA = agent.subAgent("编译并修到通过", {}, `在 ${repoRoot.value} 用 gradle 列出 Java / Kotlin 的 debug 编译任务，**串行**逐个执行，一次一个，不要一把梭。
+
+失败就当场修（参照 ${rules.value}，缺的依赖走 _api 模块中转，不要把实现类重新暴露给主模块），修完重编该任务，直到全过或确实卡住。
+
+回复正文第一行只写 \`true\`（全部通过）或 \`false\`（有卡住的），第二行起写任务清单和失败详情。`);
+
+const buildOkA = control.agentToBool("编译全过了吗", { value: buildA.result }, `上游正文第一行是 true 或 false。**只回 true 或 false 这一个词**，多一个字都会被判成 false。`);
+
+const docA = agent.subAgent("输出迁移文档", {}, `把这次迁移写成文档：范围、改了什么、主模块改成 API 中转的位置、遗留问题。
+
+范围：${scope.result}
+
+编译结果：${buildA.result}`);
+const showDocA = display.markdown("迁移文档", { content: docA.result });
+const buildStuckA = display.markdown("编译卡住，需要人工介入", { content: buildA.result });
+
+const gateBuildA = control.if("编译过了吗", { prediction: buildOkA.prediction },
+  flow(docA, showDocA),
+  flow(buildStuckA),
+);
+
+// ── 静态没过：修一轮，再查一轮。没有循环原语，就展开成固定两轮 ──────
+const fix1 = agent.subAgent("修引用", {}, `静态检查没过。
+
+${verdictReport}
+
+脚本报告：
+${staticReport}
+
+AI 检查：
+${aiCheck.result}
+
+参照 ${rules.value}，把主模块里直接用到被迁类的地方改成走 SPI（对应的 _api 模块）中转。一次批量处理多条，改完自检一遍。`);
+
+const staticCheck2 = tool.nodejs("静态引用复查", {
+  repoRoot: repoRoot.value,
+  before: scope.result,
+  after: migrate.result,
+}, `node ${flowDir}/scripts/static-check.mjs ${repoRoot} ${before} ${after} ${ok} ${report}`);
+const { ok: staticOk2, report: staticReport2 } = staticCheck2;
+
+const aiCheck2 = agent.subAgent("AI 复查", {}, `修完一轮了。脚本侧复查结果：
+
+${staticReport2}
+
+参照 ${rules.value} 再查一遍主模块对被迁类的直接依赖。
+
+**回复正文第一行必须只有 \`true\` 或 \`false\`。**`);
+
+const verdict2 = tool.nodejs("合成复查结论", {
+  scriptOk: staticOk2,
+  aiVerdict: aiCheck2.result,
+}, `node ${flowDir}/scripts/gate.mjs ${scriptOk} ${aiVerdict} ${ok} ${report}`);
+const { ok: verdictOk2, report: verdictReport2 } = verdict2;
+
+// 修过一轮之后的编译链。和上面那条是两条独立的链——分支不能汇合，fan-in 是禁止的
+const buildB = agent.subAgent("编译并修到通过（修过一轮）", {}, `在 ${repoRoot.value} 用 gradle 列出 Java / Kotlin 的 debug 编译任务，**串行**逐个执行。
+
+失败就当场修（参照 ${rules.value}，走 _api 模块中转），修完重编，直到全过或确实卡住。
+
+回复正文第一行只写 \`true\` 或 \`false\`，第二行起写清单和详情。`);
+
+const buildOkB = control.agentToBool("编译全过了吗（修过一轮）", { value: buildB.result }, `上游正文第一行是 true 或 false。**只回 true 或 false 这一个词**，多一个字都会被判成 false。`);
+
+const docB = agent.subAgent("输出迁移文档（修过一轮）", {}, `把这次迁移写成文档：范围、改了什么、主模块改成 API 中转的位置、遗留问题。
+
+范围：${scope.result}
+
+修复记录：${fix1.result}
+
+编译结果：${buildB.result}`);
+const showDocB = display.markdown("迁移文档", { content: docB.result });
+const buildStuckB = display.markdown("编译卡住，需要人工介入", { content: buildB.result });
+
+const gateBuildB = control.if("编译过了吗（修过一轮）", { prediction: buildOkB.prediction },
+  flow(docB, showDocB),
+  flow(buildStuckB),
+);
+
+const staticStuck = display.markdown("两轮静态检查仍未通过，需要人工介入", { content: verdictReport2 });
+
+const gate2 = control.if("第二轮静态检查", { prediction: verdictOk2 },
+  flow(buildB, buildOkB, gateBuildB),
+  flow(staticStuck),
+);
+
+const gate1 = control.if("第一轮静态检查", { prediction: verdictOk },
+  flow(buildA, buildOkA, gateBuildA),
+  flow(fix1, staticCheck2, aiCheck2, verdict2, gate2),
+);
+
+export const migrateRun = flow(
+  "② 建模块并迁移",
+  newModule, migrate, staticCheck, aiCheck, verdict, gate1,
+);
+
+// 人工闸门：范围确认过了再点②
+flow.resume(showScope, migrateRun);