The game should consist of a new state, called inScoreReview (or along the lines), where the users see a total score count. From then on, if the current team has scored all 3/3 clues, the users have the option to start the next turn, on their call. If the current team missed any clues, the UI will direct to a stealing component, then offer the screen to start the next turn.
A new state called REVIEW has been added. This state can be entered from the ACTIVE or STEALING state and leads to the IDLE state.
Important API changes:
The end_turn endpoint now has a new function. Calling it while in the REVIEW state will cause the teams to change and the state to transition to IDLE
The old end_turn functionality (which involved moving from the ACTIVE state to either the STEALING or IDLE state, switching teams if appropriate), now exists in the end_active_state endpoint. Calling this endpoint will move the game to either STEALING or REVIEW
The game should consist of a new state, called inScoreReview (or along the lines), where the users see a total score count. From then on, if the current team has scored all 3/3 clues, the users have the option to start the next turn, on their call. If the current team missed any clues, the UI will direct to a stealing component, then offer the screen to start the next turn.