done-done

"No proof, no done." done-done captures proof from the real product, ties every screenshot, recording and log to the exact commit, and checks that cited proof is real, fresh and not reused. You run it for the user; they only say what should be proven.

Current guidance lives in the CLI

Do not follow command or config details from memory or from this file - installed copies go stale. Get the current source of truth from the CLI.

First run command -v done-done. If it prints a path, run done-done as shown below. If not, run npx -y done-done-axi wherever this file or done-done output says done-done - nothing to install.

• done-done (no arguments, inside the repo) for this repo's proof setup and the next step
• done-done --help for every command and flag, the journey format and the exact ## Checks block
• done-done <command> --help for one command's usage and flags
• done-done --version prints the bare version first; help headers show it too, and suffixed versions are labelled pre-release.