fix: regenerate package-lock.json — unblock Frontend CI on #96–#98

[BrandDead]

Problem

npm ci was failing on PRs #96, #97, and #98 with errors like:

npm error Invalid: lock file's @vitest/utils@4.1.10 does not satisfy @vitest/utils@2.1.9
npm error Invalid: lock file's chai@6.2.2 does not satisfy chai@5.3.3
npm error Missing: tinypool@1.1.1 from lock file

The lockfile had been generated with a newer npm that resolved vitest's transitive deps to v4.x, while package.json pins vitest@^2.1.8.

Fix

Deleted and regenerated frontend/package-lock.json with npm@10.9.2 / Node 22.

• lockfileVersion: 3 (unchanged)
• vitest resolves to 2.1.9 with correct v2 transitive tree

How to unblock #96–#98

After this merges, each of those branches should rebase onto main-tL2525 (or merge main into them) to pick up the fixed lockfile. CI will go green.

[cursor]

Bugbot is not enabled for your account, so this pull request was not reviewed.

Enable Bugbot in the Cursor dashboard to get automatic reviews on future PRs.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
slide	Building	Preview	Aug 6, 2026 9:34pm