Publish complete final results with finalized trace references - #94
Open
areshand wants to merge 1 commit into
Open
Publish complete final results with finalized trace references#94areshand wants to merge 1 commit into
areshand wants to merge 1 commit into
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.
Why
The production report dropped the first six lines of an 85-line, sub-6KB final answer because result publication always kept only the last 80 lines. It also emitted the public report before normalized agent events appeared, so the first transcript referenced only lifecycle logs.
What changes
events.jsonl.Validation
Deployment
Source-only PR. It does not deploy or change trace storage.