Repository navigation
DATA-001C2: stop Auth phone copy during profile setup - #199
Merged
Merged
Conversation
✅ Deploy Preview for luminous-fox-7c393f ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
9 tasks
daliu
force-pushed
the
codex/issue-197-stop-auth-phone-copy
branch
from
July 14, 2026 00:53
1e95662 to
84fb10d
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.
Closes #197
Outcome
New member profiles keep the existing schema-compatible empty phone field even when Firebase Auth already contains a phone number. The shared create-once helper still serves both signup and callable recovery, and every existing profile remains unchanged.
Security and compatibility
user.phoneNumber.Verification
git diff --check: passed.a880177; exact DATA-001C2 — Stop profile setup from copying Firebase Auth phone numbers #197 diff SHA-256 stayed2961034bb3a6f7f76b4942702ed3a5b4aefbf43709ed0e3d12b1dbd4bfbde6ae.Officer handoff
Officer impact: New signup/profile repair will not copy a Firebase Auth phone into the member profile after the backend is deployed. Officer steps remain no-phone, synthetic-data-only, and stop-and-escalate.
Officer documentation:
docs/officers/EVENTS_SHOP_MEMBERS.md; engineering flow/status inSYSTEM_DESIGN.md.Deployment evidence: Source/tests and this pull request only. No website was published;
runmprc.comwas not changed or verified; Firebase Rules/Functions were not deployed or read back; no provider setting or production record was accessed. Live protection remains NOT AVAILABLE YET until #105/#133/#136 deploy and verify the exact Rules plus both profile Functions before any dependent website revision.