AI Implementation feature(913): Admin Area Players Management 1.00 (#57)
This commit was merged in pull request #57.
This commit is contained in:
+4
-1
@@ -11,7 +11,7 @@ scoreboard, an event window with a public countdown, theming, and admin
|
||||
controls.
|
||||
|
||||
The docs below are organized by purpose so agents can pull just the slice
|
||||
they need. Last regenerated 2026-07-23T06:39:17Z.
|
||||
they need. Last regenerated 2026-07-23T08:42:24Z.
|
||||
|
||||
# Architecture
|
||||
|
||||
@@ -100,6 +100,9 @@ they need. Last regenerated 2026-07-23T06:39:17Z.
|
||||
* [Cross-Tab Authenticated Shell Invalidation](/guides/cross-tab-invalidation.md) -
|
||||
How a logout in one tab, or an unauthorized SSE response, instantly clears
|
||||
and redirects every other open tab of the SPA.
|
||||
* [Cross-Tab Role Change Sync](/guides/cross-tab-role-change.md) -
|
||||
How a role change at `/admin/players` propagates to every other open tab,
|
||||
plus the LAST_ADMIN invariant under concurrent admin demotions.
|
||||
* [Local Development Workflow](/guides/dev-workflow.md) - How to run the
|
||||
backend and frontend together (`npm run dev`), the Angular dev-server
|
||||
proxy, and the project-local `./data/` directory.
|
||||
|
||||
Reference in New Issue
Block a user