Skip to content

feat: resume an approved session without a new QR token - #45

Merged
kvm404 merged 1 commit into
mainfrom
feat/session-resume
Aug 18, 2026
Merged

kvm404 merged 1 commit into
mainfrom
feat/session-resume

Conversation

@kvm404

@kvm404 kvm404 commented Aug 18, 2026

Copy link
Copy Markdown
Owner

Summary

  • Mint a process-lifetime resume_token at approve.
  • POST /reconnect (HTTP 200) rebinds RTP identity after a drop without a new QR.
  • Move auto-approve into handlePair so the 202 can carry resume_token.
  • Android pairing types store the token for the later reconnect service (PR 5).

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-supervise was deleted after merging #42. This branch is rebased onto main (post-#42).

Testing

  • Unit tests
  • Manual CLI verification
  • Manual Android verification

Evidence: go test ./... / -race; Android testDebugUnitTest on the original stack. CI will re-run on this rebase.

Privacy/Security Impact

  • Pairing/authentication
  • Local network transport

resume_token is never in the QR or GET /pairing. Loopback /status never includes secrets. /reconnect uses 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).

@kvm404
kvm404 marked this pull request as ready for review August 18, 2026 01:54
@kvm404
kvm404 merged commit e9a2d58 into main Aug 18, 2026
2 checks passed
@kvm404
kvm404 deleted the feat/session-resume branch August 18, 2026 01:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant