Merge pull request #21 from OnlyTerp/devin/1781761103-migration-path-consistency

* Update migration Paths 7-8 to point at current 2026.6.4 baseline

Paths 9/10/12 were updated in #20 but Paths 7 and 8 still referenced superseded
endpoints (2026.5.22 / 2026.5.24-beta.1). Point them through Path 10 and Path 12.

Co-Authored-By: Rob <onerobby@gmail.com>

* Path 7: route through Path 8 before Path 10/12

Path 7 ends at 2026.4.29-beta.1; Path 10 accepts 5.12/5.14-beta.1, so the chain
must pass through Path 8 (4.29-beta.1 -> 5.12) first.

Co-Authored-By: Rob <onerobby@gmail.com>

---------

Co-authored-by: Devin AI <158243242+devin-ai-integration[bot]@users.noreply.github.com>

Author: OnlyTerp

part26-migration-guide.md

@@ -184,7 +184,7 @@ This is the first late-April stability jump. It is worth doing before moving to
 
 ## Path 7: v2026.4.27 stable → v2026.4.29-beta.1
 
-Former beta jump. If you're upgrading today, treat this as the conceptual migration step for memory/messaging behavior and then continue to 2026.5.22 stable.
+Former beta jump. If you're upgrading today, treat this as the conceptual migration step for memory/messaging behavior, then continue through Path 8, Path 10, and Path 12 to the current 2026.6.4 stable baseline.
 
 **What changes (the ones you should act on immediately):**
 
@@ -208,7 +208,7 @@ Former beta jump. If you're upgrading today, treat this as the conceptual migrat
 
 ## Path 8: v2026.4.29-beta.1 → v2026.5.12 stable
 
-This is the former May stable baseline. Do this as the compatibility checkpoint, then continue to Path 10 before experimenting with 2026.5.24-beta.1.
+This is the former May stable baseline. Do this as the compatibility checkpoint, then continue through Path 10 and Path 12 to the current 2026.6.4 stable baseline (test 2026.5.24-beta.1 only if you need a specific feature before it lands stable).
 
 **What changes (the ones you should act on immediately):**