feat: include processed use case content on UseCaseEvent - #387
Merged
Conversation
Event handlers run outside the DSL context and cannot read outputContext or GraphQL response fields. Populate UseCaseEvent.content from processedUseCaseMap so downstream consumers can log full SOP text without ThreadLocal bridges. Co-authored-by: Cursor <cursoragent@cursor.com>
patwlan
enabled auto-merge (rebase)
June 30, 2026 10:28
patwlan
approved these changes
Jun 30, 2026
patwlan
disabled auto-merge
June 30, 2026 10:34
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
2 participants
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.
Event handlers run outside the DSL context and cannot read outputContext or GraphQL response fields. Populate UseCaseEvent.content from processedUseCaseMap so downstream consumers can log full SOP text without ThreadLocal bridges.