muster release v5.32.10

The CLI bridge refreshes an expired token instead of asking for a login. muster agent --mcp-server exposed only authenticate_muster whenever its access token had expired at start, although a refresh token was stored and muster auth status read the session as authenticated with weeks of auto-refresh left; a client on top of the bridge (platformctl, any MCP client using call_tool) failed with tool 'call_tool' not found until another muster command happened to refresh the token. The bridge now connects with the stored refresh token and the transport refreshes it on the first request; only a refresh the server refuses falls back to authenticate_muster. A refresh also keeps the ID token it returns: mcp-go’s token type has no field for it, so every refresh stored the new access token next to the old ID token, and muster auth status told the person to log in again. An expired ID token next to a refresh token now reads expired … ago (auto-refresh). (#1298)