fix(frontend): bind session tokens to backend transport - #34
Open
MyButtermilk wants to merge 4 commits into
Open
fix(frontend): bind session tokens to backend transport#34MyButtermilk wants to merge 4 commits into
MyButtermilk wants to merge 4 commits into
Conversation
MyButtermilk
marked this pull request as ready for review
August 20, 2026 21:14
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
http/wsorhttps/wssReview of the linked suggestions
The linked Claude session maps to commit
4fed456e3e30a51af644f3fdbbb3cd677a3f1fe2, which is already an ancestor ofmain.main; no duplicate change.main; no duplicate change.mainhas import locking, off-event-loop construction, deferred cache cleanup, and explicit cancellation ownership that the old simplification would weaken.Security boundary
Session-token mutation remains limited to authenticated backend paths (
/api/*and/ws). Endpoint matching now fails closed unless hostname, effective port, and transport security family all agree. HTTP and WebSocket variants are paired only within the same family (httpwithws,httpswithwss); unsupported protocols are rejected.Validation
Hybrid PR Checksrun 328 completed successfully for headff297d6ddb1e4c5998cf303d56657f1b6b5a6798.