Moderator operations

Role boundaries

role:moderator, role:admin, and role:dev may inspect queue members, view moderation records, pause/resume matches, and manage timeouts/bans. Admin/dev access is required for destructive or rating-sensitive actions such as aborting, declaring a winner, setting health, forcing certain decisions, editing users, or reverting results. role:pooler manages maps but does not inherit moderation powers.

Live match procedure

1. Identify the match GUID and verify its current status/version.
2. Pause if continued play could compound harm. Pause freezes every runnable durable timer at its remaining milliseconds.
3. Collect status history, timer records, rounds/scores, connection context, replay/video, and both player accounts.
4. Choose the least invasive supported action: resume, skip a timer, force a valid pick/score, forfeit, set health, declare a winner, or abort.
5. Enter a specific reason. Notify affected players and document any timeout or rating correction.

Admin match actions support force_pick, force_score, forfeit, abort, set_health, and declare_winner. Never edit database rows manually while normal routes can preserve invariants and history.