1# Phase 4: Summarize & Validate
2 
3Load this file when executing Phase 4. Refer back to [`upgrade-success-criteria`](../rules/upgrade-success-criteria.md) and [`upgrade-strategy`](../rules/upgrade-strategy.md) for success criteria and strategy, and [`../rules/troubleshooting.md`](../rules/troubleshooting.md) when failures occur.
4 
51. Create `.github/java-upgrade/{RUN_ID}/summary.md` from the Summary Template — replace placeholders and follow HTML-comment instructions to populate final results.
62. Apply the validation checklist from the Migration Guidelines:
7   - Migrated project passes compilation
8   - All tests pass — don't silently skip tests
9   - No legacy SDK dependencies/references exist
10   - If `azure-sdk-bom` is used, ensure no explicit version dependencies for Azure libraries in the BOM
11   - For each migration guide recorded during migration, fetch and verify the migrated code follows the guide's recommendations. Fix any deviations.
123. Populate `summary.md` (Upgrade Result, Tech Stack Changes, Commits, Challenges, Limitations, Next Steps)
134. Clean up temp files; remove HTML comments from all `.md` files
145. Verify all goals met
15