Write acceptance criteria that can be tested

A story is ready to start and "it should work well" is currently the only criterion.

Write acceptance criteria for the story below.

Rules:
1. Use Given / When / Then. Every Then must be observable by someone who cannot see the code.
2. Cover the happy path first, then: empty state, maximum state, invalid input, permission denied, network or dependency failure, and concurrent use.
3. No criterion may contain "fast", "intuitive", "reliable" or "properly" without a number or a specific observable behaviour attached.
4. Separate what must be true to ship from what would be nice, and label them.
5. List the questions that must be answered before these criteria are final, rather than guessing the answer.

End with the three criteria most likely to be quietly skipped during implementation.

Story:

Specs and stories. Turning a vague request into something a team can build: specs, PRDs, stories and acceptance criteria.