Repository navigation
fix(flow): scope exploration context to the selected root - #453
Merged
Merged
Conversation
byronwall
marked this pull request as ready for review
November 22, 2026 21:08
byronwall
enabled auto-merge (squash)
November 22, 2026 21:08
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.
Fixes #446.
The Playwright cases switch between solid-route and route-less bad-ish-solid via the real folder picker from both a route and a source anchor. They hold the original request until the new root renders, release a late error, check no old-request effect or mismatched endpoint, then exercise Back and Forward. No engine or frontier changes.
./scripts/check.sh clientpassed (typecheck + 497 tests). Browser suite requires GitHub Chromium: local Chromium in this environment has a sandbox-denied process-singleton socket. No local browser pass claimed.Survey moves: The Flow root-ownership and request-state guards change the client source being analyzed. CI reports exactly two stop-count moves in that corpus:
boundary: unproven-handoff65 → 67 (+2) andfrontier: disconnected263 → 261 (−2). All 634 trace outcomes are unchanged; no moves in the server or fixture corpus, no new trace errors or timing failures, and no engine analysis changes.