dep-upgradelisted

# Dep upgrade Upgrades fail in a characteristic way: everything is bumped at once, forty things break, and the causes are indistinguishable. Staging converts one unreadable failure into a sequence of readable ones. ## 1 — Read before running Establish what you are walking into. Use the repo's own migration tooling where it has some — it applies code transforms the manual path leaves to you: | Workspace kind (from the map) | Migration entry point | |---|---| | NX | `nx migrate <target> --dry-run`, then read `migrations.json` before applying | | Angular | `ng update <pkg> --dry-run` | | Anything with codemods | the package's own codemod CLI | | Everything else | the package's migration guide, applied by hand | For every package crossing a major version, read its migration guide and write down the breaking changes that touch **this** repo specifically. "Breaking changes exist" is not preparation; "`HttpClientModule` is deprecated and we import it in nine places" is — and the count comes from a search, not an estimate. Check peer dependencies for conflicts before starting. A peer conflict discovered halfway through contaminates every stage after it. Record the baseline: a full `green-gate` run over the whole repo *before* any change. An upgrade cannot be evaluated against an unknown starting state, and a test that was already red will otherwise be blamed on the upgrade. ## 2 — Stage it Each stage is its own commit, gated before the next begins: 1. **Manifest and lockfil