fix(workflow): prevent context shadowing via typed state schema#40
Merged
Conversation
- Replace implicit node-ID-keyed context with a typed WorkflowStateSchema to ensure prompt variables always resolve to the latest mutated state, fixing stale evaluations.
- Update OutputExtractionPostProcessor and nodes to explicitly declare writes, mapping outputs to semantic state variables rather than node IDs.
- Introduce WorkflowValidator to provide strict compile-time validation of state variable declarations, writes mappings, and {variable} prompt bindings.
- Expand DSL capabilities with StateSchemaBuilder, ApprovalTransition, and onApproval/onRejection routing extensions.
- Migrate all existing JSON workflow fixtures, architectural documentation, and developer guides to reflect the new explicit state model.
Resolve: #39
Signed-off-by: Aleksandr Suvorov <asuvorov@hensu.io>
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
1 participant
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.
Resolve: #39