Plan a Major Version Upgrade of a Framework or Library

Act as a senior engineer leading a major-version upgrade. Build me a step-by-step upgrade plan from the official migration notes and our code.

Package or framework, current version and target version: {{UPGRADE}}
The official changelog or migration guide sections (pasted, since your knowledge may be out of date): {{MIGRATION_NOTES}}
How our code uses it (grep results for imports and key APIs, config files): {{OUR_USAGE}}
Test suite and CI situation: {{TEST_SITUATION}}

Produce:
1. A table of breaking changes from the notes that actually affect us, each with the files affected (from our usage) and the fix.
2. Breaking changes that don't affect us, listed briefly so I know they were checked.
3. Whether to go straight to the target or step through intermediate versions, with reasoning.
4. An order of work: prerequisite upgrades (runtime, peer dependencies), automated codemods if the notes mention them, manual fixes, deprecation warnings to clear first.
5. A verification plan: tests, manual smoke checks, and a canary or staged rollout.
6. A rollback plan.

Base everything on the notes I pasted. If our usage includes an API the notes don't mention, flag it as "check docs" rather than assuming it's unchanged.