[sh00tg0a1]

Pull Request

What Changed

Brief description of changes:

• Function workbench: an input the statement tests with $name IS NULL (or IS NOT NULL) starts optional, and keeps whatever the author sets for "required". Every other input stays required, as before.
• Trial run: an optional input that is not given, or is null, is left out instead of reported missing.
• AI prompt (en/zh): when the description says a condition may be left out, write ($name IS NULL OR condition).
• Cypher reference (en/zh): a rule for optional conditions.

---

Why

• Related Issue: follow-up to feat(execution-factory): add a Cypher tool type usable as an object-type logic property source bkn-foundry#2670 (closed), problem 4 of the verification report
• Related Feature: Cypher functions. Backend: feat(bkn-backend): make a Cypher condition optional with $name IS NULL bkn-foundry#3097
• Background: feat(bkn-backend): make a Cypher condition optional with $name IS NULL bkn-foundry#3097 lets a statement write WHERE ($code IS NULL OR s.code = $code), and lets execution-factory leave out an input marked required: false. The workbench forced every Cypher input back to required whenever the statement changed, so this kind of function could not be saved from Studio.

---

How

• Key implementation points:
  • syncCypherInputs: finds the parameters followed by IS NULL / IS NOT NULL, with string literals and comments blanked first.
    • A new parameter that is tested this way starts with required: false.
    • A parameter that is already declared and tested keeps its required value.
    • Any other parameter is set to required: true, as before.
  • cypherArguments: skips an input with required: false that is not given or is null. An input with no required field still counts as required.
• Breaking changes (API, config, database, etc.): none.

---

Testing

• Unit tests passed locally:
  • vitest for src/modules/execution-factory, src/modules/knowledge-network/cypher and the locale parity test (572 tests), plus cypher-reference.test.ts and CypherQueryScene.test.tsx.
  • tsc -b; eslint and prettier on the touched files; the hardcoded-Chinese scan; the license check.
• Integration tests passed locally. N/A: no integration suite covers the workbench.
• Verified in test environment. Not yet in the browser. The backend half (bkn-backend and execution-factory) was verified on the dev VM in feat(bkn-backend): make a Cypher condition optional with $name IS NULL bkn-foundry#3097, with a function saved with two optional inputs.

Test notes:

• New: a new input tested with IS NULL starts optional, and a declared one keeps required. '$code IS NULL' inside a string literal does not count. An input without the test is set back to required.
• New: the trial run leaves out an optional input that is missing or null, and still reports a missing required one.

---

Risk & Rollback

• Potential risks: needs feat(bkn-backend): make a Cypher condition optional with $name IS NULL bkn-foundry#3097 on the server. Against an older bkn-backend, a statement with $x IS NULL is refused at save (the explain fails), so nothing wrong gets saved.
• Rollback plan: revert this PR.

---

Additional Notes

• Screenshots, logs, documentation links, etc.: fix(execution-factory): follow the Cypher changes in the function workbench #1315 changes the same syncCypherInputs (row-count inputs typed as numbers). Whichever merges second needs a small rebase.

🤖 Generated with Claude Code

[github-actions]

IS NULL 检测按 blankCypherLiterals 后的文本和 scan 的 span 偏移判断，字符串、注释里的 $name IS NULL 不会误判；cypherArguments 跳过未传的可选输入，zh/en 文案也都改了，没发现阻塞项。剩下一个疑点要作者确认：参数完全不传时后端怎么处理。

影响范围与未覆盖面

• 影响范围：影响执行工厂 Cypher 函数工作台的输入同步和试跑参数校验；已保存的函数里 required 为 undefined 的输入仍按必填处理。
• 未覆盖：后端（bkn-backend 与执行工厂）怎么处理缺失参数，前端仓库里核实不了。

待确认项（不阻断放行）

• src/modules/execution-factory/utils/cypher-function.ts — 可选输入没传时，cypherArguments 会把它从 parameters 里整个去掉，而不是传 null。原注释写的是「a statement using $name fails without one」，所以要确认两件事：bkn-backend 的 run_cypher 是否把缺失的参数当 null；执行工厂实际调用函数时是不传还是传 null。只要有一方会报 missing parameter，就应该改成显式传 `nam…

有异议或想再评一轮，请回复 /review——普通回帖不会触发复评，且回帖人需为本仓 OWNER/MEMBER/COLLABORATOR。