test(mv3): require bounded bookmark mutation diagnostics

[cursor]

Close the buyer-visible gap on the Manifest V3 bookmark-mutation lane: a bare bookmarks: missing result did not identify which controlled create/get/remove stage failed.

Implemented boundary

Exact current head is 3083a8430f8971540f4ffe5d291955b6eb13b31f.

• The controlled fixture returns only allow-listed bookmark stage tokens (bookmark-source-rejected, bookmark-create-rejected, bookmark-get-missing, exact mismatch tokens, bookmark-remove-rejected, and bookmark-complete-ready) and still removes the synthetic bookmark in finally cleanup.
• The compatibility runner retains only reviewed tokens, normalizes all other values to unexpected, and does not retain raw Chrome exception text, fixture titles, bookmark IDs, or bookmark URLs as diagnostic evidence.
• Doctoring records the current Chrome Extensions chrome.bookmarks primary reference in APA 7th form. This remains compatibility evidence only and is not an OriginWeave Agent bookmark grant.

Repaired live stack

Exact current lifecycle prerequisite PR #56 head is 22bf82924f9bd254caf3bfa1db1891868c18a765. Fresh exact compare #56 → this head reports ahead 6 / behind 0, with merge base exactly current #56. The child delta preserves bounded bookmark diagnostics and the current prerequisite while retaining only the intended diagnostic/doctoring changes.

GitHub base metadata has now been repaired successfully to the real lifecycle prerequisite branch test/mv3-bookmark-mutation; the earlier body claim that safe retargeting had not been accepted is obsolete. After the retarget, GitHub briefly reported mergeability as unknown/non-mergeable during recomputation, then bounded refetch returned this Draft mergeable without source churn.

Semantic integration order is now represented in both ancestry and PR metadata: #43 → #56 → #178 → #59. Current #59 has subsequently been reconciled onto this exact head and retargeted to this PR's branch; no predecessor check/review/approval transfers.

Keep this PR Draft while the prerequisite stack remains active.

Exact-current verification

On unchanged exact head 3083a8430f8971540f4ffe5d291955b6eb13b31f:

• CI run 31989368138: success;
• Manifest V3 Compatibility run 31989368104: success on pinned Chromium;
• GitHub reports the Draft mergeable after the bounded post-retarget refetch; and
• no current formal review or inline review thread is returned.

Feature-base organization security/review workflows that did not execute on this exact head remain absent evidence, not passing evidence. The requested reviewer remains the branch owner account; no independent approval is inferred from a request, author activity, bot output, or predecessor review.

Scope boundary

Do not interpret passing bookmark compatibility as Agent bookmark/history/filesystem authority, access to an ambient human profile, or a general bookmark tool. This scheduled actor does not merge, self-approve, alter workflows, add secrets, weaken checks, tag, or publish.

[seonghobae]

Conflict RCA: parent PR #56 advanced from the child base 7042b25e to 03f8e379, absorbing the bookmark mutation implementation and adding bounded WebDriver diagnostic vocabulary. Merged the current parent, retained its WebDriver allow-list, and preserved this PR’s stricter bookmark stage evidence, raw-value rejection, content-script/runner correlation, and primary-source doctoring. Exact new head: 640e594dbc0a64f251a0f28b8e80943f53337e40; semantic child delta is now 8 files (77 additions/13 deletions) versus the current parent because overlapping implementation moved into #56. Verification: 41 focused MV3 tests plus 128 subtests, rustfmt, workspace all-target/all-feature Clippy, full Rust tests, 199 Python tests plus 614 subtests, and fresh 100% functions/lines/regions/branches coverage are green.