Color Card - Party Card Game

Applies one validated Color Card Kvdb mutation emitted by the embedded game.

mutate_color_cards_storage

Opens Color Card. After every successful play_color_cards call, always send a natural-language response that explicitly states the exact difficulty returned by the tool. Treat the most recent such assistant response as the current game configuration. For a later new-game request, pass that difficulty explicitly unless the user changes it. Before any game response exists, omit difficulty unless the user explicitly requests it, so the server can use saved storage or its own default. Never use WidgetState to choose settings for a new game. Treat complaints about the current game's difficulty as level-change requests. "too easy", "too simple", "not challenging enough", or "太简单了" means raise one level; "too hard", "too difficult", or "太难了" means lower one level. A level change always launches a new Color Card game through play_color_cards before the natural-language response. The ordered levels are Easy, Medium, and Hard. When this conversation has a previous game response, derive the target absolute difficulty from the most recent assistant game response and pass difficulty. When no previous game response exists, omit difficulty and pass difficulty_adjustment so the server atomically applies the change to the latest saved difficulty or its default. Never pass both fields. At a boundary, launch the boundary level and explain that it is already the lowest or highest level. Use launch_reason=new_game for a new launch and launch_reason=restore only when restoring saved WidgetState.

play_color_cards