Release request: the three CIMD auth-server fixes (#6283, #6284, #6490) are merged but unreleased

[alex-feel]

Three embedded auth server fixes merged after the v0.46.0 cut (Aug 27), so no published release carries them yet:

• Intersect default scopes with scopes_supported when scope is omitted #6283 (closes CIMD clients that omit scope are silently rejected as 'Client does not exist' when scopes_supported does not include all DefaultScopes (breaks ChatGPT connector) #6186, merged Aug 31): when a client omits scope, the default scopes are intersected with the server's own scopes_supported instead of the login failing with "The requested OAuth 2.0 Client does not exist."
• Persist resolved CIMD clients so Redis session rehydration finds them #6284 (closes Redis storage rehydrates sessions past the CIMDStorageDecorator, so CIMD clients fail every token exchange with invalid_grant #6187, merged Sep 3): resolved CIMD clients are persisted, so Redis session rehydration finds them and token exchange stops failing with invalid_grant.
• Grant CIMD clients the server's allowed audiences #6490 (closes Embedded auth server: CIMD clients get no audience, so every refresh_token grant fails #6489, merged Sep 3): CIMD clients get the server's allowed audiences, so the refresh_token grant stops failing with invalid_request.

Together they make CIMD clients (Claude Code, Claude Desktop, ChatGPT connectors) work end to end against the embedded auth server with Redis storage: no manual client seeding, and refresh tokens that actually refresh. We run that setup in front of an internal MCP gateway, and these three are the pieces we are waiting on; until they ship we hand-seed client records and run long-lived access tokens instead of refresh. Main is 30 commits ahead of v0.46.0 and I do not see a release PR up, so I wanted to ask rather than assume: is a new cut planned soon?

Same offer as in #6435: the day a release ships, we can run the full flow against a live deployment (real Claude Code and ChatGPT clients, embedded auth server with Redis storage, CIMD registration, refresh) and report the result here.

[jhrozek]

Yes, I'd like a release to happen either tomorrow (Friday) or Monday. There's a couple of important patches we need to merge.