test(mv3): prove bounded bookmark mutation compatibility - #56
Draft
seonghobae wants to merge 3 commits into
Draft
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 10, 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 #27.
Buyer-visible gap
The pinned real-Chromium MV3 lane previously proved bookmark API visibility only through read-only
chrome.bookmarks.getTree(). A defensible compatibility claim also needs one controlled mutation lifecycle that creates, reads back, and removes test state without touching an ambient human profile.Dependency
This Draft remains stacked on exact PR #43 head
27ce89066ed1473dcd66eb26a2f91becf9df5424. It is not independently integrable while #43 remains active.TDD and RCA
The lane first added a fail-first contract requiring the controlled fixture to create one deterministic bookmark for the
127.0.0.1/page.htmlsender, read it back, and remove it infinallycleanup.Production then implemented the bounded lifecycle. The real pinned-Chromium workflow succeeded, but exact CI exposed a separate repository-contract defect:
tests/test_mv3_bookmarks_history_contract.pystill required the historicalchrome.bookmarks.getTreesource shape even though the executable fixture had intentionally moved tochrome.bookmarks.create→get→remove.The repository contract was corrected rather than weakening the browser proof. Current exact head is
e1099e35ac000c7bf87ea75666cfdd928a386370.Current implemented boundary
The fixture now:
http://127.0.0.1/.../page.htmlcontrolled sender with no embedded credentials;finallycleanup and fails the evidence if cleanup fails;Exact-head evidence
On unchanged exact head
e1099e35ac000c7bf87ea75666cfdd928a386370:31427219564: success;31427220684: success against real pinned Chromium;No predecessor-head result is transferred to this head.
Scope boundary
This is compatibility evidence only. It does not grant OriginWeave Agent bookmark authority, expose a general bookmark tool, mutate a human profile, add model calls, create persistence ownership, or complete the full issue #27 extension matrix. Chromium permission and browser compatibility remain separate from OriginWeave Agent capability/policy authority.
Canonical product documentation remains owned by PR #44. Keep this PR Draft while prerequisite #43 remains active. This scheduled actor does not merge or self-approve.