release: bump CWM.RoslynNavigator to 0.7.2 for NuGet publish

[AdamPullenPAR]

Summary

• Bumps CWM.RoslynNavigator package version from 0.7.1 to 0.7.2 so the MCP stdio stderr logging fix (CWM.RoslynNavigator logs to stdout, breaking MCP stdio JSON-RPC stream #10) can be published to NuGet.
• NuGet currently serves 0.7.0, which logs to stdout and breaks Cursor MCP clients with JSON parse errors on startup log lines.
• The code fix (LogToStandardErrorThreshold = Trace) is already merged on main; this is a release-version bump only.

Test plan

• Run the Publish to NuGet workflow with version 0.7.2
• dotnet tool update -g CWM.RoslynNavigator
• Restart Cursor and confirm cwm-roslyn-navigator MCP connects without JSON parse errors

[RomeDevv]

+1 — this also affects Claude Code, not just Cursor. The plugin-provided cwm-roslyn-navigator stdio server fails to connect on Windows with CWM.RoslynNavigator 0.7.0 (the current NuGet release): stdout carries the host/logging lines instead of pure JSON-RPC, e.g.

info: Program[0]
info: ModelContextProtocol.Server.StdioServerTransport[857250842]
Server (stream) (CWM.RoslynNavigator) transport reading messages.

which Claude Code drops with Ignoring non-JSON line on stdout: Unexpected identifier "Server"/"info". Setting Logging__Console__LogToStandardErrorThreshold=Trace on 0.7.0 confirms the fix — stdout goes clean, logs move to stderr. Would be great to get this merged and the Publish to NuGet workflow run so 0.7.2 lands. Thanks!

[AdamPullenPAR]

+1 — this also affects Claude Code, not just Cursor. The plugin-provided cwm-roslyn-navigator stdio server fails to connect on Windows with CWM.RoslynNavigator 0.7.0 (the current NuGet release): stdout carries the host/logging lines instead of pure JSON-RPC, e.g.

info: Program[0]
info: ModelContextProtocol.Server.StdioServerTransport[857250842]
Server (stream) (CWM.RoslynNavigator) transport reading messages.

which Claude Code drops with Ignoring non-JSON line on stdout: Unexpected identifier "Server"/"info". Setting Logging__Console__LogToStandardErrorThreshold=Trace on 0.7.0 confirms the fix — stdout goes clean, logs move to stderr. Would be great to get this merged and the Publish to NuGet workflow run so 0.7.2 lands. Thanks!

That makes a lot of sense. I use both and I was seeing Claude initially throw errors on the cwm-roslyn-navigator