功能修改
This commit is contained in:
@@ -11,7 +11,7 @@ First-party routes must be declared here before page implementation.
|
||||
- `/users`: 用户管理.
|
||||
- `/ai-providers`: AI 提供商管理.
|
||||
- `/maintenance`: 系统维护(审计事件与运行节点).
|
||||
- `/plugin-pages/:pluginId/:routeKey`: platform-hosted plugin page route.
|
||||
- `/plugin-pages/:pluginId/:routeKey?serverInstanceId=:serverId`: platform-hosted plugin page route with optional server context; IDs are URL encoded and the route is not shown in primary navigation.
|
||||
|
||||
## Role Scoping
|
||||
|
||||
@@ -23,3 +23,6 @@ Navigation entries are generated from the current user's capability set (`contra
|
||||
- Server creation opens inline from 服务器管理 (no separate `/servers/new` page).
|
||||
|
||||
Server and plugin detail flows must use routes, modals, or drawers. Do not build a fixed left-list/right-detail page.
|
||||
# Server Detail lifecycle route
|
||||
|
||||
The `serverDetail` route owns the Client Manager workspace as an overview operations surface. It is a detail workflow, not a permanent split pane: list pages remain full-width and destructive lifecycle commands use shared confirmation dialogs. Route state does not contain component secrets or Run session material.
|
||||
|
||||
Reference in New Issue
Block a user