Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@crates/lockfile/src/resolved_dependency/tests.rs`:
- Line 10: The bare assert! calls lack failure context; update each assertion
that checks parsed.as_link_target().is_none() (and the other plain assert!
occurrences in the same test file) to include a diagnostic message or replace
with an assertion macro that prints values (e.g., use assert!(cond, "parsed={:?}
expected none", parsed) or assert_eq!(parsed.as_link_target(), None,
"parsed={:?}", parsed)); alternatively add an eprintln! immediately before the
assertion to print the relevant variables (e.g., parsed and
parsed.as_link_target()) so failures show actual vs expected; target the
assertions using the identifier parsed and the method as_link_target (and the
other plain assert! lines noted) when making the edits.

In `@crates/package-manager/src/install.rs`:
- Line 267: The frozen-workspace preflight only validates the root importer via
satisfies_package_manifest with Lockfile::ROOT_IMPORTER_KEY, so other workspace
importers can be stale; update InstallFrozenLockfile to validate every
materialized importer before proceeding: either (a) when given workspace_root,
enumerate workspace manifests (all importer ids / package.json paths) and call
satisfies_package_manifest for each importer key found in the lockfile, or (b)
gate the existing check to run per-target importer when installing a single
importer. Specifically, modify the InstallFrozenLockfile path that currently
references workspace_root and Lockfile::ROOT_IMPORTER_KEY to iterate all
importer keys (or the actual importer being installed) and ensure
satisfies_package_manifest is invoked for each so the frozen install fails if
any importer is out of date (apply same fix to the analogous block around lines
325–330).

In `@crates/workspace/src/project_manifest.rs`:
- Around line 95-102: The code in read_exact_project_manifest lowercases the
file basename before matching, allowing case variants like "PACKAGE.JSON" to
match; change this to perform an exact match by removing the to_ascii_lowercase
call so basename remains the original file_name string (i.e., compute basename
with file_name().map(|n| n.to_string_lossy().to_string()).unwrap_or_default()),
then match basename.as_str() against "package.json" and return
PackageManifest::from_path(manifest_path.to_path_buf()).map_err(ReadProjectManifestError::Read)
or Err(ReadProjectManifestError::UnsupportedName { basename }) as before.

In `@crates/workspace/src/projects.rs`:
- Around line 149-171: The loop currently only accumulates matches into
manifest_paths and ignores negated patterns, so implement proper include vs
exclude handling: first iterate patterns and separate them into include_patterns
and exclude_patterns based on whether normalize_pattern(pattern) yields a
leading '!' (or pattern.starts_with('!'))—strip the '!' for exclude entries—then
for each include pattern use Glob::new/ glob.walk(...) to insert matches into
manifest_paths, and for each exclude pattern use Glob::new/ glob.walk(...) to
remove matching paths from manifest_paths (convert walk errors into the same
FindWorkspaceProjectsError variants as existing code). Apply the same change to
the other identical block (the one around the second occurrence) so exclusion
semantics mirror pnpm.

---

Nitpick comments:
In `@crates/lockfile/src/resolution.rs`:
- Around line 70-71: Update the hardcoded permalinked GitHub references to point
at the upstream tip by replacing any occurrences of "blob/94240bc046" with
"blob/main" in the comment links (e.g., the comment referencing
BinaryResolution.bin and the other inline links around the same area). Search
for the exact URL substring "github.com/pnpm/pnpm/blob/94240bc046" in this file
(crates/lockfile/src/resolution.rs) and update each to
"github.com/pnpm/pnpm/blob/main" so all porting references follow the coding
guideline.

In `@crates/workspace/src/manifest/tests.rs`:
- Around line 74-80: Print or log the actual error value (err) immediately
before the assert so test failures show the concrete error; for example emit err
with eprintln!, dbg!(err), or println! and then keep the existing assertion that
checks for
ReadWorkspaceManifestError::Invalid(InvalidWorkspaceManifestError::EmptyPackageEntry)
so failure output includes the error value for easier diagnosis.

In `@crates/workspace/src/projects/tests.rs`:
- Around line 72-79: Add explicit diagnostic output for the `names` variable
around the two `assert!` checks so CI failures show the enumerated projects;
before the `assert!( !names.contains(&"foo".to_string()) )` and before the
`assert!( names.contains(&"real".to_string()) )` add an explicit log such as
eprintln!("names: {:?}", names) (or dbg!(names) / tracing::debug if tests use
tracing) so the actual `names` contents are printed when an assertion fails.