I Built a CLI That Catches What AI Coding Tools Break

I've been using AI tools (Claude, Antigravity, Kiro, Copilot, Cursor) to build software for the past year. They're incredible at writing code but terrible at remembering what depends on what. Here's a scenario every AI-assisted developer knows: You ask the AI to refactor your user model. It does a great job. Clean code, good types, well-structured. What it doesn't know is that six other files import from that model. Your auth service, your cart controller, your API docs, your validation middleware. All of them still reference the old interface. The AI has no idea they exist. You don't notice either. Not until something breaks in production three sessions later. The pattern I kept seeing: After about 40 development sessions, I started tracking these failures. They fell into three buckets: Anchor drift. A core file changes, but everything that depends on it stays stale. The AI modified the source of truth without updating the consumers. Context loss. Session crashes, token limits hit, or