Hermes/multi-simadmin
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

feat: rebuild warm operations workbench

Browse Source
This commit is contained in:
Codex
2026-07-30 14:49:33 +08:00
parent 25c853dea8
commit 570edf6bb2
88 changed files with 13413 additions and 2250 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/superpowers/specs/2026-07-30-warm-operations-workbench-design.md
+10 -6
View File
@@ -51,7 +51,8 @@ Automation contains three views:
- Use solid warm surfaces. Translucency may be used only for a sticky overlay that visibly floats over scrolling content; it is not the default material.
- Remove oversized page headers and decorative English kickers.
- Use plain semantic headings rather than Animal Island ribbon titles on dense operational pages.
- Keep page gutters between 16px and 24px on ordinary desktop widths and lock very wide content to a practical maximum width.
- Keep top-level page gutters between 16px and 24px at every desktop width. The application shell remains fluid and must not introduce centered outer whitespace through a global `max-width`.
- Content-specific limits remain valid for forms, dialogs, drawers, message bubbles, and empty states where long line lengths would reduce usability; these limits must never constrain the top-level Nodes, Automation, or Settings workspaces.
### 4.2 Tokens
@@ -80,9 +81,10 @@ Automation contains three views:
### 5.1 Layout
- Remove the persistent left summary/sidebar.
- Combine summary counts, search, filters, sorting, refresh, add-instance, and batch-mode entry into a compact page header and toolbar.
- Render nodes in three columns on wide desktop, two columns on medium layouts, and one column on mobile.
- Preserve the persistent Fleet sidebar on desktop as the primary node directory. It contains the node summary, search, status facets, advanced filters, and active-filter state.
- Keep sorting, refresh, add-instance, batch-mode entry, and node cards in the main results pane so filtering and results remain visually distinct.
- At widths above 60rem, use a sticky two-column workspace with a 17rem sidebar that can collapse to a compact 4.5rem rail. At 60rem and below, stack the sidebar above the results and let the existing disclosure control collapse its contents.
- Render nodes in four columns at 112rem and above, three columns on wide desktop, two columns on medium layouts, and one column on mobile, measured within the available results pane.
- Keep panel dimensions stable so status changes and progress updates do not shift the grid.
### 5.2 Node panel
@@ -237,9 +239,11 @@ Requests and responses use strict contracts, bounded arrays/strings, exact-key v
- Real-browser flow for creating, editing, pausing, running, and deleting schedules.
- Keyboard-only completion of Fleet selection and schedule creation.
- Screenshots at 390px, 768px, 1024px, and 1440px.
- Screenshots at 390px, 768px, 1024px, 1440px, and 1920px.
- No horizontal overflow or overlapping text.
- Fleet renders one, two, or three columns at the intended widths.
- Fleet renders one, two, three, or four columns at the intended widths.
- At 1024px and 1440px, the Fleet summary and search remain in a left-hand sidebar beside the results pane. At 390px and 768px, the sidebar becomes a top disclosure without losing its heading or controls.
- At 1920px, the Nodes, Automation, and Settings top-level workspaces keep 16px to 24px outer gutters rather than a centered fixed-width shell.
- Selection controls appear only in batch mode.
- Reduced-motion and increased-contrast states remain usable.
- Existing instance actions and deep links remain functional.