3 Commits
Author SHA1 Message Date
poli0981andClaude Opus 5 ba6f19722e docs: an AI disclosure, and a CLI guide written by running the CLI
**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>
2026-08-14 19:03:58 +07:00
poli0981andClaude Opus 5 401c917f20 docs(readme): seven screenshots and a name without a space in it
The screenshots were captured on 2026-08-14 against the installed build and staged
without ever being committed or referenced. The README had no image beyond its five
badges — a GUI whose readme shows no GUI.

`setting (2).png` -> `settings.png`. A space and a `(2)` in an asset path has to be
percent-encoded in Markdown and is a filename nobody meant to publish.

Installed and Code Health lead, because they are the two screens that show what the
tool is for; the other five are behind a `<details>` so the README stays scannable.
Alt text says what each shot demonstrates rather than repeating the tab name.

Caveat worth knowing: these predate the About tab, so the sidebar in them has eight
entries and 1.0 has nine.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-08-14 17:32:20 +07:00
poli0981andClaude Opus 5 2f81b0c6ca fix(build): the lockfile edge that made every cargo job fail
`main` has been red since 3eeda05. `Cargo.lock` carried a dependency edge to
`thiserror 2.0.19` while its own package entry said `2.0.20` — a lockfile Cargo
wants to repair and `--locked` forbids repairing, so every cargo job in every
workflow died before compiling a crate:

    error: cannot update the lock file ... because --locked was passed to prevent this

The Dependabot bump (b4ab2d9) moved the package entry; 2abfef6 touched the file
afterwards and the stale edge survived. CI had gone green on a base predating
the bump, which is the same shape as the ruff-pin defect recorded in P4.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-08-14 17:32:20 +07:00