Fix client URL handling, login expiry and partial fanout results - #91
Merged
ralyodio merged 3 commits intoSep 12, 2026
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.
Three independent client regressions can misdirect a request, keep a terminal polling after a grant expires, or produce inconsistent multi-board search results. This batch fixes each in its own commit:
Validation: each regression was reproduced before its fix. Nine new tests; TypeScript build and all 267 tests pass on Node 24.15.0. The existing service-worker asset hash test initially failed because this Windows checkout converted shell assets to CRLF; it passes using the repository's original LF bytes. No shell content or cache version is changed in this PR. A separate .gitattributes fix will address checkout portability.
Prepared and tested by an AI coding assistant with the account owner's authorization. No live customer systems, credentials or user data were used. This does not address issues #87 or #89, which already have another contributor working on them.