Repository navigation
Conversation
|
This PR doesn't fully meet our contributing guidelines and PR template. What needs to be fixed:
Please edit this PR description to address the above within 72 hours, or it will be automatically closed. If you believe this was flagged incorrectly, please let a maintainer know. |
pcomans
force-pushed
the
auth-code-docs
branch
from
October 29, 2026 21:36
6513337 to
717d0c3
Compare
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 authorization-code alternative in #7: public-client app registration, PKCE loopback callbacks, explicit Gateway billing-team selection, and silent refresh when a connection is used near expiry.
Includes an execution matrix separating automated contracts, real Vercel checks, prior device-flow evidence, and remaining release checks. The guide also explains the callback reachability requirement for remote servers.
Records live authorization-code refresh: 23 consecutive inference checks passed across renewal and the original expiry, both tokens rotated without browser approval, and desktop inference succeeded. Also records an unresolved Gateway expiry-enforcement timing observation: direct old-token HTTP 200 about five seconds after expiry, followed by HTTP 401 on retry about 82 seconds after expiry; the first response body was not retained.