Project accessible Workspaces as Workplace spaces

[gbaudrit]

Area

Workplace

Feature type

User-facing capability

Problem or need

Tenant-rooted Workplace needs a user-facing organization model for agentic work without duplicating Workspace as another persisted concept. Users should discover the Workspaces they can actually use and understand them as distinct spaces with their own capabilities and activity.

Expected outcome

Every accessible Workspace can be projected as a Workplace space with stable identity, presentation metadata, authorization-aware discoverability, and navigation into its own Entry/activity experience.

Proposed solution

Reuse Workspace as the canonical domain identity and add only the presentation/query capabilities required by Workplace. A Workplace space is a projection, not a new persisted aggregate.

Scope

• Query accessible Workspaces for current Tenant/principal.
• Workplace-safe projection with name, display metadata, summary, icon/presentation where available.
• Stable space URL/deep-link identity based on Workspace identity.
• Empty/unavailable/disabled Workspace behavior.
• Ordering/search/filter hooks suitable for Tenant home.
• Authorization and pagination.
• API/client, localization, tests.

Out of scope

• New persisted Space entity.
• Cross-Workspace resource visibility.
• Space home content beyond the projection contract.

Dependencies

Parent: #338.
Depends on #339 for tenant-rooted navigation semantics.

Deployment impact

None

Acceptance criteria

• Workplace can list Workspaces accessible to the current principal in the current Tenant.
• Each accessible Workspace has a stable Workplace space projection and route.
• No duplicate persisted Space lifecycle is introduced.
• Workspace authorization remains authoritative for discovery.
• Inaccessible sibling Workspaces never leak through summaries, counts, or deep links.
• APIs paginate and browser tests cover zero/one/many accessible spaces.

Preliminary checks

• I searched for an existing issue covering this request.