Test a game with MCP

1. Validate and start

Call validate_code, then start_game with a supported player count. Keep the returned stateRef. Read Playing a session for session behavior.

Done when the build succeeds and the session returns the expected initial offers.

2. Drive legal actions

Choose an action from an active player's offers and call apply_action. Inspect the resulting state and next offers. Test refusals and the ending too.

Done when the tested sequence produces the expected decisions and scores.

3. Prepare focused positions

Use set_state for a targeted scenario, following its current tool schema. Use inspect_state to verify the result. Named TypeScript checkpoints are unavailable for this framework.

Done when the prepared position is accepted and exposes the intended test case.

4. Inspect each viewer

Call render_game for the affected players and spectator. Check private information, controls, and localized text. Restart the session after changing source.

Done when the current source renders and plays correctly for every affected viewer.