Change Impact

Analyse what a code change affects outside its own diff — broken consumers, changed contracts, and coupling that the type checker, linters and greps for symbol names will miss. Use this whenever the user asks what their change breaks, affects, touches, or impacts; when they ask "did I break anything", "what depends on this", "is this safe to merge", or ask for a blast-radius or regression check before a PR. Also use it proactively before declaring a non-trivial code change finished, and after any rename, signature change, return-type change, API or schema edit. Applies to JavaScript and TypeScript repositories, single-app and monorepo. Not a code-quality review — it repor…