Align E2E CI with the root npm lockfile

[Caneryy]

Planning

• Plan ID: N9
• Depends on: None
• PRD alignment: NFR-1

Problem

The frontend CI enforces the root lockfile while the E2E job caches apps/web/package-lock.json and runs a workspace-scoped install, creating an inconsistent and currently fragile dependency path.

Scope

Make every Node job install from the repository root with npm ci, cache the root package-lock.json, and run workspace scripts from root. Keep Playwright browser caching and single-worker behavior.

Acceptance criteria

• CI contains no reference to apps/web/package-lock.json.
• Frontend and E2E jobs use the same Node/npm versions and install command.
• Workspace layout validation runs before install-dependent checks where practical.
• CI YAML is covered by the existing workspace/check script or a focused static test.

Verification

npm run check:workspace && npm test plus a green CI run

[bobo-24]

Hi! I came across this issue and would love to work on it. I have experience with similar tasks and I'm confident I can investigate, implement a clean solution, and thoroughly test it before submitting a PR. If the issue is still open, I would appreciate it if you could assign it to me. I’ll prioritize this immediately and ensure a reliable solution is delivered as soon as possible. Thank you!

[s6pa1rta3n-lab]

/try

I will align E2E CI with the root npm lockfile:

• Update GitHub Actions workflows to remove all references to apps/web/package-lock.json.
• Configure all Node jobs to install from repository root using npm ci and cache the root package-lock.json.
• Ensure frontend and E2E jobs share consistent Node/npm versions and install commands.
• Run workspace validation prior to install-dependent checks and verify with npm run check:workspace && npm test.

[Okorie2000-code]

Hi Maintainer, I’ve reviewed the issue and the scope is clear. I’m ready to implement it and deliver a clean PR within 10hrs. Kindly assign it to me.