Repository navigation
feat(browser): bind presentation identity to versioned Chromium emulation evidence #292
Description
Activity
Writer lease ACQUIRED — bounded #292 slice only. Exact prerequisite is #229
024f63690cf05cfe6f0d4a430f0e18ea8fd2c4d6; protectedmainis87c4daa1830bac5a5228b6036752ad5633232085. Scope: introduce the smallest test-first, version-pinned WebDriver BiDi presentation-emulation capability boundary without changingoriginweave-fingerprint, workflows, rulesets, secrets, or browser/policy authority. First acceptance is fail-closed: the 2026-08-18 WebDriver BiDi capability set must not produce a complete presentation witness because requiredHardwareConcurrency(and the full Chromium platform/UA-CH surface) is not standard-BiDi authority. No production repair will be added until the exact test-only regression is observed RED.Fresh authoritative re-check on 2026-09-07 supersedes the earlier correction in this comment. The canonical W3C latest-published WebDriver BiDi URL now resolves to the 3 September 2026 Working Draft (
https://www.w3.org/TR/2026/WD-webdriver-bidi-20260903/), and that document lists 1 September 2026 as its previous version. The 18 August publication listing I previously relied on was stale relative to the canonical latest-published document. #292/#293 must therefore either update their current-standard traceability to 3 Sep or explicitly declare 18 Aug as a compatibility pin and record the delta; do not call 18 Aug the latest published revision.The capability/provenance finding remains valid against the 3 Sep draft.
emulation.setScreenSettingsOverridestill exposes onlyscreenArea { width, height }, while #229's canonicalPresentationSurface::Screenincludes color depth. Standard BiDi therefore cannot certify the wholeScreensurface without a version-pinned Chromium remainder and page-observedscreen.colorDepth/screen.pixelDepthevidence.emulation.setLocaleOverridestill accepts one locale, so orderednavigator.languagesparity remains unproven without pinned-browser post-condition evidence.Fresh #293 exact-head evidence is now also actionable:
0b0797c66f81f13fe72b709e2c1df0b6ec0026e8, CI34095314936. Production coverage101657573334passed, but Rust contracts101657573294failed after exact checkout in the Python repository contract because rootCargo.tomlincludes the new reusablecrates/originweave-bidimember andtests/test_repository_contract.pystill omits it. Rust fmt/tests/Clippy/rustdoc were skipped after that failure. #293 has been returned to Draft. Under this existing #292 writer lease, repair order should be: preserve the hosted RED; update the repository workspace contract; add/adjust a test that prevents wholeScreen/Languagescanonical-surface certification without their complete semantics; then make the smallest production capability-map/traceability change and regenerate exact-head evidence. Do not create a competing source writer.Writer lease RELEASED — lease arbitration repair. Fresh timestamp comparison shows repository-wide sole source/docs lease #255 comment
5565646422was acquired at2026-09-07T05:45:14Z, before this bounded #292 lease5566459889at2026-09-07T07:06:41Z. The later bounded lease therefore must not coexist as source authority.Before that ordering defect was detected, two ordinary non-force commits were already published on the separate #293 branch:
ba584c7f73becb03ca29ba79b8b705cf23e47050registers the already-presentoriginweave-bidiworkspace member in the repository contract, and test-only9f11b0c8268890b0620c94b6975d461f67511afaencodes the 3 Sep 2026 BiDi revision plus fail-closed complete-surface expectations. Preserve those deltas; do not force-rewrite, close, or pretend they were unmade. Exact CI34114834059for9f11b0c8...skipped both jobs while Draft, so the new semantic assertions are not an observed RED and no production capability-map repair is authorized yet.No further #292/#293 repository source or docs mutation will occur under this released lease. After the older #255 sole writer publishes and releases, the next writer must read the intervening #293 deltas, verify path overlap/non-overlap, observe the new RED through a policy-compliant execution path, then continue the minimal repair. Issue/PR state remains Draft/open; this is coordination repair, not closure or supersession.
Standards/cleanup refinement for the eventual real-Chromium GREEN: the 3 September 2026 WebDriver BiDi WD explicitly states that the remote end's device-pixel-ratio override map is not cleared when the final WebDriver session ends; DPR overrides can therefore outlive a session. The same spec exposes
browsingContext.setViewportwithdevicePixelRatio: null, whose algorithm removes the override for the affected navigable(s). See §7.3.1/§7.3.3.12: https://www.w3.org/TR/webdriver-bidi/#browsing-context and https://www.w3.org/TR/webdriver-bidi/#command-browsingContext-setViewport.This makes the generic cleanup acceptance in this issue materially stronger: do not treat
session.end, context destruction, or transport teardown as proof that presentation state has been removed. The realistic browser lifecycle test should apply a deliberately non-default DPR, prove the page-observed value, end/replace the WebDriver session as the product actually does, then prove either (a) OriginWeave explicitly resets the DPR override tonullon every still-addressable owned navigable before releasing the browser/user-context, or (b) the entire owned browser/profile boundary is destroyed and a fresh boundary cannot observe the prior DPR. A reset ACK alone is insufficient; observe the post-reset/fresh-boundary value. Crash/timeout on this cleanup path remains non-passing and must not release a reusable browser boundary as clean.This is not a request to widen PR #293's current test-only capability-map slice or to move lifecycle authority into the BiDi adapter. It is a #292 application/recovery invariant that should be carried into the typed browser-session owner and realistic E2E once the current sole repository writer releases.
Standards/provenance correction after fresh W3C publication-index and exact upstream-history verification. The current W3C Standards/Drafts index and Browser Testing and Tools WG publications page both list WebDriver BiDi Working Draft — 18 August 2026 as the latest published Working Draft. The existing issue text/comment that calls 3 September 2026 the canonical latest-published Working Draft is therefore stale; 3 September material must not be represented under a published-WD provenance contract unless W3C actually publishes such a snapshot.
For #293/#292, keep the specification identity immutable and explicit rather than making a release adapter “track current”. If the owner contract is the published Working Draft, pin the dated W3C publication identity for 18 August 2026 and, for doctoring/reproducibility, record the exact upstream source commit/digest used to derive capabilities. This matters because upstream
w3c/webdriver-bidichanged the media-feature CDDL on 18 August itself at signed commit1e5e36c43adbe24f2a4052c2ec091635c006c352(list media features (#1149)): that snapshot explicitly includesprefers-reduced-motion. A bare date alone is weaker provenance than the immutable document/source identity.The coarse-surface findings remain version-coherent against that exact 18-August source:
emulation.ScreenAreais only{ width, height }, so standard BiDi alone cannot certify #229PresentationSurface::Screenif the canonical surface also requires color depth;emulation.setLocaleOverrideaccepts one locale string/null, so it cannot by itself certify an ordered language-preference vector.ReducedMotion, however, is represented by the 18-August media-feature work and should not be removed on the basis of the earlier stale/TR/rendering.Repair order when the active repository-wide source lease is released: first correct the test/body provenance without manufacturing a 3-September published-WD RED; then derive complete-surface assertions from the immutable 18-August snapshot; only after a policy-compliant RED is observed should production capability code change. Real pinned-Chromium application and page-observed post-condition evidence remain the buyer-visible #292 acceptance boundary. This comment corrects standards evidence only; it does not reacquire the released #292 writer lease or authorize competing source/docs mutation.
Standards/provenance refresh from active adapter slice #293: exact #293 head is now
f0a3b66a4ff3034d8a4e23e9b75ca2679fd0d3de. W3C's current publications index and WebDriver BiDi cover page identify 18 August 2026 as the latest published Working Draft, not 3 September. The false September assertion has been removed from #293; the adapter now retains2026-08-18as publication identity and records immutable upstreamw3c/webdriver-bidi@1e5e36c43adbe24f2a4052c2ec091635c006c352only as the same-day source snapshot used for media-feature doctoring, includingprefers-reduced-motion.The actual capability RED remains intentionally unfixed: current production still includes complete canonical
ScreenandLanguages, while the test-first contract requires them absent because standard BiDi exposes only screen width/height and one locale rather than #229's complete color-depth/ordered-language invariants. Exact CI34166151155onf0a3b66...was skipped under Draft gating, so this is not an observed behavioral RED or GREEN and the production capability map must not advance yet. The issue body's September date is stale; use this correction and #293 current body/head as the current provenance checkpoint until the owner text is reconstructed safely.Owner-path correction after a fresh canonical W3C re-read: issue #292’s body is correct and the later comment
5574070364is not. As of 2026-09-08,https://www.w3.org/TR/webdriver-bidi/identifies WebDriver BiDi Working Draft, 3 September 2026 as the latest published version, and W3C’s publication-history page lists 3 Sep → 1 Sep → 25 Aug → 24 Aug → 18 Aug. The 18-August-only conclusion came from stale/incomplete publication-index evidence and must not drive the adapter provenance.This does not change the substantive bounded-context decision already recorded here. In the dated 3 Sep WD,
emulation.ScreenArearemains width/height only;emulation.setLocaleOverrideremains a single locale; andemulation.setMediaFeaturesOverrideincludesprefers-reduced-motion. Therefore completeScreenand orderedLanguagesremain partial/unsupported standard-BiDi surfaces, whileReducedMotionremains represented by the standard command set. The DPR cleanup invariant in comment5572561945also remains valid.Current active #293 head
f0a3b66a4ff3034d8a4e23e9b75ca2679fd0d3deregressed the publication constant/test/body to2026-08-18after the stale standards review; exact CI34166151155is terminal skipped, so that head has neither a provenance RED nor semantic GREEN. I have recorded the exact-head correction in review5135689378. When the repository-wide source lease releases, preserve the intervening #293 history but restore the 3-Sep published-WD provenance first, keep the complete-surface RED (Screen/Languagesabsent,ReducedMotionpresent), observe it through a policy-compliant execution path, then make the minimal capability-map repair. Do not infer a 3-Sep upstream source SHA solely from commit date; the dated W3C TR itself is already immutable publication identity, and any auxiliary source-commit pin must be separately verified.Current dependency evidence refresh (2026-09-08): PR #293 exact published head is
0c077445d73640a6299ea4d379faa4b0ab0226c2(the body still references9f11b0c…). #293 remains Draft; its central Rust/coverage checks are skipped while Draft, and live browser visual evidence is still unproven because the Edge diff tab rendered the older 2026-08-18 revision. The documented 3 September 2026 WebDriver BiDi boundary and explicit cleanup planner are present in the current PR, but complete Chromium page-observation acceptance remains open.Fresh owner-path correction, 2026-09-08: the issue body’s “3 September 2026 Working Draft” publication identity is stale/incorrect. Current W3C authoritative publication surfaces agree that the latest published WebDriver BiDi Working Draft is 18 August 2026: the W3C Standards/Drafts index, the WebDriver BiDi series cover page, and the Browser Testing and Tools WG publications page all show 18 August. The 3 September document is the Editor’s Draft at
w3c.github.io/webdriver-bidi/, which itself points tohttps://www.w3.org/TR/webdriver-bidi/as the latest published version. The purported immutable dated TRhttps://www.w3.org/TR/2026/WD-webdriver-bidi-20260903/is not supported by the current W3C publication inventory.This changes provenance only, not the semantic capability conclusion: standard BiDi still does not prove OriginWeave’s complete
Screen(dimensions + color depth) or orderedLanguages, while Viewport, DPR, TimeZone and ReducedMotion remain the four complete admitted surfaces in #293. Exact #293 head0c077445d73640a6299ea4d379faa4b0ab0226c2currently pins the incorrect 3-Sep publication identity; formal COMMENT review5138567735records the minimal test-first repair. Its native CI34195977205is terminal skipped, so keep #293 Draft and do not transfer local predecessor GREEN.Fresh #293 checkpoint: exact head
212a0ae2910cf62ba144db7cc0ff503e73d2f1ccnow contains the test-first documentation contract for the already-known staleARCHITECTURE.md/CHANGELOG.md/docs/doctoring.mdreferences. The contract is deliberately RED against the current branch text: those documents must stop claiming 18 August as the published WD, cite the immutable 3 September dated TR, and describe timezone/media cleanup as well as viewport/DPR. Draft CI skips native execution, so no hosted RED/GREEN is claimed yet.A separate cleanup-ownership finding is now recorded in #293 review
5139941850: W3Cfeatures: nullunsets the target media-feature override configuration; it is not a selective inverse of only OriginWeave'sprefers-reduced-motionwrite. Before #292 can claim reuse-safe cleanup, pinned Chromium must prove either an explicitly exclusive owned context/profile boundary (destroyed when restoration is not representable) or bounded snapshot/restore of prior media configuration. Seed an unrelated prior media override in the exact target and verify it survives/restores; ACK alone is not acceptance.Current #293 checkpoint after review
5139941850: exact head isef82e401030a67db52de34d9dc0ad9a42f059564on #229024f63690cf05cfe6f0d4a430f0e18ea8fd2c4d6, still Draft. The cleanup-authority defect is now narrowed at the adapter API boundary: genericplan_standard_presentation_cleanupplans only viewport/DPR and timezone reset;ResetMediaFeaturesis reachable only through explicit caller-suppliedExclusivePresentationContextandplan_exclusive_presentation_media_cleanup. This prevents a reusable-context cleanup path from silently treatingfeatures: nullas a selective inverse forprefers-reduced-motion.This is not Browser Session ownership evidence.
ExclusivePresentationContextis an attestation input; the adapter does not discover or mint exclusivity. The real pinned-Chromium acceptance remains: establish an actually exclusive disposable context/profile or restore complete pre-existing media state, apply reduced-motion, cleanup, then observe the relevant post-condition or destroy the owned boundary. ACK alone remains non-passing.Exact native CI
34213770429foref82e401...completed skipped while Draft, so no hosted Rust/Python/Clippy/rustdoc/100%-coverage GREEN is claimed. The pre-existing documentation RED also remains:ARCHITECTURE.md,CHANGELOG.md, anddocs/doctoring.mdstill need the 3 September 2026 published-WD and cleanup-authority wording repaired before #293 is documentation-complete.#293 documentation checkpoint superseding the stale body subsection: exact head is now
ef2630566fdfd3c044075316a971cdade82e740fon #229024f63690cf05cfe6f0d4a430f0e18ea8fd2c4d6, still Draft. The test-first documentation RED is repaired in source:e71a4997...alignsARCHITECTURE.md,c63339bb...alignsCHANGELOG.md, andef263056...alignsdocs/doctoring.mdwith the 3 September 2026 W3C Working Draft (https://www.w3.org/TR/2026/WD-webdriver-bidi-20260903/) and the reusable-versus-exclusive cleanup boundary. Exact file reads now satisfy the repository contract’s dated-URI/timezone/media/cleanup requirements.This does not advance browser-runtime acceptance. Current exact CI
34219091919completedskippedwhile Draft, so there is no exact-head hosted Rust/Python/Clippy/rustdoc/100%-coverage GREEN. The next buyer-visible RED remains real pinned Chromium: seed an unrelated pre-existing media override in the exact reusable target, apply OriginWeave reduced-motion, observe the intended presentation, run generic cleanup, and prove the unrelated state survives/restores. The alternative path must establish an actually exclusive disposable context/profile and prove destruction/cleanup at the Browser Session boundary.ExclusivePresentationContextalone is caller attestation, not ownership evidence; command ACK remains non-passing.PR-state-only lease ACTIVE — no source/docs/ref mutation. Scope is only to replace the stale
Dependency / delivery boundaryin the issue body with current #293 exactef2630566fdfd3c044075316a971cdade82e740f, repaired documentation state, skipped exact CI34219091919, and the unchanged real pinned-Chromium acceptance. Preserve all browser-domain invariants, standards references, #229 prerequisite, #212 ownership boundary, open state, and no merge/release claim.73 remaining items
Current #317 review disposition superseding the body's earlier “review requested” sentence: focused CodeRabbit review
5714094644completed on exact2d6e4936eb54a03a09456fdb89b5c3dc926651a7. Its sole P1 claimed the path/comment-trivia hostile regressions were absent, but exact-head verification showstests/test_browser_session_rust_path_comment_trivia_contract.pyretains all four documented cases and each invokes the canonical source-indirection fail-closed contract. The finding is invalid; no duplicate tests were added. This remains scoped static/source evidence, not executable #317 GREEN.Buyer-acceptance foundation update, superseding the #317 exact recorded in the issue body:
- Browser Session fix(browser-session): require aggregate-issued lifecycle request authority #317 is now exact
b7c59f9ea03720d341e76088794ee9f0739af678, Draft/non-mergeable,ahead 279 / behind 12 / divergedfrom canonical feat: add privacy-preserving presentation identity kernel #229c7b7b0df9f0026f8c3f5ec546203c92d795bef74. - The current trusted-adapter/source-provenance contract adds raw-identifier macro spelling to the fail-closed
include!surface. RED783bbc614d08c3a9299849524e3dbda8545ab29fdemonstrates that predecessor detection missedr#include!(...); repair5c3b86091199f436374111d6a4056d47c13c1448recognizes optionalr#without widening source paths or Cargo ownership;b7c59f9...records the Rust Reference basis and follow-up to compiler-derived source-input provenance. - feat: add privacy-preserving presentation identity kernel #229 native CI and Semgrep are GREEN, but CodeQL and Security fan-out jobs remain materialized pre-runner after their initial detection/scope jobs succeeded. Therefore feat: add privacy-preserving presentation identity kernel #229 repository/security evidence is still non-terminal and no Browser Session ancestry movement is authorized.
- Delivery order is now: 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 protocol integration → test(browser): observe pinned presentation cleanup #299 exact pinned-Chromium replay. The browser acceptance invariants remain unchanged: command ACK is not page-observed success, and apply/reset/cleanup must be independently observed from the exact owned context.
No future BiDi adapter/source path is pre-authorized by this update.
- Browser Session fix(browser-session): require aggregate-issued lifecycle request authority #317 is now exact
#317 exact
63d9e2c71835a9043e6c359ee781debea78b0c2dnow has focused independent review for the newest alias-provenance generation: no defect found in the requested source-indirection scope. The grouped rawr#includealias/comment-trivia hostile regression and inheritedinclude as aliasfail-closed repair were verified. This does not change delivery status because the exact Draft head still has no hosted repository/security workflow generation.Current-head review follow-up: focused CodeRabbit review of #317 exact
c59d41944f68491ae4d58cfe8997357acff19ee1completed and found no defect in the requested Cargo compiler-execution provenance scope. REDba9c9299...and repair80aaa562...are confirmed ancestors; the successor is traceability-only after the repair, and the compiler-authority contract continues to consume the canonical trusted-adapter topology owner. This does not change browser acceptance: no executable exact-head #317 GREEN is claimed, and #299 remains browser RED until the pinned-Chromium sequence completes.Central-owner live delta after the body refresh: protected
.github/mainadvanced to signed3449d0020ffac86315ecccfb9d5a1dd3bf421834via merged.github#2242, which prevents disabled coalesce ticks from entering the runner queue. #1857 is consequently ahead 11 / behind 277 / diverged from current protected main. This improves the central queue-control baseline to preserve during the MV3 owner restack; it does not alter #299 browser RED or retroactively settle #229 CodeQL.18 September 2026 KST foundation update: #317 is now exact
ac0c86c57f606fe61486b37740c37e37c3126ff3, Draft/non-mergeable, ahead 289 / behind 12 / diverged from #229. The current repository-security generation extends the Git-owned Cargo Rust-tool execution boundary tobuild.rustdoc: structural REDa39caf95..., repair34575910..., traceabilityac0c86c.... Compiler/wrapper/source-topology protections remain intact and no tool/adapter path is pre-authorized. Exact-head executable GREEN is not claimed; scoped current-head review is requested.Protected
.github/mainis now3449d0020ffac86315ecccfb9d5a1dd3bf421834after #2242..github#1857@afeffe3...remains the central MV3/sandbox owner, Draft/non-mergeable and now ahead 11 / behind 277 / diverged. #229 exact remains unchanged: CI/SAST/Security success, CodeQL35178432760blocked at verdict/dispatch control-plane settlement with downstream105251882999unassigned. Delivery order therefore remains terminal #229 CodeQL → ordinary/non-force #317 reconciliation preserving 12 parent + 289 child deltas → fresh #317 executable evidence → #318 → #321 → #316 → repaired central MV3 owner → #299 pinned-Chromium browser-observed replay.Real-browser delivery prerequisite update: Browser Session owner #317 is now
d2a0f587386294f8b2793d0e40ec6792f1fa5dd0(ahead 338 / behind 12 / diverged from #229). New test-first provenance contracts fail closed on rustc-managed native-tool selection throughlink-self-contained,linker-features,linker-flavor, anddlltoolwithout broad-banning unrelated codegen options. This is source-semantic repair only: current exact #317 has zero PR-triggered hosted runs and no fresh independent-review verdict yet. Do not inherit it as browser success. Real Chromium acceptance still follows terminal #229 CodeQL → non-force lineage reconciliation preserving 12 parent + 338 child deltas → fresh #317 executable/review evidence → #318 → #321 → #316 → central MV3 owner → pinned-Chromium page-observed 3/3 replay; command ACK alone remains insufficient.Browser-foundation currentization: #317 is now exact
61053c9cc3ca58f5d812f3ab64660f4e662afdce, Draft/non-mergeable and ahead 347 / behind 12 / diverged from #229. The newest owner slice closes a direct external-crate provenance gap in Git-owned Cargorustflags: REDdbd9faa623f01652c2e75904af8bec614c2e6fc9covers split, equals-form and pathless rustc--extern; repair098a596029c0cf339c070604a265593540822956extends the rustc-level external-input classifier without duplicating canonical Cargo topology or treating--externas linker-driver authority; exact61053c9...records the artifact-provenance contract.This does not advance browser acceptance. Exact #317 still has zero PR-triggered hosted runs and the requested current-head review has no new verdict yet. #229 CodeQL attempt 2 remains queued at coordinator
105398782137after compatibility shards failed closed without an authenticated dispatch verdict. #318/#321/#316 remain Draft on predecessor source generations, though their metadata now consumes61053c9...as the Browser Session prerequisite. Delivery order is now: terminal passing #229 CodeQL → non-force reconciliation preserving 12 parent + 347 child deltas → fresh #317 executable/full-review evidence → #318 → #321 → #316 → repaired central MV3 owner → #299 pinned-Chromium three-trial page-observed acceptance.--externrepair is repository input provenance only; ACK still does not count as browser success.Real-browser prerequisite currentization: Browser Session owner #317 advanced to exact
19dae976f1dcfdf261ded04c43cade986ade7712(354 ahead / 12 behind / diverged from #229). The newest source-provenance repair closes path-shaped extensionless GNU implicit-linker-script injection (8f5e49f...RED →cb95d5d...repair →b039802...benign-operand control →19dae976...traceability) but does not constitute browser success or executable GREEN. Bare extensionless filenames without a path separator and non-GNU grammar remain explicit residuals. Exact #317 still has zero hosted runs; current-head focused review is requested and pending. Keep #299 acceptance independent: actual pinned Chromium session creation, page-observed post-condition, native interaction/outcome, restoration or owned destruction, and cleanup are still required; command ACK or source-level provenance closure cannot satisfy those gates. Upstream order remains #229 CodeQL terminal passing → non-force 12-parent/354-child reconciliation → fresh #317 executable/full-review evidence → #318 → #321 → #316 → central MV3 owner → #299.Focused review follow-up: CodeRabbit completed exact
19dae976f1dcfdf261ded04c43cade986ade7712review for the extensionless implicit-linker-script slice and found no current-head defect in that requested scope. It confirmed the causal RED→repair→control chain and preserved bare linker operands, while explicitly leaving bare extensionless filenames without path separators and non-GNU grammar unresolved. This remains static/source evidence only. Exact #317 still has zero hosted runs, so #299 browser acceptance cannot inherit GREEN from it and still requires pinned-Chromium page-observed outcome/recovery/cleanup evidence.Real-browser delivery prerequisite currentization: Browser Session owner #317 is exact
a3135165afd9a1a45c4f1650765260c19f1e26f9,ahead 369 / behind 12 / divergedfrom #229. The newest source-semantic repair closes explicit rustclinker-plugin-lto=<path>artifact selection (f25634aa...RED →c368afac...canonical repair →812c8087...spelling/surface coverage →a3135165...TRACEABILITY) without copying production topology authority or treating bare/boolean LTO controls as repository plugin paths. Exact #317 has zero hosted workflow runs and current-head independent review is pending. Do not transfer this source repair as Chromium/page-observed success; #299 acceptance still requires actual browser session creation, interaction, independently observed post-condition, recovery/destruction and cleanup after parent ancestry/executable gates settle.18 September 2026 foundation currentization: Browser Session owner #317 is now exact
345b72ec49d02a1dcb0896eecb4fa64e6233a404, Draft/non-mergeable and12behind /376ahead from #229. Its newest source-security generation closes top-level rustc/rustdoc@pathresponse-file indirection for build/targetrustflagsandrustdocflags(f031bbc...RED →0c3d76ae...repair →345b72ec...TRACEABILITY). CodeRabbit independently confirmed this exact repair statically and resolved the finding; exact #317 still has zero hosted PR workflow runs, so it is not executable/browser GREEN.#229 CodeQL run
35178432760attempt 2 has transitioned from queued to completed/failure. The compatibility shards intentionally failed closed before an authenticated current-head dispatch verdict existed; coordinator105398782137then dispatched central.githubrun35303205858for the unchanged exact tuple. That central run is currently pending pre-execution/no-jobs. This is central admission/control-plane state rather than a Browser Session source defect.The real-browser invariant is unchanged: command ACK is not success. #299 remains downstream of terminal central CodeQL evidence, successful exact #229 shard rerun, ordinary/non-force 12+376 #229→#317 reconciliation, fresh executable/full-review #317 evidence, #318/#321 restacks, #316 protocol integration, and the repaired central MV3 workflow.
Buyer-gap currentness handoff (2026-09-20 KST): #317 is now exact
61d27ea6e4a1b863218a5cb5f05531260749c03b, Draft/non-mergeable,ahead 606 / behind 12 / divergedfrom canonical #229 at merge base8dcacbaebf2a6f02c5bbda8e8d6cc8bce474b693. The newest successor commit is documentation-only (CHANGELOG.md+2/-0) and closes the previously explicit generic nested[host.<key>]plus cfg-target false-positive wording gap; it does not change this issue’s browser acceptance invariants. Central #2279 is now merged into protected.github/main@e6334e229581a918e2f22de18733b76fa65d7e71; #2271 is exacta0e1424de409ec474e7bc6e9f91a9e99b8a0915eReady/mergeable with Python Security/CodeQL/Semgrep/Security Scan still queued; #2275 is exact572cfed270ae3b3cd38faca4d97ce028093e5373Draft/mergeable and still requires #2276 realcode-scanning/analysesread proof. Canonical MV3 owner.github#1857is exacta6d16c0f36e31da539ee98d550277d2169e33514, Draft/mergeable, with its Node-24 upload-artifact repair present but hosted security runs still queued. #299 therefore remains a valid 0/3 session-creation browser RED rather than acceptance evidence. Keep this issue open until the pinned-browser page-observed sequence is actually GREEN.Current Browser Session / presentation-evidence authority supersession — 2026-09-21 KST.
The foundation snapshot in this issue body is stale. Use the live chain below for any further presentation-identity/browser acceptance work:
- feat: add privacy-preserving presentation identity kernel #229 is exact
c05f6108bba2b09b43b706280916df384851043b, Draft / mergeable. Its current publication evidence is W3C WebDriver BiDi 16 September 2026 latest / 14 September 2026 previous; publication freshness remains separate from runtime qualification. - fix(browser-session): require aggregate-issued lifecycle request authority #317 is exact
70cc9d8ab9cbb79e3f7c8635ba5c4bec67d80b73, Draft / non-mergeable. Relative to current feat: add privacy-preserving presentation identity kernel #229 it is now ahead 634 / behind 22 / diverged, merge base8dcacbaebf2a6f02c5bbda8e8d6cc8bce474b693. - The prior c7b7b0/5dc759 foundation values and older ahead/behind counts in this issue are historical only; do not use them for restack, runtime qualification, or acceptance transfer.
.github#2291@a8d6261d4fc2c2a82a9b8ad6636e75677ecc5081remains the first central source prerequisite because its 24 specialized trusted-source fixtures still have an exact test-only RED plus unresolved current-head Major.- Organization Actions admission remains separately blocked under
.github#712; queued/unassigned current-head jobs are incomplete evidence, not Browser Session/source failure and not GREEN.
The next safe presentation path therefore remains: central source/admission prerequisites → #229 terminal exact-head acceptance → ordinary/non-force #229→#317 reconciliation preserving all current parent truth and 634 valid child deltas → fresh #317 executable/review/owned-quality evidence → #318/#321/#316 → protected MV3 workflow owner → #299 pinned/current-qualified real-Chromium runs. Command ACK, model review, predecessor CI, or a newer standards publication cannot substitute for browser-observed post-condition and cleanup/destruction evidence.
- feat: add privacy-preserving presentation identity kernel #229 is exact
2026-09-22 current central-prerequisite authority
This supersedes the stale
.github#2291@a8d6261d...central-prerequisite paragraph in the issue body; the browser-observed presentation invariants and #299 acceptance boundary are unchanged.Canonical
.github#2291is now exact1794626af3473ef23b9c2e678c3f06fd6c11636f, Ready / mergeable. The earlier 24-site specialized-fixture trusted-runtime RED is causally repaired in that owner. Runtime Quality35661200424and SAST35672611347are terminal success; Security35672611396, Python Security35672611349, and CodeQL35672611353remain nonterminal with remaining runner-admission work, so the owner is not accepted or immutable..github#2278@8a5251bf...remains the independent AnyIO 4.14.2 dependency prerequisite.OriginWeave #229 exact
3ec6326...now has Security/SAST success, native CI skipped, and CodeQL failure at the central verdict-publication/wake boundary after successful dispatch with a still-pending authenticated verdict. #317 remains exact70cc9d8..., 634 ahead / 25 behind / diverged from current #229. The delivery order therefore remains owner-first: central prerequisites → #229 executable native/review/ruleset acceptance → ordinary/non-force #229→#317 reconciliation → #318 → #321 → #316 → accepted central MV3 owner → immutable pin → #299 real-browser replay. Do not copy central source or promote historical Chrome/browser evidence to GREEN.
Buyer-visible gap
originweave-fingerprintowns pure presentation identity. OriginWeave still needs browser-domain proof that an admitted profile is actually applied before page script, observed from the same version-qualified Chromium context, survives required failure cases, and is safely restored or destroyed. Protocol acknowledgement alone is not success. MCP/driver transports, LLMs and sibling owners must not become deterministic browser-policy or presentation-truth owners.Current dependency authority — 23 September 2026 KST
Canonical presentation/WebDriver BiDi parent #229 is exact
60318092c410111924415b3e20ee3f4186e6472a, open / Draft / mergeable on protectedmain@87c4daa1830bac5a5228b6036752ad5633232085. W3C's live WebDriver BiDi publication history currently lists 16 September 2026, 14 September 2026, 9 September 2026, then 3 September 2026 Working Drafts. Publication freshness and runtime qualification remain separate authorities: OriginWeave's independently qualified adapter pin remains 3 September 2026 until dedicated schema/browser compatibility evidence proves a newer revision. Current #229 ordinary-forward repair lineage currentizes the publication receipt/ADR and removes prose-label coupling from the currentness oracle. Exact-head CI35713817985is Draft-skipped; SAST35713817883and Security35713817945are terminal SUCCESS. CodeQL35713817902remains nonterminal: Detect106700519278is SUCCESS, its three compatibility jobs executed and failed closed only because no authenticated terminal current-head verdict existed, and coordinator106826100321remains pre-step queued withrunner_id=0andsteps=[]. Fresh #229 review inspection has 0 unresolved threads but no qualifying current-headAPPROVEDreview. Predecessor GREEN/review evidence does not transfer.Browser Session successor #317 is exact
70cc9d8ab9cbb79e3f7c8635ba5c4bec67d80b73, open / Draft / non-mergeable. Fresh GitHub compare from current #229 is ahead 634 / behind 31 / diverged at merge base8dcacbaebf2a6f02c5bbda8e8d6cc8bce474b693. Reconciliation must be ordinary/non-force, preserve all 634 valid child deltas, and adopt/adapt current #229 standards truth without duplicating volatile publication metadata in Browser Session domain documents.The downstream Browser Session chain remains #318 exact
983fa652180e47e479c99b8903755f1fd60f0746→ #321 exact9d3c51e7ff66c952dba203a04704e53df78d2b0e→ protocol/ACL owner #316 exact8ca6c5a190d9ad2b4c7843d440e91f6070d681c2. These are Draft generations on predecessor ancestry. Mergeability on an individual child is topology only, not acceptance.Issue #212 remains the canonical owner for the volatile central workflow/sandbox/admission chain. Canonical AnyIO owner
.github#2278@8a5251bf409fe84b3dd0cba1e48992f5b8d9eda5carries the one-file AnyIO4.14.0 → 4.14.2repair; SAST, Python Security, and Security Scan are GREEN while CodeQL remains fail-closed on central verdict publication and current-head approval is missing. Canonical trusted Strix owner.github#2291@1794626af3473ef23b9c2e678c3f06fd6c11636fhas Runtime Quality/SAST/Security GREEN, Python Security failing only atpip-auditwhile inheriting protected AnyIO 4.14.0, and nonterminal CodeQL. OriginWeave must not copy either owner repair or weaken browser sandboxing.The former 21 September authority named #229
3ec6326b...and a 634-ahead/25-behind relationship. Earlier history named #229c7b7b0d..., #3175dc7592..., and 562-ahead/12-behind. Those values are historical only and no longer define dependency authority.Browser acceptance invariants
originweave-fingerprintremains the pure profile/value owner; browser adapters depend inward on it.BrowserSessionIncarnationparticipates in authorization validation and sequential-ABA separation.Real Chromium lane
PR #299 remains the browser-observed acceptance lane. Native repository CI does not substitute for browser success. Its pinned Chrome/ChromeDriver
150.0.7871.129generation is immutable historical reproducibility evidence and remains browser RED because session creation never reached the page-observed presentation/interaction/reset post-conditions.Current-Stable Chromium qualification is a separate versioned evidence generation owned through #212 and the canonical central MV3 workflow. Do not rewrite the Chrome 150 receipt in place, infer a matching Chrome-for-Testing artifact without an immutable asset/digest receipt, copy the central reusable workflow, or use
--no-sandbox.A passing pinned-browser run requires all three trials to prove ambient-distinct baseline → presentation apply → page-observed target → browser-computed semantics → native clear/type/click → accepted outcome → URL stability → explicit presentation reset → page-observed original baseline → WebDriver session/profile cleanup.
Delivery order
Required order is owner-first and acyclic:
#212 central dependency/trusted-runtime/admission prerequisites reach causal GREEN and normal protected integration → current #229 executable native CI/CodeQL/current-review/ruleset acceptance on repaired standards authority, with exact SAST/Security already GREEN → ordinary/non-force #229→#317 reconciliation preserving current parent truth + all 634 valid child deltas → fresh #317 executable repository/security/whole-current-head and owned-quality closure → #318 → #321 → #316 ordered non-force restacks → canonical central MV3 workflow acceptance/immutable consumer pin → #299 replay with actual session creation and complete page-observed post-conditions.
Keep this issue open until the exact pinned-Chromium path proves the complete sequence and reaches protected main through normal review and required workflows. No self-approval, bypass, force push, destructive rebase, gate weakening, workflow copy, source-neutral wake commit, merge, tag, release or publication is authorized here.