Repository navigation
Record Session traces beside Session logs - #1051
Merged
Merged
Conversation
This was referenced Oct 22, 2026
Merged
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.
Summary
Every Session records an OTLP Session trace beside its Session log.
Command ownership gives Ticket Runs and Base fixes the same trace ID. CLI and Console inventories list each Session once; Model evidence and review-report names stay intact.
Closes #985
Evidence
all_harnesses_write_otlp_session_traces_beside_unchanged_logsfailed because the OTLP files were missing.After: all six fake Harness formats pass through the shared recorder, the OTLP Reader and official protocol types. Whole-binary tests also cover live growth, hard kill, interruption, child Runs and inventory.
cargo clippy --all-targets -- -D warningspassed./usr/bin/time -p scripts/affected-tests origin/issue-700selectedcargo nextest run: 2,275 passed, 3 skipped. Wall time 1,317.43 s, including 20.20 s incremental compilation; test execution 1,295.597 s on the shared Linux host.Test seams
Recording::run, observed through Session logs, OTLP Reader and official OTLP request types, including live output and interruption.Review
Reviewed against
issue-700, pinned to remote basefee7a24ff749c7a777c25ec4605d054b7df13a82. The other worktree's older local branch was left intact..thirdshift-review-EwdrcB/standards.mdandspec.mdon the implementation machine.Unaddressed findings
Merge Danger
Door: two-way
Blast Radius: Sessions
Every agent Session writes two additional local files; the existing Session log remains available during this transition.
Built with codex · gpt-6.1-sol · xhigh