Ship the console under console/ with minimal coupling to lifecycle server internals; prefer a BFF over browser-held API keys.
Tenant developers use a tenant API key → see sandboxes in their namespace only.
Platform admins use a separate BFF admin token; the BFF aggregates Lifecycle calls server-side with per-tenant keys (optional read-only Kubernetes RBAC for platform pages).
Avoid (large cross-cutting PRs)
Avoid
Why
Full server auth overhaul in the same PR as the UI
High review cost and conflict with main
Browser storage of OPEN-SANDBOX-API-KEY
Use httpOnly BFF session instead
Runtime-specific diagnostics in core UI
Stay on Diagnostics API
Everything in one merge (history DB, Grafana, image catalog, K8s ops)