Repository navigation
docs(core): document Vercel OAuth billing-team selection - #6
Draft
pcomans-bot wants to merge 11 commits into
Draft
pcomans-bot wants to merge 11 commits into
pcomans-bot wants to merge 11 commits into
Conversation
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.
Documents the Vercel OAuth flow in #5: sign in, confirm an authorized billing team, then run Gateway inference with the saved token and team selector.
Adds a 52-case end-to-end plan with executed results and explicit fixture/live boundaries. All 201 tests (178 OAuth/client and 23 file-lock) and 35 repository checks passed. Live checks include adding a connection alongside the original, cancellation before and after consent, switching, inference, connection-specific revocation and isolation, interactive CLI recovery with billing-team confirmation, desktop recovery, CLI Ctrl+C cleanup at the visible team prompt, and removal of the inactive test entry. Natural token refresh passed with real Vercel rotation: both tokens changed on the same credential/team; concurrent and subsequent inference succeeded; old refresh introspected inactive; no browser approval was needed. No expiry was fabricated. Renewal is demand-driven near expiry, not periodic while idle.
The guide covers public-client registration, v2 team installation, Team Read and Gateway Use permissions, beta consent-screen limitations, rotating credentials, and failure recovery. Maintainer-client readiness, cross-team and platform coverage, and the complete cross-process refresh composition remain explicit gaps.
This branch shares the
vercel-oauth-basereview base with #5. It changes documentation only.