vite-pluslisted

# Vite+ ## Check the Installed Release Use the repository's pinned release and installed CLI as authority. Reuse a working installation; install locked dependencies only when missing or when manifest or lockfile changes require it. Inspect `pnpm exec vp --version` and use `pnpm exec vp toolchain --json` when bundled-tool relationships matter. Read the relevant packaged docs under `node_modules/vite-plus/docs/` and shipped `AGENTS.md` for the surface being changed. Upgrades also need the intervening [release notes](https://github.com/voidzero-dev/vite-plus/releases). The installed CLI and packaged docs override memorized command, config, action, hook, and dependency shapes. Carry a workaround only when it reproduces on the installed version and has a named removal condition. ## Target Contract - For pnpm creation or package-manager upgrades, target pnpm 12 or newer and pin the selected version. Bootstrap existing projects with their current pin first; preserve another package manager when migration is outside scope. - Use the repository-local CLI interactively; no global `vp` is required. Package scripts and CI may use bare `vp` when their environment provides it. - `vite.config.ts` owns Vite+, test, lint, format, pack, staged, and task config supported by the selected release. Remove parallel configs only after migration proves their settings were preserved. - Tests use the public Vite+ test imports exposed by the installed release. - Existing release, deploy,