Require provisioned browsers in Direct verification tooling - #71
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.
Direct's owned-browser helper previously let agent-browser discover installed Chrome, which can accumulate macOS code-signature clones. It now requires a task-owned executablePath, resolves symlinks, validates Chrome for Testing/Chromium with a bounded version probe, and passes the resolved selection to the isolated driver.
Owned calls reject attachment/provider/executable overrides and ambiguous batch forms. Plain batch commands remain supported; documentation explains the migration and explicit browser provisioning. Cached selection preserves cleanup if the configuration disappears. This does not add a default runtime dependency or a new delivery gate.
Prepares 0.7.24 with authored release notes. Public install examples remain pinned to the last delivered version until publication.
Validation: independent review passed; 55 focused tests (3098 assertions), typecheck, changed-file ESLint, effect checks, generated build, KB lane and final KB checks passed. Generated Bombadil changes are import alias renames from the shared source. Full exact-head CI is required before merge and release.