admin343/browser
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Complete platform management workflows

Browse Source
This commit is contained in:
npc0-hue
2026-07-14 16:39:37 +08:00
parent 7e05d0a4e7
commit 4f33f761a3
106 changed files with 11313 additions and 460 deletions
Download Patch File Download Diff File Expand all files Collapse all files
openspec/changes/polish-platform-interaction-design/specs/platform-interaction-design-polish/spec.md
+4
View File
@@ -23,6 +23,10 @@ The platform_web console SHALL provide polished, scannable, API-backed interacti
- **WHEN** an operator opens AI 提供商管理
- **THEN** the route MUST present provider identity, connection status, relay mode, model/default-model information, and redacted key references without exposing raw keys or making status dependent on color alone
#### Scenario: Management page counters stay secondary
- **WHEN** an operator opens 插件市场、用户管理, or AI 提供商管理
- **THEN** small summary counts such as installed plugins, bridge actions, validation failures, users, roles, pending reviews, providers, enabled providers, and models MUST render as compact contextual status instead of large framed KPI cards that displace the primary list, grid, table, search, or filter work surface
### Requirement: Server detail workflows are polished without direct run access
The platform_web server detail route SHALL provide polished workflow surfaces for lifecycle, logs, config, plugin controls, AI assistant, and operation history while preserving platform-mediated boundaries.