docs(guide): restructure nested-config resolution rules

Drop oxlint/oxfmt internals from the user-facing guide, lead with the
three rules (default cwd resolution, `-c` pins, `--disable-nested-config`),
and replace the per-cwd bullet lists with tables. Also drop the unverified
`typeAware`/`typeCheck` root-only caveat — current code does not enforce it.

Author: fengmk2

docs/guide/nested-config.md

@@ -1,19 +1,29 @@
 # Nested Configuration
 
-Vite+ supports multiple `vite.config.ts` files in the same repository, so packages in a monorepo can have their own lint and format settings while sharing a baseline.
+Vite+ supports multiple `vite.config.ts` files in a repository, so packages in a monorepo can have their own lint and format settings while sharing a baseline.
 
-`vp lint` and `vp fmt` resolve configuration from the **current working directory** (cwd), but with one subtle difference:
+## How `vp lint` and `vp fmt` pick a config
 
-- **`vp lint`** — cwd-only. Uses `<cwd>/vite.config.ts` if it exists. If not, falls back to Oxlint's built-in defaults — it does **not** walk up to find an ancestor config.
-- **`vp fmt`** — cwd walk-up. Walks up from cwd and uses the first `vite.config.ts` it finds. If none is found anywhere up to the filesystem root, falls back to Oxfmt defaults.
+Config resolution is driven by the current working directory (cwd):
 
-In both cases, the selected config applies to every path in the run.
+- **`vp lint`** uses `<cwd>/vite.config.ts`. If that file is missing, built-in defaults apply — `vp lint` does **not** walk up the directory tree looking for a parent `vite.config.ts`.
+- **`vp fmt`** walks up from cwd and uses the first `vite.config.ts` it finds. If none is found, built-in defaults apply.
 
-If you only need to exclude files or folders, use [`lint.ignorePatterns`](/config/lint) or [`fmt.ignorePatterns`](/config/fmt) instead.
+In both cases, the selected config applies to every path in the run — there is no per-file resolution, and configs are never merged.
 
-## How it works
+If your monorepo needs different settings per package, run `vp lint` / `vp fmt` from each package directory (for example, via `vp run -r lint`), or pin a specific config with `-c`.
 
-Given the following structure:
+If you only want to exclude files or folders from an otherwise-shared config, use [`lint.ignorePatterns`](/config/lint) or [`fmt.ignorePatterns`](/config/fmt) instead.
+
+::: tip Breaking change since the April 2026 release
+
+Earlier versions of Vite+ pinned every `vp lint` / `vp fmt` invocation to the workspace-root `vite.config.ts`, regardless of cwd. Vite+ now lets cwd-based resolution select the config, so running from a sub-package picks up that sub-package's own `vite.config.ts`. See [#1378](https://github.com/voidzero-dev/vite-plus/pull/1378) for the migration notes.
+
+:::
+
+## Example
+
+Given this layout:
 
 ```
 my-project/
@@ -29,48 +39,47 @@ my-project/
 
 `vp lint`:
 
-- From `my-project/` → uses `my-project/vite.config.ts` for every file (including files under `package1/` and `package2/`).
-- From `my-project/package1/` → uses `my-project/package1/vite.config.ts`.
-- From `my-project/package2/` → no local `vite.config.ts`, so Oxlint's built-in defaults are used.
-- From `my-project/package1/src/` → no local `vite.config.ts`, so Oxlint's built-in defaults are used even though `package1/vite.config.ts` exists one level up.
+| cwd                          | config used                         |
+| ---------------------------- | ----------------------------------- |
+| `my-project/`                | `my-project/vite.config.ts`         |
+| `my-project/package1/`       | `my-project/package1/vite.config.ts`|
+| `my-project/package1/src/`   | built-in defaults (no walk-up)      |
+| `my-project/package2/`       | built-in defaults (no walk-up)      |
 
 `vp fmt`:
 
-- From `my-project/` → uses `my-project/vite.config.ts`.
-- From `my-project/package1/` → uses `my-project/package1/vite.config.ts`.
-- From `my-project/package2/` → walks up past `package2/` and uses `my-project/vite.config.ts`.
-- From `my-project/package1/src/` → walks up past `src/` and uses `my-project/package1/vite.config.ts`.
+| cwd                          | config used                          |
+| ---------------------------- | ------------------------------------ |
+| `my-project/`                | `my-project/vite.config.ts`          |
+| `my-project/package1/`       | `my-project/package1/vite.config.ts` |
+| `my-project/package1/src/`   | `my-project/package1/vite.config.ts` |
+| `my-project/package2/`       | `my-project/vite.config.ts`          |
 
-If your monorepo needs different settings per package, run `vp lint` / `vp fmt` from each package directory (for example, via a `vp run -r lint` task), or pin a specific config with `-c`.
+## Pinning a config with `-c`
 
-## What to expect
+`-c` / `--config` bypasses cwd-based resolution. The specified file is used for every path in the run:
 
-Configuration files are not automatically merged. When a file is selected, it fully replaces any other config — there is no parent/child layering. To share settings, import the parent config and spread it; see the [monorepo pattern](#monorepo-pattern-share-a-base-config) below.
+```bash
+vp lint -c vite.config.ts
+vp fmt --check -c vite.config.ts
+```
 
-Command-line options override configuration files.
+This also works when you need a one-off config, for example a permissive CI variant.
 
-Passing an explicit config file location using `-c` or `--config` bypasses cwd-based resolution entirely, and only that single configuration file is used — for both `vp lint` and `vp fmt`.
+## `--disable-nested-config` (lint only)
 
-For lint, you can also pass `--disable-nested-config` to stop Oxlint from picking up any stray legacy config files that may exist in the tree:
+`vp lint` accepts `--disable-nested-config` to stop any auto-loading of nested lint configuration files that may exist in the tree:
 
 ```bash
 vp lint --disable-nested-config
 vp check --disable-nested-config
 ```
 
-There is no equivalent flag for `vp fmt`; pass `-c` if you need to pin a single format config.
-
-`options.typeAware` and `options.typeCheck` are root-config-only. If either is set in a nested `vite.config.ts` that ends up being selected as the lint config, `vp lint` reports an error.
-
-::: tip Breaking change since the April 2026 release
-
-Earlier versions of Vite+ always injected the workspace-root `vite.config.ts` into every `vp lint` / `vp fmt` invocation, regardless of cwd. Vite+ now lets cwd-based resolution select the config, so running `vp lint` / `vp fmt` from inside a sub-package picks up that sub-package's own `vite.config.ts`. See [#1378](https://github.com/voidzero-dev/vite-plus/pull/1378) for the migration notes.
-
-:::
+This flag has no effect on `vite.config.ts` resolution, which is already cwd-only for `vp lint`. `vp fmt` has no equivalent flag; use `-c` to pin a single format config.
 
 ## Monorepo pattern: share a base config
 
-In a monorepo, you often want one shared baseline at the root and small package-specific adjustments. Import the root `vite.config.ts` from the nested one and spread it:
+Configs are never merged automatically — the selected config fully replaces any other. To share a baseline, import the parent config and spread it:
 
 ```ts [my-project/vite.config.ts]
 import { defineConfig } from 'vite-plus';

vite.config.ts

@@ -71,6 +71,7 @@ export default defineConfig({
       'packages/cli/snap-tests/fmt-ignore-patterns/src/ignored',
       'packages/cli/snap-tests/nested-oxc-config-proj-1/**',
       'packages/cli/snap-tests-global/migration-lint-staged-ts-config',
+      'packages/cli/snap-tests/docs-nested-config',
       'docs/**',
       'ecosystem-ci/*/**',
       'packages/test/**.cjs',