**AI disclosure.** PipDock was written with substantial help from Claude Opus 5 (Anthropic, via Claude Code), and the fact was only visible as a commit trailer. `docs/AI-DISCLOSURE.md` is the full statement — model, vendor, period, what it wrote (source, tests, debugging, the VI catalogue), what review actually meant, what was not delegated, and how to verify any of it from `git log`. 172 commits, 163 with the trailer. It also says the thing worth saying: a green suite was never sufficient. Thirty-four defects reached or nearly reached `main` and not one was caught by the suite that was green at the time. Three surfaces, because three different people look in three different places: the README for someone browsing the repo, `docs/` for someone reading the code, and the **About tab** for someone who installed the app and will never open GitHub. The last one needed keys in both catalogues. **`docs/CLI-GUIDE.md`.** CLI-SPEC is the contract; this is what you type. Written against `pipdock 1.0.0` by running every command rather than by reading the spec — which is how the exit codes in it were confirmed (`PD-ENV-001` really is 3, `schema` on an unknown type really is 1) rather than copied. That also turned up a defect: `self report-bug` printed **fourteen stray spaces** in the middle of a sentence, because a multi-line string literal keeps its source indentation. Nobody had read the output. Also: `About.png` -> `about.png` so the seven screenshots share one convention, and the About shot joins the README. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
121 KiB
1182x792px
121 KiB
1182x792px