Scope genlocke retireHoF to HoF team instead of all alive Pokemon

advance_leg() now checks current_run.hof_encounter_ids first and only
retires those Pokemon and their families. Falls back to all alive
non-shiny Pokemon when no HoF team is selected (backwards compatible).

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

.beans/nuzlocke-tracker-h3fw--use-hof-team-for-genlocke-retirement-instead-of-al.md

@@ -1,11 +1,11 @@
 ---
 # nuzlocke-tracker-h3fw
 title: Use HoF team for genlocke retirement instead of all alive Pokemon
-status: todo
+status: in-progress
 type: task
 priority: normal
 created_at: 2026-02-09T09:15:00Z
-updated_at: 2026-02-09T09:15:03Z
+updated_at: 2026-02-09T09:26:16Z
 parent: nuzlocke-tracker-8w9s
 blocking:
     - nuzlocke-tracker-25mh
@@ -36,5 +36,5 @@ select(Encounter.pokemon_id).where(
 - Update the frontend `RunEncounters.tsx` to also scope `retiredPokemonIds` correctly (no change needed — it reads from the backend response)
 
 ## Checklist
-- [ ] Update `advance_leg()` to prefer `hof_encounter_ids` over all-alive query
-- [ ] Verify backwards compatibility when `hof_encounter_ids` is null
+- [x] Update `advance_leg()` to prefer `hof_encounter_ids` over all-alive query
+- [x] Verify backwards compatibility when `hof_encounter_ids` is null

.beans/nuzlocke-tracker-lqf2--fix-hooks-order-violation-in-runencounters.md

@@ -0,0 +1,11 @@
+---
+# nuzlocke-tracker-lqf2
+title: Fix hooks order violation in RunEncounters
+status: completed
+type: bug
+priority: critical
+created_at: 2026-02-09T09:22:14Z
+updated_at: 2026-02-09T09:22:58Z
+---
+
+The hofTeam useMemo was placed after early returns, causing a 'Rendered more hooks than during the previous render' error and blank page.