Skip to content

test(mv3): prove bounded history mutation compatibility - #59

Draft
seonghobae wants to merge 15 commits into
cursor/bc-62f8754b-f579-4115-9089-cace87f78155-206afrom
test/mv3-history-mutation-lifecycle
Draft

test(mv3): prove bounded history mutation compatibility#59
seonghobae wants to merge 15 commits into
cursor/bc-62f8754b-f579-4115-9089-cace87f78155-206afrom
test/mv3-history-mutation-lifecycle

Conversation

@seonghobae

@seonghobae seonghobae commented Aug 10, 2026

Copy link
Copy Markdown
Contributor

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 history API 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 branch cursor/bc-62f8754b-f579-4115-9089-cace87f78155-206a at exact head 3083a8430f8971540f4ffe5d291955b6eb13b31f.

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 4b5f393a7420541723a07243b83cdaa7e28948de established RED because the controlled history-mutation lifecycle did not exist. The real Chromium fixture now:

  • accepts only a parseable controlled http://127.0.0.1/.../page.html sender without embedded credentials;
  • derives a synthetic history URL within the same loopback fixture;
  • adds exactly that URL through chrome.history.addUrl;
  • requires exact bounded readback through chrome.history.search;
  • deletes the synthetic URL in finally through chrome.history.deleteUrl;
  • re-queries and fails compatibility evidence if cleanup did not remove the entry;
  • preserves the hardened bookmark/download prerequisite behavior, including allow-listed bookmark failure diagnostics; and
  • emits readiness/stage evidence without raw browser exception text or browsing-history contents.

Exact-current evidence

On unchanged exact head 3de7fd28be57f960bd8efd3ad9be56d016e3d48a:

  • CI run 32019562044: success;
  • Rust contracts job 95356173132: success for repository contracts, formatting, locked workspace/all-target checks, tests, strict Clippy, and rustdoc;
  • Production coverage job 95356173161: success, including exact owned-production function/line/region/branch coverage enforcement;
  • Manifest V3 Compatibility run 32019562024: success on the pinned real-Chromium lane;
  • GitHub freshly reports this Draft mergeable; and
  • current inline review threads: none.

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.

@coderabbitai

coderabbitai Bot commented Aug 10, 2026

Copy link
Copy Markdown

Important

Review skipped

Draft detected.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: c28db676-1dbf-43c5-adac-c9cca076153e

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review

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

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

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
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.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant