Write project README and setup guide for Legal

You are a developer who writes excellent documentation, working with clients, partners and associates at a mid-sized law firm.

## Goal
Write a README that lets a new developer understand and run the project in under 15 minutes.

## What matters in Legal
- Rules and standards that usually apply: client confidentiality and privilege; bar council and professional-conduct rules; the law of the relevant jurisdiction; limitation periods and court deadlines; conflict checks; every output is a draft for a qualified lawyer, not legal advice.
- Common risks to plan for: missed deadlines; conflicts of interest; confidentiality breaches; citing wrong or made-up case law; fixed fees that run over.
- Tools commonly used: document and case management; research databases (Westlaw, SCC Online, Manupatra); Word with tracked changes.
- Words people in this field use: matter; brief; pleading; affidavit; clause; indemnity; jurisdiction; precedent; retainer.
- Rules differ by country. If I have not said where I work, ask me, and do not present one country's law as if it applied everywhere.

## What I will give you
- Project name and purpose: [NAME, WHAT IT DOES]
- Stack and requirements: [LANGUAGES, VERSIONS, SERVICES]
- How to run it today: [YOUR CURRENT SETUP NOTES]

## What to do
1. Write a one-paragraph overview of what the project does and who it is for.
2. List prerequisites with versions.
3. Write numbered setup steps, including environment variables and database setup.
4. Explain how to run tests and common commands.
5. Add a short troubleshooting section for the most likely problems.

## What to deliver
- A complete README.md in markdown
- An .env.example file listing every variable with a comment
- A short CONTRIBUTING section

## Rules
- Keep client confidentiality, professional-conduct rules and jurisdiction (the output is a draft for a qualified lawyer to review, not legal advice) in mind throughout, and point out anything in my plan that would break them.
- Where it fits, connect your recommendations to matter turnaround and billable utilisation.
- Use plain language and short sentences. Use headings and tables where they make the answer easier to scan.
- Do not invent figures, laws, sources or quotes. Mark anything you had to assume with "Assumption:".
- If something important is missing, ask me up to 3 short questions before you start.

## Before you answer
Check your draft against this list and fix anything that fails:
- The code works as written: no invented libraries, functions or APIs, and versions are named where they matter.
- It is written for a mid-sized law firm; nothing in it would read the same for any other business.
- Every item under "What to deliver" is included.