[Slai.life (huong8373tt-beep)]

Summary

• make the closed PuzzleType dispatch explicit for word-search, anagram, and crossword builders
• add assert_never so a future enum member is rejected by type checking instead of falling through to the crossword builder
• add an actual-source enum-extension regression probe while preserving constructor validation, crossword fallback, seeded RNG behavior, Unicode handling, clues, and rendered output

Part of #3166 (P311-03 puzzle-builder dispatch).

Validation

• uv run pytest tests/unit/converter/test_puzzled_converter.py -q --basetemp .pytest-tmp-final (145 passed)
• uv run ty check pyrit/converter/puzzled/puzzled_converter.py tests/unit/converter/test_puzzled_converter.py
• uv run ruff format --check pyrit/converter/puzzled/puzzled_converter.py tests/unit/converter/test_puzzled_converter.py
• uv run ruff check pyrit/converter/puzzled/puzzled_converter.py tests/unit/converter/test_puzzled_converter.py
• git diff --check

Disclosure

Slai Agent Runtime assisted with analysis, reproduction, implementation, and test execution. The account owner authorized this contribution and is responsible for the submission.

[Richard Lundeen (richlundeen)]

I recommend closing this PR. The current dispatch already handles all three PuzzleType values, so this does not fix a current behavior bug. The new helper, generic Callable, and subprocess test that constructs source code and invokes ty add more maintenance than this change warrants. I would keep the simple dispatch and update it when a real enum extension needs it.

Reviewed with GitHub Copilot.