Module telemetry 

How fast an engine answered, for one finished game.

The hosted node publishes its own decision timings to Prometheus. Nothing measured the engines that run on a player’s machine, and the browser Forge build made that gap matter: the whole point of it is latency, and the only numbers we had came from a laptop under a test harness.

EnginePlayStats is one report per game, aggregates only: no deck, no cards, no opponent, nothing that identifies a player. It travels two ways — over the relay for a game the relay already knows about, and to the hub for offline play, where no server is in the loop at all.

OfflinePlayGame is the other half, and it is not anonymous: it names players, because the hosted node recorded exactly these fields for exactly these games until Play vs AI moved into the browser. Account erasure has to reach it, which Storage::delete_account does by handle.

Structs

EnginePlayStats

EngineTurnaround

EngineTypeTurnaround

OfflinePlayCard

OfflinePlayGame

The relay’s game_started + game_ended + deck_selected collapsed into one record: offline play has no connection to stream them over.

OfflinePlaySeat