PIR: Fix email data handling#8641
Merged
Merged
Conversation
This was referenced May 20, 2026
Contributor
Author
This was referenced May 20, 2026
6d572cd to
8d8f136
Compare
f6b07d2 to
73245d0
Compare
8d8f136 to
97e4aae
Compare
73245d0 to
733cabf
Compare
Contributor
Author
97e4aae to
b1d0efa
Compare
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.

Task/Issue URL: https://app.asana.com/1/137249556945/task/1214973541222175?focus=true
Description
Fix email data handling so email codes are properly passed along to the web layer.
Steps to test this PR
Will be testable on upstack PRs.
UI changes
No UI changes
Note
Medium Risk
Changes how opt-out/scan automation data is serialized to the in-WebView script layer; wrong mapping could break form fills or email confirmation, but scope is limited to PIR request assembly with strong unit coverage.
Overview
PIR broker script payloads now map each
fillFormdataSourceto its own field onUserProfile, instead of folding generated email and polled email fields intoextractedProfile.New
DataSourcevaluesfetchedEmailandemailDatadrivecompleteRequestData: generated addresses go inFetchedEmail, verification codes and similar keys fromgetEmailDatago inemailData, andextractedProfileis only populated forextractedProfile.emailExtractedDatawas removed fromExtractedProfileParamsso the web layer can resolvedata[dataSource]the way broker JSON expects.Unit tests were updated to assert per-source isolation (e.g. verification codes are not leaked on extracted-profile fills).
Reviewed by Cursor Bugbot for commit b1d0efa. Bugbot is set up for automated code reviews on this repo. Configure here.