# Task NN: <short name>

## Context
Why this task exists: what real use showed, who it's for, what's wrong today. Two to five lines.

## Read first
- `PROGRESS.md` (where things stand)
- `<the files this task touches>`
- `<any reference spec>`

Check what already exists before building. Write what you find in `PROGRESS.md`, and reuse it
instead of rewriting it. Don't break anything that works.

## Behaviour
Exactly what the user sees and what the code does. Be concrete: screens, buttons, wording (in every
language the app has), formats, limits, edge cases, errors.

1. …
2. …

## Tests
- Unit/integration: …
- End to end: run one real job with <input>, and take screenshots of <screens> into `docs/screenshots/<task>/`.
- Check: `<test command>` and `<build command>` pass.

## Done when
- [ ] …
- [ ] …
- [ ] Tests and build pass; screenshots taken and looked at.
- [ ] `PROGRESS.md` updated (decisions, results, "Resume here", "Needs <you>").
- [ ] Committed in small steps (never pushed).
