oauth: discovery chain, client metadata, server capabilities
- Oauth.Discovery walks the RFC 9728 + RFC 8414 two-step chain:
GET /.well-known/oauth-protected-resource, follow the first
authorization_servers entry, GET /.well-known/oauth-authorization-server.
Handles the RFC 8414 section 3.1 quirk that the well-known suffix is
inserted between origin and path, not appended.
- Oauth.Client models the RFC 7591 Dynamic Client Registration metadata
document plus the RFC 9449 dpop_bound_access_tokens field.
- Oauth.Server.supports / missing let profiles assert policy against the
metadata record (PAR, PKCE method, DPoP alg, grant type, response
type, auth method, scope).
7 new tests. 100 oauth tests pass.