Restore uniform participant timeline mode - #1342
Merged
Merged
Conversation
Contributor
|
🪓 PR closed, deleted preview. |
JackWilb
marked this pull request as ready for review
July 23, 2026 17:01
This was referenced Jul 29, 2026
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
devbranchanswerStatuscontract (correct,incorrect,unknown, or unconfigured)Why
PR #1262 merged into the intermediate
codex/issue-1240branch, but that merge was not present when the intermediate branch later landed ondev. As a result, the uniform timeline feature and its follow-up fixes were absent fromdev.The unrelated planning documents accidentally included in #1262's final commit are intentionally excluded.
Impact
Analysts can independently choose participant timeline ordering (Sequence or Answer time) and sizing (Time or Uniform). Uniform mode gives each task an equal-width slot and scrolls when the minimum task width exceeds the available detail-panel width.
Validation
yarn unittest --run— 145 files passed; 1,964 tests passed and 1 skippedyarn typecheckyarn lintyarn buildgit diff --check