Prioritize beans and add pre-commit hooks task

Game Data Cleanup → critical, Tests → high, pre-commit hooks → high,
boss battles → low, remaining epics → deferred.

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

.beans/nuzlocke-tracker-0jec--soullink-tracking.md

@@ -3,8 +3,9 @@
 title: Soullink tracking
 status: draft
 type: epic
+priority: deferred
 created_at: 2026-02-09T07:56:50Z
-updated_at: 2026-02-09T07:56:50Z
+updated_at: 2026-02-10T12:05:43Z
 ---
 
 Track a **soullink** — a multiplayer nuzlocke variant where two (or more) players play through the same game simultaneously. Each player's Pokemon are **linked** in pairs: if one partner's Pokemon dies, the linked Pokemon on the other player's side dies too.

.beans/nuzlocke-tracker-d98o--user-account-integration.md

@@ -3,9 +3,9 @@
 title: User Account integration
 status: draft
 type: epic
-priority: normal
+priority: deferred
 created_at: 2026-02-04T16:17:01Z
-updated_at: 2026-02-09T07:56:53Z
+updated_at: 2026-02-10T12:05:43Z
 blocking:
     - nuzlocke-tracker-0jec
 ---

.beans/nuzlocke-tracker-f0fm--romhack-integration.md

@@ -3,8 +3,9 @@
 title: Romhack Integration
 status: draft
 type: epic
+priority: deferred
 created_at: 2026-02-04T15:48:34Z
-updated_at: 2026-02-04T15:48:34Z
+updated_at: 2026-02-10T12:05:43Z
 ---
 
 Support for tracking Nuzlocke runs in popular Pokémon romhacks, which often feature custom routes, modified Pokémon, new regional forms, and altered encounter tables.

.beans/nuzlocke-tracker-igl3--name-generation.md

@@ -3,9 +3,9 @@
 title: Name Generation
 status: draft
 type: epic
-priority: normal
+priority: deferred
 created_at: 2026-02-05T13:45:15Z
-updated_at: 2026-02-08T20:33:36Z
+updated_at: 2026-02-10T12:05:44Z
 ---
 
 For nuzlockes I want to implement name generation. The user should be able to provide a naming scheme or a list of nick names that can then be selected when a new encounter is registered.

.beans/nuzlocke-tracker-neqv--add-detailed-boss-battle-information.md

@@ -3,8 +3,9 @@
 title: Add detailed boss battle information
 status: todo
 type: feature
+priority: low
 created_at: 2026-02-08T11:21:22Z
-updated_at: 2026-02-08T11:21:22Z
+updated_at: 2026-02-10T12:05:43Z
 ---
 
 Enhance boss battles with more detailed information for each boss pokemon and the player's team.

.beans/nuzlocke-tracker-rb0p--implement-pre-commit-hooks-for-linting.md

@@ -0,0 +1,19 @@
+---
+# nuzlocke-tracker-rb0p
+title: Implement pre-commit hooks for linting
+status: todo
+type: task
+priority: high
+created_at: 2026-02-10T12:05:39Z
+updated_at: 2026-02-10T12:05:39Z
+---
+
+Set up pre-commit hooks to automatically run linting before every commit, catching issues before they reach the pipeline.
+
+## Checklist
+
+- [ ] Install and configure a pre-commit framework (e.g. `pre-commit` for Python, `husky` + `lint-staged` for the frontend, or a unified approach)
+- [ ] Add backend hook: `ruff check` + `ruff format --check` on staged Python files
+- [ ] Add frontend hook: `eslint` + `tsc` on staged TS/TSX files
+- [ ] Update CI workflow to replace lint checks with test runs once the test suite is in place
+- [ ] Document the pre-commit setup in CLAUDE.md or DEPLOYMENT.md

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

@@ -3,8 +3,9 @@
 title: Game Data Cleanup
 status: todo
 type: epic
+priority: critical
 created_at: 2026-02-10T08:58:36Z
-updated_at: 2026-02-10T08:58:36Z
+updated_at: 2026-02-10T12:05:43Z
 ---
 
 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).

.beans/nuzlocke-tracker-yzpb--implement-unit-integration-tests.md

@@ -3,8 +3,9 @@
 title: Implement Unit & Integration Tests
 status: draft
 type: epic
+priority: high
 created_at: 2026-02-10T09:32:47Z
-updated_at: 2026-02-10T09:32:47Z
+updated_at: 2026-02-10T12:05:43Z
 ---
 
 Add comprehensive unit and integration test coverage to both the backend (FastAPI/Python) and frontend (React/TypeScript). The project currently has zero tests — pytest is configured in pyproject.toml with pytest-asyncio and httpx, but no actual test files exist. The frontend has no test tooling at all.