Merge pull request 'Complete Game Data Cleanup epic' (#16) from develop into main

Reviewed-on: TheFurya/nuzlocke-tracker#16

.beans/archive/nuzlocke-tracker-12cw--crash-crash-user-model-run-ownership-and-visibilit.md

@@ -1,32 +0,0 @@
----
-# nuzlocke-tracker-12cw
-title: 'Crash: Crash: User model, run ownership, and visibility migration'
-status: completed
-type: bug
-priority: high
-created_at: 2026-03-20T19:13:06Z
-updated_at: 2026-03-20T19:21:27Z
-parent: nuzlocke-tracker-bw1m
-blocking:
-    - nuzlocke-tracker-gez0
----
-
-Agent crashed while working on nuzlocke-tracker-gez0.
-
-## Exit Code
-1
-
-## Last Output
-```
-Failed to authenticate. API Error: 401 {"type":"error","error":{"type":"authentication_error","message":"OAuth token has expired. Please obtain a new token or refresh your existing token."},"request_id":"req_011CZEs5bfrivterCHgjXoWG"}
-
-```
-
-## Context
-- Bean: nuzlocke-tracker-gez0
-- Title: Crash: User model, run ownership, and visibility migration
-- Type: bug
-
-## Reasons for Scrapping
-
-This crash was caused by an expired OAuth token during agent execution - a transient session management issue, not a code bug. The underlying task (nuzlocke-tracker-bnhh) remains blocked by nuzlocke-tracker-2561 (Supabase setup) and can be resumed once that prerequisite is complete.

.beans/archive/nuzlocke-tracker-1y09--enforce-feature-branch-workflow-for-agents.md

@@ -1,68 +0,0 @@
----
-# nuzlocke-tracker-1y09
-title: Enforce feature branch workflow for agents
-status: completed
-type: task
-priority: high
-created_at: 2026-03-20T20:48:21Z
-updated_at: 2026-03-20T21:01:47Z
----
-
-## Problem
-
-Agents sometimes commit directly to `develop` instead of creating feature branches. The CLAUDE.md branching strategy documents the intent but isn't enforced — agents can ignore it.
-
-## Solution
-
-Add a Claude Code `PreToolCall` hook that blocks `git commit` when the current branch is `develop` or `main`, forcing agents to always work on `feature/*` branches. Also update CLAUDE.md to document the stricter workflow.
-
-**Scope:** Agent-only enforcement (humans can still commit on `develop` if needed).
-
-## Changes
-
-### 1. Claude Code hook (`.claude/settings.json`)
-
-Add a `PreToolCall` hook that:
-- Triggers on `Bash` tool calls containing `git commit`
-- Checks the current branch name via `git branch --show-current`
-- **Blocks** if branch is `develop` or `main` with a clear error message
-- **Allows** if branch matches `feature/*` or any other pattern
-
-```json
-{
-  "hooks": {
-    "PreToolCall": [
-      {
-        "matcher": "Bash",
-        "hooks": [
-          {
-            "type": "command",
-            "command": "bash -c 'if echo \"$TOOL_INPUT\" | grep -q \"git commit\"; then BRANCH=$(git branch --show-current); if [ \"$BRANCH\" = \"develop\" ] || [ \"$BRANCH\" = \"main\" ]; then echo \"BLOCK: Cannot commit directly to $BRANCH. Create a feature branch first: git checkout -b feature/<name>\"; exit 2; fi; fi'"
-          }
-        ]
-      }
-    ]
-  }
-}
-```
-
-> Note: Exit code 2 blocks the tool call. The hook should parse `$TOOL_INPUT` (JSON) to check for git commit commands.
-
-### 2. CLAUDE.md update
-
-Update the "Branching Strategy" section to add:
-
-- **Never commit directly to `develop` or `main`.** Always create a `feature/*` branch first.
-- When starting an **epic**, create `feature/<epic-title-slug>` off `develop`
-- When starting a **standalone task/bug** (no parent epic), create `feature/<task-title-slug>` off `develop`
-- Each task within an epic gets its own commit(s) on the epic's feature branch
-- Branch naming: use a kebab-case slug of the bean title (e.g., `feature/add-auth-system`)
-- When the epic/task is complete, squash merge into `develop`
-
-## Checklist
-
-- [ ] Add `PreToolCall` hook to `.claude/settings.json` that blocks commits on `develop`/`main`
-- [ ] Test hook by verifying it blocks a commit attempt on `develop`
-- [ ] Test hook by verifying it allows a commit on a `feature/*` branch
-- [ ] Update CLAUDE.md branching strategy with new workflow rules
-- [ ] Verify hook handles edge cases (e.g., `git commit --amend`, `git commit -m "..."`)

.beans/archive/nuzlocke-tracker-2561--supabase-auth-project-setup-and-provider-config.md

@@ -1,21 +0,0 @@
----
-# nuzlocke-tracker-2561
-title: Supabase Auth project setup and provider config
-status: completed
-type: task
-priority: normal
-created_at: 2026-03-20T15:28:08Z
-updated_at: 2026-03-20T20:04:40Z
-parent: nuzlocke-tracker-d98o
----
-
-Set up Supabase project with Auth enabled. Configure Google and Discord as social login providers. Add Supabase URL and keys to backend/frontend environment variables. This is the foundation — nothing else can start until the Supabase project exists.
-
-## Checklist
-- [ ] Create Supabase project (or configure existing one)
-- [ ] Enable email/password auth
-- [ ] Configure Google OAuth provider
-- [ ] Configure Discord OAuth provider
-- [x] Add SUPABASE_URL, SUPABASE_ANON_KEY, SUPABASE_JWT_SECRET to backend env
-- [x] Add VITE_SUPABASE_URL, VITE_SUPABASE_ANON_KEY to frontend env
-- [x] Document setup steps for local development

.beans/archive/nuzlocke-tracker-2zwg--protect-frontend-routes-with-protectedroute-and-ad.md

@@ -1,38 +0,0 @@
----
-# nuzlocke-tracker-2zwg
-title: Protect frontend routes with ProtectedRoute and AdminRoute
-status: completed
-type: task
-priority: normal
-created_at: 2026-03-21T10:06:20Z
-updated_at: 2026-03-21T10:19:41Z
-parent: nuzlocke-tracker-ce4o
-blocked_by:
-    - nuzlocke-tracker-5svj
----
-
-Use the existing \`ProtectedRoute\` component (currently unused) and create an \`AdminRoute\` component to guard routes in \`App.tsx\`.
-
-## Checklist
-
-- [x] Wrap \`/runs/new\` and \`/genlockes/new\` with \`ProtectedRoute\` (requires login)
-- [x] Create \`AdminRoute\` component that checks \`isAdmin\` from \`useAuth()\`, redirects to \`/\` with a toast/message if not admin
-- [x] Wrap all \`/admin/*\` routes with \`AdminRoute\`
-- [x] Ensure \`/runs\` and \`/runs/:runId\` remain accessible to everyone (public run viewing)
-- [x] Verify deep-linking works (e.g., visiting \`/admin/games\` while logged out redirects to login, then back to \`/admin/games\` after auth)
-
-## Files to change
-
-- \`frontend/src/App.tsx\` — wrap routes
-- \`frontend/src/components/ProtectedRoute.tsx\` — already exists, verify it works
-- \`frontend/src/components/AdminRoute.tsx\` — new file
-
-## Summary of Changes
-
-Implemented frontend route protection:
-
-- **ProtectedRoute**: Wraps `/runs/new` and `/genlockes/new` - redirects unauthenticated users to `/login` with return location preserved
-- **AdminRoute**: New component that checks `isAdmin` from `useAuth()`, redirects non-admins to `/` with a toast notification
-- **Admin routes**: Wrapped `AdminLayout` with `AdminRoute` to protect all `/admin/*` routes
-- **Public routes**: `/runs` and `/runs/:runId` remain accessible to everyone
-- **Deep-linking**: Location state preserved so users return to original route after login

.beans/archive/nuzlocke-tracker-3mwb--fix-typescript-build-errors-in-runencounterstsx.md

@@ -1,13 +0,0 @@
----
-# nuzlocke-tracker-3mwb
-title: Fix TypeScript build errors in RunEncounters.tsx
-status: completed
-type: bug
-priority: normal
-created_at: 2026-03-21T11:24:09Z
-updated_at: 2026-03-21T11:25:37Z
----
-
-Two TS errors blocking production build:\n1. Line 693: `(typeof bossResults)[number]` fails because bossResults is `BossResult[] | undefined`\n2. Line 1601: Parameter 'tm' implicitly has 'any' type
-
-## Summary of Changes\n\nFixed two TypeScript errors in RunEncounters.tsx:\n1. Used explicit `BossResult` type instead of `(typeof bossResults)[number]`\n2. Added `BossResultTeamMember` type annotation to `tm` parameter\n\nPR: #71

.beans/archive/nuzlocke-tracker-3psa--crash-bug-typescript-build-fails-due-to-optional-p.md

@@ -1,34 +0,0 @@
----
-# nuzlocke-tracker-3psa
-title: 'Crash: Bug: TypeScript build fails due to optional property type mismatches in journal components'
-status: completed
-type: bug
-priority: high
-tags:
-    - failed
-created_at: 2026-03-20T19:00:37Z
-updated_at: 2026-03-20T19:17:34Z
-parent: nuzlocke-tracker-bw1m
-blocking:
-    - nuzlocke-tracker-d5ht
----
-
-Agent crashed while working on nuzlocke-tracker-d5ht.
-
-## Exit Code
-1
-
-## Last Output
-```
-Failed to authenticate. API Error: 401 {"type":"error","error":{"type":"authentication_error","message":"OAuth token has expired. Please obtain a new token or refresh your existing token."},"request_id":"req_011CZEr8PbYrEx4DTBz6e1Z7"}
-
-```
-
-## Context
-- Bean: nuzlocke-tracker-d5ht
-- Title: Bug: TypeScript build fails due to optional property type mismatches in journal components
-- Type: bug
-
-## Summary of Changes
-
-Resolved by nuzlocke-tracker-xsdr - TypeScript build errors fixed.

.beans/archive/nuzlocke-tracker-52rw--bug-tailwind-typography-plugin-unresolvable-in-doc.md

@@ -1,50 +0,0 @@
----
-# nuzlocke-tracker-52rw
-title: 'Bug: Tailwind typography plugin unresolvable in Docker dev container'
-status: completed
-type: bug
-priority: deferred
-created_at: 2026-03-20T19:23:06Z
-updated_at: 2026-03-20T20:26:50Z
----
-
-## Problem
-
-After commit 1cd1389 added `@tailwindcss/typography` and the `@plugin '@tailwindcss/typography'` directive in `index.css`, the frontend Docker dev container fails to start with:
-
-```
-[plugin:@tailwindcss/vite:generate:serve] Can't resolve '@tailwindcss/typography' in '/app/src'
-```
-
-## Root Cause
-
-The `docker-compose.yml` volume mount `./frontend/src:/app/src:cached` overlays the host's `src/` directory into the container. The new `src/index.css` contains `@plugin '@tailwindcss/typography'`, which Tailwind's Vite plugin tries to resolve starting from `/app/src/`. 
-
-Two possible causes:
-1. **Stale Docker image** — If the image wasn't rebuilt after `@tailwindcss/typography` was added to `package.json`, the container's `node_modules` doesn't have the package. Fix: `docker compose build frontend` or `docker compose up --build`.
-2. **Resolution path issue** — Tailwind v4's `@plugin` resolution may not walk up to `/app/node_modules` from `/app/src/index.css`. This would be a persistent issue even after rebuilding.
-
-## Fix
-
-- [x] Rebuild the Docker image and test if the error persists (FIXED - error was due to stale image)
-- [~] If it persists after rebuild, add volume mounts (N/A - not needed, rebuild fixed it)
-- [~] If resolution is the issue, consider moving the `@plugin` directive (N/A - not needed)
-- [x] Verify the frontend starts correctly in Docker with `docker compose up frontend`
-
-## Files
-
-- `docker-compose.yml` (line 27: src volume mount)
-- `frontend/src/index.css` (line 2: `@plugin '@tailwindcss/typography'`)
-- `frontend/package.json` (line 22: `@tailwindcss/typography` dependency)
-- `frontend/Dockerfile`
-
-## Summary of Changes
-
-The issue was caused by a **stale Docker image** that was built before `@tailwindcss/typography` was added to `package.json`. The cached `npm ci` layer didn't include the new dependency.
-
-**Resolution:** Running `docker compose build frontend` rebuilt the image with the updated dependencies. After rebuild:
-- The frontend container starts correctly
-- The `@plugin '@tailwindcss/typography'` directive resolves successfully
-- The `.prose` typography styles are included in the compiled CSS
-
-**No code changes required.** This is a documentation of the root cause for future reference - users experiencing this error should rebuild their Docker images.

.beans/archive/nuzlocke-tracker-5svj--expose-admin-status-to-frontend-via-user-api.md

@@ -1,35 +0,0 @@
----
-# nuzlocke-tracker-5svj
-title: Expose admin status to frontend via user API
-status: completed
-type: task
-priority: normal
-created_at: 2026-03-21T10:06:20Z
-updated_at: 2026-03-21T10:23:04Z
-parent: nuzlocke-tracker-ce4o
-blocked_by:
-    - nuzlocke-tracker-dwah
----
-
-The frontend needs to know if the current user is an admin so it can show/hide the Admin nav link and protect admin routes client-side.
-
-## Checklist
-
-- [x] Add `is_admin` field to the user response schema (`/api/users/me` endpoint)
-- [x] Update `AuthContext` to fetch `/api/users/me` after login and store `isAdmin` in context
-- [x] Expose `isAdmin` boolean from `useAuth()` hook
-- [x] Handle edge case: user exists in Supabase but not yet in local DB (first login creates user row with `is_admin=false`)
-
-## Files to change
-
-- `backend/src/app/schemas/user.py` or equivalent — add `is_admin` to response
-- `backend/src/app/api/users.py` — ensure `/me` returns `is_admin`
-- `frontend/src/contexts/AuthContext.tsx` — fetch and store admin status
-
-## Summary of Changes
-
-Added `isAdmin` field to frontend auth system:
-
-- **Backend**: Added `is_admin: bool = False` to `UserResponse` schema in `backend/src/app/api/users.py`
-- **Frontend**: Updated `AuthContext` to fetch `/api/users/me` after login and expose `isAdmin` boolean
-- Edge case handled: `syncUserProfile` returns `false` if API call fails (new user auto-created with `is_admin=false` by backend)

.beans/archive/nuzlocke-tracker-7y9z--fix-test-failures-from-admin-auth-changes.md

@@ -1,13 +0,0 @@
----
-# nuzlocke-tracker-7y9z
-title: Fix test failures from admin auth changes
-status: completed
-type: bug
-priority: normal
-created_at: 2026-03-21T10:33:32Z
-updated_at: 2026-03-21T10:39:18Z
----
-
-After adding require_admin to admin endpoints, tests fail:\n1. test_pokemon.py: Write endpoints return 401 because tests use unauthenticated client instead of admin client\n2. test_runs.py: mock_auth_user has id='test-user-123' which is not a valid UUID, causing ValueError in UUID(user.id)\n\nFix: add admin_override fixture, admin_client fixture, use valid UUID for mock user, update test_pokemon.py to use admin_client for write ops.
-
-## Summary of Changes\n\n- Added `admin_override` and `admin_client` fixtures to conftest.py that override both `require_admin` and `get_current_user`\n- Changed mock user ID from `test-user-123` to a valid UUID4\n- Updated test_pokemon.py, test_games.py, and test_genlocke_boss.py to use `admin_client` for admin-protected endpoints\n- All 252 tests pass

.beans/archive/nuzlocke-tracker-8vev--crash-frontend-auth-flow-login-signup-session-mana.md

@@ -1,32 +0,0 @@
----
-# nuzlocke-tracker-8vev
-title: 'Crash: Frontend auth flow (login, signup, session management)'
-status: completed
-type: bug
-priority: high
-tags:
-    - failed
-created_at: 2026-03-20T19:01:00Z
-updated_at: 2026-03-20T19:21:54Z
-parent: nuzlocke-tracker-bw1m
-blocking:
-    - nuzlocke-tracker-l9xh
----
-
-Agent crashed while working on nuzlocke-tracker-l9xh.
-
-## Exit Code
-1
-
-## Last Output
-```
-Failed to authenticate. API Error: 401 {"type":"error","error":{"type":"authentication_error","message":"OAuth token has expired. Please obtain a new token or refresh your existing token."},"request_id":"req_011CZErA6rXo6bi18BfjCwD7"}
-
-```
-
-## Context
-- Bean: nuzlocke-tracker-l9xh
-- Title: Frontend auth flow (login, signup, session management)
-- Type: feature
-
-## Resolution\n\nThis was an infrastructure issue (Claude API OAuth token expired), not a code bug. Continuing work on the original feature bean (nuzlocke-tracker-l9xh).

.beans/archive/nuzlocke-tracker-9nmp--crash-crash-user-account-integration.md

@@ -1,34 +0,0 @@
----
-# nuzlocke-tracker-9nmp
-title: 'Crash: Crash: User Account integration'
-status: completed
-type: bug
-priority: high
-created_at: 2026-03-20T19:12:56Z
-updated_at: 2026-03-20T19:18:39Z
-parent: nuzlocke-tracker-bw1m
-blocking:
-    - nuzlocke-tracker-ndpz
----
-
-Agent crashed while working on nuzlocke-tracker-ndpz.
-
-## Exit Code
-1
-
-## Last Output
-```
-Failed to authenticate. API Error: 401 {"type":"error","error":{"type":"authentication_error","message":"OAuth token has expired. Please obtain a new token or refresh your existing token."},"request_id":"req_011CZEs4pUWwh8wYoPHzaGmx"}
-
-```
-
-## Context
-- Bean: nuzlocke-tracker-ndpz
-- Title: Crash: User Account integration
-- Type: bug
-
-## Resolution
-
-This crash was caused by Claude's OAuth token expiring during an agent session. This is an environmental/infrastructure issue, not a code bug. The token has been refreshed by starting a new agent session.
-
-No code changes required.

.beans/archive/nuzlocke-tracker-9xac--fix-stale-postgresql-enum-causing-test-failures.md

@@ -1,50 +0,0 @@
----
-# nuzlocke-tracker-9xac
-title: Fix stale PostgreSQL enum causing test failures
-status: completed
-type: bug
-priority: normal
-created_at: 2026-03-21T10:27:53Z
-updated_at: 2026-03-21T10:29:33Z
----
-
-## Problem
-
-The backend smoke tests fail with:
-```
-sqlalchemy.exc.DBAPIError: invalid input value for enum run_visibility: "public"
-```
-
-This happens during `Base.metadata.create_all` in the `engine` fixture (`backend/tests/conftest.py:27`).
-
-## Root Cause
-
-The `engine` fixture only calls `create_all` during setup and `drop_all` during teardown. If a previous test run was interrupted before teardown, the `run_visibility` PostgreSQL enum type persists in the test database with stale/incorrect values. On the next run, `create_all` (with `checkfirst=True` default) sees the enum exists and skips recreating it, but the existing enum lacks valid values, causing the `DEFAULT 'public'` to fail.
-
-PostgreSQL native enum types are not automatically dropped with `DROP TABLE` — they require explicit `DROP TYPE`.
-
-## Fix
-
-In the `engine` fixture at `backend/tests/conftest.py:23-31`, add `Base.metadata.drop_all` before `create_all` to ensure a clean slate:
-
-```python
-@pytest.fixture(scope="session")
-async def engine():
-    eng = create_async_engine(TEST_DATABASE_URL, echo=False)
-    async with eng.begin() as conn:
-        await conn.run_sync(Base.metadata.drop_all)   # <-- add this
-        await conn.run_sync(Base.metadata.create_all)
-    yield eng
-    async with eng.begin() as conn:
-        await conn.run_sync(Base.metadata.drop_all)
-    await eng.dispose()
-```
-
-## Checklist
-
-- [x] Add `drop_all` before `create_all` in the `engine` fixture (`backend/tests/conftest.py`)
-- [x] Verify tests pass with `pytest backend/tests/test_smoke.py`
-
-## Summary of Changes
-
-Added `drop_all` before `create_all` in the test engine fixture to ensure stale PostgreSQL enum types are cleared before recreating the schema. This prevents test failures when a previous test run was interrupted before cleanup.

.beans/archive/nuzlocke-tracker-9zpm--crash-backend-auth-middleware-and-jwt-verification.md

@@ -1,35 +0,0 @@
----
-# nuzlocke-tracker-9zpm
-title: 'Crash: Backend auth middleware and JWT verification'
-status: scrapped
-type: bug
-priority: high
-created_at: 2026-03-20T19:00:53Z
-updated_at: 2026-03-20T19:20:40Z
-parent: nuzlocke-tracker-bw1m
-blocking:
-    - nuzlocke-tracker-b311
----
-
-Agent crashed while working on nuzlocke-tracker-b311.
-
-## Exit Code
-1
-
-## Last Output
-```
-Failed to authenticate. API Error: 401 {"type":"error","error":{"type":"authentication_error","message":"OAuth token has expired. Please obtain a new token or refresh your existing token."},"request_id":"req_011CZEr9WsspBGfYrbAM9JRc"}
-
-```
-
-## Context
-- Bean: nuzlocke-tracker-b311
-- Title: Backend auth middleware and JWT verification
-- Type: task
-
-
-## Reasons for Scrapping
-
-This is not a code bug. The crash occurred because the agent's OAuth token to the Anthropic API expired during execution. This is an infrastructure/authentication issue, not an actionable bug in the nuzlocke-tracker codebase.
-
-The original task (`nuzlocke-tracker-b311`) can proceed once its actual prerequisite (`nuzlocke-tracker-2561` - Supabase Auth setup) is completed.

.beans/archive/nuzlocke-tracker-a8q0--crash-supabase-auth-project-setup-and-provider-con.md

@@ -1,32 +0,0 @@
----
-# nuzlocke-tracker-a8q0
-title: 'Crash: Supabase Auth project setup and provider config'
-status: scrapped
-type: bug
-priority: high
-created_at: 2026-03-20T19:00:47Z
-updated_at: 2026-03-20T19:19:24Z
-parent: nuzlocke-tracker-bw1m
-blocking:
-    - nuzlocke-tracker-2561
----
-
-Agent crashed while working on nuzlocke-tracker-2561.
-
-## Exit Code
-1
-
-## Last Output
-```
-Failed to authenticate. API Error: 401 {"type":"error","error":{"type":"authentication_error","message":"OAuth token has expired. Please obtain a new token or refresh your existing token."},"request_id":"req_011CZEr97WSkvKQrZSFbN2DA"}
-
-```
-
-## Context
-- Bean: nuzlocke-tracker-2561
-- Title: Supabase Auth project setup and provider config
-- Type: task
-
-## Reasons for Scrapping
-
-This crash was caused by an OAuth token expiration (401 authentication error), not a code bug. The agent's API credentials expired while it was running. This is an infrastructure issue that cannot be fixed by code changes - the original task simply needs to be retried with valid credentials.

.beans/archive/nuzlocke-tracker-actf--combine-renovate-dependency-updates-into-single-co.md

@@ -1,11 +0,0 @@
----
-# nuzlocke-tracker-actf
-title: Combine Renovate dependency updates into single commit
-status: completed
-type: task
-priority: normal
-created_at: 2026-03-20T14:22:33Z
-updated_at: 2026-03-20T14:26:38Z
----
-
-Cherry-pick all 10 Renovate dependency update branches into develop as a single combined commit. Branches: alembic, python-dotenv, react types, react-router-dom, ruff, sqlalchemy, tailwindcss-vite, tanstack-react-query, ty, vitejs-plugin-react.

.beans/archive/nuzlocke-tracker-b311--backend-auth-middleware-and-jwt-verification.md

@@ -1,47 +0,0 @@
----
-# nuzlocke-tracker-b311
-title: Backend auth middleware and JWT verification
-status: completed
-type: task
-priority: normal
-created_at: 2026-03-20T15:28:13Z
-updated_at: 2026-03-20T20:11:23Z
-parent: nuzlocke-tracker-d98o
-blocked_by:
-    - nuzlocke-tracker-2561
----
-
-Add Supabase JWT verification to the FastAPI backend. Create a reusable dependency that extracts and validates the Bearer token, resolves the current user, and provides it to endpoints. Protect all write endpoints (POST/PUT/DELETE) while leaving read endpoints open.
-
-## Checklist
-- [x] Add python-jose[cryptography] or PyJWT dependency
-- [x] Create auth dependency that extracts Bearer token from Authorization header
-- [x] Verify JWT against Supabase JWT secret
-- [x] Create `get_current_user` dependency (returns User or None)
-- [x] Create `require_auth` dependency (raises 401 if not authenticated)
-- [x] Apply `require_auth` to all write endpoints (POST, PUT, DELETE)
-- [x] Add tests for auth middleware (valid token, expired token, missing token)
-
-
-## Summary of Changes
-
-Added JWT authentication middleware to the FastAPI backend:
-
-- Added `PyJWT==2.10.1` dependency to `pyproject.toml`
-- Added Supabase config fields (`supabase_url`, `supabase_anon_key`, `supabase_jwt_secret`) to `core/config.py`
-- Created `core/auth.py` with:
-  - `AuthUser` dataclass for authenticated user info
-  - `_extract_token()` to parse Bearer tokens from Authorization header
-  - `_verify_jwt()` to validate tokens against Supabase JWT secret (HS256 with "authenticated" audience)
-  - `get_current_user()` dependency that returns `AuthUser | None`
-  - `require_auth()` dependency that raises 401 if not authenticated
-- Applied `require_auth` to all write endpoints (POST, PUT, PATCH, DELETE) in:
-  - `runs.py` (3 endpoints)
-  - `encounters.py` (4 endpoints)
-  - `genlockes.py` (7 endpoints)
-  - `bosses.py` (9 endpoints)
-  - `journal_entries.py` (3 endpoints)
-  - `games.py` (9 endpoints)
-- Added `tests/test_auth.py` with tests for valid/expired/invalid/missing tokens
-- Updated `tests/conftest.py` with `auth_client` fixture for tests requiring authentication
-- Updated `test_games.py` and `test_runs.py` to use `auth_client` for write operations

.beans/archive/nuzlocke-tracker-bnhh--user-model-run-ownership-and-visibility-migration.md

@@ -1,37 +0,0 @@
----
-# nuzlocke-tracker-bnhh
-title: User model, run ownership, and visibility migration
-status: completed
-type: task
-priority: normal
-created_at: 2026-03-20T15:28:18Z
-updated_at: 2026-03-20T20:16:39Z
-parent: nuzlocke-tracker-d98o
-blocked_by:
-    - nuzlocke-tracker-2561
----
-
-Create a User model synced from Supabase Auth. Add owner_id FK to runs table. Add visibility column (public/private) to runs with default public. Existing runs will have NULL owner_id (unowned).
-
-## Checklist
-- [x] Create User model (id matches Supabase user UUID, email, display_name, created_at)
-- [x] Alembic migration: create users table
-- [x] Alembic migration: add owner_id (nullable FK to users) and visibility (enum: public/private, default public) to runs table
-- [x] Update Run model with owner relationship and visibility field
-- [x] Create user sync endpoint or webhook (on first login, upsert user record from Supabase JWT claims)
-- [x] Update RunResponse schema to include owner and visibility
-- [x] Add visibility enforcement: private runs return 403 unless requester is owner
-
-
-## Summary of Changes
-
-- Created `User` model in `backend/src/app/models/user.py` with UUID primary key (matching Supabase), email, display_name, and created_at fields
-- Added Alembic migrations: `n5c6d7e8f9a0_create_users_table.py` and `o6d7e8f9a0b1_add_owner_and_visibility_to_runs.py`
-- Updated `NuzlockeRun` model with `owner_id` FK, `visibility` enum (public/private), and `owner` relationship
-- Created `POST /users/me` endpoint for user sync on first login (upserts from JWT claims)
-- Added `GET /users/me` and `PATCH /users/me` for user profile management
-- Updated `RunResponse` and `RunDetailResponse` schemas with `owner` and `visibility` fields
-- Implemented visibility enforcement in `list_runs`, `get_run`, `update_run`, and `delete_run`
-  - Private runs return 403 unless requester is owner
-  - Unowned runs (legacy) remain accessible to all
-  - Run list filters to show only public runs + user's own private runs

.beans/archive/nuzlocke-tracker-bw1m--errors.md

@@ -1,11 +0,0 @@
----
-# nuzlocke-tracker-bw1m
-title: Errors
-status: completed
-type: epic
-priority: normal
-created_at: 2026-03-20T15:19:43Z
-updated_at: 2026-03-20T15:39:27Z
----
-
-Container for crash and blocker beans created by Talos.

.beans/archive/nuzlocke-tracker-ce4o--auth-aware-ui-and-role-based-access-control.md

@@ -1,28 +0,0 @@
----
-# nuzlocke-tracker-ce4o
-title: Auth-aware UI and role-based access control
-status: completed
-type: epic
-priority: normal
-created_at: 2026-03-21T10:05:52Z
-updated_at: 2026-03-21T10:18:47Z
----
-
-The app currently shows the same navigation menu to all users regardless of auth state. Logged-out users can navigate to protected pages (e.g., /runs/new, /admin) even though the backend rejects their requests. The admin interface has no role restriction — any authenticated user can access it.
-
-## Goals
-
-1. **Auth-aware navigation**: Menu items change based on login state (logged-out users only see public browsing options)
-2. **Route protection**: Protected routes redirect to login, admin routes require admin role
-3. **Admin role system**: Define which users are admins via a database field, enforce on both frontend and backend
-4. **Backend admin enforcement**: Admin API endpoints (games, pokemon, evolutions, bosses, routes) require admin role, not just authentication
-
-## Success Criteria
-
-- [ ] Logged-out users see only: Home, Runs (public list), Genlockes, Stats, Sign In
-- [x] Logged-out users cannot navigate to /runs/new, /genlockes/new, or /admin/*
-- [ ] Logged-in non-admin users see: New Run, My Runs, Genlockes, Stats (no Admin link)
-- [ ] Admin users see the full menu including Admin
-- [x] Backend admin endpoints return 403 for non-admin authenticated users
-- [ ] Admin role is stored in the `users` table (`is_admin` boolean column)
-- [x] Admin status is exposed to the frontend via the user API or auth context

.beans/archive/nuzlocke-tracker-cm1c--crash-crash-supabase-auth-project-setup-and-provid.md

@@ -1,32 +0,0 @@
----
-# nuzlocke-tracker-cm1c
-title: 'Crash: Crash: Supabase Auth project setup and provider config'
-status: completed
-type: bug
-priority: high
-created_at: 2026-03-20T19:12:59Z
-updated_at: 2026-03-20T19:19:28Z
-parent: nuzlocke-tracker-bw1m
-blocking:
-    - nuzlocke-tracker-a8q0
----
-
-Agent crashed while working on nuzlocke-tracker-a8q0.
-
-## Exit Code
-1
-
-## Last Output
-```
-Failed to authenticate. API Error: 401 {"type":"error","error":{"type":"authentication_error","message":"OAuth token has expired. Please obtain a new token or refresh your existing token."},"request_id":"req_011CZEs55SvwXFYVzyWoU1B9"}
-
-```
-
-## Context
-- Bean: nuzlocke-tracker-a8q0
-- Title: Crash: Supabase Auth project setup and provider config
-- Type: bug
-
-## Reasons for Scrapping
-
-This crash was caused by an OAuth token expiration (401 authentication error), not a code bug. The agent's API credentials expired while it was running. This is an infrastructure issue that cannot be fixed by code changes - the original task simply needs to be retried with valid credentials.

.beans/archive/nuzlocke-tracker-d5ht--bug-typescript-build-fails-due-to-optional-propert.md

@@ -1,38 +0,0 @@
----
-# nuzlocke-tracker-d5ht
-title: 'Bug: TypeScript build fails due to optional property type mismatches in journal components'
-status: completed
-type: bug
-priority: high
-tags:
-    - failed
-created_at: 2026-03-20T15:39:00Z
-updated_at: 2026-03-20T19:17:34Z
-parent: nuzlocke-tracker-bw1m
----
-
-The frontend TypeScript build fails with 3 errors due to `exactOptionalPropertyTypes` being enabled.
-
-## Errors
-
-1. `JournalEntryPage.tsx:76` - `bossResults` and `bosses` props passed as `undefined` to `JournalEditor`
-2. `JournalEntryPage.tsx:92` - `bossResult` and `boss` props passed as `undefined` to `JournalEntryView`
-3. `RunEncounters.tsx:1170` - `bossResults` and `bosses` props passed as `undefined` to `JournalSection`
-
-## Root Cause
-
-Optional props in interfaces are declared as `prop?: Type` but callers pass `undefined` values from React Query hooks. With `exactOptionalPropertyTypes: true`, TypeScript requires `prop?: Type | undefined` to allow explicit `undefined` values.
-
-## Fix
-
-Update the interfaces in these files:
-- `JournalEditor.tsx` lines 9-10: change to `bossResults?: BossResult[] | undefined` and `bosses?: BossBattle[] | undefined`
-- `JournalEntryView.tsx` lines 8-9: change to `bossResult?: BossResult | null | undefined` and `boss?: BossBattle | null | undefined`
-- `JournalSection.tsx` lines 9-10: change to `bossResults?: BossResult[] | undefined` and `bosses?: BossBattle[] | undefined`
-
-## Summary of Changes
-
-TypeScript build errors fixed by adding `| undefined` to optional property types in journal components:
-- `JournalEditor.tsx`: `bossResults` and `bosses` props
-- `JournalEntryView.tsx`: `bossResult` and `boss` props
-- `JournalSection.tsx`: `bossResults` and `bosses` props

.beans/archive/nuzlocke-tracker-d68l--frontend-journal-entry-editor-and-list-view.md

@@ -1,69 +0,0 @@
----
-# nuzlocke-tracker-d68l
-title: 'Frontend: Journal entry editor and list view'
-status: completed
-type: task
-priority: normal
-created_at: 2026-03-20T15:15:55Z
-updated_at: 2026-03-20T15:37:39Z
-parent: nuzlocke-tracker-mz16
-blocked_by:
-    - nuzlocke-tracker-vmto
----
-
-Create the frontend UI for writing and viewing journal entries.
-
-## Design Decisions
-- Plain markdown textarea (no WYSIWYG)
-- Images via markdown URL syntax (`![alt](url)`)
-- Blank slate — no templates
-- Private only (no sharing UI)
-
-## Checklist
-
-- [x] Add `JournalEntry` TypeScript types to `frontend/src/types/`
-- [x] Create API client functions for journal CRUD
-- [x] Create `JournalList` component — chronological list of entries for a run
-  - Show title, date, preview snippet, and linked boss (if any)
-  - Link each entry to its detail/edit view
-- [x] Create `JournalEditor` component — markdown textarea with title input
-  - Optional boss result selector dropdown (link entry to a boss battle)
-  - Preview tab to render markdown
-  - Save and delete actions
-- [x] Create `JournalEntryView` component — rendered markdown display
-- [x] Add journal section/tab to the run detail page
-- [x] Add route for journal entry detail/edit view
-
-
-## Summary of Changes
-
-Implemented the frontend journal entry editor and list view with the following components:
-
-**Types created:**
-- `frontend/src/types/journal.ts` - TypeScript types for JournalEntry, CreateJournalEntryInput, UpdateJournalEntryInput
-
-**API client created:**
-- `frontend/src/api/journal.ts` - CRUD functions for journal entries
-- `frontend/src/hooks/useJournal.ts` - React Query hooks for journal data fetching and mutations
-
-**Components created:**
-- `frontend/src/components/journal/JournalList.tsx` - Chronological list of entries with title, date, preview snippet, and linked boss display
-- `frontend/src/components/journal/JournalEditor.tsx` - Markdown textarea with title input, boss result selector, write/preview tabs, save/delete actions
-- `frontend/src/components/journal/JournalEntryView.tsx` - Rendered markdown display with entry metadata
-- `frontend/src/components/journal/JournalSection.tsx` - Wrapper component for embedding in RunEncounters page
-
-**Pages created:**
-- `frontend/src/pages/JournalEntryPage.tsx` - Standalone page for viewing/editing a single journal entry
-
-**Modified files:**
-- `frontend/src/types/index.ts` - Added journal type exports
-- `frontend/src/pages/index.ts` - Added JournalEntryPage export
-- `frontend/src/App.tsx` - Added route `/runs/:runId/journal/:entryId`
-- `frontend/src/pages/RunEncounters.tsx` - Added Encounters/Journal tab navigation with JournalSection integration
-
-**Features:**
-- Tab navigation in run detail page to switch between Encounters and Journal views
-- Create new journal entries with markdown content and optional boss battle linking
-- Edit and delete existing entries
-- Write/Preview toggle in editor
-- Rendered markdown display with full prose styling

.beans/archive/nuzlocke-tracker-dwah--add-is-admin-column-to-users-table.md

@@ -1,43 +0,0 @@
----
-# nuzlocke-tracker-dwah
-title: Add is_admin column to users table
-status: completed
-type: task
-priority: normal
-created_at: 2026-03-21T10:06:19Z
-updated_at: 2026-03-21T10:10:38Z
-parent: nuzlocke-tracker-ce4o
----
-
-Add an `is_admin` boolean column (default `false`) to the `users` table via an Alembic migration.
-
-## Checklist
-
-- [x] Create Alembic migration adding `is_admin: Mapped[bool]` column with `server_default="false"`
-- [x] Update `User` model in `backend/src/app/models/user.py`
-- [x] Run migration and verify column exists
-- [x] Seed a test admin user (or document how to set `is_admin=true` via SQL)
-
-## Files to change
-
-- `backend/src/app/models/user.py` — add `is_admin` field
-- `backend/src/app/alembic/versions/` — new migration
-
-## Summary of Changes
-
-Added `is_admin` boolean column to the `users` table:
-
-- **Migration**: `p7e8f9a0b1c2_add_is_admin_to_users.py` adds the column with `server_default='false'`
-- **Model**: Updated `User` model with `is_admin: Mapped[bool]` field
-
-### Setting admin via SQL
-
-To promote a user to admin:
-```sql
-UPDATE users SET is_admin = true WHERE email = 'admin@example.com';
-```
-
-Or by user ID:
-```sql
-UPDATE users SET is_admin = true WHERE id = '<uuid>';
-```

.beans/archive/nuzlocke-tracker-ecn3--prune-stale-seed-data-during-seeding.md

@@ -1,19 +0,0 @@
----
-# nuzlocke-tracker-ecn3
-title: Prune stale seed data during seeding
-status: completed
-type: bug
-priority: normal
-created_at: 2026-02-21T16:28:37Z
-updated_at: 2026-02-21T16:29:43Z
----
-
-Seeds only upsert (add/update), they never remove routes, encounters, or bosses that no longer exist in the seed JSON. When routes are renamed, old route names persist in production.
-
-## Fix
-
-After upserting each entity type, delete rows not present in the seed data:
-
-1. **Routes**: After upserting all routes for a version group, delete routes whose names are not in the seed set. FK cascades handle child routes and encounters.
-2. **Encounters**: After upserting encounters for a route+game, delete encounters not in the seed data for that route+game pair.
-3. **Bosses**: After upserting bosses for a version group, delete bosses with order values beyond what the seed provides.

.beans/archive/nuzlocke-tracker-elcn--add-supabase-auth-config-to-production-docker-setu.md

@@ -1,13 +0,0 @@
----
-# nuzlocke-tracker-elcn
-title: Add Supabase auth config to production Docker setup
-status: completed
-type: task
-priority: normal
-created_at: 2026-03-21T11:07:01Z
-updated_at: 2026-03-21T11:08:19Z
----
-
-Update docker-compose.prod.yml and Dockerfile.prod to support Supabase Cloud auth in production.\n\n- [ ] Add SUPABASE_JWT_SECRET env var to backend in docker-compose.prod.yml\n- [ ] Add build args for VITE_SUPABASE_URL, VITE_SUPABASE_ANON_KEY, VITE_API_URL to frontend in docker-compose.prod.yml\n- [ ] Add ARG/ENV lines to Dockerfile.prod so Vite can pick up env vars at build time\n- [ ] Update .env.example with production notes
-
-## Summary of Changes\n\nUpdated 3 files to support Supabase Cloud auth in production:\n- `docker-compose.prod.yml`: added SUPABASE_JWT_SECRET to backend, added build args to frontend\n- `frontend/Dockerfile.prod`: added ARG lines so Vite inlines Supabase config at build time\n- `.github/workflows/deploy.yml`: pass build args from secrets when building frontend image\n\nPR: #69

.beans/archive/nuzlocke-tracker-evc8--crash-crash-backend-auth-middleware-and-jwt-verifi.md

@@ -1,35 +0,0 @@
----
-# nuzlocke-tracker-evc8
-title: 'Crash: Crash: Backend auth middleware and JWT verification'
-status: completed
-type: bug
-priority: high
-created_at: 2026-03-20T19:13:03Z
-updated_at: 2026-03-20T19:20:46Z
-parent: nuzlocke-tracker-bw1m
-blocking:
-    - nuzlocke-tracker-9zpm
----
-
-Agent crashed while working on nuzlocke-tracker-9zpm.
-
-## Exit Code
-1
-
-## Last Output
-```
-Failed to authenticate. API Error: 401 {"type":"error","error":{"type":"authentication_error","message":"OAuth token has expired. Please obtain a new token or refresh your existing token."},"request_id":"req_011CZEs5LCgi1Zh6MdRencGW"}
-
-```
-
-## Context
-- Bean: nuzlocke-tracker-9zpm
-- Title: Crash: Backend auth middleware and JWT verification
-- Type: bug
-
-
-## Reasons for Scrapping
-
-This is not a code bug. The crash occurred because the agent's OAuth token to the Anthropic API expired during execution. This is an infrastructure/authentication issue, not an actionable bug in the nuzlocke-tracker codebase.
-
-The original task (`nuzlocke-tracker-b311`) can proceed once its actual prerequisite (`nuzlocke-tracker-2561` - Supabase Auth setup) is completed.

.beans/archive/nuzlocke-tracker-f4d0--add-require-admin-dependency-and-protect-admin-end.md

@@ -1,49 +0,0 @@
----
-# nuzlocke-tracker-f4d0
-title: Add require_admin dependency and protect admin endpoints
-status: completed
-type: task
-priority: normal
-created_at: 2026-03-21T10:06:19Z
-updated_at: 2026-03-21T10:15:14Z
-parent: nuzlocke-tracker-ce4o
-blocked_by:
-    - nuzlocke-tracker-dwah
----
-
-Add a `require_admin` FastAPI dependency that checks the `is_admin` column on the `users` table. Apply it to all admin-facing API endpoints (games CRUD, pokemon CRUD, evolutions CRUD, bosses CRUD, route CRUD).
-
-## Checklist
-
-- [x] Add `require_admin` dependency in `backend/src/app/core/auth.py` that:
-  - Requires authentication (reuses `require_auth`)
-  - Looks up the user in the `users` table by `AuthUser.id`
-  - Returns 403 if `is_admin` is not `True`
-- [x] Apply `require_admin` to write endpoints in: `games.py`, `pokemon.py`, `evolutions.py`, `bosses.py` (all POST/PUT/PATCH/DELETE)
-- [x] Keep read endpoints (GET) accessible to all authenticated users
-- [x] Add tests for 403 response when non-admin user hits admin endpoints
-
-## Files to change
-
-- `backend/src/app/core/auth.py` — add `require_admin`
-- `backend/src/app/api/games.py` — replace `require_auth` with `require_admin` on mutations
-- `backend/src/app/api/pokemon.py` — same
-- `backend/src/app/api/evolutions.py` — same  
-- `backend/src/app/api/bosses.py` — same
-
-## Summary of Changes
-
-Added `require_admin` FastAPI dependency to `backend/src/app/core/auth.py`:
-- Depends on `require_auth` (returns 401 if not authenticated)
-- Looks up user in `users` table by UUID
-- Returns 403 if user not found or `is_admin` is not True
-
-Applied `require_admin` to all admin-facing write endpoints:
-- `games.py`: POST/PUT/DELETE for games and routes
-- `pokemon.py`: POST/PUT/DELETE for pokemon and route encounters
-- `evolutions.py`: POST/PUT/DELETE for evolutions
-- `bosses.py`: POST/PUT/DELETE for game-scoped boss operations (run-scoped endpoints kept with `require_auth`)
-
-Added tests in `test_auth.py`:
-- Unit tests for `require_admin` (admin user, non-admin user, user not in DB)
-- Integration tests for admin endpoint access (403 for non-admin, 201 for admin)

.beans/archive/nuzlocke-tracker-fbcs--crash-add-detailed-boss-pokemon-information-abilit.md

@@ -1,32 +0,0 @@
----
-# nuzlocke-tracker-fbcs
-title: 'Crash: Add detailed boss pokemon information (ability, item, nature, moveset)'
-status: completed
-type: bug
-priority: high
-tags:
-    - failed
-created_at: 2026-03-20T19:01:15Z
-updated_at: 2026-03-20T19:37:36Z
-parent: nuzlocke-tracker-bw1m
-blocking:
-    - nuzlocke-tracker-nvd6
----
-
-Agent crashed while working on nuzlocke-tracker-nvd6.
-
-## Exit Code
-1
-
-## Last Output
-```
-Failed to authenticate. API Error: 401 {"type":"error","error":{"type":"authentication_error","message":"OAuth token has expired. Please obtain a new token or refresh your existing token."},"request_id":"req_011CZErBAtQPvCEsAZyGSYmc"}
-
-```
-
-## Context
-- Bean: nuzlocke-tracker-nvd6
-- Title: Add detailed boss pokemon information (ability, item, nature, moveset)
-- Type: feature
-
-## Resolution\n\nThe crash was caused by OAuth token expiration. Work completed via nuzlocke-tracker-n926.

.beans/archive/nuzlocke-tracker-gez0--crash-user-model-run-ownership-and-visibility-migr.md

@@ -1,34 +0,0 @@
----
-# nuzlocke-tracker-gez0
-title: 'Crash: User model, run ownership, and visibility migration'
-status: scrapped
-type: bug
-priority: high
-tags:
-    - failed
-created_at: 2026-03-20T19:00:55Z
-updated_at: 2026-03-20T19:21:18Z
-parent: nuzlocke-tracker-bw1m
-blocking:
-    - nuzlocke-tracker-bnhh
----
-
-Agent crashed while working on nuzlocke-tracker-bnhh.
-
-## Exit Code
-1
-
-## Last Output
-```
-Failed to authenticate. API Error: 401 {"type":"error","error":{"type":"authentication_error","message":"OAuth token has expired. Please obtain a new token or refresh your existing token."},"request_id":"req_011CZEr9igHnUG4eR8RFWUEj"}
-
-```
-
-## Context
-- Bean: nuzlocke-tracker-bnhh
-- Title: User model, run ownership, and visibility migration
-- Type: task
-
-## Reasons for Scrapping
-
-This crash was caused by an expired OAuth token during agent execution - a transient session management issue, not a code bug. The underlying task (nuzlocke-tracker-bnhh) remains blocked by nuzlocke-tracker-2561 (Supabase setup) and can be resumed once that prerequisite is complete.

.beans/archive/nuzlocke-tracker-h205--auth-aware-navigation-menu.md

@@ -1,38 +0,0 @@
----
-# nuzlocke-tracker-h205
-title: Auth-aware navigation menu
-status: completed
-type: task
-priority: normal
-created_at: 2026-03-21T10:06:20Z
-updated_at: 2026-03-21T10:22:34Z
-parent: nuzlocke-tracker-ce4o
-blocked_by:
-    - nuzlocke-tracker-5svj
----
-
-Update the Layout component to show different nav links based on auth state and admin role.
-
-## Checklist
-
-- [x] Replace static \`navLinks\` array with dynamic links based on \`useAuth()\` state
-- [x] **Logged out**: Home, Runs, Genlockes, Stats (no New Run, no Admin)
-- [x] **Logged in (non-admin)**: New Run, My Runs, Genlockes, Stats
-- [x] **Logged in (admin)**: New Run, My Runs, Genlockes, Stats, Admin
-- [x] Update both desktop and mobile nav (they share the same \`navLinks\` array, so this should be automatic)
-- [x] Verify menu updates reactively on login/logout
-
-## Files to change
-
-- \`frontend/src/components/Layout.tsx\` — make \`navLinks\` dynamic based on auth state
-
-## Summary of Changes
-
-- Removed static `navLinks` array from module scope
-- Added dynamic `navLinks` computation inside `Layout` component using `useMemo`
-- Navigation now depends on `user` and `isAdmin` from `useAuth()`:
-  - Logged out: Home, Runs, Genlockes, Stats
-  - Logged in (non-admin): New Run, My Runs, Genlockes, Stats
-  - Logged in (admin): New Run, My Runs, Genlockes, Stats, Admin
-- Updated `isActive` function to handle Home route (`/`) correctly
-- Both desktop and mobile nav automatically use the same dynamic `navLinks` array

.beans/archive/nuzlocke-tracker-h8zw--crash-hide-edit-controls-for-non-owners-in-fronten.md

@@ -1,28 +0,0 @@
----
-# nuzlocke-tracker-h8zw
-title: 'Crash: Hide edit controls for non-owners in frontend'
-status: completed
-type: bug
-priority: high
-created_at: 2026-03-21T12:49:42Z
-updated_at: 2026-03-21T12:50:37Z
-parent: nuzlocke-tracker-bw1m
-blocking:
-    - nuzlocke-tracker-i2va
----
-
-Bean was found in 'in-progress' status on startup but no agent was running.
-This likely indicates a crash or unexpected termination.
-
-Manual review required before retrying.
-
-Bean: nuzlocke-tracker-i2va
-Title: Hide edit controls for non-owners in frontend
-
-## Summary of Changes
-
-Investigation shows commit `3bd24fc` already implemented all required changes:
-- Added `useAuth` and `canEdit = isOwner` to both `RunEncounters.tsx` and `RunDashboard.tsx`
-- All mutation UI guarded behind `canEdit` (Log Shiny/Egg, End Run, Randomize All, HoF Edit, Boss Battle, route clicks, visibility, naming scheme)
-- Read-only banners displayed for non-owners
-- No code changes needed — work was already complete

.beans/archive/nuzlocke-tracker-he1n--add-local-gotrue-container-for-dev-auth-testing.md

@@ -1,55 +0,0 @@
----
-# nuzlocke-tracker-he1n
-title: Add local GoTrue container for dev auth testing
-status: completed
-type: feature
-priority: normal
-created_at: 2026-03-20T20:57:04Z
-updated_at: 2026-03-21T10:07:40Z
----
-
-## Problem
-
-The current local Docker setup has no auth service — Supabase is only available as a cloud service. This means:
-- Auth flows (login, signup, JWT verification) cannot be tested locally
-- The frontend's `supabase.ts` falls back to a stub client (`http://localhost:54321`) that doesn't actually exist
-- Backend tests mock auth entirely via `conftest.py` fixtures, so integration testing of the full auth flow is impossible
-
-## Approach
-
-Add a **GoTrue** container (Supabase's auth engine) to the local `docker-compose.yml`. GoTrue is a standalone Go service that provides the same auth API that Supabase cloud exposes. This gives us local email/password auth without needing Discord/Google OAuth providers configured.
-
-**Architecture (Option 3):**
-- **Local dev**: Own PostgreSQL + GoTrue container → full auth testing
-- **Production**: Own PostgreSQL + Supabase cloud for auth (handles Discord/Google OAuth)
-
-GoTrue will use the existing `db` PostgreSQL container, creating its own `auth` schema (separate from the app's tables managed by Alembic).
-
-## Files to modify
-
-- `docker-compose.yml` — add GoTrue service, configure env vars
-- `.env.example` — add GoTrue-specific local defaults
-- `frontend/src/lib/supabase.ts` — point to local GoTrue when in dev mode
-- `backend/src/app/core/config.py` — may need local JWT secret default
-- `README.md` or docs — document local auth setup
-
-## Checklist
-
-- [x] Research GoTrue Docker image and required env vars (JWT secret, DB connection, SMTP disabled, etc.)
-- [x] Add `gotrue` service to `docker-compose.yml` using the existing `db` container
-- [x] Configure GoTrue to use the same PostgreSQL with its own `auth` schema
-- [x] Set local JWT secret (e.g. `super-secret-jwt-token-for-local-dev`) shared between GoTrue and the backend
-- [x] Update `.env.example` with local GoTrue defaults (`SUPABASE_URL=http://localhost:9999`, local JWT secret, local anon key)
-- [x] Update `frontend/src/lib/supabase.ts` to use `http://localhost:9999` in dev (GoTrue's local port)
-- [x] Verify backend JWT verification works with GoTrue-issued tokens (same HS256 + shared secret)
-- [ ] Test email/password signup and login flow end-to-end locally
-- [x] Verify OAuth buttons gracefully handle missing providers in local dev (show disabled state or helpful message)
-- [x] Update `docker-compose.yml` healthcheck for GoTrue readiness
-- [x] Document the local auth setup in README or contributing guide
-
-## Notes
-
-- GoTrue image: `supabase/gotrue` (official, regularly updated)
-- GoTrue needs: `GOTRUE_DB_DATABASE_URL`, `GOTRUE_JWT_SECRET`, `GOTRUE_SITE_URL`, `GOTRUE_EXTERNAL_EMAIL_ENABLED=true`, `GOTRUE_MAILER_AUTOCONFIRM=true` (skip email verification locally)
-- The `anon` key for local dev can be a static JWT signed with the local secret (Supabase docs show how to generate this)
-- Production docker-compose.prod.yml is NOT modified — it continues using Supabase cloud via env vars

.beans/archive/nuzlocke-tracker-jmkf--crash-run-ownership-assignment-and-visibility-togg.md

@@ -1,34 +0,0 @@
----
-# nuzlocke-tracker-jmkf
-title: 'Crash: Run ownership assignment and visibility toggle'
-status: completed
-type: bug
-priority: high
-created_at: 2026-03-20T19:01:04Z
-updated_at: 2026-03-20T19:28:57Z
-parent: nuzlocke-tracker-bw1m
-blocking:
-    - nuzlocke-tracker-k1l1
----
-
-Agent crashed while working on nuzlocke-tracker-k1l1.
-
-## Exit Code
-1
-
-## Last Output
-```
-Failed to authenticate. API Error: 401 {"type":"error","error":{"type":"authentication_error","message":"OAuth token has expired. Please obtain a new token or refresh your existing token."},"request_id":"req_011CZErAP1dbTeqSqRccKWyb"}
-
-```
-
-## Context
-- Bean: nuzlocke-tracker-k1l1
-- Title: Run ownership assignment and visibility toggle
-- Type: feature
-
-## Resolution
-
-This crash was caused by OAuth token expiration during agent execution, not a code bug. The token expired mid-session, causing the API to return a 401 authentication error. No code changes are required.
-
-The original feature (nuzlocke-tracker-k1l1) remains blocked by its dependencies (b311 and bnhh).

.beans/archive/nuzlocke-tracker-k1l1--run-ownership-assignment-and-visibility-toggle.md

@@ -1,40 +0,0 @@
----
-# nuzlocke-tracker-k1l1
-title: Run ownership assignment and visibility toggle
-status: completed
-type: feature
-priority: normal
-created_at: 2026-03-20T15:28:27Z
-updated_at: 2026-03-20T20:21:01Z
-parent: nuzlocke-tracker-d98o
-blocked_by:
-    - nuzlocke-tracker-b311
-    - nuzlocke-tracker-bnhh
-    - nuzlocke-tracker-l9xh
----
-
-Wire up run ownership in the UI. New runs created by logged-in users are automatically assigned to them. Add a visibility toggle (public/private) to run settings. Update run list to show owned runs and public runs separately.
-
-## Checklist
-- [x] Auto-assign owner_id when creating a new run (if authenticated)
-- [x] Add visibility toggle to run settings/edit page
-- [x] Update run list view: show 'My Runs' section for authenticated users
-- [x] Show public/private badge on run cards
-- [x] Enforce visibility on frontend (don't show edit controls for non-owned runs)
-- [x] Admin script/endpoint to assign existing unowned runs to a user by ID
-
-## Summary of Changes
-
-### Frontend
-- Updated `NuzlockeRun` type to include `visibility` (public/private) and `owner` fields
-- Updated `CreateRunInput` and `UpdateRunInput` to support visibility setting
-- **RunList.tsx**: Added "My Runs" and "Public Runs" sections for authenticated users, with private badge on owned runs
-- **RunDashboard.tsx**: Added visibility toggle dropdown in settings, restricted edit controls to run owners
-- **NewRun.tsx**: Added visibility selector during run creation
-
-### Backend
-- Created `scripts/assign_unowned_runs.py` admin script to migrate existing unowned runs to a user
-
-### Notes
-- The backend already supported auto-assigning `owner_id` on run creation (from blocking bean)
-- Unowned runs (legacy) remain editable by anyone for backwards compatibility

.beans/archive/nuzlocke-tracker-kix5--fix-e2e-tests-after-boss-feature-changes.md

@@ -1,60 +0,0 @@
----
-# nuzlocke-tracker-kix5
-title: Fix e2e tests after boss feature changes
-status: scrapped
-type: bug
-priority: normal
-created_at: 2026-03-20T19:19:31Z
-updated_at: 2026-03-20T20:49:19Z
-blocked_by:
-    - nuzlocke-tracker-neqv
----
-
-The e2e tests (accessibility + mobile) are failing because the test infrastructure hasn't been updated since the boss feature, journal, and admin pages were added.
-
-## Problems
-
-### 1. Missing pages in test coverage
-Both `accessibility.spec.ts` and `mobile.spec.ts` share a hardcoded page list that is missing several routes added since the tests were written:
-
-**Missing from page list:**
-- `runs/:runId/journal/:entryId` — Journal entry page (requires journal fixture)
-- `admin/games/:gameId` — Admin game detail page (requires game fixture ID)
-- `admin/games/:gameId/routes/:routeId` — Admin route detail page (requires route fixture ID)
-- `admin/runs` — Admin runs page
-- `admin/genlockes` — Admin genlockes page
-- `admin/genlockes/:genlockeId` — Admin genlocke detail page (requires genlocke fixture ID)
-
-### 2. Missing test fixtures/seeding
-The global-setup seeds runs, encounters, and genlockes but does **not** seed:
-- Boss battles (via `/games/{game_id}/bosses`)
-- Boss results (via `/runs/{run_id}/boss-results`)
-- Journal entries (via journal API)
-- Version groups (required for boss battles to work)
-
-The RunEncounters page now renders a boss battle section, which likely makes API calls that fail or produce unexpected DOM, causing accessibility or layout violations.
-
-### 3. Shared page list duplication
-Both spec files duplicate the same page list — should be extracted to a shared constant in `fixtures.ts`.
-
-## Checklist
-
-- [ ] Update `fixtures.ts` to export a shared page list with all current routes
-- [ ] Add boss battle seeding to `global-setup.ts` (create boss via API after game seed)
-- [ ] Add boss result seeding to `global-setup.ts` (create result for the test run)
-- [ ] Add journal entry seeding to `global-setup.ts` (create entry for the test run)
-- [ ] Add new fixture IDs to `Fixtures` interface (journalEntryId, routeId, bossId, etc.)
-- [ ] Update `accessibility.spec.ts` to use shared page list
-- [ ] Update `mobile.spec.ts` to use shared page list
-- [ ] Run e2e tests locally and verify they pass
-- [ ] Fix any new accessibility or layout violations on boss/journal pages
-
-## Files to modify
-- `frontend/e2e/fixtures.ts`
-- `frontend/e2e/global-setup.ts`
-- `frontend/e2e/accessibility.spec.ts`
-- `frontend/e2e/mobile.spec.ts`
-
-## Notes
-- The boss feature is still in progress (epic `nuzlocke-tracker-neqv`). This bean should be worked on after the boss feature is finalized to avoid churn.
-- Version groups must exist for boss battle API calls to work — check if `app.seeds` already seeds them.

.beans/archive/nuzlocke-tracker-l9xh--frontend-auth-flow-login-signup-session-management.md

@@ -1,41 +0,0 @@
----
-# nuzlocke-tracker-l9xh
-title: Frontend auth flow (login, signup, session management)
-status: completed
-type: feature
-priority: normal
-tags:
-    - failed
-created_at: 2026-03-20T15:28:24Z
-updated_at: 2026-03-20T19:26:16Z
-parent: nuzlocke-tracker-d98o
-blocked_by:
-    - nuzlocke-tracker-2561
----
-
-Add Supabase JS client to the frontend. Build login and signup pages with email/password and social login buttons (Google, Discord). Implement auth context/provider for session management, protected route wrapper, and auth-aware API client that attaches Bearer tokens.
-
-## Checklist
-- [x] Install @supabase/supabase-js
-- [x] Create Supabase client singleton with env vars
-- [x] Create AuthContext/AuthProvider with session state, login, logout, signup methods
-- [x] Build login page (email/password form + Google/Discord buttons)
-- [x] Build signup page (email/password form + Google/Discord buttons)
-- [x] Add auth callback route for OAuth redirects
-- [x] Create ProtectedRoute wrapper component
-- [x] Update API client to attach Authorization header when user is logged in
-- [x] Add user menu (avatar/email, logout) to header when authenticated
-- [x] Handle token refresh automatically via Supabase client
-
-## Summary of Changes
-
-- Installed @supabase/supabase-js package
-- Created Supabase client singleton at `frontend/src/lib/supabase.ts`
-- Created AuthContext/AuthProvider at `frontend/src/contexts/AuthContext.tsx` with session state, login, logout, signup, and OAuth methods
-- Created Login page (`frontend/src/pages/Login.tsx`) with email/password form and Google/Discord OAuth buttons
-- Created Signup page (`frontend/src/pages/Signup.tsx`) with email/password form and Google/Discord OAuth buttons
-- Created auth callback route (`frontend/src/pages/AuthCallback.tsx`) for OAuth redirects
-- Created ProtectedRoute component (`frontend/src/components/ProtectedRoute.tsx`)
-- Updated API client to attach Authorization header automatically when user is logged in
-- Added UserMenu component to Layout header showing avatar/email and logout button
-- Token refresh is handled automatically by Supabase JS client

.beans/archive/nuzlocke-tracker-ldyi--crash-crash-run-ownership-assignment-and-visibilit.md

@@ -1,34 +0,0 @@
----
-# nuzlocke-tracker-ldyi
-title: 'Crash: Crash: Run ownership assignment and visibility toggle'
-status: completed
-type: bug
-priority: high
-created_at: 2026-03-20T19:13:16Z
-updated_at: 2026-03-20T19:29:03Z
-parent: nuzlocke-tracker-bw1m
-blocking:
-    - nuzlocke-tracker-jmkf
----
-
-Agent crashed while working on nuzlocke-tracker-jmkf.
-
-## Exit Code
-1
-
-## Last Output
-```
-Failed to authenticate. API Error: 401 {"type":"error","error":{"type":"authentication_error","message":"OAuth token has expired. Please obtain a new token or refresh your existing token."},"request_id":"req_011CZEs6J7hxAdJni9KoTLcJ"}
-
-```
-
-## Context
-- Bean: nuzlocke-tracker-jmkf
-- Title: Crash: Run ownership assignment and visibility toggle
-- Type: bug
-
-## Resolution
-
-This crash was caused by OAuth token expiration during agent execution, not a code bug. The token expired mid-session, causing the API to return a 401 authentication error. No code changes are required.
-
-The original feature (nuzlocke-tracker-k1l1) remains blocked by its dependencies (b311 and bnhh).

.beans/archive/nuzlocke-tracker-liz1--fix-frontend-layout-tests-for-auth-aware-navigatio.md

@@ -1,13 +0,0 @@
----
-# nuzlocke-tracker-liz1
-title: Fix frontend Layout tests for auth-aware navigation
-status: completed
-type: bug
-priority: normal
-created_at: 2026-03-21T10:41:51Z
-updated_at: 2026-03-21T10:42:30Z
----
-
-Layout.test.tsx fails because nav links are now auth-dependent. Tests expect logged-in admin links but render with no user. Fix by mocking useAuth.
-
-## Summary of Changes\n\nMocked `useAuth` in Layout.test.tsx instead of using real AuthProvider. Added separate test groups for logged-out and logged-in-as-admin states, verifying correct nav links appear in each. All 118 frontend tests pass.

.beans/archive/nuzlocke-tracker-m8ki--split-e2e-tests-into-manual-workflow.md

@@ -1,11 +0,0 @@
----
-# nuzlocke-tracker-m8ki
-title: Split e2e tests into manual workflow
-status: completed
-type: task
-priority: normal
-created_at: 2026-02-21T16:53:37Z
-updated_at: 2026-02-21T16:54:04Z
----
-
-Remove e2e-tests job from ci.yml and create a new e2e.yml workflow with workflow_dispatch trigger only.

.beans/archive/nuzlocke-tracker-mg99--crash-add-detailed-boss-battle-information.md

@@ -1,32 +0,0 @@
----
-# nuzlocke-tracker-mg99
-title: 'Crash: Add detailed boss battle information'
-status: scrapped
-type: bug
-priority: high
-created_at: 2026-03-20T19:01:08Z
-updated_at: 2026-03-20T19:29:55Z
-parent: nuzlocke-tracker-bw1m
-blocking:
-    - nuzlocke-tracker-neqv
----
-
-Agent crashed while working on nuzlocke-tracker-neqv.
-
-## Exit Code
-1
-
-## Last Output
-```
-Failed to authenticate. API Error: 401 {"type":"error","error":{"type":"authentication_error","message":"OAuth token has expired. Please obtain a new token or refresh your existing token."},"request_id":"req_011CZErAh36SY2uCVFvs6pe8"}
-
-```
-
-## Context
-- Bean: nuzlocke-tracker-neqv
-- Title: Add detailed boss battle information
-- Type: epic
-
-## Reasons for Scrapping
-
-This is a crash report bean created when a previous agent session expired due to OAuth token timeout. This is a transient infrastructure issue, not a code bug. The original work is tracked in the child beans of nuzlocke-tracker-neqv.

.beans/archive/nuzlocke-tracker-mygi--crash-crash-add-detailed-boss-battle-information.md

@@ -1,32 +0,0 @@
----
-# nuzlocke-tracker-mygi
-title: 'Crash: Crash: Add detailed boss battle information'
-status: completed
-type: bug
-priority: high
-created_at: 2026-03-20T19:13:19Z
-updated_at: 2026-03-20T19:30:01Z
-parent: nuzlocke-tracker-bw1m
-blocking:
-    - nuzlocke-tracker-mg99
----
-
-Agent crashed while working on nuzlocke-tracker-mg99.
-
-## Exit Code
-1
-
-## Last Output
-```
-Failed to authenticate. API Error: 401 {"type":"error","error":{"type":"authentication_error","message":"OAuth token has expired. Please obtain a new token or refresh your existing token."},"request_id":"req_011CZEs6XKwjZQ4HoyPLXVxp"}
-
-```
-
-## Context
-- Bean: nuzlocke-tracker-mg99
-- Title: Crash: Add detailed boss battle information
-- Type: bug
-
-## Reasons for Scrapping
-
-This is a crash report bean created when a previous agent session expired due to OAuth token timeout. This is a transient infrastructure issue, not a code bug. The original work is tracked in the child beans of nuzlocke-tracker-neqv.

.beans/archive/nuzlocke-tracker-mz16--session-journal-blog-posts.md

@@ -1,38 +0,0 @@
----
-# nuzlocke-tracker-mz16
-title: Session Journal / Blog Posts
-status: completed
-type: epic
-priority: normal
-created_at: 2026-02-19T07:43:05Z
-updated_at: 2026-03-20T15:37:21Z
----
-
-Let users tell the story of their nuzlocke run through session journal entries (blog posts).
-
-Nuzlockes are inherently story-driven — encounters you first think are weak become the star of the show, a needed sacrifice lets the run survive, one crit in a boss battle means defeat. Users should be able to capture those moments.
-
-## Concept
-
-For each play session, users can write a short post to document what happened. Posts can:
-
-- Include rich text / markdown content
-- Embed screenshots and images
-- Automatically link to their current team (or a subset of it)
-- Reference deaths, new encounters, and other run events
-- Be tied to a specific run
-
-The journal becomes a chronological narrative of the nuzlocke run, with game data woven in automatically.
-
-## Decisions
-
-- **Editor:** Plain markdown textarea with preview
-- **Images:** Via markdown URL syntax (no uploads)
-- **Run linkage:** Entries belong to a run, optionally linked to a boss battle
-- **Visibility:** Private only (no sharing — deferred until user accounts exist)
-- **Templates:** Blank slate — no templates
-
-## Success Criteria
-
-- [x] Backend: journal entries CRUD API is complete (`nuzlocke-tracker-vmto`)
-- [x] Frontend: journal list, editor, and view are functional (`nuzlocke-tracker-d68l`)

.beans/archive/nuzlocke-tracker-n926--crash-crash-add-detailed-boss-pokemon-information.md

@@ -1,30 +0,0 @@
----
-# nuzlocke-tracker-n926
-title: 'Crash: Crash: Add detailed boss pokemon information (ability, item, nature, moveset)'
-status: completed
-type: bug
-priority: high
-created_at: 2026-03-20T19:13:24Z
-updated_at: 2026-03-20T19:37:57Z
-parent: nuzlocke-tracker-bw1m
-blocking:
-    - nuzlocke-tracker-fbcs
----
-
-Agent crashed while working on nuzlocke-tracker-fbcs.
-
-## Exit Code
-1
-
-## Last Output
-```
-Failed to authenticate. API Error: 401 {"type":"error","error":{"type":"authentication_error","message":"OAuth token has expired. Please obtain a new token or refresh your existing token."},"request_id":"req_011CZEs6sYsQqU6dmmpwcmTM"}
-
-```
-
-## Context
-- Bean: nuzlocke-tracker-fbcs
-- Title: Crash: Add detailed boss pokemon information (ability, item, nature, moveset)
-- Type: bug
-
-## Resolution\n\nThe crash was caused by OAuth token expiration. Resumed work and completed the original feature (nuzlocke-tracker-nvd6).

.beans/archive/nuzlocke-tracker-na3s--allow-multiple-games-per-region-in-custom-genlocke.md

@@ -1,11 +0,0 @@
----
-# nuzlocke-tracker-na3s
-title: Allow multiple games per region in Custom genlocke
-status: completed
-type: feature
-priority: normal
-created_at: 2026-03-17T12:29:57Z
-updated_at: 2026-03-17T12:32:05Z
----
-
-Users want to run multiple games from the same region in a genlocke (e.g., Black + Black 2 in Unova). Change availableRegions computation so custom mode shows all regions, and add a subtle indicator for already-used regions in AddLegDropdown.

.beans/archive/nuzlocke-tracker-ndpz--crash-user-account-integration.md

@@ -1,36 +0,0 @@
----
-# nuzlocke-tracker-ndpz
-title: 'Crash: User Account integration'
-status: completed
-type: bug
-priority: high
-tags:
-    - failed
-created_at: 2026-03-20T19:00:42Z
-updated_at: 2026-03-20T19:18:25Z
-parent: nuzlocke-tracker-bw1m
-blocking:
-    - nuzlocke-tracker-d98o
----
-
-Agent crashed while working on nuzlocke-tracker-d98o.
-
-## Exit Code
-1
-
-## Last Output
-```
-Failed to authenticate. API Error: 401 {"type":"error","error":{"type":"authentication_error","message":"OAuth token has expired. Please obtain a new token or refresh your existing token."},"request_id":"req_011CZEr8m1A9hiKCVyBgkCJB"}
-
-```
-
-## Context
-- Bean: nuzlocke-tracker-d98o
-- Title: User Account integration
-- Type: epic
-
-## Resolution
-
-This crash was caused by Claude's OAuth token expiring during an agent session. This is an environmental/infrastructure issue, not a code bug. The token has been refreshed by starting a new agent session.
-
-No code changes required.

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

@@ -1,17 +0,0 @@
----
-# nuzlocke-tracker-neqv
-title: Add detailed boss battle information
-status: completed
-type: epic
-priority: low
-created_at: 2026-02-08T11:21:22Z
-updated_at: 2026-03-20T20:25:11Z
----
-
-Enhance boss battles with more detailed information. Split into child beans:
-
-## Success Criteria
-- [x] Moves and abilities tables seeded (names + introduced generation)
-- [x] Boss pokemon entries support ability, held item, nature, and moveset
-- [x] Boss battle results can capture a team snapshot
-- [ ] (Future) Moves/abilities enriched with generation-specific stats

.beans/archive/nuzlocke-tracker-nvd6--add-detailed-boss-pokemon-information-ability-item.md

@@ -1,53 +0,0 @@
----
-# nuzlocke-tracker-nvd6
-title: Add detailed boss pokemon information (ability, item, nature, moveset)
-status: completed
-type: feature
-priority: low
-tags:
-    - failed
-created_at: 2026-03-20T15:11:50Z
-updated_at: 2026-03-20T19:37:18Z
-parent: nuzlocke-tracker-neqv
-blocked_by:
-    - nuzlocke-tracker-vc5o
----
-
-Add optional detail fields to boss pokemon entries: ability, held item, nature, and moveset (up to 4 moves).
-
-## Approach
-- Ability and moves reference the seeded `moves`/`abilities` tables via FK (hybrid approach — names only, no gen-specific stats yet)
-- Held item and nature stored as plain strings (items table can come later; natures are static)
-
-## Checklist
-- [x] **Migration**: Add columns to `boss_pokemon` — `ability_id` (FK|null), `held_item` (str|null), `nature` (str|null), `move1_id`–`move4_id` (FK|null)
-- [x] **Model**: Update `BossPokemon` in `backend/src/app/models/boss_pokemon.py` with relationships
-- [x] **Schemas**: Update `BossPokemonResponse` and `BossPokemonInput` in `backend/src/app/schemas/boss.py`
-- [x] **Admin UI**: Add fields to `BossTeamEditor.tsx` (ability autocomplete, item input, nature dropdown, 4 move autocomplete inputs)
-- [x] **Frontend types**: Update `BossPokemon` in `frontend/src/types/game.ts` and admin input types
-- [x] **Frontend display**: Show details on boss cards in `RunEncounters.tsx` and `BossDefeatModal.tsx`
-- [~] **Seed data**: (deferred) Update bulk import format to support new fields
-
-## Dependencies
-- Requires moves and abilities tables to be seeded first
-
-## Summary of Changes
-
-### Backend
-- Created migration `l3a4b5c6d7e8_add_boss_pokemon_details.py` adding `ability_id`, `held_item`, `nature`, `move1_id`-`move4_id` columns
-- Updated `BossPokemon` model with relationships to `Ability` and `Move`
-- Updated `BossPokemonResponse` and `BossPokemonInput` schemas with detail fields
-- Created `/moves` and `/abilities` API endpoints for autocomplete search
-- Updated `set_boss_team` endpoint to handle new fields
-- Added eager loading for ability/moves in boss queries
-
-### Frontend
-- Added `MoveRef` and `AbilityRef` types to game.ts
-- Extended `BossPokemon` type with detail fields
-- Extended `BossPokemonInput` admin type
-- Created `MoveSelector` and `AbilitySelector` autocomplete components
-- Updated `BossTeamEditor` with expandable detail section per pokemon
-- Updated `BossTeamPreview` and `BossDefeatModal` to display details
-
-### Deferred
-- Bulk import format for seed data not updated (optional fields work with existing format)

.beans/archive/nuzlocke-tracker-pl1m--crash-crash-frontend-auth-flow-login-signup-sessio.md

@@ -1,30 +0,0 @@
----
-# nuzlocke-tracker-pl1m
-title: 'Crash: Crash: Frontend auth flow (login, signup, session management)'
-status: completed
-type: bug
-priority: high
-created_at: 2026-03-20T19:13:10Z
-updated_at: 2026-03-20T19:27:57Z
-parent: nuzlocke-tracker-bw1m
-blocking:
-    - nuzlocke-tracker-8vev
----
-
-Agent crashed while working on nuzlocke-tracker-8vev.
-
-## Exit Code
-1
-
-## Last Output
-```
-Failed to authenticate. API Error: 401 {"type":"error","error":{"type":"authentication_error","message":"OAuth token has expired. Please obtain a new token or refresh your existing token."},"request_id":"req_011CZEs5tdpug65ZR5M3DSQS"}
-
-```
-
-## Context
-- Bean: nuzlocke-tracker-8vev
-- Title: Crash: Frontend auth flow (login, signup, session management)
-- Type: bug
-
-## Resolution\n\nThis was an infrastructure issue (Claude API OAuth token expired), not a code bug. Continuing work on the original feature bean (nuzlocke-tracker-l9xh).

.beans/archive/nuzlocke-tracker-t90q--crash-backend-journal-entries-model-api-and-migrat.md

@@ -1,24 +0,0 @@
----
-# nuzlocke-tracker-t90q
-title: 'Crash: Backend: Journal entries model, API, and migration'
-status: completed
-type: bug
-priority: high
-created_at: 2026-03-20T15:30:02Z
-updated_at: 2026-03-20T15:39:13Z
-parent: nuzlocke-tracker-bw1m
-blocking:
-    - nuzlocke-tracker-vmto
----
-
-Bean was found in 'in-progress' status on startup but no agent was running.
-This likely indicates a crash or unexpected termination.
-
-Manual review required before retrying.
-
-Bean: nuzlocke-tracker-vmto
-Title: Backend: Journal entries model, API, and migration
-
-## Resolution
-
-The underlying bean (nuzlocke-tracker-vmto) was already completed before the crash was detected. All backend work for journal entries is implemented and functional. A separate bug bean (nuzlocke-tracker-d5ht) was created for frontend TypeScript errors discovered during review.

.beans/archive/nuzlocke-tracker-ueub--crash-add-team-snapshot-to-boss-battle-results.md

@@ -1,30 +0,0 @@
----
-# nuzlocke-tracker-ueub
-title: 'Crash: Add team snapshot to boss battle results'
-status: completed
-type: bug
-priority: high
-tags:
-    - failed
-created_at: 2026-03-20T19:01:23Z
-updated_at: 2026-03-20T19:41:51Z
-parent: nuzlocke-tracker-bw1m
-blocking:
-    - nuzlocke-tracker-xd9j
----
-
-Agent crashed while working on nuzlocke-tracker-xd9j.
-
-## Exit Code
-1
-
-## Last Output
-```
-Failed to authenticate. API Error: 401 {"type":"error","error":{"type":"authentication_error","message":"OAuth token has expired. Please obtain a new token or refresh your existing token."},"request_id":"req_011CZErBmcConDqezwzK8kaP"}
-
-```
-
-## Context
-- Bean: nuzlocke-tracker-xd9j
-- Title: Add team snapshot to boss battle results
-- Type: feature

.beans/archive/nuzlocke-tracker-vc5o--seed-moves-and-abilities-tables-names-introduced-g.md

@@ -1,53 +0,0 @@
----
-# nuzlocke-tracker-vc5o
-title: Seed moves and abilities tables (names + introduced generation)
-status: completed
-type: task
-priority: normal
-created_at: 2026-03-20T15:11:44Z
-updated_at: 2026-03-20T15:25:11Z
-parent: nuzlocke-tracker-neqv
----
-
-Create and seed `moves` and `abilities` tables with name and generation data using the hybrid approach.
-
-## Approach
-Seed move/ability **names** with `introduced_gen` only. Full generation-specific stats (power, accuracy, type changes, effect text) will be added in a follow-up bean.
-
-This enables FK references and autocomplete from boss pokemon fields without blocking on a full moves database.
-
-## Checklist
-- [x] **Migration**: Create `moves` table (`id`, `name`, `introduced_gen`, `type` optional)
-- [x] **Migration**: Create `abilities` table (`id`, `name`, `introduced_gen`)
-- [x] **Models**: Create `Move` and `Ability` SQLAlchemy models
-- [x] **Seed data**: Seed all move names with introduced generation (source: PokeAPI or Bulbapedia)
-- [x] **Seed data**: Seed all ability names with introduced generation
-- [x] **Seed script**: Add to existing seeding pipeline (`backend/src/app/seed/`)
-- [x] **Schemas**: Create basic response schemas for API consumption
-
-## Summary of Changes
-
-### Migration
-- Created `j1e2f3a4b5c6_add_moves_and_abilities_tables.py` migration
-- `moves` table: `id`, `name` (unique), `introduced_gen`, `type` (optional)
-- `abilities` table: `id`, `name` (unique), `introduced_gen`
-- Added indexes on `introduced_gen` for both tables
-
-### Models
-- `backend/src/app/models/move.py`: `Move` SQLAlchemy model
-- `backend/src/app/models/ability.py`: `Ability` SQLAlchemy model
-- Updated `models/__init__.py` to export both
-
-### Schemas
-- `backend/src/app/schemas/move.py`: `MoveResponse`, `AbilityResponse`, and paginated variants
-- Updated `schemas/__init__.py` to export all new schemas
-
-### Seed Data
-- Created `backend/scripts/fetch_moves_abilities.py` to fetch data from PokeAPI
-- Generated `moves.json` (937 moves) and `abilities.json` (367 abilities)
-- Data includes name, introduced generation, and type (for moves)
-
-### Seed Pipeline
-- Added `upsert_moves` and `upsert_abilities` functions to `loader.py`
-- Updated `run.py` to seed moves and abilities after Pokemon
-- Updated `verify()` to include move/ability counts

.beans/archive/nuzlocke-tracker-vmto--backend-journal-entries-model-api-and-migration.md

@@ -1,62 +0,0 @@
----
-# nuzlocke-tracker-vmto
-title: 'Backend: Journal entries model, API, and migration'
-status: completed
-type: task
-priority: normal
-tags:
-    - failed
-created_at: 2026-03-20T15:15:48Z
-updated_at: 2026-03-20T15:30:47Z
-parent: nuzlocke-tracker-mz16
----
-
-Create the backend infrastructure for session journal entries.
-
-## Data Model
-
-`journal_entries` table:
-- `id` (UUID, PK)
-- `run_id` (FK to runs)
-- `boss_result_id` (FK to boss_results, nullable) — optional link to a boss battle
-- `title` (str, required)
-- `body` (text, required) — raw markdown content
-- `created_at`, `updated_at` (timestamps)
-
-## Checklist
-
-- [x] Create Alembic migration for `journal_entries` table
-- [x] Create `JournalEntry` SQLAlchemy model with relationships to `Run` and `BossResult`
-- [x] Create Pydantic schemas (`JournalEntryCreate`, `JournalEntryUpdate`, `JournalEntryResponse`)
-- [x] Create CRUD operations for journal entries
-- [x] Create API endpoints under `/runs/{run_id}/journal`:
-  - `GET /` — list entries for a run (ordered by created_at desc)
-  - `POST /` — create entry
-  - `GET /{entry_id}` — get single entry
-  - `PUT /{entry_id}` — update entry
-  - `DELETE /{entry_id}` — delete entry
-- [x] Add optional `boss_result_id` query filter to GET list endpoint
-
-
-## Summary of Changes
-
-Implemented backend infrastructure for session journal entries:
-
-**Files created:**
-- `backend/src/app/alembic/versions/k2f3a4b5c6d7_add_journal_entries_table.py` - Migration creating `journal_entries` table with UUID PK, foreign keys to `nuzlocke_runs` and `boss_results`, and timestamp columns
-- `backend/src/app/models/journal_entry.py` - SQLAlchemy model with relationships to `NuzlockeRun` and `BossResult`
-- `backend/src/app/schemas/journal_entry.py` - Pydantic schemas for create, update, and response
-- `backend/src/app/api/journal_entries.py` - API endpoints for CRUD operations
-
-**Files modified:**
-- `backend/src/app/models/nuzlocke_run.py` - Added `journal_entries` relationship
-- `backend/src/app/models/__init__.py` - Exported `JournalEntry`
-- `backend/src/app/schemas/__init__.py` - Exported journal entry schemas
-- `backend/src/app/api/routes.py` - Registered journal entries router
-
-**API Endpoints:**
-- `GET /runs/{run_id}/journal` - List entries (supports `boss_result_id` filter)
-- `POST /runs/{run_id}/journal` - Create entry
-- `GET /runs/{run_id}/journal/{entry_id}` - Get single entry
-- `PUT /runs/{run_id}/journal/{entry_id}` - Update entry
-- `DELETE /runs/{run_id}/journal/{entry_id}` - Delete entry

.beans/archive/nuzlocke-tracker-vw1z--crash-crash-add-team-snapshot-to-boss-battle-resul.md

@@ -1,39 +0,0 @@
----
-# nuzlocke-tracker-vw1z
-title: 'Crash: Crash: Add team snapshot to boss battle results'
-status: completed
-type: bug
-priority: high
-created_at: 2026-03-20T19:13:27Z
-updated_at: 2026-03-20T19:41:58Z
-parent: nuzlocke-tracker-bw1m
-blocking:
-    - nuzlocke-tracker-ueub
----
-
-Agent crashed while working on nuzlocke-tracker-ueub.
-
-## Exit Code
-1
-
-## Last Output
-```
-Failed to authenticate. API Error: 401 {"type":"error","error":{"type":"authentication_error","message":"OAuth token has expired. Please obtain a new token or refresh your existing token."},"request_id":"req_011CZEs79fEcc7KikDZH5tuz"}
-
-```
-
-## Context
-- Bean: nuzlocke-tracker-ueub
-- Title: Crash: Add team snapshot to boss battle results
-- Type: bug
-
-## Summary of Changes
-
-This crash was caused by an OAuth token expiration, not a code issue. The original feature (add team snapshot to boss battle results) has been implemented:
-
-- Created `boss_result_team` table migration
-- Added `BossResultTeam` model with relationships
-- Updated schemas with `BossResultTeamMemberInput` and `BossResultTeamMemberResponse`
-- Updated `POST /runs/{run_id}/boss-results` API to accept and save team snapshots
-- Updated `BossDefeatModal` with checkboxes for alive team members with level input
-- Added team snapshot display in boss cards on `RunEncounters.tsx`

.beans/archive/nuzlocke-tracker-wb85--replace-playstyle-rules-with-custom-rules-markdown.md

@@ -1,11 +0,0 @@
----
-# nuzlocke-tracker-wb85
-title: Replace playstyle rules with custom rules markdown field
-status: completed
-type: feature
-priority: normal
-created_at: 2026-03-20T13:48:50Z
-updated_at: 2026-03-20T13:53:08Z
----
-
-Remove hardcoreMode, setModeOnly, bossTeamMatch playstyle rules. Add a free-text markdown customRules field so users can track their own rules (especially useful for genlockes). Also: remove 'Lost' result and attempts from BossDefeatModal, always show boss team size.

.beans/archive/nuzlocke-tracker-wwnu--auth-hardening-admin-ownership-display-and-mfa.md

@@ -1,23 +0,0 @@
----
-# nuzlocke-tracker-wwnu
-title: Auth hardening, admin ownership display, and MFA
-status: completed
-type: epic
-priority: high
-created_at: 2026-03-21T12:18:09Z
-updated_at: 2026-03-21T12:38:27Z
----
-
-Harden authentication and authorization across the app after the initial auth integration went live.
-
-## Goals
-
-- [x] Runs are only editable by their owner (encounters, deaths, bosses, settings)
-- [x] Frontend hides edit controls for non-owners and logged-out users
-- [x] Admin pages show owner info for runs and genlockes
-- [ ] Genlocke visibility/ownership inferred from first leg's run
-- [ ] Optional TOTP MFA for email/password signups
-
-## Context
-
-Auth is live with Google/Discord OAuth + email/password. Backend has `require_auth` on mutations but doesn't check ownership on encounters or genlockes. Frontend `RunEncounters.tsx` has zero auth checks. Admin pages lack owner columns. Genlocke model has no `owner_id` or `visibility`.

.beans/archive/nuzlocke-tracker-wwwq--crash-show-owner-info-in-admin-pages.md

@@ -1,24 +0,0 @@
----
-# nuzlocke-tracker-wwwq
-title: 'Crash: Show owner info in admin pages'
-status: completed
-type: bug
-priority: high
-created_at: 2026-03-21T12:49:42Z
-updated_at: 2026-03-21T12:51:18Z
-parent: nuzlocke-tracker-bw1m
-blocking:
-    - nuzlocke-tracker-2fp1
----
-
-Bean was found in 'in-progress' status on startup but no agent was running.
-This likely indicates a crash or unexpected termination.
-
-Manual review required before retrying.
-
-Bean: nuzlocke-tracker-2fp1
-Title: Show owner info in admin pages
-
-## Reasons for Scrapping
-
-The original bean (nuzlocke-tracker-2fp1) had all work completed and committed before the crash occurred. The agent crashed after completing the implementation but before marking the bean as completed. No additional work was needed - just updated the original bean's status to completed.

.beans/archive/nuzlocke-tracker-xd9j--add-team-snapshot-to-boss-battle-results.md

@@ -1,34 +0,0 @@
----
-# nuzlocke-tracker-xd9j
-title: Add team snapshot to boss battle results
-status: completed
-type: feature
-priority: low
-tags:
-    - failed
-created_at: 2026-03-20T15:11:53Z
-updated_at: 2026-03-20T19:41:44Z
-parent: nuzlocke-tracker-neqv
----
-
-When recording a boss battle result, allow the player to snapshot which alive team pokemon they used and at what levels. This gives a record of "what I brought to the fight."
-
-## Checklist
-- [x] **Migration**: Create \`boss_result_team\` table (\`id\`, \`boss_result_id\` FK, \`encounter_id\` FK, \`level\`)
-- [x] **Model**: Create \`BossResultTeam\` model, add relationship to \`BossResult\`
-- [x] **Schemas**: Add \`BossResultTeamInput\` and update \`BossResultCreate\`/\`BossResultResponse\`
-- [x] **API**: Update \`POST /runs/{run_id}/boss-results\` to accept and save team snapshot
-- [x] **BossDefeatModal**: Add checkboxes for alive team members with optional level override
-- [x] **Display**: Show team snapshot when viewing past boss results in \`RunEncounters.tsx\`
-
-
-## Summary of Changes
-
-Implemented team snapshot feature for boss battle results:
-
-- Created `boss_result_team` table (`id`, `boss_result_id` FK, `encounter_id` FK, `level`)
-- Added `BossResultTeam` model with relationship to `BossResult`
-- Updated schemas with `BossResultTeamMemberInput` and `BossResultTeamMemberResponse`
-- Updated `POST /runs/{run_id}/boss-results` to validate and save team snapshot
-- Added team selection UI in `BossDefeatModal` with level override
-- Display team snapshot in defeated boss cards on `RunEncounters.tsx`

.beans/archive/nuzlocke-tracker-xsdr--crash-crash-bug-typescript-build-fails-due-to-opti.md

@@ -1,37 +0,0 @@
----
-# nuzlocke-tracker-xsdr
-title: 'Crash: Crash: Bug: TypeScript build fails due to optional property type mismatches in journal components'
-status: completed
-type: bug
-priority: high
-created_at: 2026-03-20T19:12:50Z
-updated_at: 2026-03-20T19:17:39Z
-parent: nuzlocke-tracker-bw1m
-blocking:
-    - nuzlocke-tracker-3psa
----
-
-Agent crashed while working on nuzlocke-tracker-3psa.
-
-## Exit Code
-1
-
-## Last Output
-```
-Failed to authenticate. API Error: 401 {"type":"error","error":{"type":"authentication_error","message":"OAuth token has expired. Please obtain a new token or refresh your existing token."},"request_id":"req_011CZEs4QPgAQoZbS63nnkqT"}
-
-```
-
-## Context
-- Bean: nuzlocke-tracker-3psa
-- Title: Crash: Bug: TypeScript build fails due to optional property type mismatches in journal components
-- Type: bug
-
-## Summary of Changes
-
-Fixed TypeScript build errors caused by `exactOptionalPropertyTypes: true` requiring explicit `| undefined` in optional property types.
-
-**Files changed:**
-- `JournalEditor.tsx`: Added `| undefined` to `bossResults` and `bosses` prop types
-- `JournalEntryView.tsx`: Added `| undefined` to `bossResult` and `boss` prop types  
-- `JournalSection.tsx`: Added `| undefined` to `bossResults` and `bosses` prop types

.beans/nuzlocke-tracker-009n--add-cli-export-for-all-seed-data-types.md

@@ -0,0 +1,19 @@
+---
+# nuzlocke-tracker-009n
+title: Add CLI export for all seed data types
+status: completed
+type: feature
+priority: normal
+created_at: 2026-02-08T11:37:27Z
+updated_at: 2026-02-08T11:38:48Z
+---
+
+Add export functions for games, pokemon, routes/encounters, and evolutions to the seed CLI, matching the existing export API endpoints. Consolidate with the existing --export-bosses into a single --export flag that dumps everything.
+
+## Checklist
+- [x] Add export_games() to run.py — writes games.json
+- [x] Add export_pokemon() to run.py — writes pokemon.json
+- [x] Add export_routes() to run.py — writes {game_slug}.json per game (routes + encounters)
+- [x] Add export_evolutions() to run.py — writes evolutions.json
+- [x] Replace --export-bosses with --export flag that exports all data types
+- [x] Update __main__.py docstring

.beans/nuzlocke-tracker-0arz--integration-tests-for-runs-encounters-api.md

@@ -0,0 +1,30 @@
+---
+# nuzlocke-tracker-0arz
+title: Integration tests for Runs & Encounters API
+status: draft
+type: task
+created_at: 2026-02-10T09:33:21Z
+updated_at: 2026-02-10T09:33:21Z
+parent: nuzlocke-tracker-yzpb
+---
+
+Write integration tests for the core run tracking and encounter API endpoints. This is the heart of the application.
+
+## Checklist
+
+- [ ] Test run CRUD operations (create, list, get, update, delete)
+- [ ] Test run creation with rules configuration (JSONB field)
+- [ ] Test encounter logging on a run (create encounter on a route)
+- [ ] Test encounter status changes (alive → dead, alive → retired, etc.)
+- [ ] Test duplicate encounter prevention (dupes clause logic)
+- [ ] Test shiny encounter handling
+- [ ] Test egg encounter handling
+- [ ] Test ending a run (completion/failure)
+- [ ] Test error cases (encounter on invalid route, duplicate route encounters, etc.)
+
+## Notes
+
+- Run endpoints: `backend/src/app/api/runs.py`
+- Encounter endpoints: `backend/src/app/api/encounters.py`
+- This is the most critical area — Nuzlocke rules enforcement should be thoroughly tested
+- Tests need game + pokemon + route fixtures as prerequisites

.beans/nuzlocke-tracker-0pas--extract-version-groups-and-route-ordering-to-json.md

@@ -0,0 +1,11 @@
+---
+# nuzlocke-tracker-0pas
+title: Extract version groups and route ordering to JSON files
+status: completed
+type: task
+priority: normal
+created_at: 2026-02-07T13:27:37Z
+updated_at: 2026-02-07T13:32:30Z
+---
+
+Move VERSION_GROUPS and ROUTE_ORDER from fetch_pokeapi.py into separate JSON files (version_groups.json, route_order.json) for easier editing. Update the script to load from the JSON files.

.beans/nuzlocke-tracker-0q8f--encounter-tracking-interface.md

@@ -0,0 +1,28 @@
+---
+# nuzlocke-tracker-0q8f
+title: Encounter Tracking Interface
+status: completed
+type: task
+priority: normal
+created_at: 2026-02-04T15:44:37Z
+updated_at: 2026-02-05T14:21:54Z
+parent: nuzlocke-tracker-f5ob
+---
+
+Build the main interface for tracking encounters on each route/area.
+
+## Checklist
+- [x] Create route list component showing all areas in the game
+- [x] Display encounter status per route (uncaught, caught, failed, skipped)
+- [x] Build encounter modal/form:
+  - [x] Select Pokémon from route's available encounters
+  - [x] Enter nickname for caught Pokémon
+  - [x] Mark as caught, failed (ran/KO'd), or skipped (duplicates clause)
+- [x] Show route progression (e.g., 15/45 routes completed)
+- [x] Allow editing/updating existing encounters
+- [x] Support marking gift/static encounters separately (deferred to nuzlocke-tracker-rxrt)
+
+## UX Considerations
+- Quick entry flow - minimize clicks to log an encounter
+- Visual distinction between route types (grass, water, cave, etc.)
+- Mobile-friendly for tracking while playing

.beans/nuzlocke-tracker-1e9k--populate-encounter-data-for-gen-8-stub-games.md

@@ -0,0 +1,50 @@
+---
+# nuzlocke-tracker-1e9k
+title: Populate encounter data for Gen 8+ stub games
+status: completed
+type: task
+priority: normal
+created_at: 2026-02-10T08:59:02Z
+updated_at: 2026-02-11T13:39:09Z
+parent: nuzlocke-tracker-rzu4
+---
+
+Fill in encounter data for games that currently have null/stub seed files. These games are not covered by PokeAPI and require manual curation or an alternative data source.
+
+## Games with null/stub data:
+- [ ] Sword (null)
+- [ ] Shield (null)
+- [ ] Brilliant Diamond (null)
+- [ ] Shining Pearl (null)
+- [ ] Scarlet (null)
+- [ ] Violet (null)
+- [ ] Legends Arceus (null)
+
+## Format requirements:
+Each game's JSON file must follow the existing structure:
+\`\`\`json
+[
+  {
+    "name": "Route Name",
+    "order": 1,
+    "encounters": [
+      {
+        "pokeapi_id": 25,
+        "pokemon_name": "pikachu",
+        "method": "walk",
+        "encounter_rate": 10,
+        "min_level": 5,
+        "max_level": 8
+      }
+    ],
+    "children": []
+  }
+]
+\`\`\`
+
+## Notes:
+- This is likely the largest manual task unless the "explore automated sources" task finds a viable alternative
+- Depends on findings from the automated data sources task — if automation is viable, this becomes much easier
+- Sword/Shield and Scarlet/Violet use open-world/Wild Area mechanics that may need special handling
+- Legends Arceus has a fundamentally different encounter system (overworld encounters, alpha Pokémon, space-time distortions)
+- BD/SP are remakes of Diamond/Pearl — existing D/P data could serve as a starting point

.beans/nuzlocke-tracker-1guz--component-tests-for-key-frontend-components.md

@@ -0,0 +1,30 @@
+---
+# nuzlocke-tracker-1guz
+title: Component tests for key frontend components
+status: draft
+type: task
+created_at: 2026-02-10T09:33:45Z
+updated_at: 2026-02-10T09:33:45Z
+parent: nuzlocke-tracker-yzpb
+---
+
+Write component tests for the most important frontend React components, focusing on user interactions and rendering correctness.
+
+## Checklist
+
+- [ ] Test `EncounterModal` — form submission, validation, Pokemon selection
+- [ ] Test `StatusChangeModal` — status transitions, confirmation flow
+- [ ] Test `EndRunModal` — run completion/failure flow
+- [ ] Test `GameGrid` — game selection rendering, click handling
+- [ ] Test `RulesConfiguration` — rules toggle interactions, state management
+- [ ] Test `Layout` — navigation rendering, responsive behavior
+- [ ] Test admin form modals (GameFormModal, RouteFormModal, PokemonFormModal) — CRUD form flows
+- [ ] Test `AdminTable` — sorting, filtering, action buttons
+
+## Notes
+
+- Focus on user-facing behavior, not implementation details
+- Use @testing-library/user-event for simulating clicks, typing, etc.
+- Mock API responses for components that fetch data
+- Don't aim for 100% coverage — prioritise the most complex/interactive components
+- Page components (RunEncounters, RunDashboard, etc.) are large and complex — consider testing their sub-components instead

.beans/nuzlocke-tracker-1iuh--project-setup-tech-stack.md

@@ -0,0 +1,34 @@
+---
+# nuzlocke-tracker-1iuh
+title: Project Setup & Tech Stack
+status: completed
+type: task
+priority: normal
+created_at: 2026-02-04T15:43:55Z
+updated_at: 2026-02-04T15:55:46Z
+parent: nuzlocke-tracker-f5ob
+blocking:
+    - nuzlocke-tracker-sm1b
+    - nuzlocke-tracker-k5lm
+    - nuzlocke-tracker-uw2j
+    - nuzlocke-tracker-dgax
+    - nuzlocke-tracker-0q8f
+    - nuzlocke-tracker-hm6t
+    - nuzlocke-tracker-8tuw
+    - nuzlocke-tracker-8fcj
+---
+
+Set up the initial project structure and choose the technology stack.
+
+## Checklist
+- [x] Initialize the project (e.g., Vite + React/Vue/Svelte or Next.js)
+- [x] Set up TypeScript configuration
+- [x] Configure linting (ESLint) and formatting (Prettier)
+- [x] Set up basic folder structure (components, types, utils, data)
+- [x] Add Tailwind CSS or chosen styling solution
+- [x] Create basic app shell with routing
+
+## Considerations
+- Should be a web app for accessibility
+- Consider PWA capabilities for offline use
+- Keep bundle size small for fast loading

.beans/nuzlocke-tracker-25mh--genlocke-tracking.md

@@ -0,0 +1,89 @@
+---
+# nuzlocke-tracker-25mh
+title: Genlocke tracking
+status: completed
+type: epic
+priority: normal
+created_at: 2026-02-08T12:17:19Z
+updated_at: 2026-02-09T11:07:51Z
+---
+
+Track a **genlocke** — a series of linked nuzlocke runs, typically one per generation or region. The player picks one game per generation/region and surviving Pokemon carry over between legs.
+
+## User Flow
+
+### 1. Create Genlocke
+The user starts a new genlocke and gives it a name.
+
+### 2. Select Games (Legs)
+The user picks which games to play, in order. The UI offers **preset templates** to speed this up, but the user can always customize:
+
+- **True Genlocke** — One original game per generation (Red/Blue/Yellow → Gold/Silver/Crystal → Ruby/Sapphire/Emerald → ...). Uses the original releases only.
+- **Normal Genlocke** — Uses the latest remake or enhanced version for each region (FireRed/LeafGreen → HeartGold/SoulSilver → Emerald → Platinum → ...). This is the most common format.
+- **Custom** — The user picks any games in any order. No restrictions on which games or how many.
+
+For the preset templates, the user still picks *which* game within each generation/region slot (e.g., FireRed vs LeafGreen for Gen 1). The template just determines which slots are shown. The user can add/remove/reorder legs after selecting a template.
+
+Games are grouped by **region** (not release generation) for the purpose of presets, since that's how genlocke players think about it (e.g., FireRed is a "Kanto" leg, not a "Gen 3" leg).
+
+### 3. Configure Rules
+Two categories of rules are configured:
+
+**Per-game nuzlocke rules** — The standard nuzlocke ruleset (first encounter only, permadeath, duplicates clause, level caps, etc.). These are set once and apply uniformly to all legs. Uses the existing `NuzlockeRules` interface.
+
+**Genlocke-specific rules** — Overarching rules that govern how legs connect:
+- **Keep HoF** (default) — Pokemon that enter the Hall of Fame at the end of a leg are transferred to the next leg as eggs (breed at level 1). This is the standard genlocke mechanic.
+- **Retire HoF** — Pokemon that enter the Hall of Fame are retired. They (and their evolutionary families) become unavailable in future legs (added to a cumulative dupe list). This is also known as the "Gauntlet" rule. Increases difficulty by forcing new Pokemon each leg.
+- Potentially more rules in the future (e.g., item carry-over restrictions, level scaling).
+
+### 4. Sequential Run Progression
+- When the genlocke is created, the **first leg** is automatically started as a new nuzlocke run.
+- Each leg is a full nuzlocke run, tracked exactly like any standalone run (encounters, team, bosses, graveyard, etc.).
+- When a leg is marked as **completed** (Hall of Fame), the next leg is started. A transfer step happens between legs where the user selects which surviving Pokemon to carry forward.
+- When a leg is marked as **failed** (wipe), the genlocke itself is marked as failed (game over).
+- The final leg's completion marks the entire genlocke as completed.
+
+### 5. Genlocke Overview Page
+A dedicated page showing:
+- **Progress** — Which leg is active, which are completed, which are upcoming. Visual timeline or step indicator.
+- **Configuration** — Selected games, rules, genlocke-specific rules.
+- **Cumulative Stats** — Total encounters, total deaths, total HoF entries across all legs.
+- **Lineage Tracking** — Show Pokemon that have carried over across multiple legs (their journey through the genlocke).
+- **Cumulative Graveyard** — All deaths across all legs in one view.
+
+## Data Model
+
+### New entities:
+- **`Genlocke`** — Top-level entity: name, status (active/completed/failed), genlocke rules (JSONB), created_at.
+- **`GenlockeLeg`** — Join table linking a Genlocke to a NuzlockeRun: genlocke_id, run_id, leg_order. Defines the sequence.
+
+### Changes to existing entities:
+- **`NuzlockeRun`** — No schema changes needed. A run that's part of a genlocke is just a normal run that happens to be referenced by a GenlockeLeg. The genlocke-level rules are stored on the Genlocke, not duplicated per run.
+
+### Transfer tracking:
+- **`GenlockeTransfer`** — Records which Pokemon were carried between legs: from_leg_id, to_leg_id, encounter_id (the source encounter from the completed leg), to_encounter_id (the egg/gift encounter created in the next leg).
+
+## Child Features (suggested breakdown)
+1. **Genlocke creation wizard** — Multi-step UI: name → game selection (with presets) → rules → confirm
+2. **Genlocke overview page** — Dashboard with progress, stats, configuration
+3. **Leg progression** — Auto-start next leg when current completes, transfer step
+4. **Transfer UI** — Select surviving Pokemon to carry forward between legs
+5. **Lineage tracking** — Show a Pokemon's journey across legs
+6. **Cumulative graveyard** — Deaths across all legs in one view
+7. **Gauntlet/Retire HoF rule** — Enforce the "retire" mechanic with cumulative dupe list
+
+## Success Criteria
+- [x] A user can create a new genlocke via a multi-step wizard (name, game selection with presets, rules)
+- [x] Games can be selected using True Genlocke, Normal Genlocke, or Custom presets, grouped by region
+- [x] Nuzlocke rules are configured once and applied uniformly to all legs
+- [x] Genlocke-specific rules (Keep HoF / Retire HoF) can be selected
+- [x] The first leg starts automatically upon genlocke creation
+- [x] Each leg is a full nuzlocke run, tracked identically to standalone runs
+- [x] Completing a leg triggers a transfer step where surviving Pokemon can be carried forward
+- [x] Failing a leg marks the entire genlocke as failed
+- [x] Completing the final leg marks the genlocke as completed
+- [x] A genlocke overview page shows progress, configuration, cumulative stats, lineage, and graveyard
+- [x] Transferred Pokemon appear as eggs (base form, level 1) in the next leg
+- [x] Pokemon lineage is trackable across multiple legs
+- [x] A cumulative graveyard shows all deaths across the entire genlocke
+- [x] The Retire HoF / Gauntlet rule correctly retires HoF Pokemon and adds their families to the dupe list

.beans/nuzlocke-tracker-26my--crash-show-owner-info-in-admin-pages.md

@@ -1,29 +0,0 @@
----
-# nuzlocke-tracker-26my
-title: 'Crash: Show owner info in admin pages'
-status: completed
-type: bug
-priority: high
-created_at: 2026-03-22T09:41:57Z
-updated_at: 2026-03-22T09:45:38Z
-parent: nuzlocke-tracker-bw1m
-blocking:
-    - nuzlocke-tracker-2fp1
----
-
-Bean was found in 'in-progress' status on startup but no agent was running.
-This likely indicates a crash or unexpected termination.
-
-Manual review required before retrying.
-
-Bean: nuzlocke-tracker-2fp1
-Title: Show owner info in admin pages
-
-## Resolution
-
-No work required. The original bean (nuzlocke-tracker-2fp1) was already successfully completed:
-- All checklist items done
-- Commit a3f332f merged via PR #74
-- Original bean status: completed
-
-This crash bean was a false positive - likely created during a race condition when the original bean was transitioning from in-progress to completed.

.beans/nuzlocke-tracker-29oy--boss-seed-data-pipeline.md

@@ -0,0 +1,19 @@
+---
+# nuzlocke-tracker-29oy
+title: Boss seed data pipeline
+status: completed
+type: feature
+priority: normal
+created_at: 2026-02-08T11:33:33Z
+updated_at: 2026-02-08T11:35:13Z
+---
+
+Export boss data from admin, save as seed JSON files, and load them during seeding.
+
+## Checklist
+- [x] Add unique constraint to boss_battles (version_group_id, order) + Alembic migration
+- [x] Add upsert_bosses to seed loader (loader.py)
+- [x] Add boss loading step to seed runner (run.py)
+- [x] Add boss count to verify() function
+- [x] Add export_bosses() function to run.py
+- [x] Add --export-bosses flag to __main__.py

.beans/nuzlocke-tracker-2b4r--add-route-ordering-for-gen-5-games.md

@@ -0,0 +1,36 @@
+---
+# nuzlocke-tracker-2b4r
+title: Add route ordering for Gen 5+ games
+status: scrapped
+type: task
+priority: normal
+created_at: 2026-02-10T08:58:55Z
+updated_at: 2026-02-11T13:54:47Z
+parent: nuzlocke-tracker-rzu4
+---
+
+Add route progression ordering in `route_order.json` for all games that currently lack it. Routes should be ordered to match the typical in-game progression (main story first, post-game after).
+
+## Games needing route ordering:
+- [ ] Diamond/Pearl (could alias to Platinum if progression is similar enough)
+- [ ] Black/White
+- [ ] Black 2/White 2
+- [ ] X/Y
+- [ ] Sun/Moon
+- [ ] Ultra Sun/Ultra Moon (could alias to Sun/Moon if similar enough)
+- [ ] Sword/Shield
+- [ ] Brilliant Diamond/Shining Pearl (could alias to Platinum/Diamond-Pearl)
+- [ ] Scarlet/Violet
+- [ ] Legends Arceus
+- [ ] Legends Z-A
+- [ ] Let's Go Pikachu/Eevee (currently aliased to firered-leafgreen — verify this is correct)
+
+## Approach:
+- Reference Bulbapedia "walkthrough" or "appendix" pages for progression order
+- Consider aliasing games that share the same region and route progression
+- Mark a clear divider between main story and post-game routes where applicable
+- The format is an array of route name strings in `route_order.json`, keyed by version group slug
+
+## Notes:
+- This is primarily manual work — play order guides are widely available online
+- Verify route names match exactly what's in the encounter data files (case-sensitive)

.beans/nuzlocke-tracker-2fp1--show-owner-info-in-admin-pages.md

@@ -1,62 +0,0 @@
----
-# nuzlocke-tracker-2fp1
-title: Show owner info in admin pages
-status: completed
-type: feature
-priority: normal
-tags:
-    - -failed
-    - failed
-created_at: 2026-03-21T12:18:51Z
-updated_at: 2026-03-22T09:08:07Z
-parent: nuzlocke-tracker-wwnu
----
-
-## Problem
-
-Admin pages (`AdminRuns.tsx`, `AdminGenlockes.tsx`) don't show which user owns each run or genlocke. This makes it hard for admins to manage content.
-
-## Approach
-
-### Backend
-- The `/api/runs` list endpoint already returns run data — verify it includes `owner` (id + email). If not, add it to the response schema.
-- For genlockes, ownership is inferred from the first leg's run owner. Add an `owner` field to the genlocke list response that resolves from the first leg's run.
-
-### Frontend
-- `AdminRuns.tsx`: Add an "Owner" column showing the owner's email (or "No owner" for legacy runs)
-- `AdminGenlockes.tsx`: Add an "Owner" column showing the inferred owner from the first leg's run
-- Add owner filter dropdown to both pages
-
-## Files to modify
-
-- `backend/src/app/api/runs.py` — verify owner is included in list response
-- `backend/src/app/api/genlockes.py` — add owner resolution to list endpoint
-- `backend/src/app/schemas/genlocke.py` — add owner field to `GenlockeListItem`
-- `frontend/src/pages/admin/AdminRuns.tsx` — add Owner column + filter
-- `frontend/src/pages/admin/AdminGenlockes.tsx` — add Owner column + filter
-- `frontend/src/types/game.ts` — update types if needed
-
-## Checklist
-
-- [x] Verify runs list API includes owner info; add if missing
-- [x] Add owner resolution to genlocke list endpoint (from first leg's run)
-- [x] Update `GenlockeListItem` schema to include owner
-- [x] Add Owner column to `AdminRuns.tsx`
-- [x] Add Owner column to `AdminGenlockes.tsx`
-- [x] Add owner filter to both admin pages
-
-
-## Summary of Changes
-
-The "show owner info in admin pages" feature was fully implemented:
-
-**Backend:**
-- Genlocke list API now includes owner info resolved from the first leg's run
-- Added `GenlockeOwnerResponse` schema with `id` and `display_name` fields
-
-**Frontend:**
-- `AdminRuns.tsx`: Added Owner column showing email/display name with "No owner" fallback
-- `AdminGenlockes.tsx`: Added Owner column with same pattern
-- Both pages include owner filter dropdown with "All owners", "No owner", and per-user options
-
-Commit: `a3f332f feat: show owner info in admin pages`

.beans/nuzlocke-tracker-338l--verify-fetch-pokeapipy-rewrite.md

@@ -0,0 +1,23 @@
+---
+# nuzlocke-tracker-338l
+title: Verify fetch_pokeapi.py rewrite
+status: scrapped
+type: task
+priority: normal
+created_at: 2026-02-07T15:08:10Z
+updated_at: 2026-02-07T19:05:29Z
+---
+
+All code changes are complete. Run verification:
+1. Run the script to completion
+2. Verify output (pokemon.json has forms, correct IDs, etc.)
+3. Verify cache speedup on second run
+4. Frontend build check
+
+## Checklist
+- [ ] Run fetch_pokeapi.py to completion
+- [ ] Verify pokemon.json has more entries with forms (megas, gmax, regionals)
+- [ ] Verify pokeapi_id/national_dex split is correct
+- [ ] Verify route/encounter JSON files
+- [ ] Verify cache speedup on second run
+- [ ] Frontend build passes

.beans/nuzlocke-tracker-37gk--curate-route-ordering-to-match-game-progression.md

@@ -0,0 +1,11 @@
+---
+# nuzlocke-tracker-37gk
+title: Curate route ordering to match game progression
+status: completed
+type: feature
+priority: normal
+created_at: 2026-02-07T12:25:05Z
+updated_at: 2026-02-07T12:27:11Z
+---
+
+Implement ROUTE_ORDER in fetch_pokeapi.py for progression-based sorting, and add Export Order button to AdminGameDetail. See bean j28y for full plan.

.beans/nuzlocke-tracker-3c9l--set-up-branching-structure.md

@@ -0,0 +1,16 @@
+---
+# nuzlocke-tracker-3c9l
+title: Set up branching structure
+status: completed
+type: task
+priority: normal
+created_at: 2026-02-09T15:30:35Z
+updated_at: 2026-02-10T10:49:55Z
+parent: nuzlocke-tracker-ahza
+---
+
+Create the `develop` branch from `main` and establish the `main`/`develop`/`feature/*` branching workflow.
+
+- Create `develop` branch from current `main`
+- Push `develop` to remote
+- Set `develop` as the default working branch

.beans/nuzlocke-tracker-3el1--run-progression-dividers-main-story-endgame.md

@@ -0,0 +1,29 @@
+---
+# nuzlocke-tracker-3el1
+title: Run progression dividers (main story / endgame)
+status: completed
+type: feature
+priority: normal
+created_at: 2026-02-08T13:40:14Z
+updated_at: 2026-02-08T20:25:59Z
+---
+
+Add support for dividing a run's boss battle progression into sections like "Main Story" and "Endgame" (e.g., post-Elite Four content). This helps players visually distinguish where the main campaign ends and optional/endgame content begins.
+
+## Context
+
+Currently boss battles are displayed as a flat ordered list. In many Pokemon games there's a clear distinction between the main story (up through the Champion) and endgame content (rematches, Battle Frontier, Kanto in GSC/HGSS, etc.). A visual divider would make it easier to track progress through each phase.
+
+## Scope
+
+- **Admin side**: Allow marking boss battles or defining breakpoints that separate progression phases (e.g., "everything after this boss is endgame")
+- **Run side**: Render a visual divider/section header between main story and endgame boss battles
+- Should support at minimum two sections (main story, endgame), but consider whether the design should be flexible enough for arbitrary sections (e.g., "Kanto" in HGSS)
+
+## Checklist
+
+- [ ] Decide on data model approach (e.g., a `section` field on boss battles, or a separate progression divider entity tied to the version group)
+- [ ] Add backend models and migrations
+- [ ] Add API support for managing sections/dividers
+- [ ] Update admin UI to allow assigning bosses to sections or inserting dividers
+- [ ] Update run-side boss progression display to render section headers/dividers

.beans/nuzlocke-tracker-3lfw--configure-nginx-proxy-manager-for-nuzlocke-tracker.md

@@ -0,0 +1,18 @@
+---
+# nuzlocke-tracker-3lfw
+title: Configure Nginx Proxy Manager for nuzlocke-tracker
+status: completed
+type: task
+priority: normal
+created_at: 2026-02-09T15:30:50Z
+updated_at: 2026-02-10T08:44:18Z
+parent: nuzlocke-tracker-ahza
+blocking:
+    - nuzlocke-tracker-vpn5
+---
+
+Add a proxy host entry in Nginx Proxy Manager on Unraid to route LAN traffic to the app.
+
+- Add a proxy host (e.g., `nuzlocke.local`) pointing to the frontend/API containers
+- Configure appropriate ports and forwarding rules
+- Test access from other devices on the LAN

.beans/nuzlocke-tracker-48ds--database-backup-strategy.md

@@ -0,0 +1,17 @@
+---
+# nuzlocke-tracker-48ds
+title: Database backup strategy
+status: completed
+type: task
+priority: normal
+created_at: 2026-02-09T15:30:55Z
+updated_at: 2026-02-10T10:55:15Z
+parent: nuzlocke-tracker-ahza
+---
+
+Set up a simple scheduled backup for the production PostgreSQL database.
+
+- Create a backup script using `pg_dump` that runs inside or against the PostgreSQL container
+- Set up a cron job on Unraid to run the backup on a schedule (e.g., daily)
+- Store backups in a designated location on Unraid with rotation (keep last N backups)
+- Document the restore procedure

.beans/nuzlocke-tracker-4c31--backend-setup-framework.md

@@ -0,0 +1,30 @@
+---
+# nuzlocke-tracker-4c31
+title: Backend Setup & Framework
+status: completed
+type: task
+priority: normal
+created_at: 2026-02-04T15:46:49Z
+updated_at: 2026-02-04T16:10:13Z
+parent: nuzlocke-tracker-f5ob
+blocking:
+    - nuzlocke-tracker-l7e3
+    - nuzlocke-tracker-bkhs
+---
+
+Set up the backend API project with chosen framework and structure.
+
+## Checklist
+- [x] Choose backend framework (Node.js/Express, Fastify, NestJS, Go, Python/FastAPI, etc.) - **Python/FastAPI**
+- [x] Initialize backend project
+- [x] Set up TypeScript (if applicable) - N/A (Python with type hints via Pydantic)
+- [x] Configure linting and formatting - **ruff**
+- [x] Set up project structure (routes, controllers, services, models)
+- [x] Add environment configuration (.env handling) - **pydantic-settings**
+- [x] Set up development server with hot reload - **uvicorn --reload**
+- [x] Add basic health check endpoint - `/health` and `/`
+
+## Considerations
+- Should match team's expertise
+- Consider ease of deployment
+- TypeScript preferred for type safety with frontend

.beans/nuzlocke-tracker-4ph2--fix-and-complete-route-ordering-for-all-games.md

@@ -0,0 +1,44 @@
+---
+# nuzlocke-tracker-4ph2
+title: Fix and complete route ordering for all games
+status: completed
+type: task
+priority: normal
+created_at: 2026-02-11T13:55:09Z
+updated_at: 2026-02-11T14:21:24Z
+parent: nuzlocke-tracker-rzu4
+---
+
+Audit existing route ordering and add missing ordering for all games in `route_order.json`. Use Bulbapedia walkthrough/appendix pages as the primary reference for game progression order.
+
+## Approach:
+- Reference Bulbapedia walkthrough pages (e.g. `Appendix:FireRed_and_LeafGreen_walkthrough`) to determine correct progression order
+- Cross-reference route names from walkthroughs against actual route names in encounter data files
+- Consider building a script to semi-automate this (scrape walkthrough pages → match against encounter data → generate ordering)
+
+## Games to fix (existing but incorrect):
+- [x] Platinum — fixed ordering to start with Twinleaf Town, matched names to encounter data
+
+## Games to add ordering for:
+- [x] Diamond/Pearl (separate ordering, slight differences from Platinum)
+- [x] Black/White
+- [x] Black 2/White 2
+- [x] X/Y
+- [x] Sun/Moon
+- [x] Ultra Sun/Ultra Moon (separate ordering, has additional areas)
+- [x] Sword/Shield
+- [x] Brilliant Diamond/Shining Pearl (separate ordering with Grand Underground)
+- [x] Scarlet/Violet
+- [x] Legends Arceus
+- [x] Legends Z-A
+
+## Games to audit (existing, likely correct):
+- [x] FireRed/LeafGreen (and aliases: Red/Blue, Yellow, Let's Go) — rewritten with correct encounter data names
+- [x] HeartGold/SoulSilver (and aliases: Gold/Silver, Crystal) — rewritten with correct encounter data names
+- [x] Emerald (and aliases: Ruby/Sapphire, ORAS) — rewritten with correct encounter data names
+
+## Notes:
+- Route names must match exactly what's in the encounter data files (case-sensitive)
+- "Starter" should be the first entry for each game
+- Post-game areas placed after main story areas
+- Replaces beans nuzlocke-tracker-6lud and nuzlocke-tracker-2b4r

.beans/nuzlocke-tracker-532i--ux-remove-level-field-from-boss-defeat-modal.md

@@ -1,38 +0,0 @@
----
-# nuzlocke-tracker-532i
-title: 'UX: Make level field optional in boss defeat modal'
-status: completed
-type: feature
-priority: normal
-created_at: 2026-03-21T21:50:48Z
-updated_at: 2026-03-22T09:16:12Z
----
-
-## Problem
-
-When recording which team members beat a boss, users must manually enter a level for each pokemon. Since the app does not track levels anywhere else, this is unnecessary friction with no payoff.
-
-## Current Implementation
-
-- Level input in `BossDefeatModal.tsx:200-211`
-- DB column `boss_result_team.level` is `SmallInteger NOT NULL` (in `models.py`)
-- Level is required in the API schema
-
-## Proposed Solution
-
-Remove the level field entirely from the UI and make it optional in the backend:
-
-- [x] Remove level input from `BossDefeatModal.tsx`
-- [x] Make `level` column nullable in the database (alembic migration)
-- [x] Update the API schema to make level optional (default to null)
-- [x] Update any backend validation that requires level
-- [x] Verify boss result display still works without level data
-
-
-## Summary of Changes
-
-- Removed level input field from BossDefeatModal.tsx, simplifying team selection to just checkboxes
-- Created alembic migration to make boss_result_team.level column nullable
-- Updated SQLAlchemy model and Pydantic schemas to make level optional (defaults to null)
-- Updated RunEncounters.tsx to conditionally render level only when present
-- Updated frontend TypeScript types for BossResultTeamMember and BossResultTeamMemberInput

.beans/nuzlocke-tracker-55kp--docker-development-environment-setup.md

@@ -0,0 +1,26 @@
+---
+# nuzlocke-tracker-55kp
+title: Docker Development Environment Setup
+status: completed
+type: task
+priority: normal
+created_at: 2026-02-04T16:07:25Z
+updated_at: 2026-02-04T16:13:04Z
+parent: nuzlocke-tracker-f5ob
+---
+
+Set up Docker and docker-compose for local development environment.
+
+## Checklist
+- [x] Create Dockerfile for backend API
+- [x] Create Dockerfile for frontend (if needed)
+- [x] Create docker-compose.yml with services (api, db, frontend)
+- [x] Add PostgreSQL service configuration
+- [x] Configure volume mounts for hot reload
+- [x] Add environment variable handling
+- [x] Create .dockerignore files
+- [x] Document usage in README
+
+## Notes
+- Should support hot reload for development
+- Database data should persist between restarts

.beans/nuzlocke-tracker-5bez--non-evolution-form-changes.md

@@ -0,0 +1,31 @@
+---
+# nuzlocke-tracker-5bez
+title: Non-evolution form changes
+status: completed
+type: feature
+priority: normal
+created_at: 2026-02-07T13:40:00Z
+updated_at: 2026-02-08T11:57:36Z
+---
+
+Some Pokemon can change form without evolving, using items or abilities. These form changes affect types, stats, and appearance but are not part of the evolution chain.
+
+## Examples
+
+- **Oricorio**: Changes form (Baile/Pom-Pom/Pa'u/Sensu) by using nectar items from different islands. Each form has a different type (Fire, Electric, Psychic, Ghost + Flying).
+- **Darmanitan**: Has a Zen Mode ability that changes it to Darmanitan (Zen) in battle (Fire/Psychic). Galarian Darmanitan Zen Mode is Ice/Fire.
+- **Rotom**: Changes form by interacting with appliances (Heat/Wash/Frost/Fan/Mow), each with different secondary types.
+- **Shaymin**: Changes between Land and Sky forme using the Gracidea flower.
+- **Tornadus/Thundurus/Landorus**: Incarnate vs Therian forms via the Reveal Glass.
+- **Hoopa**: Confined vs Unbound via the Prison Bottle.
+
+## Scope
+
+This is lower priority than basic form support (bean f44d) and submodule update (bean 6aje). It matters for tracking because a player might catch an Oricorio in one form and change it to another — the tracker should reflect the current form's types.
+
+## Design considerations
+
+- Should the tracker allow manually changing a caught Pokemon's form?
+- Or should it just track the form as encountered and leave it static?
+- How to represent form-change items/methods in the data model?
+- This may not need seed data support — could be a manual UI action on a caught Pokemon

.beans/nuzlocke-tracker-5o1v--improve-encounter-method-input-in-route-encounter.md

@@ -0,0 +1,28 @@
+---
+# nuzlocke-tracker-5o1v
+title: Improve encounter method input in route encounter form
+status: completed
+type: feature
+priority: normal
+created_at: 2026-02-08T19:06:10Z
+updated_at: 2026-02-08T19:17:14Z
+parent: nuzlocke-tracker-iu5b
+---
+
+Replace the free-text encounter method input in the route encounter form (RouteEncounterFormModal) with a smarter selector that leverages the known encounter methods already defined in the codebase.
+
+## Current behavior
+- The encounter method field in RouteEncounterFormModal is a plain `<input type="text">` with a placeholder "e.g. Walking, Surfing, Fishing"
+- Easy to introduce typos or inconsistent naming (e.g. "walking" vs "walk" vs "Grass")
+- The app already has a well-defined set of encounter methods in `EncounterMethodBadge.tsx` with METHOD_CONFIG and METHOD_ORDER (starter, gift, fossil, trade, walk, headbutt, surf, rock-smash, old-rod, good-rod, super-rod)
+- The backend stores this as a `String(30)` column, so it's not strictly enum-constrained
+
+## Desired behavior
+- Replace the free-text input with a dropdown/select that lists the known encounter methods from METHOD_ORDER, using the human-readable labels from getMethodLabel()
+- Include an "Other" option that reveals a text input for custom methods not in the predefined list
+- When editing an existing encounter, pre-select the correct method
+- Consider showing the colored badge preview next to each option for visual consistency with how methods appear elsewhere in the app
+
+## Files
+- `frontend/src/components/admin/RouteEncounterFormModal.tsx` — replace the text input with new selector
+- `frontend/src/components/EncounterMethodBadge.tsx` — export METHOD_CONFIG or add a helper to get the list of known methods

.beans/nuzlocke-tracker-5uoz--fix-webp-sprites-not-loading-in-production-nginx.md

@@ -0,0 +1,11 @@
+---
+# nuzlocke-tracker-5uoz
+title: Fix webp sprites not loading in production nginx
+status: completed
+type: bug
+priority: normal
+created_at: 2026-02-11T12:21:29Z
+updated_at: 2026-02-11T12:24:02Z
+---
+
+Sprites (.webp) don't load in prod while .png images work fine. The files are in the container but nginx/proxy isn't serving them correctly. Fix by adding explicit webp MIME type to nginx config.

.beans/nuzlocke-tracker-5wsn--add-run-management-to-admin-panel.md

@@ -0,0 +1,11 @@
+---
+# nuzlocke-tracker-5wsn
+title: Add run management to admin panel
+status: completed
+type: feature
+priority: normal
+created_at: 2026-02-08T09:53:01Z
+updated_at: 2026-02-08T09:53:25Z
+---
+
+Create AdminRuns page with table listing all runs (name, game, status, started date) with delete functionality. Wire it into routing and admin navigation.

.beans/nuzlocke-tracker-66hg--auto-select-boss-team-variant-based-on-starter-cho.md

@@ -0,0 +1,37 @@
+---
+# nuzlocke-tracker-66hg
+title: Auto-select boss team variant based on starter choice
+status: completed
+type: feature
+priority: normal
+created_at: 2026-02-08T20:21:40Z
+updated_at: 2026-02-08T20:34:35Z
+---
+
+When a run's starter Pokemon is known, automatically match it against boss battle condition labels (e.g., "Chose Bulbasaur") and pre-select the matching variant instead of showing the pill selector.
+
+## Context
+
+Currently, bosses with variant teams (condition_label) display a pill selector on the run page (BossDefeatModal and RunEncounters BossTeamPreview) so the user can manually toggle between team variants. However, if the run's starter choice is known, the correct variant can be inferred automatically.
+
+## Behavior
+
+- If the run has a starter Pokemon recorded, check each variant's condition label for a match (e.g., starter name "Bulbasaur" matches condition label "Chose Bulbasaur")
+- If exactly one condition label matches, auto-select that variant and hide the pill selector entirely
+- If no match is found (or the run has no starter), fall back to showing the pill selector as today
+- Matching should be case-insensitive and check if the starter name appears anywhere in the condition label (substring match)
+
+## Affected Components
+
+- `BossDefeatModal` — auto-select variant, hide pills when matched
+- `BossTeamPreview` in `RunEncounters` — same logic
+- May need to check how/where the run's starter Pokemon is stored and accessible
+
+## Checklist
+
+- [x] Determine how the starter Pokemon is stored/accessible from the run data
+- [x] Add matching logic to find the right variant from condition labels
+- [x] Update BossDefeatModal to auto-select and hide pills when starter matches
+- [x] Update BossTeamPreview in RunEncounters with same logic
+- [ ] Test with variant bosses where starter matches a condition
+- [ ] Test fallback behavior when no starter is set or no match found

.beans/nuzlocke-tracker-6aje--update-pokeapi-data-submodule-to-latest-version.md

@@ -0,0 +1,30 @@
+---
+# nuzlocke-tracker-6aje
+title: Update PokeAPI data submodule to latest version
+status: completed
+type: task
+priority: high
+created_at: 2026-02-06T10:53:45Z
+updated_at: 2026-02-07T14:35:41Z
+---
+
+The local PokeAPI data repository we use as a submodule is outdated. It's missing data for newer Pokemon forms and potentially newer games.
+
+## Why this is important now
+
+After adding form support to seeding (bean f44d), we discovered that the submodule is missing many form entries. Currently only 16 forms are included — all from Gen 7 (Alolan + Oricorio/Lycanroc). Missing forms include:
+
+- **Galarian forms** (Gen 8): Galarian Meowth, Ponyta, Rapidash, Slowpoke, Farfetch'd, Weezing, Mr. Mime, Corsola, Zigzagoon, Linoone, Darumaka, Darmanitan, Stunfisk, Yamask
+- **Hisuian forms** (Gen 8/Legends Arceus): Hisuian Growlithe, Voltorb, Typhlosion, Samurott, Decidueye, Zorua, Zoroark, Braviary, Goodra, Avalugg, Sneasel, Lilligant, Qwilfish, Sliggoo
+- **Paldean forms** (Gen 9): Paldean Wooper, Tauros
+- **Other missing forms**: Basculin (White-Striped), regional bird variants, etc.
+
+These forms have different types and stats from their base species and appear in encounter data for their respective games. Without them in the submodule, the seeding script can't create Pokemon records for them.
+
+## Action
+
+- Check for updates to the PokeAPI data repository
+- Update the submodule to the latest version
+- Re-run fetch_pokeapi.py to regenerate seed data
+- Add any new games to VERSION_GROUPS in fetch_pokeapi.py
+- Verify that form count increases significantly after update

.beans/nuzlocke-tracker-6kux--admin-panel-tabs-for-routesbosses-boss-export.md

@@ -0,0 +1,11 @@
+---
+# nuzlocke-tracker-6kux
+title: 'Admin Panel: Tabs for Routes/Bosses + Boss Export'
+status: completed
+type: feature
+priority: normal
+created_at: 2026-02-08T10:49:47Z
+updated_at: 2026-02-08T10:51:25Z
+---
+
+Add tabbed UI to AdminGameDetail (Routes/Bosses tabs) and boss battle export endpoint

.beans/nuzlocke-tracker-6lud--audit-and-fix-route-ordering-for-gen-1-4-games.md

@@ -0,0 +1,31 @@
+---
+# nuzlocke-tracker-6lud
+title: Audit and fix route ordering for Gen 1-4 games
+status: scrapped
+type: task
+priority: normal
+created_at: 2026-02-10T08:59:16Z
+updated_at: 2026-02-11T13:54:47Z
+parent: nuzlocke-tracker-rzu4
+---
+
+Review the existing route ordering for Gen 1-4 games that already have ordering defined. The current ordering may not accurately reflect typical game progression.
+
+## Games to audit:
+- [ ] FireRed/LeafGreen (and aliased: Red/Blue, Yellow, Let's Go)
+- [ ] HeartGold/SoulSilver (and aliased: Gold/Silver, Crystal)
+- [ ] Emerald (and aliased: Ruby/Sapphire, Omega Ruby/Alpha Sapphire)
+- [ ] Platinum
+
+## What to check:
+- Routes are in correct progression order (match typical walkthrough)
+- No routes are missing from the ordering
+- No routes are listed that don't exist in the encounter data
+- Aliases make sense (e.g. Red/Blue may have slightly different progression from FR/LG)
+- Post-game areas are placed after main story areas
+- Sub-areas (children) inherit parent ordering correctly
+
+## Notes:
+- Cross-reference with Bulbapedia walkthrough pages
+- The Platinum ordering currently starts with cities and mines rather than the starting town/routes — this may be incorrect
+- Diamond/Pearl currently aliases to nothing — check if it should alias to Platinum or needs its own ordering

.beans/nuzlocke-tracker-704x--run-progression-dividers-main-story-endgame.md

@@ -0,0 +1,11 @@
+---
+# nuzlocke-tracker-704x
+title: Run progression dividers (main story / endgame)
+status: completed
+type: feature
+priority: normal
+created_at: 2026-02-08T13:46:12Z
+updated_at: 2026-02-08T13:48:28Z
+---
+
+Add section field to boss battles to enable visual dividers between game progression phases (Main Story, Endgame, etc.) in both admin and run views.

.beans/nuzlocke-tracker-73ba--enforce-run-ownership-on-all-mutation-endpoints.md

@@ -1,84 +0,0 @@
----
-# nuzlocke-tracker-73ba
-title: Enforce run ownership on all mutation endpoints
-status: completed
-type: bug
-priority: critical
-created_at: 2026-03-21T12:18:27Z
-updated_at: 2026-03-21T12:28:35Z
-parent: nuzlocke-tracker-wwnu
----
-
-## Problem
-
-Backend mutation endpoints for encounters, bosses, and run updates use `require_auth` but do NOT verify the authenticated user is the run's owner. Any authenticated user can modify any run's encounters, mark bosses as defeated, or change run settings.
-
-Additionally, `_check_run_access` in `runs.py:184` allows anyone to edit unowned (legacy) runs when `require_owner=False`.
-
-### Affected endpoints
-
-**encounters.py** — all mutations use `require_auth` with no ownership check:
-- `POST /runs/{run_id}/encounters` (line 35)
-- `PATCH /runs/{run_id}/encounters/{encounter_id}` (line 142)
-- `DELETE /runs/{run_id}/encounters/{encounter_id}` (line 171)
-- `POST /runs/{run_id}/encounters/bulk-randomize` (line 203)
-
-**bosses.py** — boss result mutations:
-- `POST /runs/{run_id}/boss-results` (line 347)
-- `DELETE /runs/{run_id}/boss-results/{result_id}` (line 428)
-
-**runs.py** — run updates/deletion:
-- `PATCH /runs/{run_id}` (line 379) — uses `_check_run_access(run, user, require_owner=run.owner_id is not None)` which skips check for unowned runs
-- `DELETE /runs/{run_id}` (line 488) — same conditional check
-
-**genlockes.py** — genlocke mutations:
-- `POST /genlockes` (line 439) — no owner assigned to created genlocke or its first run
-- `PATCH /genlockes/{id}` (line 824) — no ownership check
-- `DELETE /genlockes/{id}` (line 862) — no ownership check
-- `POST /genlockes/{id}/legs/{leg_order}/advance` (line 569) — no ownership check
-- `POST /genlockes/{id}/legs` (line 894) — no ownership check
-- `DELETE /genlockes/{id}/legs/{leg_id}` (line 936) — no ownership check
-
-## Approach
-
-1. Add a reusable `_check_run_owner(run, user)` helper in `auth.py` or `runs.py` that raises 403 if `user.id != str(run.owner_id)` (no fallback for unowned runs — they should be read-only)
-2. Apply ownership check to ALL encounter/boss/run mutation endpoints
-3. For genlocke mutations, load the first leg's run and verify ownership against that
-4. Update `_check_run_access` to always require ownership for mutations (remove the `require_owner` conditional)
-5. When creating runs (standalone or via genlocke), set `owner_id` from the authenticated user
-
-## Checklist
-
-- [x] Add `_check_run_owner` helper that rejects non-owners (including unowned/legacy runs)
-- [x] Apply ownership check to all 4 encounter mutation endpoints
-- [x] Apply ownership check to both boss result mutation endpoints
-- [x] Fix `_check_run_access` to always require ownership on mutations
-- [x] Set `owner_id` on run creation in `runs.py` and `genlockes.py` (create_genlocke, advance_leg)
-- [x] Apply ownership check to all genlocke mutation endpoints (via first leg's run owner)
-- [x] Add tests for ownership enforcement (403 for non-owner, 401 for unauthenticated)
-
-## Summary of Changes
-
-Added `require_run_owner` helper in `auth.py` that enforces ownership on mutation endpoints:
-- Returns 403 for unowned (legacy) runs - they are now read-only
-- Returns 403 if authenticated user is not the run's owner
-
-Applied ownership checks to:
-- All 4 encounter mutation endpoints (create, update, delete, bulk-randomize)
-- Both boss result mutation endpoints (create, delete)
-- Run update and delete endpoints (via `require_run_owner`)
-- All 5 genlocke mutation endpoints (update, delete, advance_leg, add_leg, remove_leg via `_check_genlocke_owner`)
-
-Added `owner_id` on run creation:
-- `runs.py`: create_run already sets owner_id (verified)
-- `genlockes.py`: create_genlocke now sets owner_id on the first run
-- `genlockes.py`: advance_leg preserves owner_id from current run to new run
-
-Renamed `_check_run_access` to `_check_run_read_access` (read-only visibility check) for clarity.
-
-Added 22 comprehensive tests in `test_ownership.py` covering:
-- Owner can perform mutations
-- Non-owner gets 403 on mutations
-- Unauthenticated user gets 401
-- Unowned (legacy) runs reject all mutations
-- Read access preserved for public runs

.beans/nuzlocke-tracker-765i--update-claudemd-with-branching-rules.md

@@ -0,0 +1,20 @@
+---
+# nuzlocke-tracker-765i
+title: Update CLAUDE.md with branching rules
+status: completed
+type: task
+priority: normal
+created_at: 2026-02-09T15:30:38Z
+updated_at: 2026-02-10T10:49:56Z
+parent: nuzlocke-tracker-ahza
+blocking:
+    - nuzlocke-tracker-3c9l
+---
+
+Once the branching structure is in place, add instructions to CLAUDE.md enforcing the branching strategy:
+
+- Never commit directly to `main`
+- Day-to-day work happens on `develop`
+- New work is done on `feature/*` branches off `develop`
+- Merge flow: `feature/*` → `develop` → `main`
+- `main` is always production-ready

.beans/nuzlocke-tracker-7jba--review-and-complete-special-encounters-for-all-gam.md

@@ -0,0 +1,27 @@
+---
+# nuzlocke-tracker-7jba
+title: Review and complete special encounters for all games
+status: completed
+type: task
+priority: normal
+created_at: 2026-02-10T08:59:24Z
+updated_at: 2026-02-11T13:52:06Z
+parent: nuzlocke-tracker-rzu4
+---
+
+Only starters were missing from the encounter data. Gifts, trades, and fossils are already present in the per-game encounter JSON files.
+
+The `special_encounters.json` file previously contained starters, gifts, and fossils for Gen 1-3 — but only the starters were actually needed (the rest was redundant). Additionally, starters were missing for Gen 4+ games. Yellow and Let's Go were incorrectly aliased to firered-leafgreen (wrong starters).
+
+## Checklist:
+- [x] Remove non-starter entries from special_encounters.json
+- [x] Add Yellow starter (Pikachu) — was incorrectly aliased to firered-leafgreen
+- [x] Add Let's Go starters (Pikachu, Eevee) — was incorrectly aliased to firered-leafgreen
+- [x] Add Gen 4 starters (Diamond/Pearl/Platinum/BD/SP)
+- [x] Add Gen 5 starters (Black/White/B2/W2)
+- [x] Add Gen 6 starters (X/Y)
+- [x] Add Gen 7 starters (Sun/Moon/USUM)
+- [x] Add Gen 8 starters (Sword/Shield)
+- [x] Add Gen 9 starters (Scarlet/Violet)
+- [x] Add Legends Arceus starters
+- [x] Add Legends Z-A starters

.beans/nuzlocke-tracker-8b25--ux-allow-editing-caught-pokemon-details-on-run-pag.md

@@ -1,36 +0,0 @@
----
-# nuzlocke-tracker-8b25
-title: 'UX: Allow editing caught pokemon details on run page'
-status: draft
-type: feature
-priority: normal
-created_at: 2026-03-21T22:00:55Z
-updated_at: 2026-03-21T22:04:08Z
----
-
-## Problem
-
-Users can mistype catch level, nickname, or other details when recording an encounter, but there's no way to correct mistakes from the run page. The only option is to go through admin — which doesn't even support editing encounters for a specific run.
-
-## Current State
-
-- **Backend `EncounterUpdate` schema** (`backend/src/app/schemas/encounter.py:18-23`): Supports `nickname`, `status`, `faint_level`, `death_cause`, `current_pokemon_id` — but NOT `catch_level`
-- **Frontend `UpdateEncounterInput`** (`frontend/src/types/game.ts:169-175`): Same fields as backend, missing `catch_level`
-- **Run page encounter modal**: Clicking a route with an existing encounter opens the modal in "edit" mode, but only allows changing pokemon/nickname/status — no catch_level editing
-- The encounter modal is the create/edit modal — editing is done by re-opening it on an existing encounter
-
-## Approach
-
-### Backend
-- [ ] Add `catch_level: int | None = None` to `EncounterUpdate` schema
-- [ ] Verify the PATCH `/encounters/{id}` endpoint applies `catch_level` updates (check `encounters.py` update handler)
-
-### Frontend
-- [ ] Add `catchLevel?: number` to `UpdateEncounterInput` type
-- [ ] Ensure the encounter modal shows catch_level as editable when editing an existing encounter
-- [ ] Add catch_level field to the encounter edit modal (shown when editing existing encounters)
-
-### Testing
-- [ ] Test updating catch_level via API
-- [ ] Test that the frontend sends catch_level in update requests
-- [ ] Verify existing create/update flows still work

.beans/nuzlocke-tracker-8fcj--local-storage-persistence.md

@@ -0,0 +1,37 @@
+---
+# nuzlocke-tracker-8fcj
+title: Frontend API Integration
+status: completed
+type: task
+priority: normal
+created_at: 2026-02-04T15:44:42Z
+updated_at: 2026-02-05T13:55:52Z
+parent: nuzlocke-tracker-f5ob
+blocking:
+    - nuzlocke-tracker-uw2j
+    - nuzlocke-tracker-0q8f
+    - nuzlocke-tracker-hm6t
+    - nuzlocke-tracker-8tuw
+---
+
+Implement frontend services to communicate with the backend API.
+
+## Checklist
+- [x] Create API client/service layer
+- [x] Implement API calls for:
+  - [x] Fetch available games
+  - [x] Fetch routes for a game
+  - [x] Fetch Pokémon data
+  - [x] Create/update/delete Nuzlocke runs
+  - [x] Create/update encounters
+  - [x] Update Pokémon status
+- [x] Add loading states and error handling
+- [x] Add retry logic for failed requests
+
+## Technical Notes
+- Using native `fetch` via `src/api/client.ts` wrapper
+- Using TanStack Query for caching, loading states, and retry
+- All API responses typed with TypeScript
+- Vite dev proxy configured for `/api` → backend
+- Query hooks in `src/hooks/` for each domain (games, pokemon, runs, encounters)
+- Mutations auto-invalidate relevant query caches

.beans/nuzlocke-tracker-8tuw--run-dashboardoverview.md

@@ -0,0 +1,28 @@
+---
+# nuzlocke-tracker-8tuw
+title: Run Dashboard/Overview
+status: completed
+type: task
+priority: normal
+created_at: 2026-02-04T15:44:38Z
+updated_at: 2026-02-05T14:16:36Z
+parent: nuzlocke-tracker-f5ob
+---
+
+Create the main dashboard showing the current state of the Nuzlocke run.
+
+## Checklist
+- [x] Show run statistics:
+  - [x] Total encounters (caught/failed/skipped)
+  - [x] Total deaths
+  - [x] Routes completed
+- [x] Quick navigation to:
+  - [x] Route list / encounter tracking
+  - [x] Graveyard (fallen Pokémon)
+- [x] Show active rules as badges/icons
+- [x] Display game name and run start date
+
+## UX Considerations
+- This is the home screen users return to most
+- Keep it clean and informative at a glance
+- Easy access to add new encounters

.beans/nuzlocke-tracker-8w9s--gauntlet-rule-option-for-genlockes.md

@@ -0,0 +1,40 @@
+---
+# nuzlocke-tracker-8w9s
+title: Gauntlet rule option for genlockes
+status: completed
+type: feature
+priority: normal
+created_at: 2026-02-08T19:15:43Z
+updated_at: 2026-02-09T09:05:12Z
+parent: nuzlocke-tracker-25mh
+---
+
+Add the **Retire HoF** (aka Gauntlet) rule as a genlocke-specific rule option. When enabled, Pokemon that enter the Hall of Fame at the end of a leg are NOT transferred to the next game — instead, they and their entire evolutionary families are added to a cumulative dupe list for all subsequent legs.
+
+## Behavior
+- Toggled as a genlocke-specific rule during genlocke creation (step 3 of the wizard)
+- Mutually exclusive with "Keep HoF" — you pick one or the other
+- When a leg is completed:
+  - Surviving HoF Pokemon are marked as "retired" rather than being available for transfer
+  - Their evolutionary families (full chain: e.g., Charmander/Charmeleon/Charizard) are added to a cumulative dupe list
+  - In subsequent legs, the duplicates clause treats these families as already caught/dead
+- The cumulative dupe list grows with each completed leg, making later legs increasingly restrictive
+- The genlocke overview page should display the cumulative retired/duped families
+
+## Dependencies
+- Requires the genlocke creation wizard (to set the rule)
+- Requires the leg progression system (to trigger retirement on leg completion)
+- Should integrate with the existing duplicates clause enforcement in the encounter system
+
+## Notes
+- This is a popular variant that increases difficulty by forcing entirely new Pokemon each generation
+- The dupe list should be visible somewhere in the genlocke dashboard so the player knows which families are off-limits
+
+## Checklist
+- [x] Add a `retireHoF` boolean (or equivalent) to the genlocke rules JSONB schema
+- [x] On leg completion with Retire HoF enabled: resolve the full evolutionary families of all surviving HoF Pokemon
+- [x] Store the cumulative retired families list (could be a JSONB field on the Genlocke, or derived from completed legs)
+- [x] Implement `GET /api/v1/genlockes/{id}/retired-families` — return the list of retired evolutionary families with which leg they were retired in
+- [x] Integrate with the encounter system's duplicates clause: when logging an encounter in a genlocke leg, check the cumulative retired list and flag duplicates
+- [ ] Build a "Retired Families" display on the genlocke overview page showing all off-limits Pokemon with their sprites
+- [x] Ensure the creation wizard's genlocke rules step correctly toggles between Keep HoF and Retire HoF

.beans/nuzlocke-tracker-94hx--add-sort-options-to-run-team-overview.md

@@ -0,0 +1,29 @@
+---
+# nuzlocke-tracker-94hx
+title: Add sort options to run team overview
+status: completed
+type: feature
+priority: normal
+created_at: 2026-02-09T10:03:49Z
+updated_at: 2026-02-09T11:09:33Z
+---
+
+The Active Team / Final Team section on the run dashboard (`RunDashboard.tsx`) currently displays Pokemon in whatever order encounters arrive from the backend — there is no explicit sorting. Add a sort dropdown so the user can choose how their team is ordered.
+
+## Sort options
+- **Route order** (default) — sort by the route's `order` field, matching game progression
+- **Catch level** — sort by `catchLevel`, ascending
+- **Species name** — sort alphabetically by the display Pokemon's name (accounting for evolutions via `currentPokemon`)
+- **National Dex** — sort by the display Pokemon's `nationalDex` number
+
+## Scope
+- Frontend-only change — all data is already available in the `EncounterDetail` objects
+- Add a small sort control (dropdown or segmented buttons) above the team grid
+- Persist the selected sort in component state (no need for localStorage)
+- Apply the same sort options to both the Active Team and Graveyard sections
+
+## Checklist
+- [x] Add sort state and sort logic to `RunDashboard.tsx`
+- [x] Add sort dropdown/control above the team grid
+- [x] Apply sorting to both `alive` and `dead` encounter arrays
+- [x] Verify sort works correctly with evolved Pokemon (use `currentPokemon ?? pokemon` for name/dex)

.beans/nuzlocke-tracker-94v0--handle-pokemon-forms-properly.md

@@ -0,0 +1,11 @@
+---
+# nuzlocke-tracker-94v0
+title: Handle Pokemon Forms properly
+status: scrapped
+type: task
+priority: normal
+created_at: 2026-02-05T17:47:30Z
+updated_at: 2026-02-07T13:21:32Z
+---
+
+Some pokemon have different forms, either regional forms or based on other criteria. They behave differently, are different encounters and might have different evolutions. This needs to be handled.

.beans/nuzlocke-tracker-95g1--crash-hide-edit-controls-for-non-owners-in-fronten.md

@@ -1,28 +0,0 @@
----
-# nuzlocke-tracker-95g1
-title: 'Crash: Hide edit controls for non-owners in frontend'
-status: completed
-type: bug
-priority: high
-created_at: 2026-03-22T09:41:57Z
-updated_at: 2026-03-22T09:46:59Z
-parent: nuzlocke-tracker-bw1m
-blocking:
-    - nuzlocke-tracker-i2va
----
-
-Bean was found in 'in-progress' status on startup but no agent was running.
-This likely indicates a crash or unexpected termination.
-
-Manual review required before retrying.
-
-Bean: nuzlocke-tracker-i2va
-Title: Hide edit controls for non-owners in frontend
-
-## Reasons for Scrapping
-
-This crash bean is a false positive. The original task (nuzlocke-tracker-i2va) was already completed and merged to `develop` before this crash bean was created:
-- Commit `3bd24fc`: fix: hide edit controls for non-owners in frontend
-- Commit `118dbca`: chore: mark bean nuzlocke-tracker-i2va as completed
-
-No additional work required.

.beans/nuzlocke-tracker-9c66--integration-tests-for-genlockes-bosses-api.md

@@ -0,0 +1,30 @@
+---
+# nuzlocke-tracker-9c66
+title: Integration tests for Genlockes & Bosses API
+status: draft
+type: task
+created_at: 2026-02-10T09:33:26Z
+updated_at: 2026-02-10T09:33:26Z
+parent: nuzlocke-tracker-yzpb
+---
+
+Write integration tests for the genlocke challenge and boss battle API endpoints.
+
+## Checklist
+
+- [ ] Test genlocke CRUD operations (create, list, get, update, delete)
+- [ ] Test leg management (add/remove legs to a genlocke)
+- [ ] Test Pokemon transfers between genlocke legs
+- [ ] Test boss battle CRUD (create, list, update, delete per game)
+- [ ] Test boss battle results per run (record win/loss)
+- [ ] Test stats endpoint for run statistics
+- [ ] Test export endpoint
+- [ ] Test error cases (invalid transfers, boss results for wrong game, etc.)
+
+## Notes
+
+- Genlocke endpoints: `backend/src/app/api/genlockes.py`
+- Boss endpoints: `backend/src/app/api/bosses.py`
+- Stats endpoints: `backend/src/app/api/stats.py`
+- Export endpoints: `backend/src/app/api/export.py`
+- Genlocke tests require multiple runs as fixtures