4732f05197d744609fed2be31f9b05df732dbebe
279
Commits
| Author | SHA1 | Message | Date | |
|---|---|---|---|---|
|
|
4732f05197 |
docs: sync the specs with the accessibility pass
UI-SPEC §7 no longer describes a forced-colors list that is "not complete": the mark is data-destructive. §8 gains the five rules the pass left behind — focus on every screen replacement, names that contain the visible text, composite widgets as one tab stop, chip meanings as text, status regions that exist before their first message. TESTING says which of the three new tests holds what, and that none of them knows what a screen reader says; the manual charter gains a ten-minute accessibility pass. CLI-SPEC writes down that the CLI has no colour and nothing that animates, which was true of the code and stated nowhere. RELEASE-CI: the conversation-resolution rule the protection table never listed, the labels box that had been true for weeks, and .nvmrc, which still said 24 a month after every workflow moved to 26. README links the new files and gains Accessibility and Contributing sections. AI-DISCLOSURE and About name the model that produced 1.5.0. Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com> |
||
|
|
3e2c5e1a07 |
docs: accessibility statement, contributing guide, code of conduct and templates
GitHub's community profile listed five things missing, and the ops repository supplies no defaults despite its description, so they are added here. ACCESSIBILITY.md is at the root, where GitHub looks and where the README can link it. It follows the Accessibility Toolkit's structure, rewritten for a Windows desktop application and a CLI: the target (WCAG 2.2 AA, as a target and not a conformance claim), what is supported, a table of what was tested and by whom, what was not tested, the known limitations, and how to report a barrier without a GitHub account. It commits to an answer within seven days and to no fix date, because one person cannot honestly promise one. CONTRIBUTING.md states the rules a contributor actually meets: the checks CI runs, generated bindings, goldens, both locales, and the invariants that are not negotiable. CODE_OF_CONDUCT.md is Contributor Covenant 2.1, unmodified apart from the contact address. The pull request template carries an accessibility checklist, and accessibility.yml is an issue form that asks for impact rather than for a diagnosis. bug_report.yml keeps its name: the in-app Report bug link is built from it. Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com> |
||
|
|
d016b80014 |
fix(a11y): name dialogs by their heading, and four smaller things
A PdDialog's name was an aria-label holding what it was about, so a screen reader announced "numpy, dialog" and then "Cancel": the question being asked was on screen and never spoken. It is named by its visible heading, followed by what it is about, and described by its body. The legal gate replaces the whole shell, declares itself modal, and had no focus inside it. Its heading takes focus on arrival, as a screen's does. A package row's focus ring was drawn 2px outside a row that is absolutely positioned in a scroller and stacked against its neighbours, so three sides of it were clipped or painted over. It sits inside the row, in every mode rather than only in forced-colors. The dock bay's remove button was a bare glyph about 8px wide. It is 24px each way. Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com> |
||
|
|
885bca416c |
feat(about): the accessibility statement and where to report a barrier
Someone who cannot use part of the app is the person least able to go looking for a repository file about it. About gains an Accessibility section: a button that opens ACCESSIBILITY.md, and accessibility@poli0981.dev beside the two addresses already there, copyable the same way. No capability is widened: https://github.com/* was already in scope. Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com> |
||
|
|
a5fc204de8 |
fix(a11y): mark destructive controls by attribute for high contrast (U45)
Forced-colors drops every tint, so a danger-treated primary is drawn exactly like the Cancel beside it. The stylesheet gave five data-action values a border and had missed Remove, Allow, Clear, the Force-latest confirm and a forced plan's Confirm for as long as the list existed. The mark is one attribute, data-destructive, and destructive.test.ts reads the source to hold both halves: every button drawn in the danger colour carries it, and the stylesheet draws it. The active sidebar tab carries aria-current="page" and the outline rule matched 'true', so high contrast drew it like every other tab. Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com> |
||
|
|
f1bab20306 |
fix(a11y): say what Search is doing, and expose the tab shortcuts
Search told a screen reader nothing between a keystroke and its answer: the index loading, a search running, how many results came back and "nothing matches" were plain spans or not text at all. One status region carries them, mounted from the first render so there is an earlier state for a message to differ from. The result whose details are showing was a background colour; it carries aria-current. The sidebar's ^1..^9 hints were aria-hidden and at half opacity: about 2.6:1, and the shortcut existed nowhere else. They are drawn in a token, and each tab carries aria-keyshortcuts. Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com> |
||
|
|
6b70580b91 |
fix(a11y): finish the tab, radio group and listbox patterns (U47, U48)
Health's tabs were three buttons with role="tab": three tab stops, no arrow keys, no panel. They are one stop with Left/Right/Home/End, tied to a tabpanel. Their accessible name was an aria-label reading "Dependencies, 3 findings" over a tab that says "deptry 3", which fails WCAG 2.5.3; the name is the visible text now, followed by what the tab is about. A conflict's three choices were role="radio" with none of a radio group's keyboard. They are one stop, and the arrows move between them. The arrows move focus and choose nothing: checking what focus lands on would open Force latest's destructive confirm from an arrow key. The palette's highlight is an aria-activedescendant, not focus, so nothing scrolled the list and the selection left the visible window. It is scrolled into view. The vulture whitelist link was told from the sentence around it by a colour 1.4:1 away and underlined only on hover. It is underlined at rest. Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com> |
||
|
|
567b0ae8fa |
fix(a11y): move focus when the screen is replaced, not only when the tab changes
The shell moved focus to the new screen's heading on a tab change and on nothing else. Four things replace what <main> shows without changing the tab: the plan panel and each of its phases, the dependency view, and an opened environment. Each unmounts the control that was just pressed, so focus fell to <body>, the next Tab started from the top of the window, and a screen reader said nothing about a screen that had entirely changed. A second effect covers them, and only acts when focus was actually lost: a run advancing from resolving to preview must not pull a keyboard user off Back. The console drawer had the same hole. Escape closed it and dropped focus; it goes back to whatever opened the drawer. Its close button was named "Cancel", beside a Stop that cancels the run, and is "Close console". 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> |
||
|
|
17031c871d |
build(deps): Bump taiki-e/install-action (#99)
Bumps the actions group with 1 update in the / directory: [taiki-e/install-action](https://github.com/taiki-e/install-action). Updates `taiki-e/install-action` from 2.87.32 to 2.88.0 - [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/5488ac5a951645ce95062214902ac4b6bc1a1037...86f7a0ffb25f40114606501a311ebcfaf882ea32) --- updated-dependencies: - dependency-name: taiki-e/install-action dependency-version: 2.87.32 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: actions ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.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> |
||
|
|
df1ad1518d |
build(deps): Bump rfd (#96)
Bumps the cargo-minor-patch group with 1 update: [rfd](https://github.com/PolyMeilex/rfd). Updates `rfd` from 0.16.0 to 0.16.1 - [Release notes](https://github.com/PolyMeilex/rfd/releases) - [Changelog](https://github.com/PolyMeilex/rfd/blob/master/CHANGELOG.md) - [Commits](https://github.com/PolyMeilex/rfd/commits) --- updated-dependencies: - dependency-name: rfd dependency-version: 0.16.1 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: cargo-minor-patch ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.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> |
||
|
|
8cc0323c59 |
build(deps): Bump the code-health group in /tools with 3 updates (#94)
Bumps the code-health group in /tools with 3 updates: [certifi](https://github.com/certifi/python-certifi), [filelock](https://github.com/tox-dev/py-filelock) and [platformdirs](https://github.com/tox-dev/platformdirs). Updates `certifi` from 2026.7.22 to 2026.10.18 - [Commits](https://github.com/certifi/python-certifi/compare/2026.07.22...2026.10.18) Updates `filelock` from 4.2.1 to 4.2.4 - [Release notes](https://github.com/tox-dev/py-filelock/releases) - [Changelog](https://github.com/tox-dev/filelock/blob/main/docs/changelog.rst) - [Commits](https://github.com/tox-dev/py-filelock/compare/4.2.1...4.2.4) Updates `platformdirs` from 4.13.4 to 4.13.5 - [Release notes](https://github.com/tox-dev/platformdirs/releases) - [Changelog](https://github.com/tox-dev/platformdirs/blob/main/docs/changelog.rst) - [Commits](https://github.com/tox-dev/platformdirs/compare/4.13.4...4.13.5) --- updated-dependencies: - dependency-name: certifi dependency-version: 2026.10.18 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: code-health - dependency-name: filelock dependency-version: 4.2.4 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: code-health - dependency-name: platformdirs dependency-version: 4.13.5 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: code-health ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> |
||
|
|
0112b000ec |
docs(sonar): a version bump moves the new-code baseline one analysis late (#93)
The analysis that first sent 1.4.0 still measured from 2026-09-27; the next measured from the last analysis of the version before (2026-10-20). The docs said the version did not move it at all. They now say when it does, what that means for the merge carrying a release bump, and what main's gate read after #91. Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com> |
||
|
|
41ab1e8085 |
build(deps): Bump the cargo-minor-patch group across 1 directory with 3 updates (#92)
Bumps the cargo-minor-patch group with 3 updates in the / directory: [tokio](https://github.com/tokio-rs/tokio), [tauri](https://github.com/tauri-apps/tauri) and [tauri-build](https://github.com/tauri-apps/tauri). Updates `tokio` from 1.53.3 to 1.54.1 - [Release notes](https://github.com/tokio-rs/tokio/releases) - [Commits](https://github.com/tokio-rs/tokio/compare/tokio-1.53.3...tokio-1.54.1) Updates `tauri` from 2.12.4 to 2.12.5 - [Release notes](https://github.com/tauri-apps/tauri/releases) - [Commits](https://github.com/tauri-apps/tauri/compare/tauri-v2.12.4...tauri-v2.12.5) Updates `tauri-build` from 2.7.3 to 2.7.4 - [Release notes](https://github.com/tauri-apps/tauri/releases) - [Commits](https://github.com/tauri-apps/tauri/compare/tauri-build-v2.7.3...tauri-build-v2.7.4) --- updated-dependencies: - dependency-name: tokio dependency-version: 1.54.1 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: cargo-minor-patch - dependency-name: tauri dependency-version: 2.12.5 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: cargo-minor-patch - dependency-name: tauri-build dependency-version: 2.7.4 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: cargo-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> |
||
|
|
56ba7dcadd |
build(deps): Bump the code-health group in /tools with 2 updates (#88)
Bumps the code-health group in /tools with 2 updates: [filelock](https://github.com/tox-dev/py-filelock) and [platformdirs](https://github.com/tox-dev/platformdirs). Updates `filelock` from 4.2.0 to 4.2.1 - [Release notes](https://github.com/tox-dev/py-filelock/releases) - [Changelog](https://github.com/tox-dev/filelock/blob/main/docs/changelog.rst) - [Commits](https://github.com/tox-dev/py-filelock/compare/4.2.0...4.2.1) Updates `platformdirs` from 4.13.3 to 4.13.4 - [Release notes](https://github.com/tox-dev/platformdirs/releases) - [Changelog](https://github.com/tox-dev/platformdirs/blob/main/docs/changelog.rst) - [Commits](https://github.com/tox-dev/platformdirs/compare/4.13.3...4.13.4) --- updated-dependencies: - dependency-name: filelock dependency-version: 4.2.1 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: code-health - dependency-name: platformdirs dependency-version: 4.13.4 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: code-health ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> |
||
|
|
0085eae1ca |
build(deps): Bump taiki-e/install-action (#87)
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.87.28 to 2.87.29 - [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/1168f6810a3cb30a3514bf5756a3b7f0422c6df8...8cca0918f8471c33515202b73f56ab27f2bed283) --- updated-dependencies: - dependency-name: taiki-e/install-action dependency-version: 2.87.29 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: actions ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> |
||
|
|
2f6ad04967 |
fix: the 16 Rust findings and the coverage gap from the first CI analysis of main (#91)
The first CI analysis of main failed its gate: 16 Rust bugs and new-code coverage 78.3 % against 80 %, over all of 1.4.0 (sending a version did not move the previous-version baseline). - rust:S6677 x3: a failure's message is logged as `error`, not as a second `message` field (CLI, update flow, app startup); golden.rs reads the CLI's log to hold it, and failed first. - rust:S7493 x13: std::fs inside async fns goes through tokio::fs (tools venv sync, deptry's report, export/requirements/report commands). - Tests for 1.4.0 code nothing drove: rollback end to end, forcing a latest this Python cannot run, PEP 691 parsing (L55), user_file_error (U25), a plan verified in another environment, PyPiReleases' cache, and the plan/env stores' success and late-error paths. InstallSet::only had no caller and is removed. - ROADMAP, TESTING and CLAUDE.md record what the analysis found. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.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> |
||
|
|
a3146895a0 |
build(deps): Bump taiki-e/install-action (#81)
Bumps the actions group with 1 update in the / directory: [taiki-e/install-action](https://github.com/taiki-e/install-action). Updates `taiki-e/install-action` from 2.87.27 to 2.87.28 - [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/ab6895351a88b908e96a4697860d4ffea5e57dbe...1168f6810a3cb30a3514bf5756a3b7f0422c6df8) --- updated-dependencies: - dependency-name: taiki-e/install-action dependency-version: 2.87.28 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: actions ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.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> |
||
|
|
57ed5756c4 |
ci: unblock cargo audit on zbus 5, redact pip 26's finished progress bar, hold rfd at 0.16 (#84)
Three things have kept CI red since 2026-10-18; none touches the shipped program.
- **cargo audit** (required on every PR, and the daily Security scan) fails on
RUSTSEC-2026-0370/0371/0372: zvariant, zbus_names and zvariant_derive were folded into
zbus 6 on 2026-10-16 and marked unmaintained the same day. zbus reaches the tree only
through tauri-plugin-opener and tauri-plugin-single-instance, for D-Bus on Linux;
`cargo tree -i zbus --target x86_64-pc-windows-msvc` prints nothing. Every release of both
plugins, the 3.0 alphas included, still requires zbus ^5.9, so there is no update to take.
Ignored individually in .cargo/audit.toml with that reason and a removal condition.
`cargo audit --deny warnings` is clean locally.
- **The Monday fixture-drift job** failed on pip/build-backend-failure/stdout.txt: pip 26
ends a finished bar with the bare elapsed time, not `eta 0:00:00`, so `_is_progress` let
the transfer rate through (15.1 MB/s committed, 75.1 MB/s on the next runner). The rule now
keys on a trailing time token. Old vs new over every committed fixture line: exactly this
one line changes verdict. The fixture is restored to `<PROGRESS>` in binary mode, 7 CRLF
before and after; its blob is again
|
||
|
|
283605a4a0 |
chore(sonar): NOSONAR on the line SonarCloud flags (#80)
SonarCloud honours a NOSONAR only on the flagged line. 1.4.0 put this one on the line above the `cargo` call, so S4036 stayed open on `main` and kept the project's security rating at B while the PR gate reported "0 new issues" — the issue was old, not new. The call now fits on one line, with the marker on it. The two in `spikes/` were already on their flagged lines and are cleared. Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com> |
||
|
|
8c5f7e0b95 |
build(deps): Bump taiki-e/install-action (#79)
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.87.22 to 2.87.27 - [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/83ac0ad63c0167e6f06796fab0fce28db1bf3db0...ab6895351a88b908e96a4697860d4ffea5e57dbe) --- updated-dependencies: - dependency-name: taiki-e/install-action dependency-version: 2.87.27 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: actions ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> |
||
|
|
87dcb3452f |
fix(spikes): scrub progress bars line by line, not with a backtracking regex
SonarCloud's PR analysis flagged the progress-bar regex in capture.py's redaction again (S8786, super-linear backtracking) — the second regex form of this rule it has flagged. A per-line test cannot backtrack at all. It replaces exactly the lines the regex did on the LF text `subprocess.run(text=True)` produces, checked against seventeen sample lines including the edge cases (no space after the dashes, trailing whitespace, several "eta"s, a final line without a newline); no committed fixture changes. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>v1.4.0 |
||
|
|
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> |
||
|
|
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> |
||
|
|
42f227c1aa |
fix: what installing the build found, and what the doc pass turned up
The release build was installed and driven before tagging. Two defects showed up that no suite could see: - Every dialog opened in the window's top-left corner. Tailwind's preflight sets `margin: 0` on everything, which removes the `margin: auto` a modal <dialog> is centred by; PdDialog (and so the uninstall guard, since it was written) and the Ctrl+K palette were both affected. `m-auto` / `mx-auto`, measured in the dev server: (0,0) before, centred after. - On a profile that had never downloaded the index, Search said "preparing the package index" for ever and never offered the download. Moving the load into the background let a failed load restart on the next search, which reset the slot to Warming before the failure could be read, and the screen asked again every 150 ms. A failed load now stays failed until a refresh; a test in state.rs failed first against the old rule. From the documentation pass, each checked against the code: - The GUI's snapshot diff used the plain diff while the CLI's and the rollback used the engine-aware one, so the two heads disagreed about pip and setuptools across engines (G5). - `--json`'s help still promised NDJSON; `--yes`, `--quiet`, `--verbose`, `--log-file`, the install spec and `engine` described behaviour they did not have. Corrected, and the 32 help goldens re-blessed for exactly those lines. `pipdock engine` now marks the configured engine, as its help always said; `health --fix` printed a dirty-tree warning to stdout before its JSON; the text preview now lists withdrawn releases, as the GUI's does. - Copy that promised what the code does not do: a pinned package "can still be updated on its own" (an Exclude pin filters a named package too), a held pin left only "out of bulk updates", and an empty Environments screen pointing at a Browse… button that does not exist. - Stale comments in exec, the pip and uv parsers, index refresh, health, the pin screen, the status line, the settings store and i18n.ts (whose missing-key warning never fires). The ExecutionSummary.cancelled description is part of the public schema, so that golden and the TypeScript bindings move with it. - Metadata lookups reuse the shared HTTP client (M37 had been half done); insta was a dev dependency of core that nothing in core used; the integration workflow's checkouts no longer persist credentials; the capability file cites SECURITY §4, where the rule lives. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> |
||
|
|
310436552c |
fix: a bug-report link GitHub will open; uninstall output that finishes printing
- report.rs: the excerpt was capped at 6000 characters *before* percent-encoding, which is what decides the length GitHub sees - an accented letter costs up to nine bytes, a path separator three - so a log full of Vietnamese paths built a ~20 KB link and GitHub answered with an error page instead of the form (M51). Lines are now dropped from the front until the encoded excerpt fits; a single enormous line is trimmed rather than dropped. Two tests, both failing first. - run.rs: `pipdock uninstall` dropped its output pump's handle instead of awaiting it, so the summary could print over the last engine lines - the ones that say how the removal ended (X38). The other three pumps already waited. - bug_report.yml: the version placeholder read "1.0.0", which every release since made wrong; it now says where to find the version instead (X48). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> |
||
|
|
25f0269631 |
fix(build): the legal hash ignores line endings; the privacy policy says what is stored
build.rs hashed each document's raw length two lines above the normalisation that existed so a CRLF checkout would hash like an LF one (X25). It did not: a build from a Windows checkout with autocrlf - the runner's default - carried a different hash from an LF build of the same commit. The algorithm moves to src/legal_hash.rs, which build.rs includes by #[path] and the library compiles under cfg(test), so the tests exercise the function that runs at build time: a CRLF pair hashes like its LF pair (this failed against the old code), a changed document or text moved between documents changes the hash, and the hand-rolled SHA-256 agrees with sha2 across block boundaries. legal/, as users read it (X26): - PRIVACY §2 names what is now stored: the log files exist (they record the commands PipDock ran, so they hold package names and paths), PipDock's own tools/ and audit/ environments, and the per-release Python ranges. §3 says what the one destination, PyPI, is asked for - including pip-audit's advisory data, which comes from PyPI's own service - and adds osv.dev to the pages handed to the browser. The Vietnamese summary follows. - THIRD-PARTY §A gains rfd (the startup-failure dialog), §C osv.dev: four browser destinations, not three. Both documents are hashed into the consent record, so the legal gate is shown once more after updating - the mechanism working, as CLAUDE.md says. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> |
||
|
|
12bf723daa |
ci: failures reach someone, audits run on what is merged, releases are attested
- notify-ci-failure.yml lists its workflows by name. `workflows: ['*']` is not a wildcard to workflow_run: it matched nothing, so `main` was red from 2026-09-23 with no one told. - cargo audit runs a prebuilt cargo-audit (taiki-e/install-action, pinned by commit) with `--deny warnings`, replacing rustsec/audit-check@v2 - Node 20, a check-run write token, and on a pull request a failure only for "critical", which is how September's advisories passed every PR. .cargo/audit.toml's contract (a new informational advisory fails CI) is now what runs. - security-scan.yml: both audits daily against `main`, so an advisory against something already merged is reported the day it is published, not at the next PR. - cargo deny (licences, sources, bans) with deny.toml: the licence allowlist makes "every bundled licence is GPL-3.0-compatible" a test. The workspace declares `publish = false`, which it never had - and without which cargo-deny judged the app crates as published ones. - CodeQL analyses rust and actions as well as javascript-typescript. The comment saying CodeQL had no Rust support stopped being true in 2025. - ci-node.yml: Pages and id-token write move from the workflow to the one job that needs them (Sonar S8233); the audit installs with --ignore-scripts (S6505); a new `tauri lockstep` job fails when a Tauri crate and its npm package drift apart on Cargo.lock and package-lock.json. - release.yml: build (read-only token, no persisted credentials) and publish (attest + draft) are separate jobs; the tag must match all five version fields; SHA256SUMS.txt is LF, which `sha256sum -c` elsewhere needs; actions/attest-build-provenance attests the .exe and .msi; softprops/action-gh-release is pinned by commit; `workflow_dispatch` with `dry_run` builds any ref without attesting or drafting. - ci-integration.yml also runs for the CLI, exec, audit, release metadata, errors, store, index, Cargo.lock and rust-toolchain.toml - every one of which its end-to-end steps run through. - dependabot.yml: cooldowns, a group per ecosystem for Tauri packages and for actions and pip, TypeScript held below 6.1 (typescript-eslint's peer range), and the rust-toolchain ecosystem. A multi-ecosystem group would put both Tauri halves in one PR, but what it does to dependencies outside its patterns is undocumented; the lockstep job covers the gap instead. - Sonar: NOSONAR with reasons on the dev scripts' argv and PATH lookups; bundle-cli.mjs no longer claims to run from beforeBuildCommand. The dev CSP moves out of index.html into a Vite plugin that reads devCsp from tauri.conf.json, so a release build carries one policy, the strict one (S7039); checked in the dev server, where React Refresh's preamble still runs. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> |
||
|
|
7c6a506652 |
chore: remove what nothing uses, and finish what was half-wired
Dead code, each checked for callers first: - graph::ReverseDeps::leaves (only its own test called it), health::run::sink_for (no caller, and a doc describing something else), SnapshotProof::id and is_waived (no caller). - Two whitespace collapsers become one, errors::catalog::collapse_whitespace; the classifier's normalize is that plus lowercase. Three hand-folded SHA-256 hex digests become model::sha256_hex (build.rs keeps its own: a build script cannot use the crate it builds). - Six copies of asPdError become one, beside isPdError in ipc/errors.ts. - Thirteen strings no screen renders, from both catalogs (status.resolving/executing/ready, actions.confirm/browse/retry/openLogs, env.requiresPython/unusable, packages.updateSelectedSoon, health.notInstalled, settings.localeSystem/saved). - fixtures.rs is compiled only for tests and for xtask (feature `fixtures`), not into release. Half-wired, finished rather than deleted: engine_info had a typed wrapper and no caller, while ARCHITECTURE §7 promised a version beside each engine radio. Settings now shows it for the selected environment, and says "not found" for an engine that is not installed. Docs that described another project: core's "Phase 0" status, model.rs's specta, pip.rs's "lands in M1", snapshot.rs's "execute takes a Snapshot" (it takes a SnapshotProof), declared_source's doc stranded on validate_project, the pin validators' "character-class check" (they share pep440::is_version now), three health wrappers in ipc/index.ts each under another's doc, and three %LOCALAPPDATA% paths missing the data\ folder. Repo: production builds carry no source maps - Tauri embeds dist/ in the executable, so `sourcemap: true` shipped 2 MB of them to every user (X51). .gitignore covers insta's pending snapshots and a downloaded SHA256SUMS.txt. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> |
||
|
|
4da4c0f3ec |
fix(ui): the shell - window, grants, CSP, language, keys, table, contrast
The window (U21). It may now be maximized and snapped; the 1600x1100 cap is gone, and the content column stops at max-w-content (87.5rem) instead, centred in what is left. The window is created hidden and src-tauri/src/window.rs fits it to the monitor's work area before showing it: 1180x760 is taller than the work area of a 1920x1080 panel at 150% and of a 1366x768 laptop, so the status line and the plan panel's Confirm opened under the taskbar. Never below 900x560; pinned to the corner rather than centred off-screen when even that does not fit. UI-SPEC §5 says so. The webview's grants (U1, U32). core:default granted some sixty core commands nothing called and not core:window:allow-close, so Decline on the legal gate did nothing in the installed app while its component test - which mocks close() - passed. default.json now holds exactly the five the frontend calls, and a test in lib.rs pins the union of every capability file, plus the opener's four hosts. CSP (U56): object-src, base-uri and form-action 'none'. A release build's style-src drops 'unsafe-inline' - React sets styles through CSSOM, which CSP does not govern. index.html keeps it for `npm run dev`, where Vite injects <style> elements; both policies are enforced, so the stricter decides. To be confirmed on the installed build. Language (U3): the choice is stored and applied at start. save() sent locale: null every time, so choosing Vietnamese lasted until the window closed. Settings now load before the legal gate, so the gate is in the chosen language too, and <html lang> follows the UI. Keys: a screen's data-autofocus wins over the heading (U12) - Search's field lost focus to the shell's effect, which runs after its children's - and `/` works from Search itself. Ctrl+1..9 by e.code (U49): on AZERTY Ctrl+3 reports `"`. A release build swallows F5, Ctrl+R, Ctrl+P, Ctrl+F, F3 and Alt+arrows (U20), which reloaded, printed and found in a single-page app. Also: Security scrolls (U2); the legal gate shows a consent that cannot be recorded (U29); Report bug asks for the link again with the environment, so the issue carries the Python and engine versions, at one subprocess per click rather than per row (U31); the package table's header and rows share one set of widths and one gutter, and narrow tables drop Size so names stay visible at 900px (U22, U23); the grid is focusable (Sonar S6852); --color-danger is #F26A63 and danger badges use a 15% tint, with tokens.test.ts now compositing every badge tint over every surface (U46 - 3.92:1 before); test seeds typecheck instead of `as never`, the IPC mock uses the real isPdError and has the audit cache entry (U10). U14 and U26 were already fixed by earlier commits in this release. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> |
||
|
|
8e4b87e4ab |
feat(ui): the PEP 668 override asks first and is shown; the preview says what the report says
SECURITY §3 asks for two things the override never had: a confirmation before it turns on, and a persistent chip on every mutating screen while it applies. Turning it on now opens PdDialog with Cancel focused; turning it off saves at once. PdOverrideChip shows on Installed/Updates, Search's dock bay, the plan panel and an environment's detail - only where the override applies: the setting is on and the environment carries the EXTERNALLY-MANAGED marker. A venv never does, and a chip there would claim the flag is being sent. The preview renders the three fields ResolutionReport gained in this release, which nothing showed: - forced: "Will break (n)" in danger, each dependent named with the constraint the forced version violates; the Confirm button carries the count and the danger treatment (DISCLAIMER §2). - incompatible: left out for Requires-Python, with the range against this interpreter (invariant 10). A plan whose only content is one is no longer "nothing to change". - yanked: PD-PKG-003 as a warning row beside the change it belongs to. The summary says when the post-run check could not run (CheckReport.error) instead of showing nothing, which read as a pass (M30). The same defect survived on the empty-plan path of plan::execute, which kept its own unwrap_or(ok: true); it now goes through post_check like every other path, with a test that failed first. Also: settings load at app start once the documents are accepted, so the status line's engine and the chip are right before anyone opens Settings (U13); the plan panel names the interpreter it changes (part of U15); pins.suggestIntro no longer claims a pinned package can still be updated one at a time - an Exclude pin filters a named package too (DATA-FLOW §9.5). flow_step_forced.json is computed by derive_forced and release::mismatch over the scenario rows rather than written, for the reason fixtures.rs gives for its other computed fixtures. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> |
||
|
|
73e65303ca |
fix(ui): an answer for what the user has left is dropped
Every store awaited a command and then wrote what came back, without asking whether the question was still the one being asked. A slow answer for the environment the user had just left landed on the one they switched to: - the package list and the outdated badges (U5), pin suggestions (U43) and the snapshot timeline check the environment after each await; - a pin write re-joins the rows from the store as it is after the write, not as it was before two awaits (U6); - two clicks down the timeline show the second entry's diff whichever answers first (U42); - the dependency view loads the environment switched to while the previous one was loading, rather than bailing on "already loading" and showing nothing (U34). The plan store counts generations. Leaving a plan the backend is still working on - Back during a resolve or a guard, or out of a parked preview - now stops it there with plan_cancel, and its late answer no longer re-opens the panel the user closed (U9). A failed decision round keeps the preview (U24, the UI half). The progress subscription stays open 50 ms past the command's reply, which arrives separately from its last events and in no promised order. The uninstall guard's probe has its own phase, so the table is not swapped for the plan panel for half a second and its scroll position kept (U14). - Back from a preview is not a finished run: the selection is kept and nothing is refetched (U11). - Search asks again while the index warms instead of waiting for another keystroke (U7); the backend now always answers the first search at once. - Install from the dock bay keeps the queue until the resolve answers (U30). ui/src/stores/races.test.ts holds a command open, moves on, then lets it answer: six of its seven tests fail on the previous stores. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> |
||
|
|
a9f476a2ae |
fix(app): a claimed slot releases itself; IO errors say what happened; quieter locks
- The session slot is claimed through a guard that releases it on drop unless it was parked (U4). Release was a call every exit path had to remember, and plan_resolve, uninstall_guard and the rollback preview each had a `?` between claim and release: one failed settings read left the slot Busy and every later plan answered PD-RES-003 until a restart. The slot is a std mutex now, held only to swap a value, so the drop can take it; a test returns early through a claim and finds the slot free and the token gone. - A guard refusal in uninstall_execute keeps the flow parked: the dialog is still on screen and Force remove is still a choice, and its buttons used to answer "no plan". - A file the user chose - an export, a saved report, a requirements file - fails with the code that fits: read-only is PD-PRM-003, in use is PD-PRM-002, a full disk is still PD-SYS-002. Every one of them was PD-SYS-002, "not enough free disk space" (U25). - cache_clear holds the slot of the feature that owns the target - Health for the tools venv, the Security tab for the audit venv, the plan slot for snapshots - so a clear is refused while that feature runs instead of deleting the venv in use, and a parked preview is put back (U36). The deletion runs off the async workers. - The name index loads in the background on its own connection (U35). The load held the store's lock for 140 ms - every command that wanted the store waited behind a keystroke - on a worker the app shares; the triggering search answers ready:false, as the command's doc always said. - Environment probes run four at a time instead of in series (U19, part). - The audit's cancellation token is registered before the freeze, so Stop during it is honoured (U37); a run stopped that early skips the venv sync and reports itself cancelled. - A cache test named its scratch folder after the clock alone, so two tests in one tick shared it and the fresh-install test read the other's files. It failed once in this run; a counter fixes it. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> |
||
|
|
040571c7f7 |
fix(cli)!: one JSON document per command, env use is honoured, Ctrl-C stops the run
Changed for scripts: every `--json` invocation now prints exactly one document on stdout
(CLI-SPEC §6), with prompts, previews-before-a-prompt and prose on stderr (X5). The preview and
then the summary used to be two documents, so `pipdock install x --json | ConvertFrom-Json`
failed on the second. The document is: the ResolutionReport when nothing runs (a dry run, an
empty plan, a declined prompt - exit 2), the ExecutionSummary when something does, the FlowStep
when there is nothing to plan, the GuardReport for a refused removal (with --force, only the
summary), and the entity itself for env use, pin add/remove, snapshot create, engine and
pip-upgrade ({before, after}). Prompts moved to stderr in both modes.
- `env use` is honoured (X3): --env, then the default it set, then a .venv here - as --env's help
always said. It was written and never read. A default whose interpreter is gone is said and
skipped. The help line says "the one `env use` set" now (32 help snapshots re-blessed for that
line alone).
- Ctrl-C (and Ctrl-Break, which a supervisor can send) trips the flow's token (X6): the engine's
process tree is killed, what ran is summarized with the snapshot to roll back to, and the exit
is 130; a second press quits at once. Verified against a resolve hung on a server that never
answers: exit 130 the instant the signal arrived, no python left running.
- `update` with neither names nor --all exits 2 instead of planning nothing (X16); `audit` uses
--engine (X14); `engine` needs no environment (X15); `doctor` judges the configured engine, not
pip, so a uv-only venv passes (no pip is the uv default); an impossibility skipped off a TTY says
what and why (X26); `list` probes once instead of twice (X28); names and versions honour
`{:<32}` (X27); `snapshot diff` compares the way a rollback would across engines.
Verified with a script driving the real binary through each of these: every stdout parses as one
JSON document and every exit matches CLI-SPEC §5.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
||
|
|
77ca18cc33 |
feat(app): the GUI logs, says when it cannot start, and shows where the log is
- The GUI writes data\logs\pipdock.<date>.log through the same core::logging the CLI uses, with
the panic hook installed, so a crash leaves a record where it used to leave nothing.
- A data folder that cannot be opened is said in a dialog before any window exists (U18). The
store was opened inside Tauri's setup hook, whose failure is a panic in the event loop: a
release build has no console, so the user double-clicked and nothing happened. It now opens
before Tauri starts, and the failure shows the code, the message and the log path through
rfd - already in the tree via tauri-plugin-dialog, so Cargo.lock gains one dependency edge and
no crate. It is the one place GUI copy is written in Rust (both languages at once), because no
webview exists yet to load a catalog.
- logs_tail returns LogTail { dir, lines } - a new schema, so schema-LogTail is blessed and
schema-unknown-type lists one more type. NOT_YET is down to one entry, env_add_manual.
- Settings gains a Logs row: the folder, as a path, and "Copy recent log", which re-reads the tail
at the moment of copying so the clipboard holds the run that just went wrong. The clipboard
permission "Copy full log" already had is enough; no capability changes. en + vi copy.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
||
|
|
b7fa16a281 |
feat(logging): a log exists, and the CLI's logging flags do something
There was no log. tracing was a dependency of three crates and called zero times, --verbose and --log-file were parsed and ignored, LOG_RETENTION_DAYS had no reader, and the privacy policy described "log files (14-day rotation)" that did not exist. A bug report could attach the last run's engine output and nothing about what PipDock itself had done. core::logging owns what both heads share: one file per UTC day under data\logs (<prefix>.<date>.log, so the GUI and CLI never interleave), a sweep that keeps LOG_RETENTION_DAYS and never touches a file it did not name, tail() for reading it back, and a panic hook. What is logged: every spawn's argv, exit code and duration, every stop and its reason (exec); each resolve's outcome, each snapshot, each run's counts or refusal (flows); and the engine's own lines at DEBUG. The CLI always writes its file, at PIPDOCK_LOG or INFO; --verbose adds stderr at DEBUG; --log-file adds a copy; an internal error (exit 10) prints the log's path on stderr. Nothing goes to stdout - verified: `install --dry-run --json --log-file x` leaves one JSON document on stdout and nothing on stderr. The golden suite runs under a scratch LOCALAPPDATA now, and no golden changed. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> |
||
|
|
f4cf9e4959 |
build(tools): pin the tools venvs' whole dependency tree, not just the tools
tools-requirements.txt pins four tools and nothing beneath them, so every sync resolved their thirty-odd dependencies against whatever PyPI held that day: a Code Health report was reproducible for a build only as far as the top of the tree, and a broken or compromised release of requests, rich or msgpack reached every user on their next sync (H27). tools/tools-constraints.txt is that tree, compiled once with `uv pip compile --universal --python-version 3.10 --only-binary :all: --no-emit-package pip` (the command is in its header), embedded in the binary and passed to the bootstrap as `-c`. One file serves both venvs because a constraint does not install anything. pip is left out on purpose: it is the installer, and pip-audit's dependency on it would otherwise make pip replace itself half-way through installing pip-audit. A test refuses a ledger pin the constraints do not match, with the command to fix it, so a Dependabot bump cannot ship half-applied. The manifest hash still covers the tool pins alone, so no existing venv is forced to re-sync. Verified by syncing both venvs from nothing: every installed package is the constrained version. Hashes (`--require-hashes`) remain in the backlog. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> |
||
|
|
535b4c8707 |
fix(health, audit, index, snapshot): what was previewed is what is fixed, and smaller holes
Code Health - ruff --fix ran `check . --fix` with none of the exclusions the previewed run used (C4). Real ruff 0.17.1, verified: it rewrote every .ipynb in the tree - the preview excludes notebooks - and, in a project whose pyproject sets its own `exclude` (which replaces ruff's defaults), the files under .venv as well. The fix argv is now the read-only argv plus --fix, by construction; re-run against both cases, neither file changes. - git status runs with -c core.fsmonitor=false (M40): a project folder that carries its own .git/config could name a program for `git status` to run, and asking "is it safe to write here" would have run it. - One tool whose output cannot be read is that tool's problem, not the run's (H24). A `?` at the last step returned from the whole run, taking the other tools' findings with it. - The fix's own failures speak Code Health's codes, and a timeout says files may already have been rewritten (M39). Project paths lose Windows' \?\ prefix, which every filename in the report carried (M47). Security tab - pip-audit is given pins, not the raw freeze (H21): one editable install failed the whole audit. Index - TLS failures read the error's source chain (M32): reqwest's top-level message never mentions the certificate, so PD-NET-002's guidance never showed. - Typed, borrowing parse instead of a Value tree of 700k objects; the ingest runs on a blocking thread; connect/read timeouts replace a single 120 s total a slow link could exceed while making progress (M36). An empty project list is refused rather than ingested over the index (L55). Snapshots - Ids are fixed width and the list orders by created_at (M43): the timestamp's trimmed fraction made `…09-42Z` sort after `…09-4235606Z`. A sidecar whose id is not a PipDock id is ignored rather than used to build a freeze-file path (L54). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> |
||
|
|
545e86bd31 |
fix(flow): rollback across engines keeps pip; Hold pins hold; a failed round keeps the preview
- A rollback never removes pip, and across engines leaves pip, setuptools and wheel out of the comparison (C7). uv's freeze has no --all, so a uv snapshot never lists them; compared with pip's freeze every one looked added since, and the restore uninstalled pip from the environment. Meta::engine was recorded for exactly this and read by nothing. Verified: a uv snapshot previewed for a pip rollback now reports the environment already matches. - Hold pins are restated at their version in every resolve (H17). hold_requirements existed and nothing called it, so a held package was only left out of the upgrade list and free to move as anyone's dependency. A hold never releases the packages it collides with - only a forced pin does - so its impossibility is shown as it stands. - PinMode::Exclude's doc promised one-at-a-time updates that filter_upgrades never allowed. The rule stays DATA-FLOW §9.5 and the doc now says so (schema-Pin re-blessed for the wording). - decide() is transactional and the GUI keeps the flow parked when it fails (U24): a failed re-resolve used to leave the new request beside the old report, and plan_decide dropped the flow, so the preview on screen had a Confirm that answered "no plan". - An install no longer runs `list --outdated`, a network sweep of every installed package that nothing in an install reads (M28). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> |
||
|
|
e2e75f63fb |
feat(flow): PipDock enforces Requires-Python itself, as hard invariant 10 says
Invariant 10 says PipDock enforces Requires-Python because the engines disagree, and nothing did (C2): PD-PKG-001 existed in the catalog and was never raised. pip refused an incompatible exact pin with the "No matching distribution" it gives a typo (PD-PKG-002); uv honours the lower bound, ignores the upper one, planned scipy==1.7.3 on Python 3.14 and failed at install time building it from source. The update flow now checks three places: - exact pins the user typed (name==v, name===v), before any engine sees them. A request that is nothing but such pins is PD-PKG-001 with the range and the interpreter; otherwise the pin is left out and the preview says so (report.incompatible). - forced pins: forcing a release this Python cannot run stays held back, with the reason. - what the engine planned. pip's report already says what each release requires, so nothing is asked; for uv's plan PyPI is, and each release that excludes this Python is ruled out by name (`name!=v`) and the engine asked again, at most twice - it, not PipDock, picks what is next. crate::release asks https://pypi.org/pypi/{name}/{version}/json for info.requires_python, at most eight at once with a 15 s watchdog each, and remembers every answer forever in a new store table (an uploaded release's metadata never changes). A failure is asked again; unknown never blocks. The PyPI client is shared per process now, rather than rebuilt for every request (M37, part). Store v4. Migrations ran on every open - a journal_mode write and eight CREATE TABLEs, on a store some paths open twice per lookup - and an older build set user_version back down, so the next newer build re-ran them (M38). Both fixed, with tests. Verified on Python 3.14: `install scipy==1.7.3` is PD-PKG-001 under pip and uv alike, and `install scipy==1.7.3 six==1.17.0` plans six and says why scipy was left out. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> |
||
|
|
6ff2a10631 |
fix(flow): Force latest forces, and says what it breaks before it runs
Choosing Force latest recorded the decision in the request and nothing read it, so the "forced" resolve was the held-back one again (C6). forced_requirements had existed since M2 with no production caller. The flow now turns Strategy::ForceLatest into the resolve's GuardAdjust: the forced package pinned to its latest, and the packages whose constraints held it back released from the guard set. Forcing still failed in the canonical case, because the guard set pins every installed package the plan does not move - the forced package's own dependencies included: httpcore 1.0.9 needs h11>=0.16 and the guard had h11==0.12.0. Which pins collide is resolution, and PipDock does not resolve (invariant 3), but the engine names them in its impossibility; forced_collisions releases exactly those, installed and still pinned, and asks again, at most three times. report.forced carries each forced package with its blockers - the "Will break" rows DISCLAIMER §2 requires before anything runs - and the CLI prints them. Verified on a venv seeded with httpx 0.23.0: under pip and uv both, httpcore -> 1.0.9 and h11 -> 0.16.0, breaking httpx, named. The underlying over-pinning (a selective upgrade cannot move its target's dependencies) is recorded in the audit backlog rather than changed here. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> |
||
|
|
3cfb8f82ec |
fix(flow): PEP 668 is decided on a fresh probe, and the override works
The gate read env.externally_managed - whatever the caller last cached - before anything was probed, and the rollback flow had no gate at all (H12). The Settings override saved and nothing read it, so turning it on changed nothing (H11). Every mutating flow now starts with one preamble: probe, then decide on what the probe says. Without the override a managed environment is PD-ENV-002 before any engine command; with it, the flow carries SystemPackages::OverrideAllowed to every mutating engine call. SystemPackages is a named value, not a bool, for the reason SnapshotProof is a named waiver: hard invariant 5 says the flag is never passed implicitly, and this makes "implicitly" greppable. It reaches pip and uv installs and removals, and uv's dry run, which refuses a managed environment without it (verified, uv 0.13.1); pip's --dry-run --report is exempt and is never given it. pip implemented PEP 668 in 23.0 and added the flag in 23.0.1, so below 23.0 nothing is passed and pip 23.0 itself is PD-ENV-002. The CLI reads the override from the store both heads share - deliberately with no flag of its own - and says on stderr, every run, that it is in force. Verified against a uv-managed CPython 3.13 with an EXTERNALLY-MANAGED marker: refused without the override (exit 3); with it, pip installed and uv dry-ran and removed. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> |
||
|
|
5d63b31098 |
fix(flow): a stale or drifted preview is refused, before the snapshot
DATA-FLOW §9.3 refuses a preview older than ten minutes or one whose environment changed. Both checks existed in AcceptedPlan::verify and neither could fire (C1): the flow created the plan inside execute() with the current time, so its age was always zero; it passed the resolve-time listing as the "current" one, so the fingerprint always matched; and plan::execute compared the plan's env hash with itself. AcceptedPlan::accept now takes the basis the report was resolved over - the listing and the resolve time - and the flow re-probes in take_snapshot, after the user confirmed and before anything is written, so a refusal costs no snapshot. plan::execute verifies against the hash of the environment it is actually changing, and acts on the re-probed listing. The same rule reaches the other two flows (M44): an uninstall re-probes before its snapshot, since a package installed after the guard ran may depend on what is about to go, and a rollback compares the freeze it takes with the one its restore plan was diffed against. One plan id (M31): the snapshot said "update-<env>" for every plan ever made in an environment and the summary carried a different id. Both now carry the flow's, which is unique per plan. Five new flow tests fail on the previous code and pass on this one. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> |
||
|
|
f9984fa4fb |
refactor(flow): FlowOptions and an Engine::probe seam
Every flow probed through a free function, so nothing `start` decides - the PEP 668 gate, the graph, the drift basis, what reaches the resolver - could be reached by a test without a real interpreter, and the bugs the next commits fix were all there. Engine::probe is a provided method (it is probe.py, not an engine command; no adapter overrides it), and tests/flows.rs drives whole flows against a scripted engine that owns a small, mutable world. FlowOptions carries what the caller decides before a flow starts: the cancellation token and a clock. The token is the caller's because the first resolve runs inside `start`, and a token made there could only be handed out after the resolve it was needed to stop. The GUI registered a token of its own for that window which nothing listened to, so Stop during a first resolve did nothing at all (H13); plan_resolve now hands its token to the flow, and a test proves a hung resolve ends on Stop rather than on its watchdog. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> |