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>