Before shipping any schema change to an endpoint with external consumers.
Compare these two versions of an API response schema: [old] vs [new]. List every breaking change a consumer would hit, ordered by severity.
Anything in square brackets is meant to be replaced. The builder turns those into fields you can type into.
Tired of re-pasting the same context into every new chat? That is what the Unimatrix MCP server is for.