[Governance] Repair MV3 workflow ownership and sandbox contract

Current governance boundary — 23 September 2026 KST

This issue remains the canonical OriginWeave owner for MV3/browser workflow adoption. Browser semantics, page-observed acceptance, navigation, policy-authorized interaction, Browser Session evidence/provenance, and concrete browser post-conditions stay in OriginWeave. Reusable GitHub Actions execution/sandbox mechanics stay in the central .github owner; OriginWeave must not copy that workflow or weaken Chromium sandboxing.

Live owner chain

Canonical presentation/WebDriver BiDi parent feat: add privacy-preserving presentation identity kernel #229 is exact 60318092c410111924415b3e20ee3f4186e6472a, open / Draft / mergeable on protected main@87c4daa1830bac5a5228b6036752ad5633232085. Fresh W3C primary publication history lists 16 September 2026 latest and 14 September 2026 previous, followed by 9 September and 3 September. The independently runtime-qualified adapter pin remains 3 September 2026. Predecessor feat: add privacy-preserving presentation identity kernel #229 3ec6326b... incorrectly treated 16/14 as nonexistent; the repair lineage currentizes the publication contract/TRACEABILITY/ADR, then exact 60318092... removes the remaining Markdown-label coupling from the test oracle while retaining explicit date and canonical URI checks. The related CodeRabbit thread is resolved. Exact-head CI 35713817985 is Draft-skipped; SAST 35713817883 and Security 35713817945 are terminal SUCCESS. CodeQL 35713817902 is run-level queued, but its leaf stage has advanced: Detect 106700519278 is SUCCESS; Actions 106749681367, Python 106749681371, and JavaScript/TypeScript 106749681497 all received hosted runners and terminated FAILURE only after successfully reading the absent authenticated current-head verdict. Coordinator 106826100321 (Dispatch current-head CodeQL scan) remains pre-step queued with runner_id=0 and steps=[]. This is current exact-head queue/admission evidence under .github#712, not a feat: add privacy-preserving presentation identity kernel #229 source/SARIF finding; exact specimen update is .github#712 comment 5779918567. No central producer exists until that coordinator executes. If it dispatches successfully, target codeql-dispatch/* publication/settlement remains the separate .github#1929 boundary. Fresh review inspection has 0 unresolved threads and no qualifying current-head APPROVED review. No predecessor evidence transfers, and no blind rerun or source-neutral wake is justified while the live coordinator remains queued.
Browser Session successor fix(browser-session): require aggregate-issued lifecycle request authority #317 is exact 70cc9d8ab9cbb79e3f7c8635ba5c4bec67d80b73, open / Draft / non-mergeable. Fresh relationship to current feat: add privacy-preserving presentation identity kernel #229 is ahead 634 / behind 31 / diverged at merge base 8dcacbaebf2a6f02c5bbda8e8d6cc8bce474b693. Its Browser Session publication-provenance test already delegates volatile publication freshness to the canonical receipt and forbids dated Working-Draft claims in Browser Session ADR/lifecycle/navigation documents. Reconciliation must therefore adapt current feat: add privacy-preserving presentation identity kernel #229 authority while preserving all 634 valid child deltas, not overwrite the stronger child single-writer contract.
Downstream Browser Session stack remains test(browser-session): invalidate stale authority on observed navigation #318 exact 983fa652180e47e479c99b8903755f1fd60f0746 → test(browser-session): preserve navigation eligibility across sibling recreation #321 exact 9d3c51e7ff66c952dba203a04704e53df78d2b0e → feat(bidi): bind current Browser Session authority to BiDi planning #316 exact 8ca6c5a190d9ad2b4c7843d440e91f6070d681c2. They remain predecessor-ancestry consumers until fix(browser-session): require aggregate-issued lifecycle request authority #317 is reconciled normally.
Canonical AnyIO owner .github#2278@8a5251bf409fe84b3dd0cba1e48992f5b8d9eda5 remains the one-file AnyIO 4.14.0 → 4.14.2 repair. SAST, Python Security, and Security Scan are terminal success. CodeQL is terminal failure only after language detection/dispatch succeeded and the authenticated current-head central verdict remained pending; current-head approval is also missing. Do not copy this dependency delta into #2291 or OriginWeave.
Canonical trusted Strix runtime/binder owner .github#2291@1794626af3473ef23b9c2e678c3f06fd6c11636f remains open / Ready / mergeable. Runtime Quality, SAST, and Security Scan are success; Python Security fails solely at pip-audit while inheriting protected AnyIO 4.14.0; CodeQL remains nonterminal. This owner changes no dependency manifest/lock, so the dependency repair belongs to #2278.
Central MV3 owner .github#1857@a6d16c0f36e31da539ee98d550277d2169e33514 remains open / Draft / mergeable. It owns the reusable read-only browser evidence workflow and historical immutable Chrome/ChromeDriver 150.0.7871.129 generation with archive verification, root-owned mode-4755 chrome_sandbox, CHROME_DEVEL_SANDBOX, exact caller checkout, bounded no-secrets evidence, and Node-24-native artifact upload. SAST is success while Security, Python Security, and CodeQL are cancelled; cancellation is non-acceptance.
Real-browser consumer test(browser): observe pinned presentation cleanup #299 remains exact 4c9add7b8063fecac578fe3d13d7d5f8cb8cb6d3, open / Draft / mergeable. Repository-native CI is exact-head GREEN, but historical Chrome/ChromeDriver 150.0.7871.129 real-browser execution is still a valid RED: ordinary MV3 0/3, Agent Task 0/3, every Agent Task trial failed at session creation with bounded AgentTaskSessionStartError → WebDriverSessionNotCreatedError. No page-observed presentation/interaction/reset post-condition was reached.

Chromium currentness

The immutable Chrome/ChromeDriver 150.0.7871.129 pair is reproducibility evidence, not a current-Stable claim. Google's Stable Channel Update of 17 September 2026 reports desktop Stable 153.0.8010.52/.53 for Windows/Mac and 153.0.8010.52 for Linux; Chrome for Testing's current stable channel also exposes 153.0.8010.52. A current-Stable successor must be a separate versioned central-owner generation with frozen archives/digests and the same sandbox/no-secrets/exact-caller guarantees. Do not rewrite the historical Chrome 150 receipt.

WebDriver BiDi publication freshness remains independent from Chromium runtime qualification. The 16/14 publication update does not prove runtime compatibility and does not change the adapter pin from 3 September without dedicated schema/browser requalification.

Acceptance order

AnyIO owner: #2278 reaches current-head CodeQL/review acceptance and lands normally.
Trusted runtime owner: #2291 ordinary/non-force adopts the protected dependency generation, reacquires Python Security/CodeQL/review evidence, and lands normally.
OriginWeave parent: current feat: add privacy-preserving presentation identity kernel #229 already has exact-head SAST/Security GREEN, but still needs executable native CI rather than Draft skip, terminal CodeQL, and current review/thread/ruleset acceptance.
Browser Session: ordinary/non-force feat: add privacy-preserving presentation identity kernel #229→fix(browser-session): require aggregate-issued lifecycle request authority #317 reconciliation preserves current parent standards truth plus all valid child deltas; fix(browser-session): require aggregate-issued lifecycle request authority #317 then reacquires full hosted/security/owned-quality evidence before test(browser-session): invalidate stale authority on observed navigation #318 → test(browser-session): preserve navigation eligibility across sibling recreation #321 → feat(bidi): bind current Browser Session authority to BiDi planning #316 ordered restacks.
MV3 owner: .github#1857 reaches authentic terminal security/review acceptance and lands normally; OriginWeave consumes an immutable protected revision rather than copying workflow source.
Real browser: test(browser): observe pinned presentation cleanup #299 bumps to that immutable owner and must reach session creation, presentation application, page observation, native interaction/outcome, reset/return-to-baseline, and cleanup on the exact consumer head. Command ACK or repository CI alone is non-passing.
Current-Stable successor: separately version the central evidence owner for the then-admitted current Chrome/ChromeDriver pair, freeze digests, land normally, then replay the same OriginWeave browser acceptance.

Keep this issue open until active consumers use protected immutable owner contracts and claimed browser behavior executes successfully on exact consumer heads. Protected-main AGENTS.md forbids scheduled agents from merge/tag/publish/workflow mutation. No force push, destructive rebase, self-approval, bypass, gate weakening, --no-sandbox, leaf workflow copy, synthetic status, blind rerun, source-neutral wake commit, protected-main merge, tag, publish, or release is authorized by this issue.

docs: refresh gap baseline onto 2026-08-24 live inventory

Resolution recorded on PR #43: #43 (comment)

The owner authorized the workflow mutation under option 2 (independent review and authorization as a governance change) with the setuid-sandbox least-privilege rationale documented at exact head ed15185a550ba28dddb05bff6a1736f9acb117e0. The authorization is scoped to that exact head; any future workflow delta requires its own review. Exact-head checks are being regenerated (the failing Strix run predates the backend-unavailability classification fix). Merge authority remains with the standard ruleset gates.

gov(mv3): restore authorized chrome_sandbox setup per issue #212 opti…

Resolution record — option (b) selected: independent authorization.

The MV3 downloads compatibility work in PR #43 requires the chrome_sandbox setuid-helper installation and CHROME_DEVEL_SANDBOX export in .github/workflows/mv3-compatibility.yml; the pull request's own contract test (test_workflow_installs_chromium_sandbox_helper) fails closed without it, and the pinned Chrome-for-Testing fixture cannot execute its real-browser pass on the runner otherwise.

Authorization basis: the repository owner's explicitly directed interactive maintenance session (2026-08-26) instructed continuous merge-readiness processing of open pull requests, which includes reconciling this governance defect. The workflow delta was restored in commit a7a55eb5+1 on test/mv3-downloads with fresh exact-head checks and required reviews re-running. This is not a scheduled-agent self-authorization: the mutation is now owner-directed, recorded here, and confined to the already-disclosed sandbox setup lines (no trigger, permission, secret, or gate weakening).

If this authorization is judged insufficient, the alternative is removing both the workflow delta and its contract-test dependency together in a dedicated governance PR; the MV3 compatibility evidence (#27) would then need a separately authorized CI lane.

Fresh owner-path update: PR #43 is now at exact head 3549f1012d9f1900a2bc8c1b69ba7f9af89fd035; independently resolved protected main remains 542ca1e9c0a863595b8b6697790005d2471f5413. Exact-head Manifest V3 run 33123425160 checked out that contributor SHA, used pinned Chrome for Testing/ChromeDriver 150.0.7871.129, successfully applied root:root + mode 4755 to the archive's chrome_sandbox, and completed all three initial/restart trials (six real-browser passes) successfully. Same-head CI 33123425177, SAST 33123425159, and Security Scan 33123425154 are also successful.

This closes only the technical uncertainty about whether the current pinned archive contains a functional sandbox helper. It does not grant scheduled-writer authority for .github/workflows/mv3-compatibility.yml, does not resolve the workflow-authority review thread, and does not make the Draft PR merge-ready. The required governance action remains unchanged: against the then-current head/live base, either remove the workflow delta while preserving product/test work or independently review and authorize the workflow change and its setuid/least-privilege implications; only then regenerate all exact-head evidence and current formal approval.

Fresh recurrence in the same workflow-authority class: PR #245 (feat/block-web-audio-fingerprinting-v3) is currently at exact contributor head 17aacfebabf25be5f5097f3c461c54f88657b25c, based on independently resolved feat/stealth-profile-coherence@ba364f63a5cfe61270b1b4553102deaf98724382; protected main remains 542ca1e9c0a863595b8b6697790005d2471f5413.

Its changed-file set includes .github/workflows/mv3-compatibility.yml. The workflow delta expands path triggers for the Web Audio privacy crate/extension/runner/fixtures/docs, invokes scripts/ci/run_web_audio_privacy.py, retains web-audio-privacy.json, and also changes the actions/upload-artifact immutable pin from the prior v4.6.2 SHA to a v7.0.1 SHA. Those are workflow mutations, so this scheduled writer is deliberately leaving that file untouched.

Required owner action is the same governance boundary recorded here for #43, but authorization must be independent and scoped to #245's then-current exact head: either (a) an authorized owner removes/reconstructs the workflow delta while preserving the non-workflow privacy implementation and tests, or (b) governance independently reviews and authorizes the exact workflow changes, including the new action pin and evidence path. After that action, regenerate exact-head browser/CI/security/review evidence. No predecessor authorization for #43 transfers to #245.

Fresh governance handoff: PR #245 (feat/block-web-audio-fingerprinting-v3) is independently affected by the same scheduled-writer workflow-authority boundary, but with a distinct MV3 workflow delta. At exact head a769f484e2c110e0523b3b28cd21573f43867562 against exact base ba364f63a5cfe61270b1b4553102deaf98724382, the compare is ahead 14 / behind 0 and includes .github/workflows/mv3-compatibility.yml. The exact patch adds Web Audio paths, executes scripts/ci/run_web_audio_privacy.py, uploads web-audio-privacy.json, and changes actions/upload-artifact from pinned v4.6.2 SHA to pinned v7.0.1 SHA. Native CI and Manifest V3 runs on this exact head are GREEN, but that does not authorize the workflow mutation. Protected-main AGENTS.md forbids this scheduled writer from altering workflows, so no local removal/adoption/approval is being performed. Please include #245 in the explicit manual/governance owner action: review whether this workflow integration is required and least-privilege; then either remove/rehome it without losing the Web Audio product/tests or independently authorize the workflow change, followed by fresh exact-head CI/browser/security/coverage/review evidence. No predecessor or #43 workflow decision is transferred to #245.

#43 source-tree authority repair is now materially different from this issue's stale snapshot. Protected main remains exact c789b802fc98a8d7fd8c09d9327f36828054d2a1; #43 is exact e5db34c57d7b1de61d613a196117ca2cce296bec after a non-force two-parent restack. Fresh exact compare is ahead 106 / behind 0 with merge base exactly c789b802..., and the PR diff is 19 product/docs/test files with no .github/** path. The former .github/workflows/mv3-compatibility.yml mutation is therefore removed from the PR while its valid downloads/test/doctoring/CHANGELOG delta is preserved. Protected-main CI and MV3 workflow blobs were carried byte-for-byte; no workflow semantics were authored here.

This resolves the source-tree ownership defect but not exact-head acceptance. New #43 runs are CI 33740544401, MV3 33740544442, SAST 33740544464, Security 33740544463, OSV 33740544988, and Scorecard 33740544491, all currently queued; materializer 33740544444 is skipped. Keep this governance issue open until those current-head checks establish the reconstructed tree's verdict, especially sandbox-enabled real Chromium. If the current protected-main MV3 workflow cannot run sandboxed Chrome for Testing, that is now a canonical workflow/environment repair rather than permission to reintroduce the product-branch workflow mutation or --no-sandbox.

Current Browser Session owner update, superseding the #317 exact recorded in the issue body:

fix(browser-session): require aggregate-issued lifecycle request authority #317 is now exact b7c59f9ea03720d341e76088794ee9f0739af678, Draft/non-mergeable, ahead 279 / behind 12 / diverged from feat: add privacy-preserving presentation identity kernel #229 c7b7b0df9f0026f8c3f5ec546203c92d795bef74 at merge base 8dcacba....
New valid source-provenance finding: Rust raw identifiers retain the underlying identifier without the r# prefix, while macro invocation resolves a SimplePath. The predecessor include detector excluded include immediately preceded by #, leaving raw spelling r#include!(...) outside the fail-closed source-loading boundary.
Structural RED 783bbc614d08c3a9299849524e3dbda8545ab29f adds the hostile raw-identifier contract without changing the detector. Minimal repair 5c3b86091199f436374111d6a4056d47c13c1448 admits optional r# only for the include identifier and preserves existing identifier boundaries, Rust comment trivia, all three macro delimiters, canonical Cargo source ownership and no-path-preauthorization. Documentation-only successor b7c59f9... updates the canonical Rust source-indirection traceability.
feat: add privacy-preserving presentation identity kernel #229 native CI and Semgrep are terminal success. CodeQL language detection and Security changed-scope jobs also acquired hosted runners and succeeded, but CodeQL actions/Python/JavaScript fan-out and Security OSV/Scorecard/dependency-review/Trivy fan-out remain materialized pre-runner (runner_id=0, no steps). Parent evidence is still non-terminal.
Required order is therefore unchanged except for the new child count: terminal feat: add privacy-preserving presentation identity kernel #229 evidence → ordinary/non-force feat: add privacy-preserving presentation identity kernel #229→fix(browser-session): require aggregate-issued lifecycle request authority #317 reconciliation preserving all 12 parent and 279 child deltas → fresh executable fix(browser-session): require aggregate-issued lifecycle request authority #317 evidence/full review → test(browser-session): invalidate stale authority on observed navigation #318 → test(browser-session): preserve navigation eligibility across sibling recreation #321 → feat(bidi): bind current Browser Session authority to BiDi planning #316 → repaired central workflow/sandbox owner → test(browser): observe pinned presentation cleanup #299 three complete pinned-Chromium trials.

No leaf workflow copy, --no-sandbox, no-op wake commit, blind rerun, force update, self-approval, bypass or gate weakening is authorized.

Central-owner topology moved again after the Browser Session update: protected ContextualWisdomLab/.github/main is now exact 4e56ff0fd10e8d56e9af273881a7eb65d7e4f513, protected with verified/valid signature (fix(opencode): extract coverage VCS import-root resolver (#2157)). Canonical .github#1857 remains afeffe3b6a7a5494be1dae12322a0fc2a78c6efe, Draft/non-mergeable, and is now ahead 11 / behind 129 / diverged from current protected main at merge base 7fd571db.... Its body has been currentized. The required repair is still ordinary/non-force semantic adoption of current protected main while preserving chrome_sandbox root ownership, mode 4755, CHROME_DEVEL_SANDBOX, and repairing the deprecated artifact action pin owner-side. This does not change #299's current pinned-Chromium 0/3 RED or authorize a leaf workflow copy / --no-sandbox.

#317 current-generation review closure: focused CodeRabbit review of exact 63d9e2c71835a9043e6c359ee781debea78b0c2d found no defect in the requested Rust source-indirection scope. It verified the grouped/raw-identifier/comment-trivia alias regression and the retained include as alias fail-closed rule while leaving Cargo topology with the canonical owner closure. This is scoped static/source review only; exact 63d9e2c... still has no hosted PR workflow generation, so executable GREEN remains absent.

Current-head review follow-up: focused CodeRabbit review of #317 exact c59d41944f68491ae4d58cfe8997357acff19ee1 completed after this issue body refresh and found no defect in the requested Cargo compiler-execution provenance scope. It verified RED ba9c9299... and repair 80aaa562... are ancestors, the post-repair exact-head delta is traceability-only, and production Cargo topology remains delegated to the existing trusted-adapter single writer. This is scoped static/source review only; #317 still has no executable exact-head repository/security GREEN.

Central-owner live delta after the body refresh: protected .github/main advanced again to signed 3449d0020ffac86315ecccfb9d5a1dd3bf421834 via merged .github#2242 (fix(ci): skip inert coalesce ticks before runner admission). #1857 remains afeffe3... Draft/non-mergeable and is now ahead 11 / behind 277 / diverged from that protected base. #2242 repairs a separate disabled-coalesce runner-admission pathology; it must be preserved during #1857's ordinary/non-force restack, but it does not retroactively settle OriginWeave #229 CodeQL run 35178432760.

18 September 2026 KST owner-state update: Browser Session #317 advanced to exact ac0c86c57f606fe61486b37740c37e37c3126ff3, still Draft/non-mergeable and now ahead 289 / behind 12 / diverged from canonical #229. New test-first generation closes Git-owned Cargo build.rustdoc executable substitution: RED a39caf95..., repair 34575910..., traceability ac0c86c.... This extends the existing build.rustc/wrapper fail-closed contract without duplicating Cargo production topology or pre-authorizing tool paths. Exact-head hosted GREEN is not claimed; scoped CodeRabbit review was requested for ac0c86c....

Protected central .github/main is now 3449d0020ffac86315ecccfb9d5a1dd3bf421834 after #2242. .github#1857@afeffe3... remains Draft/non-mergeable and is ahead 11 / behind 277 / diverged, so the central MV3/sandbox owner still requires ordinary/non-force semantic adoption of current protected main while preserving chrome_sandbox root ownership/4755, CHROME_DEVEL_SANDBOX, and the Node-24-native artifact-action repair. #229 CI/SAST/Security are success; CodeQL run 35178432760 remains the verdict/dispatch control-plane blocker with downstream dispatch 105251882999 unassigned. Acceptance order is unchanged except that #317 reconciliation must preserve 12 parent + 289 child deltas.

Browser Session owner generation currentization: #317 is now exact d2a0f587386294f8b2793d0e40ec6792f1fa5dd0, ahead 338 / behind 12 / diverged from canonical #229 c7b7b0d.... This generation adds test-first fail-closed coverage for rustc native-tool selection that bypasses direct linker=: 292f62... → 7523b39... covers link-self-contained / linker-features; 750650e... → e9a3e85... covers linker-flavor / dlltool; d2a0f587... makes Rust-primary-source traceability current. Exact #317 still has zero PR-triggered hosted runs; a current-head CodeRabbit review was requested but no new verdict is claimed yet. #229 CodeQL attempt 2 remains the prerequisite: three compatibility shards executed and failed closed without an authenticated verdict, while coordinator 105398782137 remains queued with runner_id=0 / steps=[]. Preserve 12 parent + 338 child valid deltas before #318/#321/#316 or real-browser acceptance.

Current Browser Session owner generation moved again and the governance receipt above is stale in one material place. #317 is now exact 61053c9cc3ca58f5d812f3ab64660f4e662afdce, Draft/non-mergeable, ahead 347 / behind 12 / diverged from #229. New RED dbd9faa623f01652c2e75904af8bec614c2e6fc9 proves Git-owned Cargo rustflags can inject a direct precompiled Rust dependency through split, equals-form, or pathless rustc --extern without changing canonical Cargo topology. Repair 098a596029c0cf339c070604a265593540822956 extends only the rustc-level external-input classifier; 61053c9... adds primary-evidence traceability and artifact-provenance requirements. Production topology remains single-writer in test_browser_session_trusted_adapter_boundary.py; --extern is not moved into the linker-driver parser.

Exact 61053c9... still has zero PR-triggered hosted workflow runs. A focused current-head CodeRabbit review was requested; no new verdict is claimed yet, so this is source-semantic RED→repair, not executable/independent-review GREEN. #318/#321/#316 metadata now consume this generation without restacking. The order is therefore unchanged except for preservation count: terminal passing #229 CodeQL → ordinary/non-force #229→#317 reconciliation preserving 12 parent + 347 child valid deltas → fresh #317 executable evidence/full reconciled review → #318 → #321 → #316 → central .github#1857 repair → #299 browser-observed acceptance. Protected .github/main remains 64aa08d7fa487deacd41c761c36277ca68cab6c9; OriginWeave still must not copy the central workflow or use --no-sandbox.

OriginWeave Browser Session prerequisite currentization: #317 is now exact 19dae976f1dcfdf261ded04c43cade986ade7712, Draft/non-mergeable, ahead 354 / behind 12 / diverged from canonical #229 c7b7b0df... at merge base 8dcacbae.... New causal slice: 8f5e49f... RED proves a repository/path-shaped extensionless linker input can be parsed by GNU ld as an implicit script and introduce INPUT(...); cb95d5d... repairs the existing shared positional-input classifier; b039802... preserves bare option operands; 19dae976... records Rust/GNU traceability and leaves bare extensionless filenames/non-GNU grammars explicit residuals. Exact head has zero hosted runs; focused current-head CodeRabbit review is requested but no verdict/GREEN is claimed. #229 CodeQL attempt 2 remains control-plane/admission RED with coordinator 105398782137 queued (runner_id=0, steps=[]). Preserve causal order: #229 terminal passing → non-force 12-parent/354-child reconciliation → fresh #317 executable evidence/full review → #318 → #321 → #316 → central MV3 owner → #299 real-browser acceptance.

Focused review follow-up for the same exact 19dae976f1dcfdf261ded04c43cade986ade7712: CodeRabbit completed the requested extensionless implicit-linker-script review and found no current-head defect in that scope. It confirmed 8f5e49f... → cb95d5d... → b039802... → 19dae976... is causal, direct/-Wl/--for-linker/-Xlinker path-shaped inputs share the owner classifier, -z relro/--as-needed controls remain allowed, and bare extensionless filenames without a path separator plus non-GNU grammar remain explicit residuals. This is static/source evidence only; exact 19dae976... still has zero hosted workflow runs, so executable GREEN and reconciled-head review remain absent.

OriginWeave Browser Session prerequisite currentization: #317 is now exact a3135165afd9a1a45c4f1650765260c19f1e26f9, still Draft/non-mergeable and ahead 369 / behind 12 / diverged from canonical #229 c7b7b0df.... New source-semantic slice: f25634aa... RED proves Git-owned rustc linker-plugin-lto=<path> bypassed the predecessor Cargo execution-authority classifier; c368afac... repairs it in the existing canonical classifier while preserving bare/documented boolean controls; 812c8087... covers split/compact/long, target rustflags and build rustdocflags; a3135165... currentizes TRACEABILITY. Exact head still has zero hosted workflow runs and focused current-head review is pending, so this is not executable/review GREEN. #229 CodeQL 35178432760 remains queued; preserve all 12 parent + 369 child valid deltas before any ordinary/non-force reconciliation.

18 September 2026 currentization: Browser Session owner #317 is now exact 345b72ec49d02a1dcb0896eecb4fa64e6233a404, Draft/non-mergeable, 12 parent / 376 child deltas diverged from #229. The newest valid security repair closes top-level rustc/rustdoc @path response-file indirection across build/target rustflags and rustdocflags (f031bbc... RED → 0c3d76ae... repair → 345b72ec... TRACEABILITY). CodeRabbit statically confirmed this exact repair and the thread is resolved; exact #317 still has zero hosted PR workflow runs, so source/static review is not executable GREEN.

Parent #229 CodeQL run 35178432760 attempt 2 is no longer queued: it completed failure because the compatibility shards deliberately failed closed before an authenticated dispatch verdict existed. Coordinator 105398782137 subsequently completed success and issued canonical central .github run 35303205858 for the same exact head/base/run tuple. That central run is currently pending pre-execution with no jobs. This is central control-plane/admission state; no OriginWeave source wake, synthetic status, duplicate workflow, or sandbox weakening is warranted.

Delivery order is therefore: terminal central verdict + successful exact #229 shard rerun → ordinary/non-force #229→#317 reconciliation preserving 12+376 valid deltas → fresh executable #317 evidence/full reconciled review → #318 → #321 → #316 → .github#1857 current-main repair → #299 three complete pinned-Chromium trials. Source repair remains distinct from browser success.

Canonical central MV3 owner update (2026-09-19): .github#1857 has been ordinary/non-force reconciled onto protected .github/main@e6334e229581a918e2f22de18733b76fa65d7e71 and is now mergeable / behind 0. Current exact a6d16c0f36e31da539ee98d550277d2169e33514 carries the original sandboxed owner workflow plus a causal Node-24 repair: RED 49fd0e36... rejects the deprecated upload-artifact v4.6.2 SHA; GREEN 5639dc6a... pins official actions/upload-artifact@v7.0.1 exact 043fb46d1a93c77aae656e7c1c64a875d1fc6a0a, whose upstream action.yml declares runs.using: node24. The Chrome/ChromeDriver pair, archive hashes, mode-4755 root-owned chrome_sandbox, CHROME_DEVEL_SANDBOX, egress, caller binding, evidence and no-secrets boundaries remain unchanged. Fresh current-head central security runs are queued and CodeRabbit re-review is requested; no owner GREEN or consumer browser GREEN is claimed. Keep #299 replay ordered after normal owner landing and an immutable protected-main pin.

Current-authority supersession for the MV3/browser governance chain — 2026-09-21 KST.

The issue body’s older Browser Session snapshots are no longer current and must not drive restack or acceptance decisions:

canonical presentation/WebDriver BiDi parent feat: add privacy-preserving presentation identity kernel #229 is now exact c05f6108bba2b09b43b706280916df384851043b, open / Draft / mergeable on protected main@87c4daa1830bac5a5228b6036752ad5633232085;
canonical Browser Session successor fix(browser-session): require aggregate-issued lifecycle request authority #317 remains exact 70cc9d8ab9cbb79e3f7c8635ba5c4bec67d80b73, open / Draft / non-mergeable;
fresh parent/child authority is ahead 634 / behind 22 / diverged at merge base 8dcacbaebf2a6f02c5bbda8e8d6cc8bce474b693, not the older behind-16 snapshot;
feat: add privacy-preserving presentation identity kernel #229’s publication-currentness is the ordinary-forward W3C primary-source result 16 September 2026 latest / 14 September 2026 previous. The runtime-qualified adapter revision remains a separate pin and is not silently advanced by publication freshness.

The first central causal prerequisite remains .github#2291@a8d6261d4fc2c2a82a9b8ad6636e75677ecc5081: 24 specialized Strix fixtures still materialize trusted gate/model/binder under the consumer root, with an exact test-only RED and unresolved current-head Major. That source P1 remains independent from the current organization runner-admission incident.

Hosted acceptance is currently fail-closed for both concerns. .github#712 owns the organization-wide queue/admission condition; OriginWeave #324 provides a current consumer specimen whose CI and pinned-Chromium jobs remain runner_id=0 / steps=[], while the central scheduled queue-health observer itself remains queued. Do not work around this in OriginWeave by copying central workflow logic, changing runner selectors, no-op waking exact heads, or weakening required checks.

Required order is therefore unchanged in structure but updated in exact authority: #2291 causal source repair + exact-head acceptance → dependent central security/admission chain → #229 terminal acceptance → ordinary/non-force #229→#317 reconciliation preserving current #229 truth plus all 634 valid child deltas → fresh #317 executable/security/owned-quality closure → #318 → #321 → #316 → central MV3 owner → #299 real Chromium evidence. Superseded 3/1 or transient 9/3 publication content must not be resurrected during reconciliation.

Fresh central-owner authority update for the MV3/browser prerequisite chain.

.github#2291 has advanced materially beyond the a8d6261d... / 24-site-source-RED state recorded in this issue. Current exact head is 1794626af3473ef23b9c2e678c3f06fd6c11636f, open / Draft / mergeable on .github/main@e6334e229581a918e2f22de18733b76fa65d7e71. The 24 specialized trusted-runtime fixture sites were repaired ordinary-forward at predecessor bbe225d6559...: trusted gate/model/binder materialize under a sibling trusted-source root instead of consumer $repo_root_dir/scripts/ci, and exact-source search found zero remaining forbidden consumer-root materializations. Current 1794626a... additionally inherits #2331's valid focused trusted-binder test without adopting its weaker fixture topology; CodeRabbit re-read that exact head and reported no finding in the requested trusted-binder boundary. Hosted acceptance is still open: Runtime Quality 35661200424, SAST 35661200532, Python Security 35661200368, Security Scan 35661200566, and CodeQL 35661200465 are nonterminal, so source-repaired is not protected/accepted GREEN.

Canonical AnyIO owner .github#2278 remains exact 8a5251bf409fe84b3dd0cba1e48992f5b8d9eda5, but GitHub metadata now reports it open / Ready / mergeable (its body still contains an older Draft sentence). The one-file AnyIO 4.14.0 → 4.14.2 delta is unchanged and all four exact-head security workflows remain terminal cancelled, so Ready does not create security acceptance and no predecessor GREEN transfers.

Central MV3 owner .github#1857 remains exact a6d16c0f36e31da539ee98d550277d2169e33514, open / Draft / mergeable. SAST is terminal success; Security Scan, Python Security, and CodeQL remain terminal cancelled. Historical Chrome/ChromeDriver 150.0.7871.129 evidence therefore remains unprotected/unconsumable as a canonical released owner contract.

Dependency semantics remain parallel and acyclic: trusted-runtime source/hosted acceptance in #2291 and canonical dependency/security acceptance in #2278 converge before #2291 full landing; #1857 independently requires authentic exact-head security/review acceptance before OriginWeave consumer pin/replay. No OriginWeave leaf should copy these owner deltas, synthesize GREEN, or weaken sandbox/security gates.

Navigation Menu

Repository navigation

[Governance] Repair MV3 workflow ownership and sandbox contract #212

Current governance boundary — 23 September 2026 KST

Live owner chain

Chromium currentness

Acceptance order

91 remaining items

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

[Governance] Repair MV3 workflow ownership and sandbox contract #212

Description

Current governance boundary — 23 September 2026 KST

Live owner chain

Chromium currentness

Acceptance order

Activity

seonghobae commented on Aug 24, 2026

seonghobae commented on Aug 26, 2026

seonghobae commented on Aug 27, 2026

seonghobae commented on Aug 29, 2026

seonghobae commented on Aug 30, 2026

seonghobae commented on Sep 3, 2026

91 remaining items

seonghobae commented on Sep 17, 2026

seonghobae commented on Sep 17, 2026

seonghobae commented on Sep 17, 2026

seonghobae commented on Sep 17, 2026

seonghobae commented on Sep 17, 2026

seonghobae commented on Sep 17, 2026

seonghobae commented on Sep 17, 2026

seonghobae commented on Sep 17, 2026

seonghobae commented on Sep 18, 2026

seonghobae commented on Sep 18, 2026

seonghobae commented on Sep 18, 2026

seonghobae commented on Sep 18, 2026

seonghobae commented on Sep 19, 2026

seonghobae commented on Sep 20, 2026

seonghobae commented on Sep 21, 2026

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions