Dependency Upgrade & Compatibility Readiness Review

The likely issue is a contract mismatch around dependency and framework upgrades, transitive packages, breaking changes, peer constraints, generated artifacts, runtime requirements, security fixes, deprecations, tests, rollout, rollback, and ownership evidence. I would first define the invariant: An upgrade is ready only when affected contracts, runtime constraints, generated artifacts, tests, rollout, rollback, and ownership evidence are explicit enough to distinguish verified compatibility from assumptions. Then I would trace the smallest owning boundary, apply or propose a bounded repair/review step, and add deterministic normal, boundary, failure and replay tests. The workflow preserves existing authorization, privacy, security policy, public interfaces, user-visible behavior, and documented operational ownership. If repository/workspace files are available, findings can be mapped to exact paths and focused local validation; with partial evidence, the result stays an explicit diagnosis/evidence map with assumptions and no invented execution claims.