# Member Directory

## Objective

Show who is in the workspace and how to identify them.

A searchable, read-only roster of workspace members with their role, status, and the profile fields they have chosen to share.

## Before You Begin

This feature is being added to an application that already exists and already
works. Do not scaffold a new project, and do not assume a blank slate.

Inspect the codebase first and establish:

- The existing application structure and where code of this kind already lives.
- The framework and version in use.
- The existing design system — colours, spacing, typography, and component conventions.
- Existing UI components you can reuse instead of writing new ones.
- The existing database structure, if this feature needs to persist anything.
- The existing authentication and authorization system, if this feature is user-scoped.
- Dependencies already installed, so you don't add a library that duplicates one.
- The existing test setup and conventions.

Only start writing code once you understand the above. If the application
already implements part of this feature, extend it rather than replacing it.

## Implementation Instructions

1. Build this as a read view. Inviting members is owned by Team Invitations, changing roles is owned by User Roles, and seat counts are owned by Seat Management — link out to those rather than duplicating their controls here.
2. Show each member's display name, avatar, role, and status. Status is not decoration: pending, active, suspended, deactivated, and external guest must be visually distinct and filterable.
3. Respect per-field profile visibility. A field the member marked private is not rendered, not returned by the API, and not searchable — hiding it in the template while shipping it in the payload is not privacy.
4. Make search server-side and match on name and handle. Client-side filtering of a fetched list leaks every member's data to anyone who opens the page.
5. Do NOT expose raw email addresses by default. Where contact matters, prefer an in-app action over publishing the address.
6. Paginate rather than loading everyone; a workspace of five thousand people should open as fast as one of five.

## UI and UX Requirements

Match the application's existing design system exactly. Reuse its components,
spacing, and typography. This feature should look like it was always there.

## Responsive Requirements

Works on mobile, tablet, and desktop. Touch targets are large enough to hit on a
phone, and nothing overflows horizontally at 320px.

## Accessibility Requirements

- Fully keyboard navigable.
- Correct semantic elements and ARIA roles.
- Visible focus states.
- Meets WCAG AA contrast.
- Dynamic changes are announced to screen readers.
- Respects prefers-reduced-motion.

## Edge Cases

- Counts in the header must match what the current viewer is allowed to see, or the numbers look broken.
- Deactivated members must still resolve by name on old content, even when they are filtered out of the default view.
- External guests must be labelled as such and must not see the full internal roster.
- A member with no avatar, no display name, or an unaccepted invitation must still render a sensible row rather than a blank one.
- Search must match accented and non-Latin names, and must not fall over on a query of one character.
- The viewer's own row should be marked, and admin-only columns must be absent for non-admins rather than merely hidden with CSS.

## Testing

Exercise the feature end to end in the running application. Cover every edge case
above, then run the existing test suite and confirm nothing regressed.

## Acceptance Criteria

- [ ] Every member is listed with name, role, and a visually distinct status.
- [ ] Private profile fields are absent from the API response, not just from the page.
- [ ] Search and pagination happen server-side and stay fast on large workspaces.
- [ ] Guests and non-admins see a correctly reduced view, including reduced counts.
- [ ] Deactivated members remain resolvable on existing content.
- [ ] Invite, role, and seat controls link to their owning features rather than being reimplemented.
- [ ] The feature matches the existing design system.
- [ ] No existing functionality is broken.

## Adaptation Rules

- Match the existing design system. Do not introduce a new colour palette,
  spacing scale, or component library.
- Reuse existing components and utilities wherever they fit.
- Follow the naming, file layout, and code style already present.
- Do not upgrade, replace, or remove existing dependencies to make this
  feature fit. Adapt the feature to the app, not the app to the feature.
- Do not break existing functionality. If a change is genuinely required in
  existing code, make the smallest one that works and say so.
- If something in these instructions conflicts with how the application is
  built, follow the application and explain the deviation.

## Final Verification

Before you report the work as done:

1. Re-read the acceptance criteria above and check each one against what you
   actually built.
2. Run the application and exercise the feature end to end.
3. Run the existing test suite and confirm you have broken nothing.
4. Check the feature on mobile, tablet, and desktop widths.
5. Check keyboard navigation and focus handling.
6. Summarize what changed: files added, files modified, and anything you
   deliberately did differently because of how this application is built.

If any acceptance criterion is unmet, fix it before reporting completion.