Schema regression testing for releases #141
Description
Issue #112 is exactly the kind of breakage I keep running into with MCP servers, which is part of why I built mcp-observatory.
It snapshots tool/prompt/resource schemas, compares them between runs, and fails verify if something regressed, so it slots into CI pretty naturally.
Happy to wire up an example against mcp-framework if useful. Seems like it could catch the #112 class of bug before release.
Also noticed you're looking for maintainers. Open to chatting if there's overlap.