changelog-to-upgrade-planlisted

# Changelog To Upgrade Plan ## Purpose Convert release notes into an actionable upgrade plan without losing breaking changes or operational risk. ## Fit - Use when release notes or migration docs need to become owner-ready upgrade work. - Do not use when the change is a direct version bump with no changelog, impact surface, or rollout concern. ## Inputs - Changelog, migration guide, release announcement, or dependency diff. - Current version and target version. - Known app usage, test commands, deployment path, and rollback constraints. ## Workflow 1. Extract breaking changes, deprecations, security fixes, and behavior changes. 2. Map changes to affected code paths, config, users, and runtime environments. 3. Classify each item as required, optional, risky, or informational. 4. Define test coverage needed before rollout. 5. Create rollback and monitoring notes for the first deployment. ## Output Produce Markdown with: - Upgrade Snapshot - Impact Map - Required Changes - Test Plan - Rollout And Rollback - Open Questions ## Validation - Version numbers and dates are copied exactly from evidence. - Breaking changes are not buried under optional improvements. - Test recommendations match the affected surfaces. - Rollback is realistic for the repository or service. - Unknown local usage is labeled as an assumption.