v0.5.2 — Re-authenticate after a revoked token, quieter startup

Patch release with four fixes. The token store is namespaced by package version, so users authenticate again after upgrading.

Fixed

• When WordPress rejects the stored OAuth token before its local expiry, the proxy opens the sign-in page and retries once with the new token instead of failing on every start. Only a 401 that refuses a bearer token triggers this; a 401 asking for other credentials is reported as before. (#136, #141)
• The OAuth callback server fails startup when its port is already taken instead of opening a browser tab that redirects to a dead port. (#138)
• Startup no longer logs WordPress transport error with Invalid state: Controller is already closed or This operation was aborted when the SDK releases unread response bodies or aborts the event stream on close. (#140)

Changed

• The MCP SDK dependency moved from 1.26.0 to 1.31.0. (#131)

Full changelog: v0.5.1...v0.5.2

Contributors

• @gavande1 — re-sign-in after a rejected token (#136)
• @galatanovidiu — callback port failure (#138), quieter startup (#140), Bearer challenge guard (#141), release (#142)
• @dependabot — MCP SDK update (#131)

Thanks to @ManniGH for the report and analysis behind #137.