test(browser): execute controlled Agent Task on pinned Chrome - #70
Draft
seonghobae wants to merge 2 commits into
Draft
test(browser): execute controlled Agent Task on pinned Chrome#70seonghobae wants to merge 2 commits into
seonghobae wants to merge 2 commits into
Conversation
|
Important Review skippedDraft detected. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
This was referenced Aug 11, 2026
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.
Partial implementation of #28, stacked on PR #65.
Buyer-visible gap
PR #65 provides the deterministic controlled Agent Task fixture, but it is still only static test infrastructure. The next bounded step is to prove that the exact pinned Chrome for Testing build already used by OriginWeave CI can launch an isolated browser profile, load that fixture, perform real WebDriver input/click operations, observe the exact same-document post-condition, and tear the task profile down without inventing a product adapter or model claim.
Dependency
This Draft is stacked on unchanged exact PR #65 head
0888fe3a6ef6da547a37fd075733cc73dc52b2aband is not independently integrable before that prerequisite.TDD / RCA sequence
197ce14a5e407d61ac35b38b45c0cd042dd6278cintroduced the Agent Task pinned-browser contract before the executable runner boundary existed.31453444370, Rust contracts job93662306248, checked out that exact head and failed in Python repository contracts with 12 intended assertions. The failures were precisely the absent Agent Task fixture path, extension-disabled launch configuration, WebDriver value/click/post-condition commands, cleanup/evidence labels, and the two new runtime functions/constants. This is the observed RED boundary, not a synthetic or predecessor failure.f9917cdd8050c9fdf0aefa669f4d981af85479d6reuses the existing pinned Chrome for Testing150.0.7871.129/ revisionr1639810runner without modifying workflow authority. It adds a separate Agent Task execution boundary that uses a fresh temporary profile, disables extensions, clears/types the synthetic field through real WebDriver, clicks the submit control, verifiesdata-state="submitted"and the synthetic result text, emits bounded credential-free repeatability evidence, and proves profile removal after each trial.Exact-head proof
On unchanged exact head
f9917cdd8050c9fdf0aefa669f4d981af85479d6against unchanged prerequisite #65 head0888fe3a6ef6da547a37fd075733cc73dc52b2ab:31453647157: success;93662920741: Python repository contracts, canonical formatting, workspace/all-target check, full tests, strict Clippy and rustdoc all success;93662920759: exact owned production function/line/region/branch enforcement success;31453647201, job93662920705: success using Chrome for Testing150.0.7871.129/ revisionr1639810;mv3-compatibility-f9917cdd8050c9fdf0aefa669f4d981af85479d6, digestsha256:ab1ebc01a45cfbc92992bc178f86f7a733c0ce4d8e934850e66929afe18cb8a5: Agent Task3/3, pass rate1.0; every trial reportspost_condition=true,input_echo_verified=true,extensions_disabled=true,profile_cleaned=true; existing MV3 compatibility also remains3/3with all reported surfaces true;No predecessor-head check or review is transferred. This Draft remains stacked and must not be marked independently ready or merged while #65 is active.
Truth boundary
This lane is executable CI evidence, not the final OriginWeave browser runtime. CSS selectors are test-harness locators for the controlled fixture and are not represented as semantic role/name authority. This branch does not implement or claim WebDriver BiDi/CDP product-adapter semantics, OriginWeave semantic observation/node-handle composition, deterministic Agent policy dispatch, trusted telemetry/process attribution, secret brokerage, model execution, persistence, or completion of issue #28. Those remain separate active prerequisites and the later real runtime composition boundary.