change-dependencieslisted

# Change Dependencies Change external dependencies through primary evidence, the repository's native tooling, and a verified compatibility boundary. Read `references/evidence.md` when compatibility, supply-chain risk, or update policy is material. If delegation is explicitly authorized, use `delegate-work` to route current compatibility research to a documentation specialist and keep implementation ownership separate. ## Establish the change - Identify the exact package, current and target versions, reason, affected manifests and lockfiles, supported runtimes, platforms, and deployment constraints. - For an addition, prove the existing platform or dependency set does not already provide the needed capability. - For a replacement or removal, trace every direct consumer, generated artifact, plugin, peer dependency, and runtime integration before editing. - Keep unrelated dependency churn out of scope. ## Inspect the baseline - Read package-manager configuration, manifests, lockfiles, toolchain pins, workspace boundaries, and the dependency's real call sites. - Inspect the resolved dependency graph, including relevant transitive and peer dependencies. - Run the smallest meaningful baseline: deterministic install or restore, static checks, focused tests, build, and a representative runtime path. - Record existing failures separately. Do not attribute them to the dependency change without evidence. ## Verify compatibility - Prefer official package metadata, release notes,