Repository navigation
fix(checkin): show truthful guest contact receipts - #4662
Merged
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This branch was successfully deployed
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.
What
The signed guest check-in contact form now shows a retry error when saving returns null or rejects. Its success receipt says the host has the guest’s contact information and directs attendance-confirmation questions to the host. The intentional honeypot response remains identical and performs no write.
Why
The form previously displayed “You’re checked in” even after a failed CRM capture. This door creates or resolves a Space contact; it does not write a verified event-attendance receipt.
Risk
Small action and copy change. Signed Space/event-label/tier binding, rate-limit refusal and CRM consent/opt-out handling stay intact. Infrastructure failures share one generic error; no contact identity or provider detail is returned. Ledger row SHARE-GUEST-RECEIPT remains open for release verification. The exact new regression patch was specifically approved by Daniel.
How to verify
Reconciled with main 2d5b549 using a normal merge; head b8c2d6f.
Root owns the merge sequence; auto-merge is off.