chore: refresh npm lockfile within existing ranges

[shaboooooozy1]

Why:

Closes: N/A — recurring conservative dependency maintenance. Regenerates package-lock.json within the existing package.json version ranges (no manifest edits) so the site picks up in-range patch/minor releases.

What's being changed (if available, include any code snippets, screenshots, or gifs):

package-lock.json only, regenerated with npm update. 42 direct dependencies moved to their latest in-range release (149 packages changed in total, 44 added, 36 removed — all transitive refreshes chosen by the resolver within declared ranges).

Direct dependency bumps:

Package	Old	New
@actions/core	3.0.0	3.0.1
@axe-core/playwright	4.11.1	4.12.1
@eslint/js	9.39.3	9.39.5
@graphql-inspector/core	7.1.2	7.1.3
@graphql-tools/load	8.1.8	8.1.15
@playwright/test	1.58.2	1.61.1
@primer/behaviors	1.10.2	1.10.3
@primer/octicons	19.22.0	19.29.2
@primer/octicons-react	19.22.0	19.29.2
@primer/primitives	11.3.1	11.9.0
@primer/react	38.13.0	38.33.0
ajv	8.18.0	8.20.0
azure-kusto-data	7.0.4	7.2.0
dayjs	1.11.19	1.11.21
dereference-json-schema	0.2.1	0.2.2
dotenv	17.3.1	17.4.2
eslint	9.39.3	9.39.5
eslint-plugin-github	6.0.0	6.1.1
eslint-plugin-no-only-tests	3.3.0	3.4.0
eslint-plugin-prettier	5.5.5	5.5.6
eslint-plugin-primer-react	8.5.2	8.6.1
globals	17.3.0	17.7.0
graphql	16.12.0	16.14.2
helmet	8.1.0	8.3.0
http-proxy-middleware	3.0.5	3.0.7
jiti	2.6.1	2.7.0
js-cookie	3.0.5	3.0.8
js-yaml	4.1.1	4.3.0
lint-staged	16.2.7	16.4.0
liquidjs	10.24.0	10.27.2
lodash / lodash-es	4.17.23	4.18.1
next	16.1.6	16.2.11
nock	14.0.11	14.0.16
ora	9.3.0	9.4.1
sass	1.97.3	1.101.3
semver	7.7.4	7.8.5
start-server-and-test	2.1.3	2.1.5
swr	2.4.0	2.4.2
tsx	4.21.0	4.23.1
vitest	4.0.18	4.1.10
walk-sync	4.0.1	4.0.2

Deliberately held back (still within range, unchanged from the previous lockfile):

• @primer/css stays at 21.3.1 — 21.5.x declares a peer dependency on @primer/primitives@9.x || 10.x, which conflicts with the root's ^11.3.1 range under strict resolution (the repo's package-lock-lint CI would reject a --legacy-peer-deps lockfile).
• prettier stays at 3.8.1 — 3.9.x changes some formatting decisions; with 3.9.6 installed, npm run lint reported 59 prettier/prettier errors against the checked-in source. Reformatting source files is out of scope for a lockfile refresh, so prettier is held at the version the codebase is formatted with.

Verification run in this environment (Node v22, npm 10.9.7 — engines want ^24, npm emitted an EBADENGINE warning but installs fine):

• npm update / full install completed successfully (scripts enabled)
• npm install --package-lock-only --ignore-scripts --include=optional (same command as the package-lock-lint workflow) leaves the lockfile unchanged — strict peer resolution accepts it
• npm run tsc (tsc --noEmit): passes clean, ~24s
• npm run lint (eslint over all ts/tsx): passes clean, ~40s

Deferred to CI: the full next build and the vitest suite (CI builds the site before running tests; a vitest smoke run here failed only on the missing .next production build, which is environmental, not dependency-related). Playwright/browser tests also deferred to CI.

Check off the following:

• A subject matter expert (SME) has reviewed the technical accuracy of the content in this PR. In most cases, the author can be the SME. Open source contributions may require an SME review from GitHub staff. (No content changes — lockfile only.)
• The changes in this PR meet the docs fundamentals that are required for all content. (Not applicable — no content changes.)
• All CI checks are passing and the changes look good in the review environment.

🤖 Generated with Claude Code

https://claude.ai/code/session_01HLNXGDL9moA6d5M4d72jxb

---

Generated by Claude Code