Product
The incident page
This is the signed-in view, shown signed out. Every change and severity below is real @zevruna/diff output; the execution trace is a demo run, because a public page cannot show you someone else's production traffic.
ZV-2481 · acme-crm · snapshot 2db7b40e39df
contacts.create, 2 breaking changes
Found 6m ago · 2 agents affected · broken for 6m and counting
Press Accept as new contract to adopt acme-crm's new schema as the one your code should match. That makes zevruna check fail until your call sites are updated, which is what stops the broken version reaching production.
Execution trace
run_01j9f2Outcome: task not completed, every request returned 200.
What changed
MCP contract2 breaking, 1 risky, 3 changes in total.
Blast radius
since 14:03| Agent | Contract impact | Runs touching this server | Failed runs | Failure rate | Last failure |
|---|---|---|---|---|---|
| intake-agent | breaking | 2,481 | 1896 | 76.4% | 2m ago |
| outreach-agent | breaking | 431 | 81 | 18.7% | 9m ago |
| crm-sync | not declared | 0 | - | - | - |
Contract impact comes from your manifests. The run columns are measured from telemetry, an agent can be impacted on paper and simply not have run yet.