[UI] Team Management and Pending Invites (Phase 10)

[CRamsan]

Phase 10 — Team Management and Pending Invites

Implement the Team Management screen with role-based tabs and pending invitations management. This is split from #409 which covered all of Settings & Profile.

Screens & Composables

SettingsTeamScreen.kt (SET-04) — tabbed screen with three tabs:

1. Admins — members with Owner or Admin role
2. Staff — members with Staff role
3. Pending Invites — (SET-05, see below)

Each member card shows: avatar, full name, email, role badge, "..." overflow menu with Change Role and Remove actions.

Invite Member button (FAB or top-bar): opens invite form with email field + role picker, submitting calls POST /orgs/{orgId}/invites.

Pending Invites tab (SET-05)

• Lists invitations where accepted_at IS NULL AND cancelled_at IS NULL
• Each InviteCard: email, role, sent date, expiry date
• Resend button: re-sends email + extends expiry
• Cancel button: confirmation dialog then cancels invite
• Empty state: "No pending invitations."

Navigation

• Route.TeamManagement registered in NavGraph
• Accessible from Settings (via SET-06 in [UI] Resident Maintenance Requests screens — Submit and Track (Phase 9) #431)

Dependencies

• [BE] Organization Membership API Contracts and Backend Services (Phase 0) #426 — Org Membership API (for invite, list members, remove member, resend/cancel invite endpoints)
• [ORG] My Organizations screen + Org Detail + Leave/Transfer ownership (Phase 1) #392 — Org Membership frontend (for member data)

What type of task is this?

Development