? Verifying lockfile against supply-chain policies (369 entries)... Lockfile is up to date, resolution step is skipped Progress: resolved 1, reused 0, downloaded 0, added 0 Packages: +200 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Progress: resolved 200, reused 0, downloaded 55, added 0 Progress: resolved 200, reused 0, downloaded 140, added 8 Progress: resolved 200, reused 0, downloaded 199, added 167 Progress: resolved 200, reused 0, downloaded 200, added 200, done ✗ Lockfile failed supply-chain policy check (369 entries in 3.6s) [ERR_PNPM_MINIMUM_RELEASE_AGE_VIOLATION] 2 lockfile entries failed verification: playwright-core@1.61.1 was published at 2026-06-23T19:49:05.000Z, within the minimumReleaseAge cutoff (2026-06-23T05:25:50.953Z) playwright@1.61.1 was published at 2026-06-23T19:48:57.000Z, within the minimumReleaseAge cutoff (2026-06-23T05:25:50.953Z) The lockfile contains entries that the active policies reject. This can mean the lockfile is stale, or that someone committed a lockfile that bypassed the policy locally — inspect recent changes to pnpm-lock.yaml before trusting it. If the changes look expected, run "pnpm clean --lockfile" and then "pnpm install" to rebuild from a fresh resolution. Alternatively, relax the policy that flagged them.