wtclaude
be44839896
The org lead's rule, settled 2026-09-22: who is online is always the
narrowest audience - staff - unless an operator deliberately widens it,
and a count is fine where a list of names is not.
The public site broke that in three places since phase 4. The Online
tab named every player, the feed carried joins, respawns, deaths, chat
and tallies, and the leaderboard's lastSeen - refreshed every minute by
a gather tally - said who was on as plainly as either. All three now
sit behind one setting:
* PRESENCE_KINDS, a subset of the public allowlist, gated per request.
Below the audience the feed keeps the server's own story (wipe, start,
shutdown) and says presenceHidden rather than looking quiet.
* the Online route answers { players: [], hidden, count, audience } -
same shape, so an older client renders empty rather than breaking.
* rungs staff / signed_in / public, fleet-wide default in a new
rust_settings table with an optional per-server override on
rust_servers; an unknown stored word narrows to staff.
* the viewer's standing is RE-READ from the users row (ctx.users.getById),
not taken from the token, so a demotion or a ban applies on the next
request. Walked: a moderator demoted mid-session lost the roll call on
the same cookie.
* per-viewer answers are Cache-Control: private, no-store.
* GET/PUT /admin/rust/visibility (requireRole admin) and an admin page,
Rust visibility; every save is one activity-log row.
The browser walk also found every empty state in this module rendering
as a blank box. Core's EmptyState renders children only; this module
passed title/message (the shape the Integration Kit template teaches)
and React dropped both without a word. Fixed module-side with a small
Empty wrapper - nothing core or module-uo renders changes - and a client
test that refuses a titled EmptyState or a PageHeader subtitle.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01E14m6SuuY6i1vASFeGDBeY
47 lines
2.2 KiB
SQL
47 lines
2.2 KiB
SQL
-- ── The teardown ──────────────────────────────────────────────────────────
|
|
--
|
|
-- Destructive, and run ONLY by an explicit admin purge (MODULE_API.md §2.6).
|
|
-- Nothing on the boot path executes this file, and uninstalling the module does
|
|
-- not either: removing an operator's data is a second decision they make on
|
|
-- purpose, offered inside the uninstall flow and confirmed separately.
|
|
--
|
|
-- It exists because `schema.sql` does. A module that can create tables and
|
|
-- cannot drop them leaves an operator with orphaned data and no supported way to
|
|
-- remove it, so core refuses to load a module that declares one without the
|
|
-- other.
|
|
--
|
|
-- **Drop in the reverse of creation order**, which this file depends on:
|
|
-- `rust_server_state` carries a foreign key into `rust_servers`, so dropping the
|
|
-- parent first fails on the constraint — and a purge that fails halfway leaves
|
|
-- exactly the orphaned data it exists to remove.
|
|
--
|
|
-- What does NOT belong here: rows written into core's tables. Core prunes what
|
|
-- it knows this module registered, because it is the side that knows which
|
|
-- registrant owned what.
|
|
|
|
-- Phase 7b.
|
|
DROP TABLE IF EXISTS rust_settings;
|
|
DROP TABLE IF EXISTS rust_config_writes;
|
|
|
|
-- Phase 7. Children before parents: every one of these carries a foreign key
|
|
-- into `rust_servers`, `users` or `rust_perm_groups`.
|
|
DROP TABLE IF EXISTS rust_perm_catalogue;
|
|
DROP TABLE IF EXISTS rust_perm_sync;
|
|
DROP TABLE IF EXISTS rust_perm_revocations;
|
|
DROP TABLE IF EXISTS rust_perm_drift;
|
|
DROP TABLE IF EXISTS rust_perm_pushed;
|
|
DROP TABLE IF EXISTS rust_perm_grants;
|
|
DROP TABLE IF EXISTS rust_perm_group_members;
|
|
DROP TABLE IF EXISTS rust_perm_group_permissions;
|
|
DROP TABLE IF EXISTS rust_perm_groups;
|
|
DROP TABLE IF EXISTS rust_account_links;
|
|
DROP TABLE IF EXISTS rust_ingest_cursor;
|
|
DROP TABLE IF EXISTS rust_presence;
|
|
DROP TABLE IF EXISTS rust_events;
|
|
DROP TABLE IF EXISTS rust_gather_totals;
|
|
DROP TABLE IF EXISTS rust_player_wipe_stats;
|
|
DROP TABLE IF EXISTS rust_players;
|
|
DROP TABLE IF EXISTS rust_wipes;
|
|
DROP TABLE IF EXISTS rust_server_state;
|
|
DROP TABLE IF EXISTS rust_servers;
|