test(browser): record controlled Agent Task resource evidence - #72
Draft
seonghobae wants to merge 6 commits into
Draft
test(browser): record controlled Agent Task resource evidence#72seonghobae wants to merge 6 commits into
seonghobae wants to merge 6 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 #71.
Buyer-visible gap
Issue #28 requires real browser/task RSS, observation bytes, action latency and task duration. PR #70/#71 prove real pinned-Chromium task execution plus browser-computed role/name evidence, but the runtime evidence previously lacked measured resource fields.
Dependency / current stack
This Draft now targets exact current PR #71 head
f82a3b27243adbb14c28af22d408a25cb3c296e9; current exact #72 head ise0b5d43c3a869605aaefa2e4752de7b1b641ddbd. The branch has already been aligned to the moved prerequisite and GitHub reports it mergeable against that exact base. Keep Draft while #71/#70/#65 remain active. No prerequisite check, review, status, or mergeability evidence transfers.TDD / implemented boundary
a9402a13c9ed429b8f3be2c623b994a0dfda3bb4required strict Linux/proc/<pid>/statusRSS parsing/sampling, ChromeDriver-issuedgoog:processID, and boundedbrowser_process_rss_bytes,semantic_observation_bytes,action_latency_ms, andtask_duration_msevidence.31454745237, Rust contracts job93666110420, checked out that exact test-only head and failed at the intended repository contract because_parse_linux_proc_status_rss_bytesdid not exist. This is the observed RED boundary.VmRSSparsing with unit/shape/u64 overflow rejection; bounded/proc/<pid>/statusreads for the ChromeDriver-issued browser PID; exact UTF-8 JSON byte size for the two controlled role/name observations; monotonic clear/type/click action latency; and end-to-end task duration. Invalid/missing process identity or malformed resource evidence fails closed.e0b5d43c3a869605aaefa2e4752de7b1b641ddbdpreserves that evidence behavior while descending from exact current test(browser): verify semantic role and name before controlled action #71 headf82a3b27243adbb14c28af22d408a25cb3c296e9.Exact-head proof
On unchanged exact head
e0b5d43c3a869605aaefa2e4752de7b1b641ddbdagainst exact current prerequisite #71 headf82a3b27243adbb14c28af22d408a25cb3c296e9:31549872719: success;31549872700: success;No predecessor-head result is transferred.
Truth boundary
This lane is execution evidence only.
browser_process_rss_bytesis intentionally narrower than task RSS: a single ChromeDriver-reported browser PID does not attribute Chromium renderer/GPU/utility descendants and must not be presented as whole-browser or whole-task RSS. Full multi-process attribution belongs to the separately stacked process-tree evidence lane and later trusted adapter/process-set composition with #51/#66.semantic_observation_bytesmeasures only the bounded controlled role/name evidence serialized by this runner; it is not raw DOM size, model-context cost, source-node/network provenance, or productSemanticNodeObservationcomposition. No GPU/VRAM/local-AI evidence, production browser adapter, policy dispatch, or real-site compatibility is claimed.