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>
23 lines
1001 B
Plaintext
23 lines
1001 B
Plaintext
# Code Health tools — CODE-HEALTH-SPEC §2.
|
|
#
|
|
# These are installed into PipDock's own isolated environment at
|
|
# %LOCALAPPDATA%\PipDock\data\tools\.venv, NEVER into the user's environment. Exact `==` pins are
|
|
# resolved at PipDock release time; there are no floating versions at runtime, so a report is
|
|
# reproducible for a given PipDock build. Their dependencies are pinned too, by
|
|
# tools-constraints.txt beside this file — regenerate it whenever a pin here moves (the command is
|
|
# in its header).
|
|
#
|
|
# Dependabot bumps these in their own group (see .github/dependabot.yml) so a tool upgrade is
|
|
# never bundled with application dependencies — a ruff minor can change findings across every
|
|
# user's report, and that deserves its own review.
|
|
#
|
|
# Versions verified against PyPI 2026-07-27.
|
|
|
|
deptry==0.25.1
|
|
vulture==2.16
|
|
ruff==0.17.1
|
|
|
|
# P1 (Security tab, PRD P1-1). Pinned now so spike SP-4 has something concrete to invoke while
|
|
# it settles the foreign-environment audit flags.
|
|
pip-audit==2.10.1
|