Blast Radius
- Name the changed contract: type, value, state transition, API, storage shape, timing, style token, or side effect.
- Enumerate direct readers/writers/callers and any serialized/public boundaries.
- Trace transitive assumptions by search, type references, tests, runtime wiring, and history as available.
- Identify the strongest fact that would make the change safe and prove that fact by running or inspecting code when possible.
- Return affected surfaces grouped as definite, plausible, and ruled out with evidence. Never write "safe" without the proof behind it.