Fix Jev fast path after automatic screenshots - #3068
Merged
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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.
Normal vision-capable runs include an initial screenshot, and may include automatic screenshots later. The fast browser path added in #3065 treated any non-text block anywhere in the conversation as unsupported, so these routine captures prevented Jev from running at all.
This change lets the AX-only Jev path proceed after initial and automatic browser captures without sending their pixels to TypeSafe. Current user attachments, explicit screenshot-tool results, and unknown non-text inputs still route the decision to the active model. Pages containing password, OTP, payment, or file controls fall back as a whole, including when a sensitive control appears after Jev selected an action. Exported traces now show Jev routing, fallback, usage, and skip reasons without including bounded request evidence.
Chrome and Firefox behavior, tests, architecture notes, privacy documentation, and the manual benchmark guide are updated together.
Validation:
npm run test:systemone:fast— 26 unit regressions, 20 real-browser assertions, and both-browser fixture scoring passnpm run test:systemone— 24 scheduler/client regressions passnpm run test:security— 60/60 checks passnode test/selection-scope-restoration.mjspassesnode scripts/benchmark-offline-relevance.mjspasses its existing checknpm testreaches the repository's two existing release-artifact failures: the changelog is behind package version 36.7.3 anddist/webbrain-chrome-36.7.3.zipis absent; 2,391test/run.jschecks passNo live or paid Jev calls were made.