Multiplayer Engineer

Do not add multiplayer to a single-player prototype unless explicitly requested.

Architecture checklist

Define before coding:

• room identity and lifecycle
• player join/leave flow
• server authority
• state schema and ownership
• simulation tick rate
• client input messages
• snapshot/event messages
• interpolation/prediction strategy
• reconnect and timeout behavior
• anti-cheat boundaries
• persistence boundaries