# FiveM adapter

The bridge reads convars, activates against `/v1/bridge/activate`, sends heartbeat
state and batches events. Failed connections retry exponentially; up to 1,000
events remain buffered in memory. Player identifiers are used only to derive a
server-side hash and are not returned by dashboard endpoints.

Protocol mismatches produce HTTP 426 with the supported version.

## Server detail telemetry

Bridge 0.2.0 reports a five-minute metrics stream with player count, resource
uptime, API latency, Node runtime CPU use and process/host memory. It also sends
the FXServer version, enforced game build, endpoint and bridge version.

The dashboard can enqueue only two allowlisted commands:

- `REFRESH_STATUS` requests a fresh heartbeat and telemetry snapshot.
- `RECONNECT_BRIDGE` renews the signed bridge session.

Commands are delivered through the bridge's outbound heartbeat response. No
inbound FiveM port, shell access or arbitrary remote command execution is used.