fix: regenerate docs/package-lock.json to resolve storybook binary not found

[Copilot]

The "Deploy preview / Build" CI job was failing with sh: 1: storybook: not found (exit code 127). The storybook binary was never symlinked into docs/node_modules/.bin/ after npm install.

What are you trying to accomplish?

Fix the failing CI job caused by the storybook CLI binary not being available after npm install in the docs/ directory.

What approach did you choose and why?

The committed docs/package-lock.json locked esbuild as a nested install under node_modules/storybook/node_modules/esbuild (v0.27.3). This inconsistent resolution — caused by the mixed Storybook 8/10 peer dependency graph in docs/package.json — prevented npm from correctly symlinking the storybook binary.

Regenerating the lock file (deleting it and re-running npm install) resolves esbuild@0.27.4 at the top level, which allows npm to correctly link node_modules/.bin/storybook.

Key difference in the new lock file:

• Before: node_modules/storybook/node_modules/esbuild@0.27.3 (nested, binary not linked)
• After: node_modules/esbuild@0.27.4 (top-level, binary correctly linked)

What should reviewers focus on?

The only change is docs/package-lock.json. The large diff is expected for a lock file regeneration — package versions are broadly the same, just resolved differently. The Storybook 8/10 version mix in docs/package.json (which is the root cause of the fragile resolution) remains unchanged; fixing that is a separate concern.

Can these changes ship as is?

• Yes, this PR does not depend on additional changes. 🚢

Warning

Firewall rules blocked me from connecting to one or more addresses (expand for details)

I tried to connect to the following addresses, but was blocked by firewall rules:

• storybook.js.org
  • Triggering command: /home/REDACTED/work/_temp/ghcca-node/node/bin/node node /home/REDACTED/work/css/css/docs/node_modules/.bin/storybook build -o public/storybook ms.mjs (dns block)

If you need me to access, download, or install something from one of these locations, you can either:

• Configure Actions setup steps to set up my environment, which run before the firewall is enabled
• Add the appropriate URLs or hosts to the custom allowlist in this repository's Copilot coding agent settings (admins only)

Original prompt

Fix the failing GitHub Actions workflow Deploy preview / Build
Analyze the workflow logs, identify the root cause of the failure, and implement a fix.
Job ID: 66861717721
Job URL: https://github.com/primer/css/actions/runs/23022339886/job/66861717721

---

📱 Kick off Copilot coding agent tasks wherever you are with GitHub Mobile, available on iOS and Android.

[changeset-bot]

⚠️ No Changeset found

Latest commit: 8542119

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR