Structure a README that gets someone running

A project with working code and a README that says only its name.

Write a README for the project below, aimed at someone who found it five minutes ago and is deciding whether to use it.

Order, and keep it in this order:
1. **One sentence** saying what it is and who it is for. No taglines.
2. **What problem it solves**, and one sentence on what it deliberately does not do.
3. **Install**, exact commands, with prerequisites and versions stated.
4. **Smallest working example**, copy-pasteable, with the real output shown underneath.
5. **Common tasks**, the three or four things most users will actually do.
6. **Configuration**, or a link to it if long.
7. **Limitations and known issues**, honestly.
8. **Contributing and licence**, last and brief.

No badges beyond build and version. No architecture diagram. If you need information I have not supplied, list the questions at the end rather than inventing details.

Project:

Getting someone started. READMEs, setup guides, onboarding and glossaries for the person meeting this for the first time.