Charles YaoandClaude Opus 5 2692243792 feat(workflow-generator): bind branch-node ids to the planner's handles ...

The planner names a branch's outgoing source_handle values (rule 12) in
one LLM call; the node builder chooses the case / class / action ids in
another, and nothing told it the planner had already chosen. ESQ1-303's
if-else was built with case "true" against planned edges on
"score_equals_60" / "else", so both arms were skipped.

The builder already receives the planned edges with their handles in
"Normalized plan and topology". The if-else, question-classifier and
human-input snippets now state the contract: declared ids MUST be those
planned handles; the ELSE arm is implicit ("false") and is never a case.
human-input also gets a matching clause for its implicit timeout arm
("__timeout"), which must never be declared as a user action. Shared
with cmd+K /create and /refine; the postprocess repair stays as a
fallback.

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

2026-09-22 01:01:18 -07:00

..

prompts

feat(workflow-generator): bind branch-node ids to the planner's handles

2026-09-22 01:01:18 -07:00

__init__.py

perf(workflow-generator): parallelize node config generation (#38975)

2026-07-17 02:34:15 +00:00

runner.py

feat(workflow-generator): reject undeclared branch handles and bad http bodies

2026-09-22 00:52:26 -07:00

tool_catalogue.py

fix(dify-builder): wire resource readiness into recommender/gap prompts

2026-09-20 16:41:52 -07:00

types.py

feat(workflow-generator): reject undeclared branch handles and bad http bodies

2026-09-22 00:52:26 -07:00