tin-berri 1af7a403c6 feat(mcp): start the named server's OAuth directly for a resource-scoped gateway flow (#39933) ... An aggregate gateway DCR authorize whose RFC 8707 resource resolves to exactly one gateway-managed oauth2 server sealed that server into the flow and then sent the browser to the generic connect grid anyway, so the user had to find the server the client had already named and click Connect. The connect URL now carries only the flow handle. GET /authorize/flow classifies the sealed flow as unscoped, interactive, M2M, or stale, and returns the matching state to the page. Interactive flows require a live per-user vendor credential before minting and do not burn the flow on an early submit. M2M flows use the gateway's configured service credential and finish without an interactive OAuth trip. Stale flows fail closed instead of becoming unscoped. The existing explicit Finish action and a new Cancel path preserve deliberate user intent.		2026-09-07 23:40:02 -07:00
..
mcp_server	feat(mcp): start the named server's OAuth directly for a resource-scoped gateway flow (#39933)	2026-09-07 23:40:02 -07:00
out	chore: update Next.js build artifacts (2026-09-05 23:25 UTC, node v24.19.0)	2026-09-05 16:25:57 -07:00
post_call_rules.py	refactor: add black formatting	2023-12-25 14:11:20 +05:30