Repair disconnected message history after unread seek and refresh - #741
Merged
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
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.
After Jump to first unread loads an older window, manual Refresh could join it to a disconnected latest page and retain a stale later cursor. Refresh now replaces that window with the latest page and resets both cursors. Automatic refresh/read-ack fallback preserves older reading windows, and ordinary refresh replaces disconnected new arrivals instead of inventing continuous history. Drafts and existing composer behaviour are retained.
Native task:
#V#task_agent_5497a7092c696239e79ced69414ac9a1. Follow-up repair for #740; no deployment requested. #692 remains open, and its composer changes are outside these production hunks.Validation: supplied regression reproduced before repair; all 29 exchange-view tests pass, 58 tests across six affected frontend suites pass, and the previous 24 backend tests pass through PDM. Static lint and diff checks pass. Chromium fixture at 390×850 and 1280×850 exercises Conversation actions → Refresh messages, verifies replacement, cursor reset, preserved draft, resumed polling and history access, plus existing seek/read/send paths. Evidence and limitations:
docs/engineering/unread_refresh_repair_2026_09_17.md.Merge decision changes — the focused repair now satisfies Tier 1 acceptance; merge when required CI passes. Browser evidence uses synthetic HTTP data, not production authentication. Partial read receipts retain uncertain unread labels and Retry until confirmed or explicitly refreshed.