48 lines
2.9 KiB
Markdown
48 lines
2.9 KiB
Markdown
## ADDED Requirements
|
|
|
|
### Requirement: Server cards use compact runtime action overlays
|
|
|
|
The platform_web server management page SHALL expose server-card runtime actions through a compact anchored overlay that does not resize, stretch, or reflow the server card.
|
|
|
|
#### Scenario: Operator opens runtime actions from a server card
|
|
|
|
- **WHEN** an operator selects the 运行操作 trigger on a server card
|
|
- **THEN** runtime actions MUST appear in a compact overlay anchored near the trigger instead of as a tall in-card vertical command stack
|
|
- **AND** the server card layout, neighboring cards, metrics, progress bars, title, and status badge MUST remain structurally stable
|
|
|
|
#### Scenario: Operator dismisses runtime actions
|
|
|
|
- **WHEN** the runtime action overlay is open
|
|
- **THEN** outside click, Escape, and selecting an action MUST dismiss the overlay
|
|
- **AND** the action dispatch MUST continue to use the existing platform-mediated runtime APIs
|
|
|
|
### Requirement: Runtime actions show task progress dialogs
|
|
|
|
The platform_web server management and server detail runtime action surfaces SHALL show a modal task flow after an operator selects a runtime action so the operator can see meaningful progress instead of a silent click-and-finish interaction.
|
|
|
|
#### Scenario: Operator generates a run package
|
|
|
|
- **WHEN** an operator selects 生成 run for a server
|
|
- **THEN** platform_web MUST open a modal task dialog that shows stage progress for code pull, environment install/check, dependency download, compile/build, package finalization, and terminal success or failure
|
|
- **AND** the dialog MUST include a readable progress meter, current stage, recent task log lines, and final artifact/job summary when the platform API returns
|
|
|
|
#### Scenario: Operator starts a queued runtime maintenance action
|
|
|
|
- **WHEN** an operator selects dependency check, dependency install, push update, live logs, or historical logs from the runtime action surfaces
|
|
- **THEN** platform_web MUST show a modal task dialog with action-specific staged progress and final queued job or navigation status
|
|
- **AND** the dialog MUST keep sensitive runtime credentials, raw host paths, direct sockets, and secret material hidden
|
|
|
|
### Requirement: Server card metrics remain readable over themed backgrounds
|
|
|
|
Server card metric tiles SHALL keep labels and values readable across black mecha, magical-girl, and uploaded-background states.
|
|
|
|
#### Scenario: Metrics are unavailable or pending
|
|
|
|
- **WHEN** 玩家, TPS, 延迟, or 任务 values render as pending or unavailable placeholders such as `…` or `--`
|
|
- **THEN** both the label and value text MUST remain legible over the card background and selected workspace background
|
|
|
|
#### Scenario: Custom background is active
|
|
|
|
- **WHEN** an uploaded background is active behind server cards
|
|
- **THEN** metric tiles MUST use stronger surface material, borders, and text contrast so operational data is not visually swallowed by the background image
|