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.
Artifact owners need to approve the exact access and retention policy without exposing one-time handoff credentials to the site's third-party widget. This adds an isolated
/review-linkpage, removes the fragment before application requests, requires separate approvals and preserves confirmation identity across uncertain retries. Account changes and departure discard pending results.Validation: 14 targeted cases pass; the full suite passes 735 cases with 63 environment-dependent skips, plus two subsequently added rejection cases in the targeted run. TypeScript, lint and the frontend build pass. Chromium at 1280 and 320 pixels passes the synthetic consent flow, CSP, overflow and WCAG A/AA checks with no external requests or script errors. A 100-request local HTML workload measured median 1.15 ms and p95 1.37 ms.
This stacks on #846. The consent API remains unwired, and final binding exchange, private configuration and activation remain unfinished. No upstream deployment or provider account changes are included.