feat: complete OAuth account lifecycle - #23
Merged
Conversation
artiphishle
marked this pull request as ready for review
July 12, 2026 11:07
…ankhorage/supabase-auth into phase3/complete-oauth-account-lifecycle
…ankhorage/supabase-auth into phase3/complete-oauth-account-lifecycle
…ankhorage/supabase-auth into phase3/complete-oauth-account-lifecycle
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.
Goal
Complete every remaining Phase 3 responsibility owned by
@ankhorage/supabase-authin one repository PR. This is intentionally not split into smaller follow-up PRs.Included scope
AuthUserprofile_creation_failedoutcomes when the identity exists but the profile invariant failsSecurity boundary
Lifecycle events expose only correlation ID, provider, stage, status, and typed error code. They never expose authorization codes, callback URLs, access/refresh tokens, provider credentials, private keys, service-role keys, session payloads, or profile rows.
Profile verification uses the authenticated session only for the request boundary. Returned errors remain user-safe and contain no row or token contents.
Repository boundary
This PR owns the complete Supabase adapter/account lifecycle. Generated-app wiring belongs to the later single Studio repository completion PR; generated database/profile invariants belong to the later single Infra repository completion PR. No additional mini PR is planned for this repository.
Part of #18.