docs(migrate): document manual installation (#2365)

The manual migration setup is documented in the README, but is missing
from the website migration guide.

This PR adds the dev dependency installation command and the npm, pnpm,
and Yarn override examples, including why Vitest must match the bundled
version.

🤖 Generated with Codex

---------

Co-authored-by: MK (fengmk2) <fengmk2@gmail.com>

Author: liangmiQwQ

.claude/skills/sync-upstream-dependency-docs/SKILL.md

@@ -0,0 +1,21 @@
+---
+name: sync-upstream-dependency-docs
+description: Sync exact upstream dependency versions embedded in Vite+ documentation after the automated dependency upgrade. Use when bundled Vite, Vitest, Oxlint, Oxfmt, tsdown, Rolldown, or related package versions change.
+allowed-tools: Read, Grep, Glob, Edit, Bash
+---
+
+# Sync upstream dependency docs
+
+1. Read `$UPGRADE_DEPS_META_DIR/versions.json` and consider only entries whose `old`
+   and `new` values differ.
+2. Search `README.md`, `packages/*/README.md`, and `docs/**/*.md` for each changed
+   package name and its old exact version. Do not treat changelogs, RFC examples,
+   snapshots, or broad ranges such as `vitest@4.x` as current-version references.
+3. Update references that promise to match Vite+'s currently bundled version. In
+   particular, keep every exact Vitest pin in the manual-migration examples in sync,
+   including `docs/guide/migrate.md`, `README.md`, and `packages/cli/README.md` when
+   those examples are present.
+4. Preserve the surrounding wording and formatting. Do not rewrite examples whose
+   version is intentionally historical or illustrative.
+5. Re-run the searches for the changed packages and inspect the focused diff. No
+   stale exact version may remain in documentation that describes the current bundle.

.github/workflows/upgrade-deps.yml

@@ -140,13 +140,15 @@ jobs:
                help documents. If it is `false`, do not modify help documents.
             5. Compare tsdown CLI options with `vp pack` and sync new/removed options per
                `.claude/skills/sync-tsdown-cli/SKILL.md`.
-            6. Install the global CLI:
+            6. Follow `.claude/skills/sync-upstream-dependency-docs/SKILL.md` to
+               update version-specific documentation for dependencies changed in this run.
+            7. Install the global CLI:
                - `pnpm bootstrap-cli:ci`
                - `echo "$HOME/.vite-plus/bin" >> $GITHUB_PATH`
-            7. If any Rust code or `Cargo.toml` was modified, run `cargo check
+            8. If any Rust code or `Cargo.toml` was modified, run `cargo check
                --all-targets --all-features` and `cargo shear`; fix anything they report.
-            8. Run `pnpm run lint` (requires a prior `just build`); fix any errors.
-            9. Smoke-test the CLI: `vp -h`, `vp run -h`, `vp lint -h`, `vp test -h`,
+            9. Run `pnpm run lint` (requires a prior `just build`); fix any errors.
+            10. Smoke-test the CLI: `vp -h`, `vp run -h`, `vp lint -h`, `vp test -h`,
                `vp build -h`, `vp fmt -h`, `vp pack -h`.
 
             ### Generated artifacts and build diffs

README.md

@@ -196,7 +196,7 @@ See [Automatic Version Updates](https://viteplus.dev/guide/ci#automatic-version-
 If you are manually migrating a project to Vite+, install these dev dependencies first:
 
 ```bash
-npm install -D vite-plus @voidzero-dev/vite-plus-core@latest
+vp install -D vite-plus
 ```
 
 You need to add overrides to your package manager so that other packages resolve the Vite+ versions: alias `vite` to `@voidzero-dev/vite-plus-core`, and pin `vitest` to the version Vite+ bundles (run `vp --version`) so the whole project shares a single Vitest copy with `vp test`. Without the `vitest` pin, a dependency or workspace package can pull a different Vitest than the bundled runner, splitting Vitest's internals (mocks, `expect`, runner state):

docs/guide/migrate.md

@@ -69,6 +69,40 @@ After running the migration:
 - Run `vp test`
 - Run `vp build`
 
+## Manual Installation & Migration
+
+If you are manually migrating a project to Vite+, install these dev dependencies first:
+
+```bash
+vp install -D vite-plus
+```
+
+You need to add overrides to your package manager so that other packages resolve the Vite+ versions: alias `vite` to `@voidzero-dev/vite-plus-core`, and pin `vitest` to the version Vite+ bundles (run `vp --version`) so the whole project shares a single Vitest copy with `vp test`. Without the `vitest` pin, a dependency or workspace package can pull a different Vitest than the bundled runner, splitting Vitest's internals (mocks, `expect`, runner state):
+
+```json
+"overrides": {
+  "vite": "npm:@voidzero-dev/vite-plus-core@latest",
+  "vitest": "4.1.10"
+}
+```
+
+If you are using `pnpm`, add this to your `pnpm-workspace.yaml`:
+
+```yaml
+overrides:
+  vite: npm:@voidzero-dev/vite-plus-core@latest
+  vitest: 4.1.10
+```
+
+Or, if you are using Yarn:
+
+```json
+"resolutions": {
+  "vite": "npm:@voidzero-dev/vite-plus-core@latest",
+  "vitest": "4.1.10"
+}
+```
+
 ## Migration Prompt
 
 If you want to hand this work to a coding agent (or the reader is a coding agent!), use this migration prompt:

packages/cli/README.md

@@ -190,7 +190,7 @@ See [Automatic Version Updates](https://viteplus.dev/guide/ci#automatic-version-
 If you are manually migrating a project to Vite+, install these dev dependencies first:
 
 ```bash
-npm install -D vite-plus @voidzero-dev/vite-plus-core@latest
+vp install -D vite-plus
 ```
 
 You need to add overrides to your package manager so that other packages resolve the Vite+ versions: alias `vite` to `@voidzero-dev/vite-plus-core`, and pin `vitest` to the version Vite+ bundles (run `vp --version`) so the whole project shares a single Vitest copy with `vp test`. Without the `vitest` pin, a dependency or workspace package can pull a different Vitest than the bundled runner, splitting Vitest's internals (mocks, `expect`, runner state):