? Verifying lockfile against supply-chain policies (1248 entries)...
Progress: resolved 1, reused 0, downloaded 0, added 0
Progress: resolved 101, reused 0, downloaded 0, added 0
Progress: resolved 243, reused 0, downloaded 0, added 0
Progress: resolved 326, reused 0, downloaded 0, added 0
Progress: resolved 349, reused 0, downloaded 0, added 0
Progress: resolved 451, reused 0, downloaded 0, added 0
Progress: resolved 511, reused 0, downloaded 0, added 0
Progress: resolved 607, reused 0, downloaded 0, added 0
Progress: resolved 662, reused 0, downloaded 0, added 0
Progress: resolved 693, reused 0, downloaded 0, added 0
Progress: resolved 733, reused 0, downloaded 0, added 0
Progress: resolved 749, reused 0, downloaded 0, added 0
Progress: resolved 750, reused 0, downloaded 0, added 0
Progress: resolved 870, reused 0, downloaded 0, added 0
Progress: resolved 971, reused 0, downloaded 0, added 0
✗ Lockfile failed supply-chain policy check (1248 entries in 18.2s)
[ERR_PNPM_MINIMUM_RELEASE_AGE_VIOLATION] 2 lockfile entries failed verification:
  baseline-browser-mapping@2.11.15 was published at 2026-08-17T14:32:44.032Z, within the minimumReleaseAge cutoff (2026-08-17T12:39:40.689Z)
  electron-to-chromium@1.5.409 was published at 2026-08-18T02:04:55.580Z, within the minimumReleaseAge cutoff (2026-08-17T12:39:40.689Z)

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.
Progress: resolved 1156, reused 0, downloaded 0, added 0