20 lines
1.1 KiB
Markdown
20 lines
1.1 KiB
Markdown
## ADDED Requirements
|
|
|
|
### Requirement: Persisted SCUM operations datasets
|
|
The system SHALL expose persisted SCUM users, squads, activity events, gifts, and map points through Platform APIs scoped to a server instance.
|
|
|
|
#### Scenario: a completed sync is queried
|
|
- **WHEN** an operator requests a SCUM dataset for an instance with persisted records
|
|
- **THEN** Platform returns only the corresponding persisted `scum_*` rows for that instance
|
|
|
|
### Requirement: SCUM operations console views
|
|
The first-party management console SHALL provide themed views for 用户, 队伍, 活动, 礼包, and 地图 using Platform's persisted SCUM dataset APIs, with an explicit empty state when no sync has completed.
|
|
|
|
#### Scenario: data is available
|
|
- **WHEN** an operator opens a SCUM-enabled server after a data sync
|
|
- **THEN** the console displays the returned persisted dataset without browser-side SQLite or log access
|
|
|
|
#### Scenario: no data is available
|
|
- **WHEN** an operator opens a SCUM-enabled server with no completed data sync
|
|
- **THEN** each dataset view displays an empty state rather than synthetic records
|