Repository navigation
Add Supabase clean consumer acceptance and correct rollout status - #61
Merged
Merged
Conversation
Robertpaschal
marked this pull request as ready for review
October 27, 2026 13:29
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.
The setup guides still said no native sign-in had occurred after the successful controlled Sprout pilot. They now distinguish that observed result from the open broader rollout gates, including the newly observed link-only Supabase fallback that cannot complete Sprout's code-based sign-in.
Adds a clean consumer install check to CI. It imports the private adapter outside the monorepo and verifies all six auth actions, secure-change recipients, invalid-signature rejection and retry after handler reconstruction, using synthetic transport and ledger query fixtures. It does not send email or establish independent customer onboarding.
Validation: clean consumer check, 40 adapter tests, package typecheck, design/truth audit and whitespace checks passed locally. Fresh Sprout simulator build, opt-in hosted request UI test, core tests and disposable SQL tests are documented separately. Actual two-client sync remains open; this PR changes no production runtime or credentials.