chore(deps): upgrade vite-plus to 0.2.1 (#34)

## Problem

The project is on vite-plus 0.1.x, which pulls Vitest in through the
`@voidzero-dev/vite-plus-test` wrapper. v0.2.1 consumes upstream Vitest
directly and drops that wrapper.

## Fix

- Bump `vite-plus` and the `vite -> @voidzero-dev/vite-plus-core`
override to `0.2.1` in the catalog.
- Remove the `@voidzero-dev/vite-plus-test` wrapper: drop the `vitest`
catalog entry, override, and `peerDependencyRules`. The project has no
direct vitest usage (all tests import from `vite-plus/test`), so vitest
now arrives transitively via vite-plus.

## Verification

- Dependency tree resolves to a single `vitest@4.1.9`; no
`@voidzero-dev/vite-plus-test` reference remains.
- `vp test`: 31/31 passed (native Vitest banner `RUN v4.1.9`).
- `vp check`: formatting, lint, and type checks pass.

Author: fengmk2

.vscode/settings.json

@@ -5,5 +5,17 @@
   "editor.formatOnSaveMode": "file",
   "editor.codeActionsOnSave": {
     "source.fixAll.oxc": "explicit"
+  },
+  "[javascript]": {
+    "editor.defaultFormatter": "oxc.oxc-vscode"
+  },
+  "[javascriptreact]": {
+    "editor.defaultFormatter": "oxc.oxc-vscode"
+  },
+  "[typescript]": {
+    "editor.defaultFormatter": "oxc.oxc-vscode"
+  },
+  "[typescriptreact]": {
+    "editor.defaultFormatter": "oxc.oxc-vscode"
   }
 }

CLAUDE.md

@@ -11,6 +11,7 @@ Docs are local at `node_modules/vite-plus/docs` or online at https://viteplus.de
 - [ ] Run `vp install` after pulling remote changes and before getting started.
 - [ ] Run `vp check` and `vp test` to format, lint, type check and test changes.
 - [ ] Check if there are `vite.config.ts` tasks or `package.json` scripts necessary for validation, run via `vp run <script>`.
+- [ ] If setup, runtime, or package-manager behavior looks wrong, run `vp env doctor` and include its output when asking for help.
 
 <!--VITE PLUS END-->