[Story]: Dedicated role-management view (PM/Admin) reachable from settings

[adoLime]

User Story

As a PM/Admin, I want a dedicated role-management view (list, create, retire, assign functional project roles) reachable from the settings hub, so that I can manage roles in a proper full-screen view instead of only through a modal in the team-management page.

Context & Motivation

• Type: Functional (Project administration / UX)
• Parent epic: 02 EPIC - Security, Privacy & Local AI Governance #51 (02 EPIC – Security, Privacy & Local AI Governance)
• Teams: team:frontend
• Source: User request — "neue Projekt rollen anlegen (für PM/admin) etc." as part of a settings hub.
• Already implemented (reused, not rebuilt):
  • Project role CRUD — ProjectRoleController (backend: create / list / retrieve / delete + assign/unassign to user).
  • ProjectRolesModal (frontend: modal entry inside TeamManagementPage).
  • Story [Story]: PM-managed functional project roles + connector/source gating #175 (open, Sprint 4) — PM-managed functional project roles + connector/source gating. [Story]: PM-managed functional project roles + connector/source gating #175 is NOT modified by this story — it stays as planned for Sprint 4. This story only adds a dedicated full-screen view that makes the existing role CRUD better reachable.
• New in this story:
  • A dedicated role-management view (full page, not a modal): list roles, create, retire, assign/unassign to users.
  • Reachable from the settings hub (sister story "Settings hub + chat generation loading state", Epic 12 EPIC - UX, Documentation & Pilot Release #63) for users with PM/Admin role.
  • Non-PM/Admin users see a hidden / 403-equivalent section (RBAC [Story]: RBAC with Admin / User separation #93).

Acceptance Criteria

• A dedicated role-management view exists (full page, not a modal): lists all functional project roles with name, description, and assigned-member count.
• PM/Admin can create a new role (name + description) from the view.
• PM/Admin can retire (delete) a role from the view, with a confirm step.
• PM/Admin can assign / unassign a role to/from a user from the view.
• The view is reachable from the settings hub for users with PM/Admin role; non-PM/Admin see a hidden / 403-equivalent section (RBAC [Story]: RBAC with Admin / User separation #93).
• Reuses the existing role CRUD service / ProjectRoleController — no new backend endpoint.
• All actions use icon + text labels (not colour alone — per AGENTS.md §7); responsive (desktop primary, mobile stacks — §8); works in light/dark themes.
• Empty / loading / error states; i18n (en/de).

Sub-Tasks (by team)

• Frontend — dedicated role-management view (list / create / retire / assign-unassign); wire to existing role CRUD service; RBAC-gated entry from the settings hub.
• QA — tests for role CRUD in the view, PM/Admin access vs. non-PM/Admin 403, responsive + light/dark.

Dependencies

• Reuses (no rebuild, no new backend): ProjectRoleController (role CRUD), existing role CRUD service in the frontend.
• Depends on: sister story "Settings hub + chat generation loading state" (Epic 12 EPIC - UX, Documentation & Pilot Release #63) for the settings-hub entry point — can start with a fallback nav entry if the hub is not ready yet.
• Does NOT modify [Story]: PM-managed functional project roles + connector/source gating #175 — [Story]: PM-managed functional project roles + connector/source gating #175 (PM-managed functional roles + connector gating, Sprint 4) stays as planned; this story only adds a dedicated view on top of the existing CRUD.