Control plane first
The next UI phase prioritizes spaces, members, invites, and the product shell that future modules depend on.
Control plane foundation
This app now separates public entry from the authenticated workspace so the control plane can grow around real tenant-aware product flows.
This phase now uses real login for shell access while keeping temporary UI-layer tenant data for spaces, members, and invites until those module reads are API-connected.
The next UI phase prioritizes spaces, members, invites, and the product shell that future modules depend on.
The backend already supports collaboration primitives. The UI now gets a structure that can expose them coherently.
The route model stays locale-aware so future product flows can localize without reworking navigation.