Charles YaoandClaude Opus 5 fe3f8154b5 feat(dify-builder): carry node usage rules on the Builder-only directive ...

Meeting item 9 asked for per-node usage detail in the generator prompts.
Those prompts are shared with cmd+K, so the detail rides the channel the
Builder already owns instead: _WORKFLOW_TOPOLOGY_DIRECTIVE, prepended to
every generator instruction at build.py:377 and invisible to cmd+K. That
mechanism is proven -- it is why workflow mode never gets 'answer' nodes.

The rules added are the ones that broke real builds: tool nodes expose
text/files/json and not 'result' (ESQ1-296, ESQ1-289), document-extractor
needs a file input, container children belong inside the container
(ESQ1-288), if-else operators must match the variable's type
(ESQ1-285/290), and http-request inputs belong on the start node
(ESQ1-286).

Deliberately does NOT restate the node whitelist: the generator's shared
system prompt already carries it, and duplicating it would burn planner
output budget that ESQ1-300 already implicates.

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

2026-09-20 23:08:27 -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): carry node usage rules on the Builder-only directive

2026-09-20 23:08:27 -07:00

__init__.py

…

conftest.py

…

pytest_dify.py

…

seed_legacy_model_type_dirty_data.py

…

workflow_test_utils.py

…