From 7e18cdb9a00e110f74520b70fa040e48ca0227e1 Mon Sep 17 00:00:00 2001 From: demassimo <87481244+demassimo@users.noreply.github.com> Date: Thu, 16 Oct 2025 20:40:00 +0200 Subject: [PATCH] Document dashboard placement of status and Discord tools --- AGENTS.md | 5 ++++- docs/module-usage-report.md | 5 ++++- 2 files changed, 8 insertions(+), 2 deletions(-) diff --git a/AGENTS.md b/AGENTS.md index ce84b62..642997f 100644 --- a/AGENTS.md +++ b/AGENTS.md @@ -14,7 +14,10 @@ that together provide a management dashboard for Rust game servers. ## Documentation expectations When you add or modify modules, consult `docs/module-architecture-guide.md` for placement rules and update it if you introduce a -new pattern. Keep `docs/module-usage-report.md` aligned with the current code so that unused files are easy to spot. +new pattern. Keep `docs/module-usage-report.md` aligned with the current code so that unused files are easy to spot. Note that the +Rust server status surface lives exclusively under the **Server workspace → Settings** view, while the Discord ticketing and +authentication tools remain anchored to the main dashboard's **Discord** tab—documentation should reflect those established UI +locations. ## Coding conventions diff --git a/docs/module-usage-report.md b/docs/module-usage-report.md index a24f9f3..12750d7 100644 --- a/docs/module-usage-report.md +++ b/docs/module-usage-report.md @@ -1,6 +1,9 @@ # Module usage report -This document summarises how the major backend and frontend modules are referenced so we can spot redundant code paths. +This document summarises how the major backend and frontend modules are referenced so we can spot redundant code paths. Remember +that the Rust server status interface is intentionally scoped to the **Server workspace → Settings** view, and the Discord ticket +queue plus linked-account authentication tools are concentrated in the main dashboard's **Discord** tab; keep those placements in +mind when reviewing module wiring. ## Backend modules