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

chore: remove OpenSpec workflow

Browse Source
This commit is contained in:
npc0-hue
2026-08-20 17:05:13 +08:00
parent 1ada76ecc8
commit 58642ff9dc
5 changed files with 7 additions and 30 deletions
Download Patch File Download Diff File Expand all files Collapse all files
platform_web/AGENTS.md
+1 -1
View File
@@ -12,7 +12,7 @@ Do not define API clients, shared DTOs, route definitions, schemas, or bridge co
## Interaction Rules
Management list pages must keep the primary list, grid, or table as the full-width working surface. Do not add permanent right-side create/edit/detail panes or fixed left-list/right-form master-detail layouts for users, plugins, AI providers, servers, or similar management resources. Use modals, drawers, or detail routes for create, edit, and detail workflows unless a future OpenSpec change explicitly requires an inline split layout.
Management list pages must keep the primary list, grid, or table as the full-width working surface. Do not add permanent right-side create/edit/detail panes or fixed left-list/right-form master-detail layouts for users, plugins, AI providers, servers, or similar management resources. Use modals, drawers, or detail routes for create, edit, and detail workflows unless an explicit future product/design decision requires an inline split layout.
Server card and resource-row action menus must behave like real compact dropdowns/popovers, not like full-height button towers. The screenshot-failure pattern is explicitly forbidden: opening "运行操作" or any similar trigger must not inject a tall vertical stack of large command buttons inside a card, over a card, or between cards where it covers metrics, health bars, titles, status badges, or neighboring cards.
platform_web/theme/README.md
+2 -2
View File
@@ -23,7 +23,7 @@ This directory owns the platform_web visual system. Keep the console in a unifie
## Background Rules
- `defaultThemePaletteId` must remain `mecha-black` unless an OpenSpec change explicitly replaces the visual direction.
- `defaultThemePaletteId` must remain `mecha-black` unless an explicit future product/design decision replaces the visual direction.
- `defaultThemeBackgroundId` should point to a built-in mecha desktop preset that works without uploaded imagery.
- Built-in presets use CSS variables named `--workspace-background-pattern-*` and render behind the app shell.
- Uploaded backgrounds use `--workspace-background-image`, set `data-custom-background="true"`, and take visual precedence over the selected preset.
@@ -70,4 +70,4 @@ This directory owns the platform_web visual system. Keep the console in a unifie
3. If a new shared pattern is truly needed, add it in `base.css` and describe its intended use here.
4. When placing empty/loading/error states inside an existing shared panel, verify the state view does not introduce a second framed panel or accessory layer.
5. If a new palette or background preset is added, update `tokens.ts`, `tokens.test.ts`, and any CSS contract tests together.
6. Run the relevant focused checks before claiming completion. Use `npm run typecheck`, `npm test`, `npm run build`, and `scripts/check-structure.sh` when the scope warrants them; run `openspec validate <change> --strict` only when an OpenSpec change was created.
6. Run the relevant focused checks before claiming completion. Use `npm run typecheck`, `npm test`, `npm run build`, and `scripts/check-structure.sh` when the scope warrants them.