Contract Drift: catch the breaking API change in the PR

The most expensive outages are the quiet ones: someone changes an endpoint's shape, the provider ships green, and a caller in another repo breaks in production.

Contract Drift (we call it the Time Machine) diffs your API surface between analyses. When an endpoint is removed, renamed, drops authentication, or drops input validation, Impact cross-references the org graph: does any other repo still call the old shape?

• Consumers found → a critical, breaking finding, with every stale call site named.
• Findings are ranked by live caller count — "BREAKING · 7 callers" sits above cosmetic changes.
• It shows up in your Issues, PR review, and quality gate with zero extra setup.

A breaking change that tanks the score and fails the gate — that's the product working exactly as intended.