Update Elixir Dependencies (Strict Checklist)

This skill is intentionally written as a no-skip checklist. Agents must follow it exactly.

Non-negotiables (DO NOT SKIP)

You may update all dependencies marked "Update possible" in a single batch.
Any dependency that is blocked only by the project's mix.exs version constraint is NOT truly blocked. It must be moved into the update batch by changing the constraint.
Review diffs individually for each dependency being updated (even in a batch).
After updating dependencies, run the verification gates:
- mix compile --warnings-as-errors (must pass for both dev and test environments)
- mix format --check-formatted
- mix test
If any gate fails: STOP, fix, re-run the failing gate(s) until green, then continue.
Never "force" blocked updates caused by transitive constraints. Report them instead.

Run: