Update the README from the diff

Cursor reads what changed and proposes README edits only where the public instructions are now wrong.

A short README diff, or an explicit note that the README does not need to change.

1. 1

   Limit the diff

   Review the branch you are about to merge, not the whole history of the repo.

2. 2

   Reject new sections

   A README update for this case is a correction, not a rewrite.

3. 3

   Run the command you changed

   If a setup command moved, run the new one from a clean reading of the README.

Compare the current diff to the README. Update the README only where a public instruction is now false.

Rules:
- Do not add a marketing introduction.
- Do not document internal files.
- If a command, flag, or setup step changed, show the old line and the new line.
- If nothing user-facing changed, say so and do not edit the file.
- Keep the existing heading structure.

Agents like to add badges and feature lists. Delete them.

Sample case written by Hidden Logic Lab. Not affiliated with Cursor.