Stage 10: admin console & dictionary ops (complaint review, hot-reload, broadcasts) (#11)
This commit was merged in pull request #11.
This commit is contained in:
+12
-2
@@ -110,5 +110,15 @@ wins, losses, draws, max points in a game, and max points for a single move (the
|
||||
best play, which already includes every word it formed plus the all-tiles bonus).
|
||||
|
||||
### Administration *(Stage 10)*
|
||||
Admin (Basic Auth at the gateway) reviews word complaints, manages dictionary
|
||||
versions, and inspects users/games.
|
||||
Operators reach a server-rendered admin console at `${DOMAIN}/_gm` — the backend
|
||||
renders it; the gateway gates it with HTTP Basic Auth on its public listener and
|
||||
proxies it verbatim. The console lists and inspects **users** (profile, statistics,
|
||||
identities, their games) and **games** (summary + seats), works the **word-complaint
|
||||
review queue** — resolving each as reject / accept-add / accept-remove — and exposes
|
||||
the **dictionary**: the resident versions per variant, a **hot-reload** of a new
|
||||
version from `BACKEND_DICT_DIR/<version>/`, and the **pending wordlist changes**
|
||||
derived from accepted complaints (which feed the offline rebuild and are marked
|
||||
applied after a reload). When a Telegram connector is configured an operator can also
|
||||
**message a user** (by their Telegram identity) or **post to the game channel**.
|
||||
State-changing actions are protected by a same-origin check; the console tracks no
|
||||
operator identity.
|
||||
|
||||
Reference in New Issue
Block a user