Repository navigation
feat: resume an approved session without a new QR token - #45
Merged
Merged
Conversation
kvm404
marked this pull request as ready for review
August 18, 2026 01:54
This was referenced Aug 18, 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
resume_tokenat approve.POST /reconnect(HTTP 200) rebinds RTP identity after a drop without a new QR.handlePairso the 202 can carryresume_token.Why
v0.2 PR 4. Mid-meeting Wi-Fi recovery needs a credential that is not the 2-minute QR token.
Replaces #44, which GitHub closed when
feat/gst-supervisewas deleted after merging #42. This branch is rebased ontomain(post-#42).Testing
Evidence:
go test ./.../-race; AndroidtestDebugUnitTeston the original stack. CI will re-run on this rebase.Privacy/Security Impact
resume_tokenis never in the QR orGET /pairing. Loopback/statusnever includes secrets./reconnectuses constant-time compare. Different phone while a session is live is 409. No disk trust store in this PR.Notes
Draft stacked on merged #42. Does not implement Android NetworkCallback reconnect (PR 5) or persistent trust (PR 6).