Follow-up to #70

Issue #70 was closed with the note that help(action="version") now exposes "the running version, latest available version, release URL, and the endpoint-provided changelog/release notes, with a local fallback."

Observed behavior (server v0.5.40)

help(action="version") returns only:

Server version: 0.5.40. Latest available: 0.5.40. Releases: https://github.com/contextstream/mcp-server/releases

• ✅ Running version, latest version, and canonical releases URL are present (the Popup 'View all releases' links to github.com/contextstream/mcp/releases (404); propose release_notes tool for agents #70 broken-link fix is confirmed working).
• ❌ The changelog/release-notes body is NOT in the output. There is no "what changed / breaking changes / features" payload — only the URL pointer.

So the "endpoint-provided changelog/release notes" described in the fix comment is not actually surfaced through the version action in this client. An agent still cannot get machine-readable release context without fetching the GitHub releases page separately.

Questions / requests

1. Changelog body: Was the changelog payload dropped, or is it exposed via a different action/tool (e.g. a mcp_server_version tool referenced in the fix but not present in this client's help action set)? Please surface the changelog body in help(action="version") as described, or document where it lives.
2. Intended usage of the Releases URL: Should agents be expected to fetch https://github.com/contextstream/mcp-server/releases themselves to get notes, or is the URL only a human pointer? If self-fetching is intended, please document that consumption pattern (and note that the releases page is paginated / not machine-readable JSON). If a tool is intended, please expose it.

Environment

• Hosted MCP server: v0.5.40
• Client: VS Code + GitHub Copilot Chat (remote HTTP MCP at https://mcp.contextstream.io/mcp)
• Related: issue Popup 'View all releases' links to github.com/contextstream/mcp/releases (404); propose release_notes tool for agents #70 (original), issue Recap Bot stalls via VS Code Copilot MCP path; recaps are session-boundary triggered, not a daily cron #72 (recap retrieval API), new issue on help(action="tools") catalog.