6 Commits
Author SHA1 Message Date
poli0981andClaude Opus 5.5 957343c07b fix(core): a free-threaded python3.14t.exe is a Python too
Found by running env list against this machine: the python.org
installer puts python3.14t.exe (PEP 703) beside python.exe, the registry
lists it, and the new name rule refused it — so Add interpreter… could
not add an interpreter discovery itself reports. A version may now end
in t; pythonw3.14t, pythont and python3.14tt are still refused.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-21 23:22:12 +07:00
poli0981andClaude Opus 5.5 cfa5b4e1be docs: Add interpreter… in the specs, ACCESSIBILITY.md and the privacy policy
PRD P0-1, UI-SPEC §4, CLI-SPEC (env add/remove, their JSON, --env's new
refusal), CLI-GUIDE, ERROR-CATALOG (PD-ENV-001's new cases, and the
first button its advice ever had) and TESTING's golden count. SECURITY
§2 claimed for two milestones that interpreter paths were canonicalized
before use while the only check was existence; it now describes the
validator that makes it true. PRD also records P0-9's first-run uv
detection, P1-7 and P2 as not planned in maintenance mode.

legal/PRIVACY-POLICY.md 1.3 names the interpreter paths a person adds,
kept until removed, in both languages. With the repository URL it
already changed, the first-run gate shows once in 1.6.0.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-21 23:22:12 +07:00
poli0981andClaude Opus 5.5 ccae96dbeb chore: move to poli0981org — self-contained CI, Qodana, an npm licence gate, this week's dependencies (#119)
The repository now lives in the poli0981org organization, and this makes it at home there.

- main was red since 2026-11-18: RUSTSEC-2026-0543 (chrono), in Cargo.lock only through serde_with's weak features and compiled into nothing; ignored with its reason and exit condition.
- Supersedes #113–#118 (Rust 1.100.0, rusqlite 0.42.0, Tauri 2.12.6, code-health pins, actions, npm) plus jsdom 31.0.1; minimatch 11 closes GHSA-g3hv-75wg-m249. rfd 0.18 (#112) is held again until tauri-plugin-dialog moves.
- Dependabot's tauri groups never worked (it picks the most specific group); exclude-patterns on the catch-alls fix it.
- CI is self-contained: no workflow calls poli0981/.github; every action is pinned by commit; notify.yml vendors the Discord notifier.
- npm licences: scripts/check-licenses.mjs, deny.toml's allowlist for the npm half. Required, with cargo deny and tauri lockstep — eight required checks.
- Qodana in two parts (Rust, TS/JS), full scans, a triaged Rust baseline, fail on anything new. The Rust container needed its toolchain and CARGO_HOME pointed somewhere writable before it analysed anything.
- SonarQube Cloud analyses into poli0981org_pipdock; every npm ci runs with --ignore-scripts (S6505).
- Every repository URL points at the organization. README's attestation command for 1.4.0/1.5.0 had stopped working; it now says --owner poli0981 --signer-repo poli0981/pipdock.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-21 21:50:41 +07:00
poli0981andClaude Opus 5.5 7124227262 docs: the specs say what the code does; 1.4.0 recorded, with its audit backlog
Every spec checked against the code rather than against itself, in four passes that each read the
branch's commits and then the source:
- CLI-SPEC/CLI-GUIDE: one JSON document per command (with the per-command table and the paths
  that print nothing), environment selection, logging, Ctrl-C and exit 130, the prompts as they
  are rather than the [A]bort and countdown that never existed, `.heldBack`, a `pipdock audit`
  section, and the rules every mutating command now follows.
- ARCHITECTURE/DATA-FLOW/ERROR-CATALOG: the Engine trait's real signatures, Requires-Python's
  three checkpoints, store v4 and the log folder, §7's return types and events, the state machine
  with re-probing and Force latest, where each §9 invariant is enforced, and 35 codes in 32 rows.
- SECURITY/TESTING/RELEASE-CI/CODE-HEALTH-SPEC: the PEP 668 override as built, four browser hosts
  and the exact capability set, attested releases, the new CI, the tools constraints, and test
  tiers that describe what runs rather than what was planned.
- UI-SPEC/PRD/README/I18N: the screens as they render, the keyboard, tokens and their contrast
  sweep, the feature matrix's status, attestation instructions, and I18N's one stated exception.

ROADMAP gets the 1.4.0 record — what was wrong, what running found that reading did not, what was
deliberately not done — and the **Audit backlog**: every finding not fixed, with where it is and
why it waited. CLAUDE.md's counts and contradictions are corrected, with the rules this release
left behind. changelog/1.x.md has the 1.4.0 entry, including "Changed for scripts" and "You will
see this once". AI-DISCLOSURE, README and About say which model and who released what. The legal
documents' effective date moves to the release date.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-17 00:55:27 +07:00
poli0981andClaude Opus 5 6e22c7d502 docs: 1.1.0 in the CLI guide and the README's feature table
The guide said it was run against 1.0.0, which would leave a reader wondering whether
`pin suggest` exists. It does not: all four of 1.1.0's features are GUI-only, and the
guide now says so in a table with the nearest CLI equivalent for each, plus the note
that `pins::suggest`, `requirements::parse` and `cache::usage` are in core so a
subcommand is small when someone asks for one.

The README's feature table still described pin auto-suggest as a promise and did not
mention requirements files, disk usage or the palette at all. Also dropped "(v1)"
from its heading, which stopped being true at the tag.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-08-14 21:37:07 +07:00
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