Make Workplace routing and shell tenant-rooted

[gbaudrit]

Area

Workplace

Feature type

User-facing capability

Problem or need

Workplace currently opens without making the Tenant root explicit. As Workspaces become user-facing spaces, routing and shell state need to distinguish Tenant-level navigation from one selected Workspace space.

Expected outcome

Workplace has an explicit Tenant root route and navigation shell, with optional navigation into one accessible Workspace space without treating that Workspace as globally implicit.

Proposed solution

Introduce Tenant-rooted Workplace routes and shell state. Preserve selected Workspace only when the user intentionally enters a space or follows a deep link owned by that Workspace.

Scope

• Tenant root route and shell initialization.
• Space selection/navigation state.
• Tenant/Workspace breadcrumbs and deep-link semantics.
• Compatibility redirects from current routes where needed.
• Authentication/tenant resolution and authorization errors.
• Localization, responsive UX, tests.

Out of scope

• Space content UX.
• Tenant dashboard aggregation.
• Entry exposure semantics.

Dependencies

Parent: #338.

Deployment impact

None

Acceptance criteria

• Workplace opens at an explicit Tenant-level route/state.
• No Workspace is silently treated as the global Workplace context.
• Entering a Workspace space is explicit and reversible.
• Deep links retain the owning Workspace where required.
• Existing routes have deterministic compatibility behavior.
• Unauthorized Tenant/Workspace access fails safely.
• Browser tests cover root, navigation, refresh, and deep-link cases.

Preliminary checks

• I searched for an existing issue covering this request.