Repository navigation
fix(dashboard): distinguish stored and transcript message counts - #3218
Merged
Merged
Conversation
|
![devin-ai-integration[bot]](https://avatars.githubusercontent.com/in/811515?s=60&v=4){kind=small}
Contributor
There was a problem hiding this comment.
🔍 Devin Review: 1 flag
Not posted on this PR by your GitHub settings — view it in Devin Review. (Configure)
This was referenced Oct 9, 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
1 participant
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.
The transcript inspector displayed the raw stored-message total beside canonical page counts and called the terminal cursor “last page.” That implied a shared denominator even when storage and the available transcript differ, as reported in #3211.
Label the raw total as “stored messages,” keep it out of the page range, and describe the terminal cursor as the last available page. Explain that reaching it does not account for every stored message. Paging continues to follow only the server-issued cursor, and the rendered list is named “Transcript messages.”
Validation: the mismatched-count DOM regression failed before the change; all 19 focused session UI tests pass, including refusal states and forward/backward cursor navigation. TypeScript checking and commitlint pass. The focused UI tests also pass after rebasing onto current master. Commands used the Bazel-managed Node runtime.
Addresses the count-guidance portion of #3211. This does not claim to explain the original 478-raw/290-canonical discrepancy or close that investigation. #3200 already contains the terminal-page coverage correction and the source-read fix for #3202; those changes are not duplicated here.