chore(deps): bump vite-plus to v0.2.0

[fengmk2]

Summary

Bump vite-plus and related packages to the pkg.pr.new prerelease build for v0.2.0.

Updated where applicable:

• vite-plus -> pkg.pr.new build
• vite (alias/override -> @voidzero-dev/vite-plus-core)
• vitest pinned to bundled 4.1.9 (the @voidzero-dev/vite-plus-test wrapper was removed upstream; vitest is now plain upstream)
• minimumReleaseAge enabled with vite-plus packages excluded (pnpm/bun/npm as applicable)

Test plan

• CI passes

[gemini-code-assist]

Code Review

This pull request updates dependency configurations across the workspace, replacing standard registry versions of vite and vite-plus with temporary pkg.pr.new URLs and bumping vitest to version 4.1.9. Feedback highlights that using temporary pkg.pr.new URLs in the template package.json will cause installation failures for end-users once those builds are garbage-collected, and suggests using standard npm registry versions instead. Additionally, it is recommended to use the catalog: specifier in the overrides section of pnpm-workspace.yaml to avoid duplicating dependency URLs and keep the configuration DRY.

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.

[gemini-code-assist]

Using temporary pkg.pr.new URLs in the template package.json will cause issues for end-users who use create-remdx to bootstrap new projects. Prerelease builds on pkg.pr.new are temporary, not guaranteed to be permanently available, and can be slow or rate-limited. When this package is published, new projects created from this template will fail to install dependencies if these builds are garbage-collected.

Consider using standard npm registry versions (even if prereleases/tags like alpha, beta, or next) or a placeholder that is dynamically replaced during the bootstrapping process.

Suggested change

	"vite": "https://pkg.pr.new/voidzero-dev/vite-plus/@voidzero-dev/vite-plus-core@1856",
	"vite-plus": "https://pkg.pr.new/voidzero-dev/vite-plus@1856"
	"vite": "npm:@voidzero-dev/vite-plus-core@^0.2.0",
	"vite-plus": "^0.2.0"

[gemini-code-assist]

You can use the catalog: specifier in overrides to avoid duplicating the dependency URLs/versions between the catalog and overrides sections. This keeps the configuration DRY and easier to maintain when updating dependencies in the future.

  vite: 'catalog:'
  vitest: 'catalog:'