Repository navigation
feat: validate reviewed Goal Run configuration - #8
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Add Prepare CALL-E Goal Run to choose a published Goal by title, version, and ID, show its input/result fields, and check mapped values against a saved reviewed interface. Invalid values or changed publications stop the example before creation.
Ship an importable workflow and plugin version 0.4.0. Existing creation and lookup tools keep their original-request replay and accepted-ID recovery behavior.
Evidence
After: The selector and preparation node expose required fields, types, defaults, result definitions, and publication changes; 261 tests pass, including the execution tool's actual output shape.
confirmed=yes), unchanged-request replay returning the same Run ID, and recovery by ID. Missing, wrongly typed, and unknown fields stop before the execution node. Controlled API cases additionally verify changed fields, publication during acceptance, and saved-request recovery after publication.Merge Danger
Door: two-way
Reverting removes the new helper and example. No data migration or deployment is included.
Blast Radius: Dify
Applies to workflows adopting the new preparation node. The example retains accepted IDs when the API accepts a different published version and requires review before downstream action.