Add Python tool scaffold for PokeDB data import

Set up tools/import-pokedb/ with CLI, JSON loader, and output models.
Replaces the Go/PokeAPI approach with local PokeDB.org JSON processing.

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

.beans/nuzlocke-tracker-vdks--validation-and-full-generation.md

@@ -0,0 +1,29 @@
+---
+# nuzlocke-tracker-vdks
+title: Validation and full generation
+status: todo
+type: task
+created_at: 2026-02-11T08:43:29Z
+updated_at: 2026-02-11T08:43:29Z
+parent: nuzlocke-tracker-bs05
+---
+
+Validate the new tool's output against existing data and generate seed data for all games.
+
+## Checklist
+
+- [ ] **Diff against existing data**: For games we already have PokeAPI-sourced data for, compare the PokeDB output. Identify and investigate discrepancies:
+  - Missing routes or encounters
+  - Different encounter rates
+  - Different level ranges
+  - Missing or extra pokemon
+- [ ] **Fix discrepancies**: Adjust mappings, parsing, or aggregation logic to resolve legitimate differences. Document cases where PokeDB provides better/different data than PokeAPI.
+- [ ] **Generate for all games**: Run the tool for every game version in `version_groups.json`. Verify output is valid JSON and structurally correct.
+- [ ] **New game coverage**: For games not previously supported (or with incomplete PokeAPI data), verify the output looks reasonable by spot-checking a few routes.
+- [ ] **Update route_order.json**: Add route orderings for any new games that didn't have entries. This may require manual curation.
+- [ ] **Update special_encounters.json**: Add special encounters for any new games. This may require manual curation.
+
+## Notes
+- This is the final validation step before we can replace PokeAPI as the data source
+- Some discrepancies are expected — PokeDB may have more complete data than PokeAPI
+- Route ordering for new games will likely need manual work