Repository navigation
Release 0.6.5 with fail-closed browser proxy custody - #2
Merged
Merged
Conversation
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.
Browser measurement now requires explicit proxy admission, with bounded custody callbacks and cleanup, expiry checks, quarantine on unconfirmed cleanup, and credential-safe errors. Supplied usage observations remain separate from nominal estimates; URL proxies do not fabricate metering.
Canonical public-package export from accepted private source 1f5c59d103af943b9c1b1974d0064d1aa245b02e. All 306 canonical files match; public workflows are unchanged. Public package checks: 489 passed. Candidate installed acceptance: 14 checks plus offline mock journey. Live provider comparison remains separate.