Repository navigation
fix(flow): guard frontier trace actions and clear stale anchors - #449
Merged
Merged
Conversation
byronwall
marked this pull request as ready for review
November 22, 2026 20:20
byronwall
enabled auto-merge (squash)
November 22, 2026 20:20
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.
Verified defect (UX-006)
On main a4d2a8e, the rendered inspector offers both
Trace from hereandAdd to the tracefor a synthetic frontier box. Both handlers serialize its display ID as a program element. A component regression failed on the old implementation by finding the invalid trace button.Change
Verification
scripts/check.sh client: passed, TypeScript + 496 tests.socket() failed: Operation not permitted, also on an escalated retry. Browser CI must pass before merge; no local end-to-end pass claimed.No merge performed.