reaatech/mcp-schema-evolution

These packages give you a diff engine and CI policy for MCP tool schemas, classifying every change between two `Tool[]` snapshots as breaking, non-breaking, or patch. You'd adopt them to prevent breaking MCP consumers when you add, remove, or rename tool fields, catching unintended changes before a release. The core library returns `Result<T>` objects instead of throwing, and the CI package enforces policy through a pipe-delimited acknowledgment file that lets you explicitly allow intentional breaking changes.