Counts and rollups only — what people actually wrote lives on the hall, not here. Worries mirrored from an external board carry their source; a mirror that quietly stopped looks exactly like a quiet week, so its freshness is called out.
Oldest open — longest-sitting first, the way the hall reads it
Who is carrying what
Quests
Users & roster
Retired characters
Telemetry
Client diagnostics
Bundles submitted from clients (Doctor → Submit diagnostics), scrubbed at capture. The cross-bundle view reads the newest 40 together — fleet identity posture and which errors are shared rather than local.
Portrait cache
Every miss here is a paid render, capped per day — one render is meant to serve the whole team. Worn means a guild row currently points at that combo; the rest are faces nobody is wearing any more. They are kept on purpose: deleting one costs a re-render the next time somebody builds that combo.
Logs
Problems
Endpoints — click to filter
Callers
Subsystems
Campaign banner
What everyone will see
Clients poll GET /campaign. The banner offers, the USER clicks — nothing is seeded into any session without that click.
Previous campaigns
Saving a changed campaign files the outgoing one here (one copy per id, newest first). load refills the form — bump the id before saving if people already dismissed it.
…
Feature flags
Flat JSON of gates. Since 0.1.51480 no client reads them — multi_character and server_xp were the last,
removed in PR 6371 (the XP ledger is always on; the multi-character roster UI is gone). GET /flags still answers older clients, with the boolean entries only (strings stay server-side).
{} is the expected state.
Audit trail
Native crashes
Buckets — one row per signature, newest first; click one for its dumps
Dumps
A signature is EXCEPTION · fault module · via first non-system module on the stack · process type
(process type only when it is not the main/browser process; via only when the fault is inside the OS heap / C runtime).
The stack scan is a heuristic: every pointer-sized word on the crashing thread's stack that lands inside a loaded module,
innermost first — no unwinding and no symbols, so stale return addresses can appear. Download the .dmp for WinDbg / minidump_stackwalk.
Usage history
Team — people who hit the weekly cap / ran out of a session, per week
People × week — weekly-window peak %; ×n = sessions that ran out; click a person for their accounts, an account for its detail
Peaks are the highest reading in each ISO week (UTC). Ran out = a 5-hour session window whose reading reached
the ran-out line (counted once per window). Accounts are the real account where the client reports it (October 2026 onward);
older readings are grouped by the profile label, and default is a different account for each person.
A reset is seen when an account's weekly window rolls over or expires between two readings.
Mail
Ledger — metadata only; opening one is audited
Last 14 days
Senders
Never opened, by recipient — direct mail, no read receipt
Agent reports
Who each agent mails. A change applies to the agent's next report — no deploy, no env var. People add and remove themselves in the hall (Ravens); by person sets it for anyone who doesn't. An agent's new report appears here the first time it names one, and shows in Ravens once you approve it. Retire turns a report off for everyone and takes it out of Ravens (restore brings everyone back).