[TASK][Frontend] Build the branch team workspace and invitation flows

[vugarsafarzada]

Source of Truth

• PRD: https://www.notion.so/3435ef9e213280eaa56ad864787cda02
• Repo: Reziphay/nextjs-app
• Task type: execution-ready frontend task for AI/code agents
• Backend dependency: nodejs-app#8

Current Codebase Snapshot

• src/app/(protected)/brands/page.tsx already has a progress=team mode and renders BrandTeamWorkspace.
• src/app/(protected)/notification/page.tsx already enriches team invitation feed items, so invitation UX is partially expected by the current app structure.
• Existing team flows are not yet fully built out to cover owner operations, member movement, and service assignment states.

Goal

Complete the branch-team management surface so brand owners can run a branch team and invited USOs can understand/respond to their team state without ambiguity.

In Scope

• Owner-facing per-branch team workspace.
• Search/invite UX for inviting USO users into a branch team.
• UI for pending, accepted, rejected, and removed states.
• Invited-user accept/reject flows tied to notification/workspace entry points.
• Remove and move-member actions when backend exposes them.
• Service-assignment display and controls once backend assignment data is available.
• Responsive layout and clear role-based action visibility.

Suggested Implementation Order

1. Start from the existing BrandTeamWorkspace surface rather than building a parallel page.
2. Add API/client support for richer workspace payloads and invitation actions.
3. Build invitation creation + invite-state rendering first.
4. Add member management actions next.
5. Add service-assignment rendering and controls after the backend contract stabilizes.
6. Reconcile notification-entry UX with the workspace so invites feel like one coherent flow.

Important Constraints For Agents

• Do not break the current notification feed behavior for team invitations.
• Keep owner-only actions visually and behaviorally distinct from invited-user actions.
• Avoid over-fragmenting the experience into too many pages if the current page-mode approach can handle it cleanly.

Deliverables

• Completed branch team workspace UI.
• Invitation accept/reject/create flows.
• Member-management and assignment surfaces.
• Localized empty/loading/error states.

Acceptance Criteria

• Brand owner can invite a USO from the UI.
• Invited user can accept/reject from a clear UI entry point.
• Team workspace shows current members, pending invites, and status clearly.
• Move/remove actions are exposed only where allowed.
• Service assignment state is visible once backend returns it.

Out of Scope

• Team chat/messaging.
• Staff scheduling calendars beyond what is required to display assignments.