Add Game Data Cleanup epic with subtasks

Track the work needed to audit and complete encounter data and route
ordering across all supported games. Covers automated source exploration,
Gen 8+ stub population, ORAS/Let's Go completion, route ordering for
Gen 5+, Gen 1-4 ordering audit, and special encounters review.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

.beans/nuzlocke-tracker-rzu4--game-data-cleanup.md

@@ -0,0 +1,31 @@
+---
+# nuzlocke-tracker-rzu4
+title: Game Data Cleanup
+status: todo
+type: epic
+created_at: 2026-02-10T08:58:36Z
+updated_at: 2026-02-10T08:58:36Z
+---
+
+Audit and fix the game seed data to ensure all supported games have accurate encounter data and correct route ordering. PokeAPI provides a solid basis for Gen 1-7, but later games (Gen 8+) have no encounter data at all (stub/null JSON files), and route ordering is only defined for Gen 1-4. This is mostly manual work, but we should explore automated/semi-automated options where possible (e.g. scraping community wikis, leveraging existing fan-curated datasets).
+
+## Current State
+
+### Encounter data status:
+- **Complete (from PokeAPI):** Red, Blue, Yellow, FireRed, LeafGreen, Gold, Silver, Crystal, HeartGold, SoulSilver, Ruby, Sapphire, Emerald, Diamond, Pearl, Platinum, Black, White, Black 2, White 2, X, Y, Sun, Moon, Ultra Sun, Ultra Moon
+- **Stub/null (no data):** Sword, Shield, Scarlet, Violet, Brilliant Diamond, Shining Pearl, Legends Arceus
+- **Minimal/partial:** Omega Ruby, Alpha Sapphire (96 lines each), Let's Go Pikachu/Eevee (134 lines each), Legends Z-A (1298 lines, partially complete)
+
+### Route ordering status (route_order.json):
+- **Defined:** firered-leafgreen (+ aliases: red-blue, yellow, lets-go), heartgold-soulsilver (+ aliases: gold-silver, crystal), emerald (+ aliases: ruby-sapphire, omega-ruby-alpha-sapphire), platinum
+- **Missing:** diamond-pearl, black-white, black-2-white-2, x-y, sun-moon, ultra-sun-ultra-moon, sword-shield, brilliant-diamond-shining-pearl, scarlet-violet, legends-arceus, legends-z-a
+
+### Special considerations:
+- Existing PokeAPI data may have inaccurate encounter rates or missing special encounters (gifts, fossils, starters)
+- Sub-area grouping (children) may need review — some routes are split into too many/few sub-areas
+- The `special_encounters.json` file handles manual additions but may be incomplete for later gens
+
+## Approach
+- Manual curation is the primary approach for most tasks
+- Explore automated options: community datasets (e.g. veekun/pokedex, PokeAPI CSV data), wiki scraping, or other structured data sources
+- Use the admin panel and export CLI to verify/edit data after seeding