Versioning and compatibility

Tool contracts

• Treat tool name + argument schema as a public API for the upstream mapper and hosts.
• Additive changes (optional fields) are safer than renames or semantic breaks.

Deprecating tools

1. Add the replacement tool and map it upstream.
2. Migrate prompts / docs / automations to the new tool.
3. Remove the old tool only after no production upstream mapping references it.

Server versions

Bump server version metadata when rolling incompatible changes so you can correlate errors with deployments.