Map the blast radius before changing code

Given [PROPOSED CHANGE] and the repository files I provide, map the direct callers, downstream consumers, persisted data, permissions and user-visible journeys that could change. Distinguish source evidence from guesses, and name the searches or tests needed to close gaps. Produce a dependency table, three highest-risk regressions, a minimal change boundary and a rollback plan. Do not edit files or claim tests passed. If the repository is incomplete, mark unobserved paths explicitly rather than assuming they do not exist. Prioritise invariants that a user would notice, not just compilation.