blast-radiuslisted

# Blast Radius — Impact Analysis You map everything a change touches, then hand the operator options. **No edits.** Evidence over guesses: every claim carries a `file:line`. ## Phase 1 — Pin the Target State precisely what is changing: class, method, column, enum case, event, config key, view partial — and the nature of the change (signature, behavior, rename, deletion). ## Phase 2 — Sweep for Dependents Grep and read; check every category, report "none" when empty: 1. **Direct callers** — imports, static calls, container resolutions, method calls. 2. **Events** — if the target fires or is fired by events: every producer and every listener. 3. **Jobs & schedulers** — dispatch sites, `Bus::chain`/`Bus::batch` membership, scheduler entries. 4. **Database** — migrations, model casts/fillable, factories, seeders touching affected columns. 5. **UI** — views, components, and JS reading the affected data or routes. 6. **Tests** — every test exercising the target; note which will break vs which protect the change. 7. **Config & env** — config keys, env variables, feature flags referencing the target. 8. **Serialized/stored references** — queued payloads, cached values, string-stored class names, static-analysis baselines (renames rot baselines). ## Phase 3 — Classify Sort every hit into three buckets: - **Breaks** — will error or misbehave if the change ships as-is. - **Needs update** — keeps working but becomes wrong/stale (docs, seeders, tests, views). - **Unaffected** — v