# Avatar Group

## Objective

Show who is involved in a compact space without a pile of broken images.

A stacked set of member avatars with deterministic ordering, an overflow count, and access to the full list.

## 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. Find the places that show several people at once — assignees, collaborators, workspace members, comment participants — and render them through one grouped component.
2. Order the stack deterministically by a stable rule such as role then name, so the same group renders in the same order on every load and every device.
3. Cap the number shown and collapse the remainder into a single count that is announced meaningfully, not as a bare number sitting after a row of pictures.
4. Make the group activatable to reveal the full list of people with their full names, since the stack itself can only ever be a summary.
5. Do not rely on a photograph being present. Every member needs a fallback built from their name, and every fallback needs to survive a missing name, a single-character name, and a name in a non-Latin script.

## 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

- Unstable ordering makes the same group look like different groups across two pages. Sort by a stable field rather than by whatever order the API returned.
- The overflow indicator must be a real count with an accessible name explaining what it counts, and activating it must reach the same full list as the group itself.
- Two members with the same initials produce two identical circles. Vary the fallback deterministically per person and make sure hovering or activating still resolves who is who.
- The full membership must be reachable without hovering, since hover is unavailable on touch and unreliable with a keyboard.
- Avatar images fail to load often enough that the failure is the normal case. The fallback must render immediately and must not leave a broken image icon or an empty hole in the stack.
- A group with one member should not render as a stack, and a group with none needs a defined empty treatment rather than a lone overflow bubble.
- Overlapping avatars must not overlap their hit areas if each is individually interactive; either give each a clear target or make only the group activatable.

## 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

- [ ] The same set of people renders in the same order on every load.
- [ ] Overflow collapses into a count with an accessible description.
- [ ] The full member list is reachable by keyboard and on touch.
- [ ] Missing images fall back to a generated placeholder with no broken image state.
- [ ] Members with identical initials are visually and textually distinguishable.
- [ ] Groups of zero and of one have defined treatments distinct from the stacked case.
- [ ] 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.