Charles YaoandClaude Opus 5 f12d8f4e0f feat(dify-builder): plan in Dify node vocabulary, not business language ...

propose_plan_v1's system prompt was two sentences with no node vocabulary,
so it planned in business language -- "Send a Feishu notification",
"Connect to the database". Those steps became the generator's
"# User instruction" verbatim, asking it to map work onto nodes that do
not exist, and the failure only surfaced at build-generate-graph, minutes
after the user had approved the plan (ESQ1-279).

The generator already knows the node types: its SHARED system prompt
carries the whitelist. The gap was upstream, in the Builder's own planner.
Naming the vocabulary here makes that existing whitelist sufficient.

Builder-only: nothing under core/workflow/generator/ is touched, so the
cmd+K /create and /refine features are unaffected.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

2026-09-20 23:05:34 -07:00

..

fixtures/workflow

…

helpers

…

integration_tests

chore: add some type (#37173)

2026-09-19 09:26:15 +00:00

test_containers_integration_tests

fix(builder): avoid layout conflicts and serialize draft updates (#42601)

2026-09-21 09:48:02 +08:00

unit_tests

feat(dify-builder): plan in Dify node vocabulary, not business language

2026-09-20 23:05:34 -07:00

__init__.py

…

conftest.py

…

pytest_dify.py

…

seed_legacy_model_type_dirty_data.py

…

workflow_test_utils.py

…