JGengine multiplayer

Ownership

This skill owns network topology, authority, transports, sessions/presence, replication/projection, reconnect, hosted runners, and persistence adapters. Serializable game state and save semantics stay in jgengine-gameplay.

Use capabilities.md for intent-to-import discovery, api.md for signatures, and reference.md for transport, host, projection, persistence, and deployment recipes.

Canonical workflow

1. Choose authority and trust boundaries before transport.
2. Keep commands/intents separate from authoritative state transitions.
3. Define serializable snapshots/deltas and viewer-specific projection.
4. Select a transport pipe and host adapter without changing game protocol.
5. Add reconnect, idempotency, persistence cadence, and failure behavior.
6. Test multiple clients, visibility boundaries, and restore/rejoin behavior.

Design rules