Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@crates/package-manager/src/add.rs`:
- Around line 100-106: The current prefix derivation uses unwraps that can
panic: the expression around manifest.path().parent().map(...).unwrap() and
to_str().unwrap() should be made robust. Replace the chain that sets prefix (the
variable named prefix in add.rs derived from manifest.path()) with safe
handling: check manifest.path().parent() and provide a sensible fallback if None
(e.g., use the manifest path itself or "."), and convert the parent path to a
UTF-8-safe string using to_string_lossy() or OsString handling instead of
to_str().unwrap(), ensuring no panics occur on non-UTF-8 paths. Ensure the new
logic preserves the existing semantics of prefix when parent exists and
documents the fallback choice.

In `@crates/package-manager/src/symlink_direct_dependencies.rs`:
- Around line 74-90: The current parallel loop panics on symlink errors via
expect("symlink pkg"); change the loop to propagate errors by using
par_iter().try_for_each and make the closure return Result<(),
SymlinkDirectDependenciesError>, replacing expect(...) with
symlink_package(...)? and mapping the symlink error into
SymlinkDirectDependenciesError; ensure the surrounding function's
signature/return type supports returning Result so the propagated error from the
closure bubbles up instead of aborting a rayon worker (refer to symlink_package,
PkgNameVerPeer::new, and SymlinkDirectDependenciesError to locate and convert
the error).
- Around line 100-105: The match currently maps DependencyGroup::Peer to
dependency_type = None but the later emit/symlink path still processes it;
change the logic to skip peers entirely by adding an early guard: if group ==
DependencyGroup::Peer { continue; } (or equivalent) before computing
dependency_type so the code that emits "pnpm:root added" and creates the symlink
is not executed for peers; reference the DependencyGroup enum, the
dependency_type variable, and the code path that emits "pnpm:root added"/creates
the symlink to locate where to insert the guard.

---

Nitpick comments:
In `@crates/package-manager/src/symlink_direct_dependencies/tests.rs`:
- Around line 80-85: Before the non-assert_eq! assertions, add context logging
of the checked path and the call result: evaluate and store the result of
is_symlink_or_junction(&modules_dir.join("fastify")) and log the path and the
bool/Result (e.g., using dbg! or tracing::info!) immediately before the assert!;
do the same for is_symlink_or_junction(&modules_dir.join("@pnpm.e2e/dev-dep"))
and for the matches! expression referenced around the second location (line
~139), logging the value being matched and the subject path/structure; keep
assert_eq! uses unchanged and only add logs immediately prior to the non-assert
assertions so test diagnostics follow the project guideline.

In `@crates/reporter/src/tests.rs`:
- Around line 266-465: Several tests add assert! presence checks without prior
diagnostic logging; insert logging calls before those non-assert_eq! assertions
to aid CI debugging. For each test function
(package_manifest_event_matches_pnpm_wire_shape,
root_event_matches_pnpm_wire_shape, stats_event_matches_pnpm_wire_shape,
request_retry_event_matches_pnpm_wire_shape) add a dbg! or eprintln! of the
serialized JSON (the local variable json produced from envelope.pipe_ref(...) ->
serde_json::from_str) immediately before the assert! loops that check
.get(...).is_none() (and before the for k in [...] {
assert!(json["..."].get(k)... ) } blocks); prefer dbg!(json) for complex objects
and eprintln! for short scalar checks, and do not add logging before existing
assert_eq! scalar comparisons. Ensure you reference the json variable and place
the logging right before the offending assert! so failures emit the payload.

Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@crates/package-manager/src/symlink_direct_dependencies.rs`:
- Around line 72-82: The entries vector currently collects package entries from
each dependency group (skipping DependencyGroup::Peer) which can include
duplicates and cause concurrent symlink races; update the construction of
entries (the let entries: Vec<(&PkgName, &_, DependencyGroup)> block that uses
dependency_groups and project_snapshot.get_map_by_group) to first merge/flatten
entries by package name and apply the same precedence rules used elsewhere for
direct-dependency flattening (so each package appears only once with the
highest-precedence group), then collect that deduplicated list before the
parallel loop (par_iter) so no duplicate symlink work or duplicate `pnpm:root
added` events occur.

Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@crates/package-manager/src/symlink_direct_dependencies/tests.rs`:
- Around line 95-96: Before the two assert! checks that call
is_symlink_or_junction on modules_dir.join("fastify") and
modules_dir.join("@pnpm.e2e/dev-dep"), add diagnostic logging that prints the
full path and the result of is_symlink_or_junction (or the error) so failures
show context; specifically, evaluate the path into a local variable (e.g.,
fastify_path / dev_dep_path), call is_symlink_or_junction and log the path and
the returned Result/boolean (using eprintln! or println!) immediately before the
assert!, and apply the same pattern to the other occurrence noted around line
239 so test failures include the checked path and result.