test(mv3): prove bounded history mutation compatibility - #59
Draft
seonghobae wants to merge 15 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 was referenced Aug 16, 2026
Reconcile the declared MV3 stack by preserving the history add/read/delete lifecycle while importing the exact current bookmark-diagnostic prerequisite. The merged fixture keeps both bounded mutation contracts, and the runner/docs retain the allow-listed bookmark diagnostic evidence without transferring predecessor checks or reviews.
Rebuild the history-mutation lane on the exact current PR #178 tree while preserving only its controlled history source/test delta and changelog evidence. Keep the prerequisite bookmark diagnostics, ChromeDriver cleanup resilience, and extension-authority hardening intact. No predecessor check or review evidence transfers.
seonghobae
added a commit
that referenced
this pull request
Aug 17, 2026
Rebuild the update-migration lane on the exact current PR #59 tree while preserving its controlled update/version-migration source, tests, and changelog evidence. Carry forward the prerequisite bookmark/history behavior and the current ChromeDriver cleanup resilience, including primary-error preservation and successful hard-kill recovery. No predecessor check or review evidence transfers.
Advance the controlled history-mutation lane onto exact current PR #178 while preserving its history-only semantic delta and the prerequisite's latest bookmark doctoring. No predecessor check or review evidence transfers.
seonghobae
changed the base branch from
test/mv3-bookmark-mutation
to
cursor/bc-62f8754b-f579-4115-9089-cace87f78155-206a
August 17, 2026 10:18
seonghobae
added a commit
that referenced
this pull request
Aug 17, 2026
Advance the extension update-migration lane onto exact current PR #59 while preserving its controlled migration-only semantic delta. The child tree already contains the prerequisite doctoring content, so this is a topology reconciliation only. No predecessor check or review evidence transfers.
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. This Draft is the controlled history-mutation child of the bookmark-diagnostic lane.
Buyer-visible gap
The pinned real-Chromium Manifest V3 lane previously proved the
historyAPI only through read-only search. A defensible compatibility claim also needs one controlled mutation lifecycle inside the ephemeral compatibility profile without touching ambient human browsing history.Live dependency / repaired stack
Exact current head is
3de7fd28be57f960bd8efd3ad9be56d016e3d48a. Its exact semantic prerequisite and GitHub base is PR #178 branchcursor/bc-62f8754b-f579-4115-9089-cace87f78155-206aat exact head3083a8430f8971540f4ffe5d291955b6eb13b31f.Fresh exact compare #178 → this head reports ahead 13 / behind 0, with merge base exactly
3083a8430f8971540f4ffe5d291955b6eb13b31f. Relative to #178, the semantic delta is limited to the controlled history lifecycle, its dedicated contract test, and its changelog evidence. No prerequisite/predecessor check, review, or approval is transferred.GitHub base metadata is now aligned with the real prerequisite branch. The earlier body claim that metadata still named #56 and that source ancestry alone represented the stack is obsolete. Semantic integration order is represented in both ancestry and PR metadata: #43 → #56 → #178 → #59.
Keep this PR Draft while the prerequisite stack remains active.
TDD and implemented boundary
The earlier test-only head
4b5f393a7420541723a07243b83cdaa7e28948deestablished RED because the controlled history-mutation lifecycle did not exist. The real Chromium fixture now:http://127.0.0.1/.../page.htmlsender without embedded credentials;chrome.history.addUrl;chrome.history.search;finallythroughchrome.history.deleteUrl;Exact-current evidence
On unchanged exact head
3de7fd28be57f960bd8efd3ad9be56d016e3d48a:32019562044: success;95356173132: success for repository contracts, formatting, locked workspace/all-target checks, tests, strict Clippy, and rustdoc;95356173161: success, including exact owned-production function/line/region/branch coverage enforcement;32019562024: success on the pinned real-Chromium lane;Feature-base central/security workflows not executed for this exact head remain absent evidence, not passing evidence. No predecessor, prerequisite, skipped, queued, cancelled, synthetic-merge, stale, status-only, or model-only result is promoted as current proof.
Scope boundary
Compatibility evidence only. This lane does not grant OriginWeave Agent history or bookmark authority, expose history/bookmark tools, access a human/default profile, persist OriginWeave-owned browser-history data, add model calls, widen network authority, alter workflows, or make a release claim. Chromium permission and compatibility remain separate from OriginWeave Agent capability/policy authority. Passing automation is not independent approval. This scheduled actor does not merge, self-approve, alter workflows, add secrets, weaken checks, tag, or publish.