Greptile Summary

Fixes spurious re-resolves for npm (and yarn) lockfiles caused by package.json override blocks that package-lock.json cannot serialise, so any non-empty overrides always made the npm lock look stale. The fix gates the overrides/ignoredOptionalDependencies drift comparison on a new kind_records_resolution_metadata predicate, keeping strict checking only for formats that actually round-trip that metadata (aube, pnpm, bun).

• check_drift_workspace_for_kind / check_drift_for_kind are added as the new public API; all three call-sites in resolve.rs are migrated to pass the LockfileKind from the parse result.
• resolution_metadata_drift_reason extracts the override + ignored-optional comparison into one helper, and the kind_records_resolution_metadata gate is a single matches! expression easy to audit against the full variant list.
• Two regression tests are added: one confirming npm lockfile stays Fresh when the manifest has overrides, another confirming Bun stays Stale (bun.lock does serialise overrides, so strict checking is correct there).

Confidence Score: 5/5

Safe to merge — the change narrows when a lockfile is considered stale for npm/yarn formats, matching their actual on-disk capabilities, and the production install paths are all updated to pass the lockfile kind through the drift check.

The logic is straightforward: a single predicate gates the override/ignored-optional comparison on whether the lockfile format can round-trip that metadata. The bun.lock format does serialise overrides (confirmed in bun/read.rs and bun/write.rs), so treating Bun as strict is correct. All three call-sites in resolve.rs are migrated consistently. No existing strict-checking paths for aube or pnpm are changed.

No files require special attention.

Important Files Changed

_{Reviews (2): Last reviewed commit: "fix(lockfile): avoid npm override drift ..." | Re-trigger Greptile}