Clarify legacy-peer-deps requirement for vitest 4 migration

[Copilot]

User requested removal of .npmrc with legacy-peer-deps=true after updating coverage package to enable vitest 4 migration.

Current State

The PR already updates:

• vitest 3.2.4 → 4.0.6
• @vitest/coverage-v8 3.2.4 → 4.0.6

However, @nuxt/[email protected] still declares peerOptional vitest@^3.2.0, creating a peer dependency conflict that requires legacy-peer-deps=true.

Blocker

Cannot remove .npmrc until @nuxt/test-utils releases vitest 4 support. Open upstream PR: nuxt/test-utils#1470

Changes

Documented the blocker in PR comment thread. No code changes needed at this time.

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.

[Copilot]

Just as a heads up, I was blocked by some firewall rules while working on your feedback. Expand below for details.

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:

• pkg.pr.new
  • Triggering command: npm install (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)