b140d4d82a
- 313 new markdown files created - 30 relationships embedded - 313 entries indexed - State initialized with usage data
745 B
745 B
| id | type | title | tags | importance | confidence | created | updated | |||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| cfc0687c-a071-42ea-a906-1dd8b1c7484a | decision | Store DeckConfig with Decks |
|
0.7 | 0.8 | 2026-01-31T17:32:48.578182+00:00 | 2026-01-31T17:32:48.578182+00:00 |
When a deck is created, the DeckConfig used for validation should be persisted with the deck in the database. This ensures: 1) The deck can be re-validated later with the same rules it was created under, 2) Different game modes can have different rules, 3) Historical decks remain valid even if default rules change. Implementation: Add deck_config JSONB column to decks table, update DeckResponse to include it, update deck service to persist on create/update.