Release Docs Proof — README & API QA

Illustrative missing-evidence receipt; no repository, CLI, or examples were run.

Target revision: not supplied. Documentation set: README quickstart, flag reference, PR description, and draft release notes named by the requester but not accessible. The ledger therefore cannot mark any claim verified or contradicted. It records four pending groups: installation prerequisites, quickstart command and output, changed flag names/defaults, and release/migration statements. For each group it asks for the exact file, intended release revision, implementation or generated CLI contract, and safe execution environment.

Documentation gate: NEEDS EVIDENCE. No command was executed and no patch was applied. If the files become available, the next pass will pin the revision, trace each affected claim to code or contract evidence, classify side effects, run only safe examples, and propose exact corrections for contradictions. A command that writes to a live service or consumes credentials remains unverified unless the user supplies suitable authorization and isolation. Even a later documentation PASS would apply only to the checked claims, not to deployment or whole-product readiness.