fix(reify): report added count for fresh linked installs

[manzoorwanijk]

Under install-strategy=linked, a fresh npm install that actually creates .store entries and symlinks printed up to date, audited N packages instead of added N packages, misleading users and CI into thinking nothing changed.

reify-output counts adds with actualTree.inventory.has(d.ideal). Under the linked strategy the diff's ideal nodes belong to the isolated store tree (locations under node_modules/.store/<key>/node_modules/<name>), while the actualTree returned after reify is the logical hoisted-layout tree. The two never share node identity, so the lookup always failed and added stayed 0.

The ADD branch now also counts a node when it is a real store package node (isInStore && !isLink), which maps 1:1 to a hoisted package add. This excludes the internal store symlinks and the top-level consumer symlink, so the count matches hoisted for registry dependencies (verified: minimatch 4/4, rimraf 12/12, express 69/69). Omitted/incompatible optional deps have no store entry and are still not counted, and hoisted behavior is unchanged.

Known limitations (tracked separately): workspace and file:/npm link additions are represented as links rather than store nodes under linked, so they are not yet counted here — counting them is entangled with the self-link bug (#9398) and the undeclared-workspaces bug (#9618). The --json add[].path for a counted store package points to its .store realpath rather than a logical node_modules/<name> path.

References

Fixes #9623

[github-actions]

🎉 Backport to release/v11 created: #9667