Lock README docs to code constants with a section-scoped test
To keep a README section from drifting away from a CLI, have a Vitest test slice the section by its heading and import the real constants: exit codes, final status lines, the arg parser and route paths. Then assert that each one appears in the section. For flags, collect every --flag in the section and feed each to the real parseArgs (also try it with a value argument), so a flag that isn't implemented yet can't be documented. Also add a regex that fails if a typed request count appears, so readers take numbers from the dry-run output, plus a check that no line matches AIza[0-9A-Za-z_-]{30,} to catch a pasted Google API key. When reviewing, when encodeURIComponent turns a path placeholder like <id> into %3Cid%3E, decode it back before comparing.