Include input payload in execution events and add output schemas to reasoner examples #146
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
…easoner examples - Include input payload in status update, completion, and failure events - Add explicit output schemas to analyzeSentiment and processWithNotes reasoners - Improves event data completeness for downstream consumers Co-Authored-By: Claude <noreply@anthropic.com>
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
Changes Made
inputfield to event data when publishing execution eventsoutputSchemaconfiguration toanalyzeSentimentandprocessWithNotesreasonersWhy
Event consumers can now access the original input payload alongside results, enabling better debugging and observability. The explicit output schemas in examples demonstrate best practices for typed reasoner outputs.
Test Plan
🤖 Generated with Claude Code