Guide first-time Linq sign-in - #92
Merged
Merged
Conversation
…idance # Conflicts: # src/auth/tests/linq.test.ts
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.
Summary
Desktop
Mobile
Make Linq's required first-time sign-in flow visible before a user requests an OTP.
sms:deep link to the deployment's onboarding numberLINQ_PHONE_NUMBERoverride and otherwise resolve the number through Linq's V3available_numberendpoint2008) from sender authorization (2006) and no-eligible-line failuresBehavior and boundaries
The button opens the user's Messages client but does not send anything. The user still sends the first message explicitly. The lookup is app-scoped, bounded to three seconds, validated as E.164, and fails soft so Linq or Connect availability cannot prevent the sign-in form from rendering.
Local OTP bypass and deployments without a Linq connector retain their existing behavior.
Validation
pnpm exec vitest run src/auth/tests/linq.test.ts src/auth/tests/auth-linq.test.ts src/app/sign-in/_tests/phone-auth-form.test.ts— passed; 3 files and 19 testspnpm check— passed; 46 test files and 220 tests, plus lint, TypeScript, formatting, Knip, and package boundariespnpm exec turbo run build:app --force— passed after merging currentmainsms:+12025550123, and served/sign-inwith HTTP 200 from a clean Next cacheReviewer focus
No changeset is needed for this application repository.