first commit

2026-07-11 14:56:10 +08:00
commit 7e05d0a4e7
660 changed files with 78119 additions and 0 deletions
@@ -0,0 +1,71 @@
+## ADDED Requirements
+
+### Requirement: Role-based default workspace
+The platform web application SHALL route authenticated users to a default workspace based on their authorized role set.
+
+#### Scenario: Platform administrator lands on platform overview
+- **WHEN** an authenticated platform administrator opens the platform web application
+- **THEN** the application displays the platform overview as the default workspace
+
+#### Scenario: Server administrator lands on server list
+- **WHEN** an authenticated server administrator without platform administrator privileges opens the platform web application
+- **THEN** the application displays the server list as the default workspace
+
+#### Scenario: Server owner lands on server list
+- **WHEN** an authenticated server owner without platform administrator privileges opens the platform web application
+- **THEN** the application displays the server list as the default workspace
+
+### Requirement: Role-scoped navigation
+The platform web application SHALL render navigation entries only for areas the current user is authorized to use.
+
+#### Scenario: Platform administrator sees platform areas
+- **WHEN** a platform administrator views the desktop navigation
+- **THEN** the navigation includes platform overview, server management, plugin marketplace, user management, AI provider management, and system maintenance entries
+
+#### Scenario: Server administrator cannot see platform overview
+- **WHEN** a server administrator without platform administrator privileges views navigation
+- **THEN** the navigation does not include platform overview, user management, AI provider management, or system maintenance entries
+
+### Requirement: Platform overview first-screen health
+The platform overview SHALL present operational health information needed by platform administrators in the first screen without requiring navigation to secondary pages.
+
+#### Scenario: Platform overview shows required metrics
+- **WHEN** a platform administrator opens the platform overview
+- **THEN** the first screen shows server online/offline counts, game type distribution, CPU usage, memory usage, disk usage, and LLM connectivity health
+
+#### Scenario: Platform overview shows recent operational signals
+- **WHEN** recent logs, faults, or plugin update signals are available
+- **THEN** the platform overview displays a recent signal summary with entries that link to the relevant server, plugin, or AI provider context
+
+### Requirement: Server list first-screen operations
+The server list SHALL present the server status fields needed by server owners and server administrators in the first screen.
+
+#### Scenario: Server card shows required status
+- **WHEN** a server owner or server administrator views their server list
+- **THEN** each server card shows online/offline state, player count, TPS, latency, CPU usage, memory usage, and disk usage when available
+
+#### Scenario: Server list supports search and status filtering
+- **WHEN** a server owner or server administrator needs to find a server
+- **THEN** the server list provides search and status filtering controls without requiring access to platform overview
+
+### Requirement: Themeable game-style workspace
+The platform web application SHALL support a colorful anime/game visual style while preserving operational readability.
+
+#### Scenario: User-uploaded background is applied safely
+- **WHEN** a user applies an uploaded background image
+- **THEN** content panels, controls, logs, forms, and metric text remain readable through contrast surfaces or overlays
+
+#### Scenario: Status is not color-only
+- **WHEN** server, LLM, plugin, or operation status is displayed
+- **THEN** the status is represented with text or iconography in addition to color
+
+### Requirement: Responsive role workspace
+The platform web application SHALL adapt role-specific workspaces for narrow screens without removing essential first-screen information.
+
+#### Scenario: Platform overview on narrow screen
+- **WHEN** a platform administrator opens the platform overview on a narrow screen
+- **THEN** online/offline server counts, resource load, LLM health, and recent operational signals remain reachable from the initial vertical flow
+
+#### Scenario: Server list on narrow screen
+- **WHEN** a server owner or server administrator opens the server list on a narrow screen
+- **THEN** the application displays single-column server cards with search, status filtering, and server status fields available without horizontal scrolling