Add protected operator console prototype

docs/specs/ui-operator-console.md

@@ -76,6 +76,19 @@ The first useful prototype should implement read-heavy surfaces before mutation-
 
 Use whynot-design quiet, document-like operational language: mostly neutral surfaces, strong typography hierarchy through labels and tables, no marketing hero, no decorative imagery, no gradients, no animation beyond basic hover/focus feedback. The console should feel like a control room notebook rather than a product landing page.
 
+
+## First Prototype
+
+The first prototype is a protected server-rendered route at `/console`. It uses the existing FastAPI runtime, inline whynot-aligned tokens/classes, and the current SQLAlchemy read model to show:
+
+- readiness gates;
+- hub registry rows;
+- migration run ledger rows;
+- non-secret API consumer metadata;
+- recent interaction events.
+
+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.
+
 ## 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.