refactor: trim duplicated rationale in the Renovate preset and docs

The rule-level description restated the preset's top-level description;
keep only the fact stated nowhere else (why minimumReleaseAge and
schedule are pinned on the group). The CI guide now names all four
commands the skew guard fails, not just build and test.

Author: fengmk2

default.json

@@ -3,7 +3,7 @@
   "description": "Shared Renovate preset for Vite+ projects: keeps vite-plus, the vite catalog alias (@voidzero-dev/vite-plus-core), and the pinned vitest family in one grouped update. Consume with \"extends\": [\"github>voidzero-dev/vite-plus\"].",
   "packageRules": [
     {
-      "description": "vite-plus and @voidzero-dev/vite-plus-* are published together at one version, and vp pins vitest (plus aligned @vitest/* providers) to the version bundled in vite-plus. One grouped PR keeps the set in lockstep. Explicit minimumReleaseAge and schedule give every member one eligibility policy, so another preset cannot hold one member back and split the group.",
+      "description": "Explicit minimumReleaseAge and schedule give every member one eligibility policy, so another preset cannot hold one member back and split the group.",
       "groupName": "vite+",
       "matchPackageNames": ["vite-plus", "@voidzero-dev/vite-plus-*", "vitest", "@vitest/*"],
       "minimumReleaseAge": "1 day",

docs/guide/ci.md

@@ -39,7 +39,7 @@ These settings apply only to GitHub Actions workflows. For GitLab CI/CD and Azur
 
 ## Dependency Update Bots
 
-`vp create` and `vp migrate` write two npm entries that must stay on one version: the `vite-plus` dependency and the `vite` alias (`npm:@voidzero-dev/vite-plus-core@<version>`). Projects that use `vp test` also carry a `vitest` override pinned to the version bundled in Vite+. A dependency bot sees unrelated packages and updates each one in its own PR. Either PR leaves the project on a Vite+ pairing that was never published together, and `vp build` and `vp test` fail on the mismatch.
+`vp create` and `vp migrate` write two npm entries that must stay on one version: the `vite-plus` dependency and the `vite` alias (`npm:@voidzero-dev/vite-plus-core@<version>`). Projects that use `vp test` also carry a `vitest` override pinned to the version bundled in Vite+. A dependency bot sees unrelated packages and updates each one in its own PR. Either PR leaves the project on a Vite+ pairing that was never published together, and `vp dev`, `vp build`, `vp preview`, and `vp test` fail on the mismatch.
 
 Configure your bot to update these packages in one grouped PR.