Operations

Battles, games, dashboard, search, menu and notifications.

📄️The active casino's audit trail, newest first

Who changed what, on which record, and what it looked like before.

The same entry the list returns, with `properties` unabridged.

Read-only, plus one write. **Opening a battle is the casino backend's act

A battle belonging to another casino is a `404`, not a `403` — the answer must

The one write on this surface. Only a battle that is still `OPEN` can be

Four cards for the active casino — battles opened, battles completed,

Answers **every** game with a boolean, not just the allowed ones — a screen

A `PUT` with a boolean rather than a `POST` and a `DELETE`: the control is a

A flat list of nodes, each naming its parent — the client assembles the tree.

The WHOLE arrangement, not a delta, applied in one transaction — a partial

Every field is optional and every one distinguishes ABSENT from CLEARED:

Only the signed-in operator's rows — there is no route that reads someone

**No permission check** — ownership is the authorization, and it is enforced

Backs the command palette, so it is bounded rather than exhaustive: it

Whether this casino's backend was told that a battle ended, and if not, why not.

The trail is newest first and bounded at ten entries — enough to see what a

Re-POSTs the stored payload to the casino's endpoint, **synchronously**, and