Evaluator README Generator

Goal

Most READMEs are written for a teammate who already has context. This one is written for someone who has never seen the project and has a few minutes to decide if it works and what it's about — an evaluator, a judge, a reviewer. Every section exists to answer a specific question that person will actually ask, in the order they'll ask it: what is this, can I run it, how is it built, why was it built this way, does it actually work.

The primary outcome is a file written to disk: README.md at the project root.

Non-negotiable rule

Every command and every claim in the README must be verified against the real project — its actual package manager scripts, its actual entry points, its actual environment variables. Never invent a command that looks plausible for the stack; check it. A quickstart that doesn't run is worse than no quickstart, because it's the first thing an evaluator tries.