coulomb/core-hub
Archived
2
0
Fork 0
generated from coulomb/repo-seed
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Add operator UI rebuild backlog

Browse Source
This commit is contained in:
Bernd Worsch
2026-06-27 21:34:10 +02:00
parent 0401551de9
commit 9d8921603e
5 changed files with 100 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

9
docs/specs/ui-operator-console.md
View File

@@ -89,6 +89,15 @@ The first prototype is a protected server-rendered route at `/console`. It uses
The route requires the same bearer-token authentication as protected `/api/v2` resources. It intentionally renders only API key prefixes and non-secret lifecycle metadata.
## Rebuild Backlog
The broader UI rebuild is gated behind deployed API evidence and CLI parity.
`docs/specs/operator-ui-rebuild-backlog.md` is the implementation backlog
extracted from the `/console` prototype: readiness overview, registry explorer,
evidence stream, migration/cutover, action-required gates, and access metadata
only. New screens must preserve the prototype's protected-route, desktop/mobile,
no-overlap, and non-secret assertions.
## Open Implementation Choice
The preferred first implementation is a thin FastAPI-served HTML/HTMX or static custom-element shell that consumes `/api/v2` and later Core Hub-native read endpoints. A heavier SPA should wait until the API and workflows prove the extra runtime is useful.