Getting started — requirements, installation, and first launch.
Native hosts — enrollment, game files, capacity, agent updates, and recovery.
Users and access — roles, sessions, telemetry credentials, and password recovery.
Fleet settings — concurrency, retention, and cleanup.

Fleet operations

Provisioning — lifecycle actions, safety checks, queues, and diagnostics.
Collections — reusable map lineups and promoted launch files.
Lobby autoscaling — policies, ownership, pause controls, and the pilot procedure.
Maintenance — health recovery, drift repair, updates, and scheduled restarts.

Releases and analytics

Beta test plans — game reporters, test requirements, coverage, and outcomes.
Plugin releases — GitHub release discovery and imports.
Metrics — utilization, capacity pressure, and hosting experiments.
Leaderboard and matches — player statistics, match history, and the read API.

Development

Development guide — local setup, architecture, checks, and database diagnostics.
UI patterns — shared components, forms, navigation, and refresh behavior.

Plans

Player achievements and visual refresh proposes calendar leaderboards, personal-best highlights, shareable result cards, and consistent map and status presentation.

Lobby autoscaling records the implemented design and the production dry run, pilot measurements, and rollout still to complete. Current operating instructions live in the guides above.

Research

Reducing idle CPU use — runtime tuning and lobby availability experiments.
Leaderboard query benchmark — historical SQL measurements and methodology.

Research records its baseline and measurement limits; consult the guides for current behavior.

Keep operating instructions in guides/, contributor guidance in development/, unfinished delivery or rollout work in plans/, and investigations in research/. When a plan is complete, fold its lasting guidance into the relevant guide and remove the superseded document. Git history preserves earlier reviews and plans.