Greptile Summary

This PR extends the remote_tarball_integrity_survives_lockfile_reuse_roundtrip test by adding a (react@18.2.0) peer-context suffix to the packages: and snapshots: keys in the lockfile fixture, so the initial exact-key lookup fails and the URL-matching fallback path in read.rs is exercised.

• The importer's version: field is left without a context suffix, matching how pnpm writes it; only the packages/snapshot keys carry the suffix, which is the scenario that triggers the fallback at raw.packages.iter().find_map(…).
• The existing integrity-roundtrip assertions (sha512-demo and the tarball: URL) are retained, verifying that the fallback correctly picks up the resolution block and propagates integrity through a write/re-read cycle.

Confidence Score: 5/5

Test-only change; no production code is touched.

The diff touches a single test fixture by adding a peer-context suffix to two YAML keys. The assertions remain identical in intent (integrity and tarball URL survive a write/re-read cycle), and the change deliberately routes execution through the URL-based fallback lookup that already exists in the parser, providing coverage that was previously absent for that code path.

No files require special attention.

Important Files Changed

_{Reviews (1): Last reviewed commit: "test(lockfile): cover remote tarball fal..." | Re-trigger Greptile}