nuzlocke-tracker/.beans/nuzlocke-tracker-m86o--add-naming-scheme-selection-to-run-configuration.md

title, status, type, priority, created_at, updated_at, parent, blocking

title	status	type	priority	created_at	updated_at	parent	blocking
Add naming scheme selection to run configuration	completed	task	normal	2026-02-11T15:56:44Z	2026-02-11T20:37:00Z	nuzlocke-tracker-igl3	nuzlocke-tracker-bi4e

Allow users to select a naming scheme (category) for their Nuzlocke run.

Requirements

• Add a naming_scheme column to the NuzlockeRun model (nullable string — user may not want auto-naming)
• Provide a dropdown/selector in run creation and run settings where the user can pick a category
• List available categories dynamically by querying a backend endpoint that reads the dictionary file
• Allow changing the naming scheme mid-run

Implementation Notes

• Storage: Dedicated nullable naming_scheme column on NuzlockeRun (not in the rules JSONB). This is a first-class run setting.
• Migration: Add an Alembic migration for the new column.
• API: Add/update the run creation and update endpoints to accept namingScheme.
• Categories endpoint: Add a GET endpoint that returns the list of available category names from the dictionary file, so the frontend can populate the dropdown.

Checklist

• Add naming_scheme nullable column to NuzlockeRun model
• Create Alembic migration for the new column
• Update run Pydantic schemas to include namingScheme
• Update run creation and update endpoints to persist the naming scheme
• Add GET endpoint to list available naming categories from the dictionary
• Add naming scheme selector to run creation UI
• Add naming scheme selector to run settings UI