2 Commits

Include renames

Author	SHA1	Message	Date
David KayaandCopilot	0fd7a04a51	fix: try both RFC 9728 and appended well-known URL paths for MCP OAuth discovery ... Some MCP servers place .well-known metadata at the appended path (e.g. /v1/.well-known/oauth-protected-resource) instead of the RFC 9728 compliant inserted path. Now tries the RFC-compliant URL first and falls back to the appended form. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>	2026-03-27 20:00:50 +01:00
David KayaandCopilot	d73eaae30b	fix: correct well-known URL construction per RFC 9728 ... The .well-known/{suffix} segment was being appended to the full URL path instead of inserted after the origin. For example: Wrong: https://api.example.com/mcp/.well-known/oauth-protected-resource Correct: https://api.example.com/.well-known/oauth-protected-resource/mcp/ - Extract buildWellKnownUrl() helper in mcpTokenStore (Electron-free) - Fix all 3 call sites: requiresOAuth probe, PRM discovery, auth server metadata - Add 6 unit tests for URL construction with various path shapes Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>	2026-03-27 19:46:25 +01:00