test(mv3): require bookmarks and history compatibility

[seonghobae]

Buyer-visible gap

Partial implementation of #27. OriginWeave's pinned real-Chromium compatibility lane already proved core Manifest V3 service-worker, content-script, storage, DNR, tabs, windows, scripting, commands, side-panel, real-click, and restart-persistence behavior, but buyer-facing compatibility evidence still lacked executable read-only bookmarks and history coverage.

Test-first implementation

The slice began with formatting-clean RED contract head d593d0b10c35ea9cd98181500a8466d3d97e6556, which required before fixture implementation:

• explicit bookmarks and history fixture permissions;
• real service-worker execution of chrome.bookmarks.getTree and chrome.history.search;
• content-script evidence propagation for both APIs;
• repeatability evidence requiring both surfaces on every pinned-Chromium pass.

Production fixture/evidence changes then added the permissions, real service-worker calls, DOM evidence propagation, and runner-side requirements. The runner now includes both surfaces in each browser pass and in the existing three-trial initial/restart repeatability gate; a missing or failing surface fails closed rather than being omitted from the report.

Exact-head evidence

Exact current head d79a13a401a00657bf39f405a3ae3fcde2d920fe is non-draft and mergeable on protected main a2e3ce2b2cfe4329c47190c0df3ecac4ff4220c0 with no ancestry drift.

On this unchanged exact head:

• CI 31336052777: success, including repository contracts and exact production coverage enforcement;
• Manifest V3 Compatibility 31336052761: success against the pinned real Chrome for Testing lane;
• Security Scan 31336052740: success;
• SAST Semgrep 31336052757: success;
• CodeRabbit exact-head commit status: success;
• no unresolved review threads are returned.

The repository's merged solo-maintainer governance keeps all technical/security gates mandatory while the non-author approval gate is conditionally on hold only when GitHub itself does not require counted approval and fewer than two eligible non-author reviewers exist. No self-approval or synthesized review evidence is used here.

Scope boundary

Read-only compatibility evidence only. This slice does not mutate bookmarks or history, add downloads/native messaging/Web Store behavior, widen OriginWeave Agent authority, add model calls, or make a universal Chrome-extension compatibility claim.

Partial implementation of #27.

[coderabbitai]

Warning

Review limit reached

@seonghobae, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 51 seconds

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 0471ac16-8d74-46cd-bf98-34272ae0f92a

📥 Commits

Reviewing files that changed from the base of the PR and between a2e3ce2 and d79a13a.

📒 Files selected for processing (5)

• scripts/ci/run_mv3_compatibility.py
• tests/fixtures/mv3_basic/content_script.js
• tests/fixtures/mv3_basic/manifest.json
• tests/fixtures/mv3_basic/service_worker.js
• tests/test_mv3_bookmarks_history_contract.py

---

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.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}