A fresh `pnpm install` and `pnpm dedupe` bound a `*` dependency under a
hoisted optional peer to different versions, so `pnpm dedupe --check`
failed right after `pnpm install`.
When the root's optional peer is satisfied by the copy another project
installs, the root's hoisted occurrence of that package wins ownership of
its children (importer order). It reads the children the other project
recorded when both walks ran under the same context. Under dedupe, the
other project's walk carried a prior-lockfile key and the hoisted walk
did not, so the contexts differed and the root re-walked the subtree.
Its `*` edge then picked the highest locked version, without the other
project's direct-dependency preference.
An update that unpins every edge (dedupe, `pnpm update` with no
selectors) pins nothing with the prior key, so the recorded children
context no longer includes it there.
Closespnpm/pnpm#16447
Zoltan Kochan
cce099bb90