main
27
Commits
| Author | SHA1 | Message | Date | |
|---|---|---|---|---|
|
|
38e0226878 |
chore(release): 1.6.0
The five places the version lives, moved together: Cargo.toml, Cargo.lock, package.json, package-lock.json and tauri.conf.json. `cargo metadata --locked` agrees. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> |
||
|
|
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> |
||
|
|
95e45d7acc |
chore(release): 1.5.0
The five places the version lives, moved together: Cargo.toml, Cargo.lock, package.json, package-lock.json and tauri.conf.json. `cargo metadata --locked` agrees. Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com> |
||
|
|
9754b95e66 |
test(a11y): run axe-core over every screen, and fix the grid it failed
No accessibility tooling stood behind any of this: roles were asserted one at a time, wherever a test happened to reach for getByRole. axe-core now runs over every screen inside the shell and over the components with structure of their own. It is called directly: eslint-plugin-jsx-a11y peers ESLint 9 at most and this repository is on 10, and the matcher packages are wrappers pinned to a runner's major. color-contrast stays off under jsdom and stays tokens.test.ts's job. Its first run failed on the package grid, which is fixed here: - the row checkbox was a direct child of role="row"; it is in a gridcell - the header had five column headers over six cells; the checkbox and action columns are named, visually hidden - the grid says rows are multi-selectable, which aria-selected needs And one axe cannot see: a pin chip's meaning lived in a title attribute on a span that cannot take focus. It is text now, visually hidden. Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com> |
||
|
|
2329d55298 |
build(deps): cooled-down npm, actions and tools bumps (supersedes #103, #104, #105) (#106)
* build(deps): Bump taiki-e/install-action Bumps the actions group with 1 update: [taiki-e/install-action](https://github.com/taiki-e/install-action). Updates `taiki-e/install-action` from 2.88.0 to 2.89.1 - [Release notes](https://github.com/taiki-e/install-action/releases) - [Changelog](https://github.com/taiki-e/install-action/blob/main/CHANGELOG.md) - [Commits](https://github.com/taiki-e/install-action/compare/86f7a0ffb25f40114606501a311ebcfaf882ea32...682ce6c3c696a4cd5168a05f98e51aa02b877941) --- updated-dependencies: - dependency-name: taiki-e/install-action dependency-version: 2.89.1 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: actions ... Signed-off-by: dependabot[bot] <support@github.com> * build(deps): Bump the npm-minor-patch group with 6 updates Bumps the npm-minor-patch group with 6 updates: | Package | From | To | | --- | --- | --- | | [i18next](https://github.com/i18next/i18next) | `26.7.1` | `26.7.2` | | [react-i18next](https://github.com/i18next/react-i18next) | `17.1.12` | `17.1.13` | | [zustand](https://github.com/pmndrs/zustand) | `5.0.16` | `5.1.0` | | [@tailwindcss/vite](https://github.com/tailwindlabs/tailwindcss/tree/HEAD/packages/@tailwindcss-vite) | `4.3.4` | `4.3.5` | | [tailwindcss](https://github.com/tailwindlabs/tailwindcss/tree/HEAD/packages/tailwindcss) | `4.3.4` | `4.3.5` | | [vite](https://github.com/vitejs/vite/tree/HEAD/packages/vite) | `8.3.5` | `8.3.6` | Updates `i18next` from 26.7.1 to 26.7.2 - [Release notes](https://github.com/i18next/i18next/releases) - [Changelog](https://github.com/i18next/i18next/blob/master/CHANGELOG.md) - [Commits](https://github.com/i18next/i18next/compare/v26.7.1...v26.7.2) Updates `react-i18next` from 17.1.12 to 17.1.13 - [Changelog](https://github.com/i18next/react-i18next/blob/master/CHANGELOG.md) - [Commits](https://github.com/i18next/react-i18next/compare/v17.1.12...v17.1.13) Updates `zustand` from 5.0.16 to 5.1.0 - [Release notes](https://github.com/pmndrs/zustand/releases) - [Commits](https://github.com/pmndrs/zustand/compare/v5.0.16...v5.1.0) Updates `@tailwindcss/vite` from 4.3.4 to 4.3.5 - [Release notes](https://github.com/tailwindlabs/tailwindcss/releases) - [Changelog](https://github.com/tailwindlabs/tailwindcss/blob/main/CHANGELOG.md) - [Commits](https://github.com/tailwindlabs/tailwindcss/commits/v4.3.5/packages/@tailwindcss-vite) Updates `tailwindcss` from 4.3.4 to 4.3.5 - [Release notes](https://github.com/tailwindlabs/tailwindcss/releases) - [Changelog](https://github.com/tailwindlabs/tailwindcss/blob/main/CHANGELOG.md) - [Commits](https://github.com/tailwindlabs/tailwindcss/commits/v4.3.5/packages/tailwindcss) Updates `vite` from 8.3.5 to 8.3.6 - [Release notes](https://github.com/vitejs/vite/releases) - [Changelog](https://github.com/vitejs/vite/blob/main/packages/vite/CHANGELOG.md) - [Commits](https://github.com/vitejs/vite/commits/v8.3.6/packages/vite) --- updated-dependencies: - dependency-name: i18next dependency-version: 26.7.2 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: npm-minor-patch - dependency-name: react-i18next dependency-version: 17.1.13 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: npm-minor-patch - dependency-name: zustand dependency-version: 5.1.0 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: npm-minor-patch - dependency-name: "@tailwindcss/vite" dependency-version: 4.3.5 dependency-type: direct:development update-type: version-update:semver-patch dependency-group: npm-minor-patch - dependency-name: tailwindcss dependency-version: 4.3.5 dependency-type: direct:development update-type: version-update:semver-patch dependency-group: npm-minor-patch - dependency-name: vite dependency-version: 8.3.6 dependency-type: direct:development update-type: version-update:semver-patch dependency-group: npm-minor-patch ... Signed-off-by: dependabot[bot] <support@github.com> * build(deps): sonarqube-scan-action 8.4.1; regenerate tools constraints sonarqube-scan-action 8.4.1 was six days old at Monday's Dependabot run and is past the seven-day cooldown today. tools-constraints.txt is regenerated with the command in its header, bounded to the releases that are past the cooldown (filelock 4.2.7, platformdirs 4.14.3). The result is byte-identical to the hand edit in #104, which is the check that edit was missing. Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com> --------- Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> Co-authored-by: Claude Fable 5.2 <noreply@anthropic.com> |
||
|
|
093ea4fce4 |
build(deps): dependencies to latest; classify pip 26.3's backend-unavailable (#102)
- cargo update (~60 bumps, 627 -> 616 crates) clears the yanked async-executor 1.14.0 that had turned cargo audit red on main and on every Dependabot PR since 2026-11-03 (Linux-only, never in the shipped binary). rusqlite 0.41.1 (SQLite 3.54.1), no code change. rfd 0.17 with tauri-plugin-dialog 2.8.4, which met the rfd ignore's own condition, so the ignore goes. - npm: thirteen packages to latest; TypeScript still held at 6.0.3 (typescript-eslint peers <6.1). - Tools: ruff 0.17.3, certifi, msgpack, platformdirs; constraints regenerated. - Actions: taiki-e/install-action v2.87.32, sonarqube-scan-action v8.4.0; Node 24 -> 26 LTS. "Latest" means the newest release past each ecosystem's Dependabot cooldown. - pip 26.3 renders an unloadable build backend as `error: backend-unavailable`, which fell through to PD-BLD-003; a classifier rule restores PD-BLD-002. Found by the drift job; live corpus re-captured with pip 26.3 / uv 0.13.7, the 26.2.1 capture frozen as pip-26.2/, and a test holds both renderings to one code. - Docs: ARCHITECTURE §10 re-verified, ERROR-CATALOG, TESTING, ROADMAP, CLAUDE.md. Supersedes #97, #98, #99, #100, #101. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> |
||
|
|
d8ef9c4e99 |
build(deps): Bump the npm-minor-patch group with 4 updates (#95)
Bumps the npm-minor-patch group with 4 updates: [@tanstack/react-virtual](https://github.com/TanStack/virtual/tree/HEAD/packages/react-virtual), [i18next](https://github.com/i18next/i18next), [react-i18next](https://github.com/i18next/react-i18next) and [zustand](https://github.com/pmndrs/zustand). Updates `@tanstack/react-virtual` from 3.14.21 to 3.14.22 - [Release notes](https://github.com/TanStack/virtual/releases) - [Changelog](https://github.com/TanStack/virtual/blob/main/packages/react-virtual/CHANGELOG.md) - [Commits](https://github.com/TanStack/virtual/commits/@tanstack/react-virtual@3.14.22/packages/react-virtual) Updates `i18next` from 26.5.4 to 26.5.7 - [Release notes](https://github.com/i18next/i18next/releases) - [Changelog](https://github.com/i18next/i18next/blob/master/CHANGELOG.md) - [Commits](https://github.com/i18next/i18next/compare/v26.5.4...v26.5.7) Updates `react-i18next` from 17.1.0 to 17.1.5 - [Changelog](https://github.com/i18next/react-i18next/blob/master/CHANGELOG.md) - [Commits](https://github.com/i18next/react-i18next/compare/v17.1.0...v17.1.5) Updates `zustand` from 5.0.15 to 5.0.16 - [Release notes](https://github.com/pmndrs/zustand/releases) - [Commits](https://github.com/pmndrs/zustand/compare/v5.0.15...v5.0.16) --- updated-dependencies: - dependency-name: "@tanstack/react-virtual" dependency-version: 3.14.22 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: npm-minor-patch - dependency-name: i18next dependency-version: 26.5.7 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: npm-minor-patch - dependency-name: react-i18next dependency-version: 17.1.5 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: npm-minor-patch - dependency-name: zustand dependency-version: 5.0.16 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: npm-minor-patch ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> |
||
|
|
aaa97f1b02 |
build(deps): Bump the npm-minor-patch group with 5 updates (#89)
Bumps the npm-minor-patch group with 5 updates: | Package | From | To | | --- | --- | --- | | [i18next](https://github.com/i18next/i18next) | `26.4.7` | `26.5.4` | | [react-i18next](https://github.com/i18next/react-i18next) | `17.0.20` | `17.1.0` | | [@tauri-apps/cli](https://github.com/tauri-apps/tauri) | `2.12.3` | `2.12.4` | | [typescript-eslint](https://github.com/typescript-eslint/typescript-eslint/tree/HEAD/packages/typescript-eslint) | `8.71.2` | `8.72.0` | | [vite](https://github.com/vitejs/vite/tree/HEAD/packages/vite) | `8.3.4` | `8.3.5` | Updates `i18next` from 26.4.7 to 26.5.4 - [Release notes](https://github.com/i18next/i18next/releases) - [Changelog](https://github.com/i18next/i18next/blob/master/CHANGELOG.md) - [Commits](https://github.com/i18next/i18next/compare/v26.4.7...v26.5.4) Updates `react-i18next` from 17.0.20 to 17.1.0 - [Changelog](https://github.com/i18next/react-i18next/blob/master/CHANGELOG.md) - [Commits](https://github.com/i18next/react-i18next/compare/v17.0.20...v17.1.0) Updates `@tauri-apps/cli` from 2.12.3 to 2.12.4 - [Release notes](https://github.com/tauri-apps/tauri/releases) - [Commits](https://github.com/tauri-apps/tauri/compare/@tauri-apps/cli-v2.12.3...@tauri-apps/cli-v2.12.4) Updates `typescript-eslint` from 8.71.2 to 8.72.0 - [Release notes](https://github.com/typescript-eslint/typescript-eslint/releases) - [Changelog](https://github.com/typescript-eslint/typescript-eslint/blob/main/packages/typescript-eslint/CHANGELOG.md) - [Commits](https://github.com/typescript-eslint/typescript-eslint/commits/v8.72.0/packages/typescript-eslint) Updates `vite` from 8.3.4 to 8.3.5 - [Release notes](https://github.com/vitejs/vite/releases) - [Changelog](https://github.com/vitejs/vite/blob/main/packages/vite/CHANGELOG.md) - [Commits](https://github.com/vitejs/vite/commits/v8.3.5/packages/vite) --- updated-dependencies: - dependency-name: i18next dependency-version: 26.5.4 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: npm-minor-patch - dependency-name: react-i18next dependency-version: 17.1.0 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: npm-minor-patch - dependency-name: "@tauri-apps/cli" dependency-version: 2.12.4 dependency-type: direct:development update-type: version-update:semver-patch dependency-group: npm-minor-patch - dependency-name: typescript-eslint dependency-version: 8.72.0 dependency-type: direct:development update-type: version-update:semver-minor dependency-group: npm-minor-patch - dependency-name: vite dependency-version: 8.3.5 dependency-type: direct:development update-type: version-update:semver-patch dependency-group: npm-minor-patch ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> |
||
|
|
4a617722d6 |
ci(sonar): CI-based SonarQube Cloud analysis, with Rust and TypeScript coverage (#85)
Automatic analysis could not build, so it never analysed the Rust two thirds of the code and imported no coverage; it also sent no project version, leaving the previous-version new-code period anchored to the first analysis. sonar.yml runs on Windows, produces cargo-llvm-cov and vitest LCOV plus clippy's JSON, and scans with sonarqube-scan-action v8.3.0 (pinned), passing the version from package.json. The token reaches the scan step alone; the job is skipped without one (Dependabot, forks) and refuses a dispatch off main, which this plan cannot analyse. Unblocks the required audits, red on main since 2026-10-21: rustls-webpki 0.103.16, webpki-root-certs 1.0.11, clipboard-win 5.4.3, zod 4.6.7. Dependabot groups vitest with @vitest/*. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> |
||
|
|
3d45f2e936 |
build(deps): Bump the npm-minor-patch group across 1 directory with 2 updates (#82)
Bumps the npm-minor-patch group with 2 updates in the / directory: [react-i18next](https://github.com/i18next/react-i18next) and [eslint](https://github.com/eslint/eslint). Updates `react-i18next` from 17.0.19 to 17.0.20 - [Changelog](https://github.com/i18next/react-i18next/blob/master/CHANGELOG.md) - [Commits](https://github.com/i18next/react-i18next/compare/v17.0.19...v17.0.20) Updates `eslint` from 10.12.0 to 10.13.0 - [Release notes](https://github.com/eslint/eslint/releases) - [Commits](https://github.com/eslint/eslint/compare/v10.12.0...v10.13.0) --- updated-dependencies: - dependency-name: eslint dependency-version: 10.13.0 dependency-type: direct:development update-type: version-update:semver-minor dependency-group: npm-minor-patch - dependency-name: react-i18next dependency-version: 17.0.20 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: npm-minor-patch ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> |
||
|
|
6cd7e99385 |
chore(release): 1.4.0
The version in all five places it lives — Cargo.toml, Cargo.lock, package.json, package-lock.json and tauri.conf.json — checked with `cargo metadata --locked` and with the release workflow's own tag check run locally against v1.4.0. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> |
||
|
|
91a846c0fd |
build(deps): every dependency to its latest release
Supersedes Dependabot #75, #76 and #77, which could not merge while `main`'s audits were red. Rust (floors raised to what is locked, so the manifests say what is built): - tauri 2.11.5 → 2.12.4 and tauri-build 2.7.3, with the plugins dialog 2.8.3, opener 2.7.2, clipboard-manager 2.5.0 and single-instance 2.5.4 — in lockstep with `@tauri-apps/*` 2.12, which Tauri's own version check requires. - **rusqlite 0.37 → 0.40.2** (libsqlite3-sys 0.38.2, SQLite 3.53.2). ARCHITECTURE §10 held it because libsqlite3-sys used the then-unstable `cfg_select!`; that is stable since 1.95 and the toolchain is now 1.99.1. Nothing here used `u64`/`usize` `ToSql` (disabled by default since 0.38) or `prepare_cached` (optional since 0.38), and 0.40.1 fixes a SAVEPOINT-name injection. - reqwest 0.13.5, tokio 1.53.3, tokio-util 0.7.20, jiff 0.2.38, clap 4.6.7, schemars 1.2.3, sha2 0.11.1, thiserror 2.0.21, serde_json 1.0.154, async-trait 0.1.92, insta 1.49.0, and 211 transitive updates (h2 0.4.20 among them). npm: React 19.3.1, Vite 8.3.4, @vitejs/plugin-react 6.1.2, **Vitest 5.0.5** (all 18 `vi.mock` calls were already top-level), ESLint 10.12.0, typescript-eslint 8.71.2, jsdom 30.1.3, @tanstack/react-virtual 3.14.21, i18next 26.4.7, react-i18next 17.0.19, @types/* current. **TypeScript stays 6.0.3**: typescript-eslint 8.71.2 still peers `>=4.8.4 <6.1.0`. Code Health pin: ruff 0.16.3 → 0.17.1. Verified by running it, not by reading its changelog: `health/sample/capture.py` reproduces all four committed `ruff/*.json` byte for byte, and exit codes 0/1/2 still mean clean/findings/error. Two things the upgrade surfaced in the frontend, both real: - virtual-core 3.19 measures the scroll element with `clientWidth`/`clientHeight` (it used `getBoundingClientRect()`), and that first reading replaces `initialRect`. jsdom reports 0, so 13 table tests and 5 App-level ones went back to rendering an empty grid; the setup now stubs the two properties beside the `offset*` ones. - jsdom 30.1 implements "a closed `<dialog>`'s contents cannot take focus", which is the spec. React applies `autoFocus` by calling `focus()` during commit — *before* PdDialog's effect calls `showModal()` — and never writes the `autofocus` attribute, so neither path focused Cancel. It worked in WebView2 only because Cancel is the first focusable element. PdDialog and the palette now focus explicitly after `showModal()`, and return focus to whatever opened them on close (it fell to `<body>` before). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> |
||
|
|
2300b637a9 |
build(deps): Bump @vitest/mocker and vitest
Bumps [@vitest/mocker](https://github.com/vitest-dev/vitest/tree/HEAD/packages/mocker) to 4.1.11 and updates ancestor dependency [vitest](https://github.com/vitest-dev/vitest/tree/HEAD/packages/vitest). These dependencies need to be updated together. Updates `@vitest/mocker` from 4.1.10 to 4.1.11 - [Release notes](https://github.com/vitest-dev/vitest/releases) - [Changelog](https://github.com/vitest-dev/vitest/blob/main/docs/releases.md) - [Commits](https://github.com/vitest-dev/vitest/commits/v4.1.11/packages/mocker) Updates `vitest` from 4.1.10 to 4.1.11 - [Release notes](https://github.com/vitest-dev/vitest/releases) - [Changelog](https://github.com/vitest-dev/vitest/blob/main/docs/releases.md) - [Commits](https://github.com/vitest-dev/vitest/commits/v4.1.11/packages/vitest) --- updated-dependencies: - dependency-name: "@vitest/mocker" dependency-version: 4.1.11 dependency-type: indirect - dependency-name: vitest dependency-version: 4.1.11 dependency-type: direct:development ... Signed-off-by: dependabot[bot] <support@github.com> |
||
|
|
02cc17d95d |
docs: the dependency view recorded, and 1.3.0
UI-SPEC §4 gains the screen and **loses the sentence it contradicted**. It said the third row action folds all three into a `⋮` menu "with the budget intact"; that makes uninstall four clicks where §5's table records three, hand-counted. The correction is written as a correction rather than an overwrite, because the reason it slipped through is the useful part: four is under the ceiling of five, and a ceiling is not a ratchet — a table of measured counts is. §5 gains the row, §6 the component, ARCHITECTURE §4 the forward direction and the whole-graph value. **The dangling cross-reference is repaired by writing what it promised.** `ROADMAP.md` has pointed at "the analysis above" for what blocks P1-6 and P1-7 since 1.2.0, and no such analysis was anywhere in the document — the survey lived only outside the repository, and the sentence had been copied into CLAUDE.md as well. P1-6's half is its slice record. P1-7's is now written too, and counted against the tree rather than recalled: no toast component, no notification/autostart/tray dependency, one plan-scoped `tokio::spawn` and zero intervals in either head, and no surface that can report a failure at 03:00 while `logs_tail` is still `NOT_YET`. Drafting this commit I nearly shipped a CLAUDE.md line claiming that survey existed before I had written it, which is the same defect one layer up. Version in five places, moved together: the workspace inherits it, so `Cargo.toml`, `package.json` and `tauri.conf.json` are the only hand edits and the two lockfiles are regenerated. Hand-editing `Cargo.lock` would have been wrong twice over — `scopeguard` and `simd_cesu8` are also at 1.2.0 and `fs_extra` was already at 1.3.0. `cargo metadata --locked` passes, which is the one-command check. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> |
||
|
|
99a25f3fa4 |
build(deps): ruff 0.16.3, zustand 5.0.15, typescript-eslint 8.67.0
Landed here rather than by merging #48 and #49, for two reasons that are the same reason: both branches were cut before Slice 0 and P1-1, so each was ~3,400 lines behind `main` and both touched `package.json`, which the 1.2.0 bump had since moved. A green check on a stale base is the thing that broke `main` twice already. **The ruff bump does not stand alone**, which is the P4 defect in full: `health/mod.rs` asserts the rendered requirements body against a literal carrying `ruff==0.16.2`, and `fixtures.rs` hardcodes the same string into `HealthReport.toolVersions`. Bumping the ledger alone turns both red. Ledger, test literal and fixture move together, with `ui/src/test/fixtures/health_*.json` regenerated. rusqlite 0.40 (#50) is closed rather than deferred: ARCHITECTURE §10 holds it at 0.37 because `libsqlite3-sys` 0.38.1's build script needs the unstable `cfg_select!`, and `rust-toolchain.toml` still pins 1.94.1. That is a compile failure, not a preference. 386 Rust tests, 204 UI tests, fmt/clippy/typecheck/lint clean, `npm audit` finds nothing. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> |
||
|
|
bee85dcdc2 |
chore(release): 1.2.0, and the Security tab recorded
Version in all five places — `Cargo.toml`, `Cargo.lock`, `package.json`, `package-lock.json`, `tauri.conf.json` — and `cargo metadata --locked` verified after, which is the one-command check that would have caught the `thiserror` lockfile breakage that had `main` red for a day in Phase 4. The ROADMAP stage record, and three rules in CLAUDE.md that the diff does not show: - **A spec can promise a field that has never existed.** SECURITY §6 and PRD P1-1 both asked for a severity pip-audit publishes under neither vulnerability service, and §6 named a venv the code had refused since P2. Found by running the tool and reading its JSON, not by reading the specs against each other. When a spec describes an external tool, the tool is the authority. - **A watchdog is a unit, not a number.** Borrowing Code Health's 120 s gave an audit a linter's budget for a network fetch, and it fired on the first real run. A borrowed constant carries its original units with it. - **Adding a field to a struct that is summed is a bug the suite will not see.** `total_bytes` kept adding three entries after a fourth arrived, with every cache test green. Post-1.0 is down to two items: the dependency-graph view and the scheduled check. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> |
||
|
|
edb7544b93 |
chore(release): 1.1.0, and the P1 wave closed
Five places again — Cargo.toml, Cargo.lock, package.json, package-lock.json, tauri.conf.json — and `cargo metadata --locked` earned its place in the checklist by failing on the first attempt, exactly the way `main` was broken this morning. The shipped CLI reports `pipdock 1.1.0`. The stage record covers all four slices and the four things running them said that reading could not: 94 suggestions on a real environment, a parser that turns prose into a package name, a cache manager for a logs directory that does not exist, and a palette that ranked an action above the screen it belongs to. **One PRD row corrected rather than ticked.** P1-4 asked for the engine caches (`pip cache`, `uv cache`) as well as PipDock's own. Those belong to the engine, live outside `%LOCALAPPDATA%\PipDock\`, and purging them is a subprocess rather than a file delete — a different feature wearing the same word. The row says "partly shipped" and names what is missing, and the roadmap's open list carries it. UI-SPEC §1's "signature moves" sentence stops saying the palette is P1; §8 gains Ctrl+K; §4 gains the Disk usage section and why it lists three artefacts. Two rules into CLAUDE.md, both paid for this afternoon: a parser correct for trusted input is a hole for untrusted input, and check a thing exists before shipping a size and a Clear button for it. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> |
||
|
|
196f0408e4 |
chore(release): 1.0.0
Five places, and they have to move together — a stale lockfile is exactly how `main`
has been red since
|
||
|
|
f3ac703382 |
build(deps-dev): Bump the npm-minor-patch group across 1 directory with 6 updates
Bumps the npm-minor-patch group with 6 updates in the / directory: | Package | From | To | | --- | --- | --- | | [@testing-library/jest-dom](https://github.com/testing-library/jest-dom) | `7.0.0` | `7.0.1` | | [@types/node](https://github.com/DefinitelyTyped/DefinitelyTyped/tree/HEAD/types/node) | `26.1.2` | `26.2.0` | | [eslint](https://github.com/eslint/eslint) | `10.8.0` | `10.8.1` | | [eslint-plugin-react-refresh](https://github.com/ArnaudBarre/eslint-plugin-react-refresh) | `0.5.3` | `0.5.4` | | [typescript-eslint](https://github.com/typescript-eslint/typescript-eslint/tree/HEAD/packages/typescript-eslint) | `8.65.0` | `8.66.0` | | [vite](https://github.com/vitejs/vite/tree/HEAD/packages/vite) | `8.2.0` | `8.2.1` | Updates `@testing-library/jest-dom` from 7.0.0 to 7.0.1 - [Release notes](https://github.com/testing-library/jest-dom/releases) - [Changelog](https://github.com/testing-library/jest-dom/blob/main/CHANGELOG.md) - [Commits](https://github.com/testing-library/jest-dom/compare/v7.0.0...v7.0.1) Updates `@types/node` from 26.1.2 to 26.2.0 - [Release notes](https://github.com/DefinitelyTyped/DefinitelyTyped/releases) - [Commits](https://github.com/DefinitelyTyped/DefinitelyTyped/commits/HEAD/types/node) Updates `eslint` from 10.8.0 to 10.8.1 - [Release notes](https://github.com/eslint/eslint/releases) - [Commits](https://github.com/eslint/eslint/compare/v10.8.0...v10.8.1) Updates `eslint-plugin-react-refresh` from 0.5.3 to 0.5.4 - [Release notes](https://github.com/ArnaudBarre/eslint-plugin-react-refresh/releases) - [Changelog](https://github.com/ArnaudBarre/eslint-plugin-react-refresh/blob/main/CHANGELOG.md) - [Commits](https://github.com/ArnaudBarre/eslint-plugin-react-refresh/compare/v0.5.3...v0.5.4) Updates `typescript-eslint` from 8.65.0 to 8.66.0 - [Release notes](https://github.com/typescript-eslint/typescript-eslint/releases) - [Changelog](https://github.com/typescript-eslint/typescript-eslint/blob/main/packages/typescript-eslint/CHANGELOG.md) - [Commits](https://github.com/typescript-eslint/typescript-eslint/commits/v8.66.0/packages/typescript-eslint) Updates `vite` from 8.2.0 to 8.2.1 - [Release notes](https://github.com/vitejs/vite/releases) - [Changelog](https://github.com/vitejs/vite/blob/main/packages/vite/CHANGELOG.md) - [Commits](https://github.com/vitejs/vite/commits/v8.2.1/packages/vite) --- updated-dependencies: - dependency-name: "@testing-library/jest-dom" dependency-version: 7.0.1 dependency-type: direct:development update-type: version-update:semver-patch dependency-group: npm-minor-patch - dependency-name: "@types/node" dependency-version: 26.2.0 dependency-type: direct:development update-type: version-update:semver-minor dependency-group: npm-minor-patch - dependency-name: eslint dependency-version: 10.8.1 dependency-type: direct:development update-type: version-update:semver-patch dependency-group: npm-minor-patch - dependency-name: eslint-plugin-react-refresh dependency-version: 0.5.4 dependency-type: direct:development update-type: version-update:semver-patch dependency-group: npm-minor-patch - dependency-name: typescript-eslint dependency-version: 8.66.0 dependency-type: direct:development update-type: version-update:semver-minor dependency-group: npm-minor-patch - dependency-name: vite dependency-version: 8.2.1 dependency-type: direct:development update-type: version-update:semver-patch dependency-group: npm-minor-patch ... Signed-off-by: dependabot[bot] <support@github.com> |
||
|
|
9fee1cd077 |
fix(ci): a bundling concern had leaked into every compile
CI caught two things the previous commits broke, and the first is pointed: I declared the CLI sidecar in `tauri.conf.json`, and **`tauri-build` validates `externalBin` at build-script time** — so plain `cargo clippy` and `cargo test` on `pipdock-app` began failing in a fresh clone with *"resource path `binaries\pipdock-x86_64-pc-windows-msvc.exe` doesn't exist"*. It passed locally only because I had already staged the file. That is exactly the "works on my machine" failure the commit that introduced it claimed to be preventing. `externalBin` moves to `src-tauri/tauri.bundle.conf.json`, merged with `--config` only when bundling. Compiling the app does not need the sidecar; bundling it does, and the config now says so. Verified the way it should have been the first time: **`src-tauri/binaries/` deleted**, then `cargo clippy -p pipdock-app --all-targets` and `cargo test --workspace` both clean — and `npm run bundle` from that same state stages the sidecar and produces two installers, the NSIS payload still carrying `pipdock-app.exe` and `pipdock.exe`. The whole recipe now lives in one `npm run bundle` script the workflow calls, so nobody has to remember that `--locked` goes after `--` or that the overlay exists. RELEASE-CI §3.1 records both traps rather than just the command. Second breakage: `ci-integration.yml` hardcoded `%LOCALAPPDATA%\PipDock\tools` in three places — it quarantines `ruff.exe` there to prove `PD-HLT-001` — and the data root had moved under `data\`. A test that reaches into a path by hand is a test that has to be told when the path moves. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> |
||
|
|
debc05edee |
fix(bundle): ship the CLI, which the installer had been leaving behind
The first bundle ever built for this project contained exactly one binary. NSIS payload: `pipdock-app.exe`. MSI `app.cab`: one file. **`pipdock.exe` was not installed at all** — while PRD P0-12 is "CLI core parity", CLI-SPEC documents the entire surface, `golden.rs` pins 58 snapshots of its output, and the README's own Quick start opens with `pipdock env list`. A user who installed PipDock had none of it. Found by listing the installer. `tauri.conf.json` declared no `externalBin` and no `resources`, so there was nothing to notice in a diff — the config was correct for a GUI-only app, and nobody had built one to see what came out. `scripts/bundle-cli.mjs` builds the CLI and stages it as a sidecar under the host triple, which Tauri strips at bundle time, so it installs as plain `pipdock.exe` beside the GUI. The triple is asked of `rustc -vV` rather than assumed, since a guess breaks the moment anyone cross-compiles. It runs from `beforeBuildCommand`, not only from the release workflow. A locally built installer and a released one have to be the same artifact; a bundle that differs by who built it is how "works on my machine" reaches a release. This build proves the clean-checkout case too — `src-tauri/binaries/` is gitignored and did not exist when the build started. **`PATH` is deliberately left alone** (owner decision, 2026-08-13). PipDock does not modify the user's environment, which is the restraint SECURITY §5 already applies to not shipping a self-updater; the README says where the binary lands and gives the one-liner to add it if that is what you want. Verified by rebuilding and listing both installers: NSIS 5.7 → 8.8 MB carrying `pipdock-app.exe` and `pipdock.exe`; MSI 7.6 → 11.6 MB carrying `Path` and `Bin_pipdock.exe`. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> |
||
|
|
e4f1596d95 |
chore(ui): the folder picker Tauri already had permission for
`tauri-plugin-dialog` has been registered in Rust since the shell was scaffolded and `dialog:allow-open` has been granted in `default.json` since then too — but `@tauri-apps/plugin-dialog` was never in `package.json`, so there was no JS binding to call. A permission with no way to exercise it, which is invisible until something tries. `pickProjectFolder` lives in `@/ipc` rather than in the component that calls it. `PdErrorRow` imports `plugin-opener` directly and that is fine, because `openUrl` is fire-and-forget and a test has nothing to assert about it. Here the return value *is* the interaction — which folder the user chose is what every screen test has to script — and TESTING §2 requires mocking at the typed wrapper layer. A component-level import would lint clean and be unmockable, which is the worst combination. `ipcMock` gains it, resolving to `null`: cancelled is the honest default, and a picker that silently produced a folder would let a test assert a run it never asked for. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> |
||
|
|
4710841caa |
build(deps-dev): Bump the npm-minor-patch group across 1 directory with 5 updates
Bumps the npm-minor-patch group with 5 updates in the / directory: | Package | From | To | | --- | --- | --- | | [@types/react](https://github.com/DefinitelyTyped/DefinitelyTyped/tree/HEAD/types/react) | `19.2.17` | `19.2.18` | | [@types/react-dom](https://github.com/DefinitelyTyped/DefinitelyTyped/tree/HEAD/types/react-dom) | `19.2.3` | `19.2.4` | | [@vitejs/plugin-react](https://github.com/vitejs/vite-plugin-react/tree/HEAD/packages/plugin-react) | `6.0.4` | `6.0.5` | | [jsdom](https://github.com/jsdom/jsdom) | `30.0.0` | `30.0.1` | | [vite](https://github.com/vitejs/vite/tree/HEAD/packages/vite) | `8.1.5` | `8.2.0` | Updates `@types/react` from 19.2.17 to 19.2.18 - [Release notes](https://github.com/DefinitelyTyped/DefinitelyTyped/releases) - [Commits](https://github.com/DefinitelyTyped/DefinitelyTyped/commits/HEAD/types/react) Updates `@types/react-dom` from 19.2.3 to 19.2.4 - [Release notes](https://github.com/DefinitelyTyped/DefinitelyTyped/releases) - [Commits](https://github.com/DefinitelyTyped/DefinitelyTyped/commits/HEAD/types/react-dom) Updates `@vitejs/plugin-react` from 6.0.4 to 6.0.5 - [Release notes](https://github.com/vitejs/vite-plugin-react/releases) - [Changelog](https://github.com/vitejs/vite-plugin-react/blob/main/packages/plugin-react/CHANGELOG.md) - [Commits](https://github.com/vitejs/vite-plugin-react/commits/plugin-react@6.0.5/packages/plugin-react) Updates `jsdom` from 30.0.0 to 30.0.1 - [Release notes](https://github.com/jsdom/jsdom/releases) - [Commits](https://github.com/jsdom/jsdom/compare/v30.0.0...v30.0.1) Updates `vite` from 8.1.5 to 8.2.0 - [Release notes](https://github.com/vitejs/vite/releases) - [Changelog](https://github.com/vitejs/vite/blob/main/packages/vite/CHANGELOG.md) - [Commits](https://github.com/vitejs/vite/commits/create-vite@8.2.0/packages/vite) --- updated-dependencies: - dependency-name: "@types/react" dependency-version: 19.2.18 dependency-type: direct:development update-type: version-update:semver-patch dependency-group: npm-minor-patch - dependency-name: "@types/react-dom" dependency-version: 19.2.4 dependency-type: direct:development update-type: version-update:semver-patch dependency-group: npm-minor-patch - dependency-name: "@vitejs/plugin-react" dependency-version: 6.0.5 dependency-type: direct:development update-type: version-update:semver-patch dependency-group: npm-minor-patch - dependency-name: jsdom dependency-version: 30.0.1 dependency-type: direct:development update-type: version-update:semver-patch dependency-group: npm-minor-patch - dependency-name: vite dependency-version: 8.2.0 dependency-type: direct:development update-type: version-update:semver-minor dependency-group: npm-minor-patch ... Signed-off-by: dependabot[bot] <support@github.com> |
||
|
|
4207f679f1 |
build(deps): add @tanstack/react-virtual
UI-SPEC §4 calls the Installed table virtualized, and S2's exit criterion is that a 200-package environment scrolls smoothly. Headless is what decides it: the row carries a checkbox, chips and an overflow menu, which a component-driven virtualizer would fight for control of. Two packages added — it brings only `@tanstack/virtual-core`. Peer range covers React 19 (`^16.8 || ^17 || ^18 || ^19`). `npm audit --audit-level=high`: **found 0 vulnerabilities**. Worth recording rather than leaving to a green CI tick — ARCHITECTURE §10 documents `eslint-plugin-react` being refused over exactly this gate, so it is a real filter and not a formality. It only became a meaningful signal one commit ago: the gate was failing on `main` until brace-expansion was bumped, and a red gate tells you nothing about what you just added. Its own commit so a future audit bisect lands on one line. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> |
||
|
|
a553bf7460 |
feat: the first working screens — legal gate, Environments, Settings
Stage 1's vertical slice. The bridge that has been names-only since Phase 0 now
carries real data end to end, and there is something to look at.
Environments is the right first screen because it exercises the whole bridge with
zero mutation risk: multi-process discovery with live progress, three error codes,
the PEP 668 MANAGED chip, the hidden_user_site partial-listing note, an empty
state, and a selection that feeds the status line. The legal gate ships with it
rather than last -- it is the first thing the app renders, so leaving it for later
would mean every manual test session for months starts on a screen that is not the
real one.
What had to exist first:
- core::settings. Engine choice lived in pipdock-cli behind a private KEY_ENGINE,
so the Settings screen would have had to guess the same key and encoding. A
setting written by one head and unreadable by the other is worse than none.
- scan-progress finally has a producer. ARCHITECTURE section 7 names the event
and never says what it carries; ScanProgress is that payload. Discovery is the
slowest thing PipDock does before it can show anything -- a registry walk,
py -0p, uv python list and a venv scan, each spawning processes -- so a first
screen that sits blank through all of it is the worst possible first
impression.
- docsHash, referenced twice in the docs and defined nowhere. Computed at build
time in build.rs, because the documents are deliberately not shipped: the gate
links to the GitHub copies, so a runtime hash would be a hash of files that are
not on the user's disk. Verified to change when a document changes and to
return to its old value when reverted -- it is a re-consent trigger, not an
integrity check. The SHA-256 is written out rather than pulled in, so nothing
new joins the supply chain of the thing that decides whether users see the
gate.
Capabilities are split by concern and scoped, per the comment already in
default.json about never broadening preemptively. Verified in the generated ACL:
opener is allowed only `https://github.com/*`, and clipboard is write-text with
allow-read-text deliberately absent -- nothing here has a reason to read what the
user copied, and a tool that runs subprocesses should not be able to.
Smaller decisions worth naming:
- A row whose probe failed renders in place with its code rather than vanishing.
One broken interpreter must not hide the rest, which is the rule env list
already follows.
- A consent record that cannot be read fails *closed*. The gate is shown.
- Tabs without a screen yet stay in place and stay focusable. Hiding them would
renumber every Ctrl+N after them and make the user learn the map twice.
- useUiStore is a sixth store beside ARCHITECTURE section 9's five: which tab is
showing is shell state, not a domain.
- The i18n parity test now compares plural *bases*. Vietnamese has a single
plural form (I18N section 1), so a correct vi catalog carries only _other --
the old test would have reported it as incomplete and pushed the next person
into adding a bogus _one to silence it.
Verified by launching the real app, not only by tests: it starts, the capabilities
are accepted with the scopes above, and the frontend builds to 275 kB.
226 Rust tests, 19 frontend tests; fmt, clippy, typecheck, lint and npm audit
clean. No `invoke` outside ui/src/ipc.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
|
||
|
|
6fa4845428 |
build(deps-dev): Bump @types/node in the npm-minor-patch group (#5)
Bumps the npm-minor-patch group with 1 update: [@types/node](https://github.com/DefinitelyTyped/DefinitelyTyped/tree/HEAD/types/node). Updates `@types/node` from 26.1.1 to 26.1.2 - [Release notes](https://github.com/DefinitelyTyped/DefinitelyTyped/releases) - [Commits](https://github.com/DefinitelyTyped/DefinitelyTyped/commits/HEAD/types/node) --- updated-dependencies: - dependency-name: "@types/node" dependency-version: 26.1.2 dependency-type: direct:development update-type: version-update:semver-patch dependency-group: npm-minor-patch ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> |
||
|
|
8f6b7ed24b |
feat: scaffold the Tauri shell, React UI and CI
Completes the Phase 0 scaffold. The app builds, links and renders; no screens yet. Frontend (ARCHITECTURE section 9, UI-SPEC section 2): - React 19 + Vite 8 + Tailwind 4 with the UI-SPEC dark terminal-tech tokens, plus a contrast test asserting WCAG AA over every text/surface pair, which UI-SPEC section 8 requires be verified. - EN and VI catalogs with a test that vi has every en key and no orphans, standing in for the CI parity script I18N section 1 asks for. - A local eslint rule enforcing the no-hardcoded-JSX-strings policy. eslint-plugin-react was the obvious choice but caps at ESLint 9, which drags in six high-severity advisories that would fail npm audit in CI; a local rule also implements the documented allowlist (product name, package names, versions, catalog codes, glyphs) precisely, which react/jsx-no-literals cannot express. Verified it fires on real copy and stays quiet on all five allowed shapes. - no-restricted-imports keeps invoke() out of components, so the "no component calls invoke directly" rule is enforced, not just stated. Tauri (ARCHITECTURE section 7): commands and events only, identifier com.skullmute.pipdock, NSIS and MSI targets, minimal capability set, placeholder icon pending the Phase 3 branding pass. CI (docs/RELEASE-CI.md section 1 as corrected): - ci-rust.yml and release.yml are project-local, on Windows runners, because no reusable Rust or Tauri workflow exists in the ops repo. Windows matters here: env discovery reads the PEP 514 registry and the py launcher, so a Linux run would skip the code most likely to break. - ci-node.yml calls the ops web-react reusable and adds the npm audit job that reusable lacks. - codeql.yml is JS/TS only; CodeQL has no Rust analyzer. - Discord notifiers replace the six-platform notify.yml that never existed. Every caller carries an explicit permissions block. - Action versions checked against the registry rather than assumed: checkout v7, cache v6, gh-release v3, setup-node v6. Two toolchain holds, both forced and both recorded: - TypeScript 6.0.3, not 7: typescript-eslint peers on <6.1.0. - ESLint 10 with eslint-plugin-react dropped, as above. Verified: cargo fmt/clippy -D warnings/28 tests green, tsc clean, 18 vitest tests green, eslint clean, npm audit reports 0 vulnerabilities, vite build and both binaries link. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> |