feat(export): preserve event times and attach metadata#6
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.
What changed
traces exportso root spans no longer fall back to 1970 when some events lack top-level time fields.--attr key=valueand--metadata file.json, copied into exported span attributes after redaction.Why
Agent projects need to export raw event traces and still attach generic run metadata such as task id, arm, model, score, or campaign id. This keeps traces domain-neutral while letting downstream eval/reporting tools join spans to experiment rows.
Verification
pnpm vitest run tests/file-export.test.tspnpm typecheckpnpm test(70/70)pnpm build2026-06-27T21:33:03.000Z, end2026-06-27T21:37:31.743Z, metadata attached,has1970=false.has1970=false.019eb95c-a384-7df2-80c8-8d35ae01af3c; 53,914 spans in analysis path.