Story: Account avatars are too dark to see
Table of Contents
This page documents a story in Sprint 27. It captures the goal, current status, acceptance criteria, and the tasks that compose it.
1. Goal
An account's avatar reads as an identity on the dark theme, whether the account is a person, a service, or an administrator.
2. Status
| Field | Value |
|---|---|
| State | DONE |
| Parent sprint | Sprint 27 |
| Now | Nothing. |
| Waiting on | Nothing. |
| Next | Nothing. |
| Last touched | 2026-10-06 |
3. Acceptance
- Every seeded account avatar is drawn in the theme's ink and no longer reads as disabled.
- The seed regenerates from external/avatars with images_generate_sql.py –config system_avatars.
4. Tasks
| Task | State | Start | End | Description |
|---|---|---|---|---|
| Scaffold story: Account avatars are too dark to see | DONE | 2026-10-06 | 2026-10-06 | Story scaffolding rides this task: documents, sprint wiring, and the scaffold PR. Close it before merging that PR. |
| Draw the account avatars in the theme's ink | DONE | 2026-10-06 | Initial task for: Account avatars are too dark to see |
5. Decisions
6. Out of scope
7. Result
The 27 avatars in external/avatars are recoloured from #212121 to
#e3e3e6, the theme's ink, and the seed regenerates from them. The running
environment's images were updated in place and the BFF image cache cleared, so
the Accounts list and the Root Tenant People tab draw legible avatars. One
environment quirk worth recording: /api/images/:id is served immutable
for a year, so a browser that fetched an avatar before the in-place update
keeps it until its site data is cleared. A provision creates fresh image ids,
so the durable fix does not meet that cache.