chore: bump vite-plus to ^0.3.1

[smiggleworth]

Bumps the vite-plus devDependency from ^0.3.0 to ^0.3.1. package-lock.json resolves vite-plus at 0.3.1 (verified against the installed tree, not just the manifest).

Why the vite devDependency also changed

vite-plus 0.3.1 changed how it depends on Vite. 0.3.0 depended on @voidzero-dev/vite-plus-core under its own package name; 0.3.1 depends on it through an alias:

"vite": "npm:@voidzero-dev/vite-plus-core@0.3.1"

Because of that, vp pack now hard-requires the project's own node_modules/vite to be the same alias, and fails the build otherwise:

error: Failed to resolve pack command: GenericFailure,
Expected @voidzero-dev/vite-plus-core@0.3.1, but found vite@8.2.2
at node_modules/vite/package.json.
Run `vp migrate` to align the Vite alias, then run `vp install`.

So the vite devDependency is aliased to match. This is the same Vite alignment vp migrate performs, applied by hand to keep the diff scoped to dependencies — a full vp migrate also rewrites AGENTS.md, editor config, and pre-commit hooks, none of which belong in a version bump.

Worth flagging for review: this arrived in a patch release, but it is a breaking change in what vite-plus requires of the host project.

Peer dependency ranges: deliberately unchanged

Neither peer range was touched.

• vite-plus: "^0.2.8 || ^0.3.0" — ^0.3.0 already admits 0.3.1, so no change is needed to consume the new version. Narrowing it to ^0.3.1 would break anyone on 0.2.x for no benefit.
• vite: "^8.2.2" — this describes what consumers bring. They install real Vite 8; the vite-plus core distribution is a development-only concern of this repo. Propagating the alias into the peer contract would be a breaking change for every consumer.

Checks

Ran the full CI sequence locally. All green:

Check	Result
fmt --check	pass (38 files)
lint	pass
build	pass
test	pass — 7 files, 67 tests
typecheck	pass
test:publint	pass

Nothing needed fixing beyond the alias.

Pre-existing failure, not fixed here

npm run pack:check fails, and it fails identically on a clean origin/main checkout — it is unrelated to this bump and left alone.

tests/package-artifacts.js parses npm pack --ignore-scripts --dry-run --json and expects a top-level array:

Error: Expected one packed artifact, received undefined.

Under npm 12 (packageManager is pinned to npm@12.0.1) that command no longer returns an array, so result.length is undefined. It is not part of the CI workflow — CI runs fmt, lint, build, test, and typecheck — so it does not gate this PR, but it does gate npm run check and prepublishOnly. Worth a separate fix.