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

..

main

fix: correct well-known URL construction per RFC 9728

2026-03-27 19:46:25 +01:00

renderer

fix: clear live agent status on cancel

2026-03-25 22:20:57 +01:00

scripts

feat: add native platform installers for Windows, macOS, and Linux

2026-03-26 13:06:50 +01:00

shared

feat: add tool metadata registry with human-readable labels

2026-03-26 19:27:36 +01:00