Repository navigation
Use Jev with the upstream execution sequence in 0.3.6 - #8
Merged
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
1 participant
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.
Jev Bookmarks still pinned an older Jev fork that adds an initial BLOCKED observation wait. Update the dependency to the maintained fork that uses the upstream execution sequence, with the matching simplified Browser Harness Git dependency. Bump the preview to 0.3.6 and document the dependency change.
The URL selection, browser adapter, usefulness judgment, history connection and harness skills are unchanged. Validation: 21 Python tests pass (one platform skip), three extension tests pass, Ruff and package build pass. The pinned Jev and Browser Harness sources have also passed their tests on macOS, Windows and Linux. No new live-model latency or all-harness cold-connection claim is made.