fix(chat): prevent queue recovery panel flashing during normal sends - #3192
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
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.
Problem and fix
Every ordinary desktop send briefly opened the host queue panel with zero queued messages and an unknown-delivery warning. The durable outbox was exposed as recovery state while its RPC was still awaiting acknowledgement.
Track live transmissions separately from persisted recovery records in the shared desktop/mobile queue client. Observer refreshes exclude live transmissions; failed acknowledgements and recreated pages still expose the original durable record for explicit, idempotent recovery. Persist-before-send and actual host queue display are preserved. Ignore stale overlapping outbox reads.
Also align three queue/rollback typography declarations with the current main branch's typography gate using existing semantic tokens.
Validation
check:webCanvas, appearance, typography, and theme/color gates passed. Web UI TypeScript passed separately after populating the new worktree with existing generated API bindings (their Rust contract sources are unchanged).Remote coverage uses simulated host RPCs and real Chrome storage; no live phone/host end-to-end run or installed desktop update is claimed.