Dependency upgrade

Upgrades fail in a predictable way: several are attempted at once, something breaks, and nobody can tell which one did it. The whole batch gets reverted, the work is wasted, and the project falls further behind.

One dependency per commit, always. It is the difference between a bisectable history and an afternoon of guessing.

1. Establish that the current state is green

Run the full test suite before touching anything. If it is already failing or flaky, fix that first — you cannot attribute a failure to an upgrade when the baseline is red.

Record what "working" means beyond tests: the app starts, a smoke path succeeds, the build produces the same artifacts.

Done when: you have a green baseline and know how you would notice a regression.