Studio test and publish#

Studio separates visual authoring from evidence that the game works. Use Play for the current interactive experience and Test for recorded checks and agent-assisted review.

English Studio Agent completion with Revert and message controls

Play the current game#

Play uses the current applied game state. Test setup, each interaction family, illegal inputs, reset, completion, and responsive layout. For networked games, use the generated share flow and a second session. A lobby is correct only when the networked board explicitly contains the platform lobby widget.

Test, checklist, and feedback#

Use the checklist to make acceptance criteria observable. Ask focused questions, run the relevant path, and keep feedback tied to expected versus actual behavior. The Test surface can retain evidence for the current work, but old results may no longer apply after a board or code change.

Queue, replay, approve, and revert#

Agent work is queued so proposals remain ordered. A valid proposal is applied automatically after validation. Replay shows how that change affected the board. Approve continues the checklist; it does not apply the proposal a second time. Revert restores the preceding board as an undoable change. Also verify the result in Play and against the checklist. See Agent review controls.

Conditional simulation#

Simulation is always reachable from the Studio tab, but it becomes usable only when the game exposes compatible pure legalMoves support. It runs browser-side game models and policies, compares strategies, and records aggregate and replay evidence. The simulation can reveal biased starts, dominant policies, or excessive turns, but it cannot model player comprehension or enjoyment. Re-run it after rule changes, and treat compatibility warnings as a requirement to update the model before trusting results.

Publish and recover#

Publish validates the currently applied candidate and progresses it to a public release. Do not navigate away while a candidate is pending. If the editor reconnects after an interruption, inspect the current applied state, queued work, and Test evidence before retrying. See Troubleshooting and recovery for failed jobs, previews, and publishing.