chore: upgrade vite-plus to 0.2.1

[fengmk2]

Problem

vite-plus v0.2.1 consumes upstream Vitest directly. The @voidzero-dev/vite-plus-test wrapper is gone; vitest now comes in transitively through vite-plus.

Changes

• Catalog: vite-plus 0.1.24 -> 0.2.1, vite -> @voidzero-dev/vite-plus-core@0.2.1 (core override kept).
• Catalog: vitest -> upstream 4.1.9 (was the vite-plus-test alias); @vitest/coverage-istanbul 4.1.6 -> 4.1.9 (this repo uses vitest directly).
• Dropped the vitest peerDependencyRules accommodations for the wrapper/old vitest.
• Repointed scripts/lib/vitest-blob-timings.mjs at the vitest package (blob-parser chunk is identical; the wrapper was just vitest re-bundled).

Verification

No wrapper references remain outside node_modules; the lockfile resolves to a single vitest@4.1.9. vp check passes (format + lint/types). vp test run --project unit is 6907/6909; the 2 failures are pre-existing environment flakes, not from this change: asset-prefix (.vite temp-file race, passes on isolated retry) and font-google (real Google Fonts fetch against a hardcoded 15s timeout, slow on this network).

[gemini-code-assist]

Code Review

This pull request updates dependencies in pnpm-workspace.yaml, transitioning from the custom @voidzero-dev/vite-plus-test package to upstream vitest (v4.1.9), and updates vite and vite-plus to v0.2.1. Consequently, scripts/lib/vitest-blob-timings.mjs is updated to resolve the vitest package directly using createRequire and load its bundled blob parser. Feedback suggests wrapping the readdir call for chunksDir in a try-catch block to handle potential errors gracefully and provide a clearer error message if the directory is missing.

Important

The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.