chore(deps): bump vite-task to the auto-tracking classification branch

[wan9chi]

Motivation

Picks up voidzero-dev/vite-task#571
so it can be exercised end to end from a published preview build.

That change teaches automatic tracking how to classify a path that a task both
reads and writes. Two cases are currently broken without it:

• a task that publishes its output directory by renaming a staging directory
  into place records all of its writes against a path that no longer exists at
  archive time, so the archive is empty and a later cache hit restores nothing
• a task that reads its own generated files records them as inputs, so its
  fingerprint changes every run and it can never hit

The practical effect is that workspaces of plain tsdown/tsc packages need
hand-written input/output patterns to cache at all.

This PR is only a dependency bump — no vite-plus code changes.

Notes

Needs the preview-build label so publish-preview.yml produces a pkg.pr.new
release to test against a real workspace.

[netlify]

✅ Deploy Preview for viteplus-preview canceled.

Name	Link
🔨 Latest commit	88ab459
🔍 Latest deploy log	https://app.netlify.com/projects/viteplus-preview/deploys/6a6623ddc749b00008aa83ba

[github-actions]

Native binary sizes (88ab459)

Final release artifacts built by the canonical build-upstream and build-windows-cli actions.

Artifact	Format	Base	PR	Change
vp (Linux x64)	Binary	10.31 MiB	10.31 MiB	0 B (0.00%)
vp (Linux x64)	gzip -9	4.42 MiB	4.42 MiB	-3.31 KiB (-0.07%)
NAPI (Linux x64)	Binary	33.07 MiB	33.10 MiB	+32.00 KiB (+0.09%)
NAPI (Linux x64)	gzip -9	12.72 MiB	12.74 MiB	+17.56 KiB (+0.13%)
vp (macOS ARM64)	Binary	7.64 MiB	7.65 MiB	+16.13 KiB (+0.21%)
vp (macOS ARM64)	gzip -9	3.84 MiB	3.84 MiB	+1.87 KiB (+0.05%)
NAPI (macOS ARM64)	Binary	40.50 MiB	40.51 MiB	+16.14 KiB (+0.04%)
NAPI (macOS ARM64)	gzip -9	16.97 MiB	16.98 MiB	+13.46 KiB (+0.08%)
vp (Windows x64)	Binary	8.35 MiB	8.35 MiB	+1.50 KiB (+0.02%)
vp (Windows x64)	gzip -9	3.64 MiB	3.63 MiB	-617 B (-0.02%)
NAPI (Windows x64)	Binary	27.51 MiB	27.54 MiB	+30.00 KiB (+0.11%)
NAPI (Windows x64)	gzip -9	10.70 MiB	10.71 MiB	+7.79 KiB (+0.07%)
Trampoline (Windows x64)	Binary	203.00 KiB	203.00 KiB	0 B (0.00%)
Trampoline (Windows x64)	gzip -9	97.91 KiB	97.91 KiB	-1 B (-0.00%)
Installer (Windows x64)	Binary	4.44 MiB	4.44 MiB	0 B (0.00%)
Installer (Windows x64)	gzip -9	2.08 MiB	2.08 MiB	-55 B (-0.00%)

[github-actions]

Registry bridge build (88ab459)

This commit build is published to the registry bridge, which serves these as ordinary npm versions (every other package proxies to npmjs):

Package	Version
vite-plus	0.0.0-commit.88ab4592d55342c11a070c47e8fc7205f675fda3
@voidzero-dev/vite-plus-core	0.0.0-commit.88ab4592d55342c11a070c47e8fc7205f675fda3

Install the Vite+ CLI built from this commit, then migrate a project:

# macOS / Linux
curl -fsSL https://vite.plus | VP_PR_VERSION=2260 bash

# Windows (PowerShell)
$env:VP_PR_VERSION="2260"; irm https://vite.plus/ps1 | iex

After installing, upgrade the current project's vite-plus to this test build with:

vp migrate

Or point your package manager at the bridge registry https://registry-bridge.viteplus.dev/:

Package manager	Registry config
npm / pnpm / Bun	.npmrc: registry=https://registry-bridge.viteplus.dev/
Yarn (v2+)	.yarnrc.yml: npmRegistryServer: "https://registry-bridge.viteplus.dev/"

Then pin the build (vite aliases to vite-plus-core; pnpm can use a catalog, npm an overrides entry):

{
  "devDependencies": {
    "vite-plus": "0.0.0-commit.88ab4592d55342c11a070c47e8fc7205f675fda3",
    "vite": "npm:@voidzero-dev/vite-plus-core@0.0.0-commit.88ab4592d55342c11a070c47e8fc7205f675fda3"
  }
}

[github-actions]

🐳 Docker preview image

Built from this PR's registry bridge build:

Image	Compressed size
ghcr.io/voidzero-dev/vite-plus:pr-2260	237MB

# remove any stale local copy from a previous run, then pull fresh
docker rmi ghcr.io/voidzero-dev/vite-plus:pr-2260 2>/dev/null; docker pull ghcr.io/voidzero-dev/vite-plus:pr-2260

Quick check:

docker run --rm ghcr.io/voidzero-dev/vite-plus:pr-2260 vp --version

See docs/guide/docker.md for usage.