GeezerVison

LLM Description written by Claude Code:claude-opus-5-5

Fixes #616

Summary

socket-patch apply on a cold or pruned Cargo cache exits 1 again, as it did in 4.x. The error names cargo fetch as the remedy. Before this change it exited 0 with status: "success", and the next cargo build --locked compiled the unpatched crate.

Root cause

#555 (the #403 fix) made apply treat any manifest purl that the project lock resolves, but that isn't on disk, as a calm package_not_installed "lockfile-only" skip. For npm that means the package was deliberately left out (a platform-gated optional dependency, or --omit=dev). Cargo never leaves a locked crate out on purpose: cargo fetch unpacks every Cargo.lock entry into registry/src, target-gated ones included (checked locally with a cfg(windows) dependency on macOS). So a locked crate that is missing just hasn't been fetched yet, and the next build downloads or re-extracts it unpatched.

Fix

• lockfile_resolved (crates/socket-patch-cli/src/commands/apply.rs) no longer counts pkg:cargo/ purls as lockfile-only (lock_resolution_is_calm). An unfetched crate is now an ordinary unresolved purl: an all-miss run exits 1 / partialFailure, and a partial miss prints the usual warning, as in 4.x.
• Cargo misses carry an actionable remedy in three places: the package_not_installed event detail, the human error block and the human warning (run \cargo fetch` first …`).
• No target-gated special case is needed, because cargo fetch unpacks every locked crate, so it always fixes the miss.
• The npm calm skips are unchanged, and their tests still pass.
• Docs: the CLI_CONTRACT package_not_installed row, and docs/ecosystems.md "Cargo: shared registry cache", which now says to run cargo fetch before apply.

Per-issue checklist

• Cargo apply on a cold or pruned registry cache now exits 0 as "lockfile-only", then the next cargo build downloads and compiles the unpatched crate (regression from #555) #616: tests/apply/lockfile_only_skip.rs
  • cargo_crate_on_cold_registry_cache_fails_with_fetch_remedy (empty CARGO_HOME)
  • cargo_crate_with_pruned_registry_src_fails_with_fetch_remedy (.crate cached, registry/src pruned)
  • Each checks the JSON (exit 1, partialFailure, a detail with the cargo fetch remedy), the human output and --silent.

Red → green

• Before the fix, both new tests failed: left: 0 right: 1, envelope "status":"success", with the reason Resolved by the project lockfile but not installed on this host (lockfile-only).
• After the fix, the apply binary passes 124/124, including the existing npm npm apply exits 1 when every patch targets a platform-skipped optional dependency (fsevents, @esbuild/*), so the setup hook fails npm ci and npm install on other OSes #403 tests.

Commands run

• cargo fmt --all -- --check: clean for the changed files. The only diff is pre-existing on main, in socket-patch-core/src/patch/redirect/upstream/mod.rs.
• cargo clippy --workspace --all-features -- -D warnings: clean.
• cargo test -p socket-patch-cli --lib apply: 64 passed.
• cargo test -p socket-patch-cli --test apply --test in_process_cargo_apply --test e2e_safety_cargo_build --test e2e_vex_lockfile --test scan_vendor_e2e: all green.
• cargo test -p socket-patch-cli --no-fail-fast (full suite): 207 binaries green. The only 2 failures are local-environment only, in e2e_vendor_cargo_build old-toolchain legs (Bad CPU type in executable: an x86 rustup 1.41 toolchain on Apple silicon without Rosetta). They are unrelated to this change.

🤖 Generated with Claude Code

Generated by Claude Code