chore(deps): lock file maintenance

[renovate]

This PR contains the following updates:

Update	Change
lockFileMaintenance	All locks refreshed

---

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.

🔧 This Pull Request updates lock files to use the latest dependency versions.

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • Between 12:00 AM and 03:59 AM, only on Monday (* 0-3 * * 1)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[rspurgeon]

Please keep this PR open, but do not merge it while renovate/stability-days is pending. Closing it is not useful because Renovate marks lock-file-maintenance PRs as immortal and will recreate it.

This PR currently resolves the transitive dependency nanoid to 3.3.17, which is affected by GHSA-2v37-7h3g-55p8. The fixed 3.3.18 release was published on August 7, 2026, but Kong's shared Renovate policy requires releases to be at least 12 days old. For npm lockfile generation, Renovate applies that cooldown when resolving transitive dependencies, so the fixed release was not yet eligible when this PR was created.

Process to follow:

1. Mark this PR do-not-merge while the stability check is pending.
2. After nanoid@3.3.18 has cleared the 12-day window (approximately August 19 at 16:41 UTC), allow Renovate to refresh the branch. If it does not refresh automatically, use the rebase/retry checkbox in the PR description.
3. Confirm the updated site/package-lock.json resolves nanoid to 3.3.18 or later.
4. Confirm npm audit no longer reports GHSA-2v37-7h3g-55p8.
5. Merge only after renovate/stability-days and all required CI checks pass; then remove the do-not-merge marker.

The passing signal is therefore an updated Renovate commit containing nanoid >= 3.3.18 with the stability and required CI checks green—not merely the passage of the calendar date.