Skip to content

docs(core): document Vercel OAuth billing-team selection - #6

Draft
pcomans-bot wants to merge 11 commits into
vercel-oauth-basefrom
vercel-oauth-docs
Draft

pcomans-bot wants to merge 11 commits into
vercel-oauth-basefrom
vercel-oauth-docs

Conversation

@pcomans-bot

@pcomans-bot pcomans-bot commented Oct 29, 2026 •

Copy link
Copy Markdown
Collaborator

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-base review base with #5. It changes documentation only.

@pcomans pcomans changed the title docs(core): explain inference-only Vercel OAuth setup docs(core): document Vercel OAuth billing-team selection Oct 29, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants